-
Notifications
You must be signed in to change notification settings - Fork 51
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
Eth Beacon receiver in dancelight #717
Conversation
solo-chains/runtime/dancelight/src/bridge_to_ethereum_config.rs
Outdated
Show resolved
Hide resolved
WASM runtime size check:Compared to target branchdancebox runtime: 1416 KB (no changes) ✅ flashbox runtime: 836 KB (no changes) ✅ dancelight runtime: 1980 KB (no changes) ✅ container chain template simple runtime: 1096 KB (no changes) ✅ container chain template frontier runtime: 1392 KB (no changes) ✅ |
Coverage Report@@ Coverage Diff @@
## master girazoki-eth-receiver- +/- ##
==========================================================
+ Coverage 64.78% 64.93% +0.15%
+ Files 297 299 +2
+ Lines 51963 52255 +292
==========================================================
+ Hits 33661 33927 +266
+ Misses 18302 18328 +26
|
solo-chains/runtime/dancelight/src/bridge_to_ethereum_config.rs
Outdated
Show resolved
Hide resolved
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.
Seems alright. Apart from the minor issue in test @tmpolaczyk reported.
This PR adds the eth beacon receiver pallet from snowbridge. I also did set it up to Holesky in dancelight, as we will be connected to it.
I am mostly re-using the tests jsons generated by snowbridge in this case as I dont think it is worth generating new ones. These should also make sure our tests break if something in the pallet changes.
The main tests I am adding are for: