-
Couldn't load subscription status.
- Fork 113
fix(levm, l1): fix hive tests rpc #2176
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
Conversation
Lines of code reportTotal lines added: Detailed view |
EF Tests ComparisonSame results between main branch and the current PR. |
Benchmark Results ComparisonPR ResultsBenchmark Results: Factorial
Benchmark Results: Factorial - Recursive
Benchmark Results: Fibonacci
Benchmark Results: ManyHashes
Benchmark Results: BubbleSort
Benchmark Results: ERC20 - Transfer
Benchmark Results: ERC20 - Mint
Benchmark Results: ERC20 - Approval
Main ResultsBenchmark Results: Factorial
Benchmark Results: Factorial - Recursive
Benchmark Results: Fibonacci
Benchmark Results: ManyHashes
Benchmark Results: BubbleSort
Benchmark Results: ERC20 - Transfer
Benchmark Results: ERC20 - Mint
Benchmark Results: ERC20 - Approval
|
Benchmark Block Execution Results Comparison Against Main
|
| TxResult::Success => { | ||
| new_state.extend(report.new_state.clone()); | ||
| } | ||
| TxResult::Success => {} |
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 were adding the new states in two places. I removed this one and kept the second one
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.
Great work ^_^
**Motivation** - When executing ethereum/rpc simulation with LEVM we have errors in a lot of tests. The error is when executing the blocks for the setup for these tests and how we created the withdrawals requests introduced in EIP-7002 **Description** - First, when we execute the transactions, we weren't handling if the account was delegated and we weren't using the correct bytecode. For this, we add the check for delegated accounts and get the bytecode. This is made when creating a new VM and using the function `eip7702_get_code()`. - Second, when creating the withdrawals requests, we were overwritting and loosing some of the new values in the account updates. We now merge both updates. - When running the system contract for the withdrawals requests introduced in EIP 7002, we were creating a new `CacheDB` instead of using the one with updated values. **Status** - All RPC Hive tests were passing, but with the changed made [here](lambdaclass#2179), 12 are failing due to a new missing implementation. Links to lambdaclass#2158 --------- Co-authored-by: Tomás Paradelo <[email protected]>
Motivation
Description
For this, we add the check for delegated accounts and get the bytecode. This is made when creating a new VM and using the function
eip7702_get_code().CacheDBinstead of using the one with updated values.Status
Links to #2158