-
Notifications
You must be signed in to change notification settings - Fork 384
Remove bridge features from moonbase runtime #3437
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
Remove bridge features from moonbase runtime #3437
Conversation
WASM runtime size check:Compared to target branchMoonbase runtime: 2676 KB (no changes) ✅ Moonbeam runtime: 2848 KB (no changes) ✅ Moonriver runtime: 2844 KB (no changes) ✅ Compared to latest release (runtime-3900)Moonbase runtime: 2676 KB (+316 KB compared to latest release) Moonbeam runtime: 2848 KB (+368 KB compared to latest release) Moonriver runtime: 2844 KB (+364 KB compared to latest release) |
Coverage Report@@ Coverage Diff @@
## master rq/remove-bridge-features-from-moonbase-runtimes +/- ##
====================================================================================
+ Coverage 74.09% 74.10% +0.01%
- Files 406 404 -2
- Lines 98579 98522 -57
====================================================================================
- Hits 73037 73005 -32
- Misses 25542 25517 -25
|
manuelmauro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Do we need any migration for this?
I would say that we don't need a migration, those pallets were never included in Alphanet, only on betanet and stagenet. |
What does it do?
Reverts most of the changes included in Bridge setup (Stagenet <-> Betanet)
What important points should reviewers know?
Since we now have a proper testnet for testing the bridge between
MoonbeamandMoonriver, there is no longer the need to have the bridging functionality in the moonbase-runtime.