Ported Migration Script to Rust #752
Merged
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.
@DannyDelott Reported an issue on Monday that he couldn't access the
getPoolConfigfunction on theStETHHyperdriveinstance deployed by theDevnetMigration.s.solscript. After investigating the issue, I found that theer was no bytecode stored at thestethHyperdriveaddress. Since the last release, we addedcreate2to the deployment, and from reading through Foundry's open issues, there are a number of issues relating tocreate2deployments in Foundry scripts and tests. With this in mind, I decided to re-write the migration script in Rust to fix the issue. It appears that this worked.