Add process of verifying TeleporterMessenger #669
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
geoff-vball
requested review from
iansuvak,
richardpringle,
bernard-avalabs,
michaelkaplan13 and
cam-schultz
cam-schultz
approved these changes
Dec 3, 2024
Co-authored-by: cam-schultz <[email protected]> Signed-off-by: Geoff Stuart <[email protected]>
contracts/teleporter/README.md
Outdated
| forge verify-contract 0x253b2784c75e510dD0fF1da844684a1aC0aa5fcf \ | ||
| src/teleporter/TeleporterMessenger.sol:TeleporterMessenger \ | ||
| --chain-id 13337 \ |
There was a problem hiding this comment.
should this be <YOUR_CHAIN_ID>?
There was a problem hiding this comment.
Why yes, thank you stranger 👀
…nto verify-contract
iansuvak
approved these changes
Dec 4, 2024
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.
Why this should be merged
Closes #663
How this works
Uses
forgeandsourcify. I couldn't find any way of using an artifact that would could generate to prevent the user from having to check outv1.0.0of the repo.How this was tested
Tested on test chain that someone from Beam was having issues with.
How is this documented