-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
State Trie Migration v1 #2907
State Trie Migration v1 #2907
Conversation
Some considerations about state tree migration can be found here: https://forum.polkadot.network/t/state-trie-migration/852/ |
Co-authored-by: Rodrigo Quelhas <[email protected]>
Coverage Report@@ Coverage Diff @@
## master tarekkma/state_migration +/- ##
============================================================
+ Coverage 79.18% 79.23% +0.05%
Files 299 299
+ Lines 87226 87602 +376
============================================================
+ Hits 69065 69405 +340
+ Misses 18161 18197 +36
|
WASM runtime size check:Compared to target branchMoonbase runtime: 2188 KB (no changes) ✅ Moonbeam runtime: 2148 KB (no changes) ✅ Moonriver runtime: 2148 KB (no changes) ✅ Compared to latest release (runtime-3200)Moonbase runtime: 2188 KB (+228 KB compared to latest release) Moonbeam runtime: 2148 KB (+224 KB compared to latest release) Moonriver runtime: 2148 KB (+224 KB compared to latest release) |
State version upgrade breaks our Zombienet tests because After 3300 is released, Zombienet tests should be changed back and work as expected with the branch built client. |
What does it do?
What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?