Taurus storage migration for "Private EVM" #3360
Draft
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.
TODO
taurus-runtime-upgrade
How to review this PR
This PR is the third in a series of PRs which add "private EVM" functionality to subspace. It upgrades the existing Taurus storage format for this feature. (Mainnet doesn't need an upgrade, because it doesn't have any EVMs deployed.)
The PR diff includes the migration from #3342, please ignore the
migration
module andVersionCheckedMigrateDomainsV1ToV2
type.The first PR in the series is #3359, it moves some test code around, and makes minor fixes.
The second PR in this series is #3350, which adds the feature to Mainnet.
What it does
This PR upgrades the domain registry storage into a new format which stores the initial contract creation allow list.
It also merges all the changes in #3350 into the
taurus-runtime-upgrades
branch.Code contributor checklist: