Implements protocol updates for SentMessage #491
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for storybook-component-library canceled.
|
✅ Deploy Preview for kyc-optimism-io-faq ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for op-dapp-console-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Deploying superchain-paymaster-nft-mint-example with
|
| Latest commit: |
f35e68c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d3aff582.superchain-paymaster-nft-mint-example.pages.dev |
| Branch Preview URL: | https://nick-fix-viem-sent-message.superchain-paymaster-nft-mint-example.pages.dev |
nitaliano
changed the title
tremarkley
approved these changes
Oct 1, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The protocol recently updated how it handled
SentMessageevents notable it's just no longer an anonymous eventdecodeSentMessageto accept an array of logs instead of the raw hex payloaddecodeSentMessagewill now return the parsed log so we can generate the message idextractMessageIdentifierFromLogto calldecodeSentMessagenow internally