-
Notifications
You must be signed in to change notification settings - Fork 224
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
Update wasm lanes and opcode costs #5022
Update wasm lanes and opcode costs #5022
Conversation
bors r+ |
Merge conflict. |
Conflicts: execution_engine_testing/tests/src/test/explorer/faucet.rs
@@ -850,7 +854,8 @@ mod tests { | |||
let mut rng = TestRng::new(); | |||
run_test_case(TOO_MANY_STANDARD, &mut rng); | |||
run_test_case(FULL_STANDARD, &mut rng); | |||
run_test_case(LESS_THAN_MAX_STANDARD, &mut rng); | |||
// NOTE: current prod chainspec has a limit of 1 large transaction, so one less is 0 which |
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 use the prod chainspec in tests? I thought we use local
? Could we have different limitations in local env? That would allow this test to be still valid?
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.
Historically we were always keeping local and prod chainspec consistent
bors r+ |
Build succeeded: |
1de16a7
into
casper-network:feat-2.0
This PR updates lanes, and max gas per block to accommodate more native transfers equal to the amount available under 1.5.x.
As for Wasm lanes, there's ongoing work to update the matching algorithm to find a slot based on a payment amount. The effective limit will be the sum of costs from the Wasm lines (500CSPR). Here, updated Wasm lanes from this PR will be compatible with the new mechanism. Opcode cost multipliers are also scaled up to accommodate the new computational limit.