fix(website): useSafeTransactionStatus also uses new safe abi #1397
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an issue with the useSafeTransactionStatus hook where transaction status was not being accurately determined. The hook has been updated to use the Safe 1.4.1 ABI to check transaction logs, ensuring accurate identification of transaction success or failure.
This transaction worked as it uses the old Safe ABI.
This transaction did not work as it uses the Safe 1.4.1 ABI. This PR resolves that issue.
Closes https://linear.app/usecannon/issue/CAN-555/safe-status-check-is-not-working-on-newer-txs