-
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
fix unfairness on proof size check estimation #2946
Conversation
WASM runtime size check:Compared to target branchMoonbase runtime: 2280 KB (no changes) ✅ Moonbeam runtime: 2236 KB (no changes) ✅ Moonriver runtime: 2256 KB (no changes) ✅ Compared to latest release (runtime-3200)Moonbase runtime: 2280 KB (+320 KB compared to latest release) Moonbeam runtime: 2236 KB (+312 KB compared to latest release) Moonriver runtime: 2256 KB (+332 KB compared to latest release) |
Coverage Report@@ Coverage Diff @@
## master ahmad-evm-native-transfer-test +/- ##
==================================================================
- Coverage 79.13% 79.12% -0.01%
Files 303 303
- Lines 88050 88015 -35
==================================================================
- Hits 69675 69637 -38
+ Misses 18375 18378 +3
|
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.
We should revert the Cargo.lock
changes. This PR should only update frontier and moonkit dependencies
What does it do?
It points frontier and moonbeam to the latest pin in stable, which includes this commit.
What important points reviewers should know?
batch_not_callable_by_smart_contract
was removed because the same functionality is covered bybatch_is_not_callable_by_dummy_code
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?