Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
How to use
Prepare devtools transactions to send on Solana, eg.:
Run converter:
Simulate resulting base64 transactions in Solana Inspector (sometimes it might not be possible due to depending on previous state changes).
Take the "dstTarget" and "dstCallData" and push it through the Governance bridge. Remember to drop some SOL in the process to CPI Authority (eg. for Pause Proxy
AYPtjx4Hc8us1ikULUedkmZ3wtiD6tmL7gK3qe4V3oHt). You can send manually on Solana or use Native Drop feature of LZ.Disclaimer:
Script hasn't been audited. Please take caution where using the script, and double check generated transaction accounts, data, ideally by running simulation in Solana Explorer.