This repository has been archived by the owner on Jul 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 857
[MPT - stack trie] fix witness generation #1752
Comments
This is partially resolved by #1779, but would be good to add some further tests which would test |
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 26, 2024
### Description - Fix in the stack trie `GetProof` method - Added description for `TestTransactions` ### Issue Link #1752 ### Type of change - [x ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Refactor (no updates to logic) ### How Has This Been Tested? `TestTransactions` and `TestGetProof` in `zkevm-circuits/geth-utils/gethutil/mpt/witness/gen_witness_transactions_test.go`.
1 task
KimiWu123
added a commit
that referenced
this issue
Mar 6, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 7, 2024
### Description closed #1752 - Adding different numbers of txs to test different trie status (e.g. one leaf only, one ext. , one branch and one leaf ...etc) - Fixing `GetProof` (if input is an ext node, it always assign first child of the root ext. node, `st.children[0]`) - Fixing `getNodeFromBranchRLP` (if input is an leaf, it could throw an exception) - Refactoring `getNodeFromBranchRLP` ### Issue Link #1752 ### Type of change - [x] Bug fix (non-breaking change which fixes an issue)
1 task
KimiWu123
added a commit
that referenced
this issue
Apr 19, 2024
…fix-witness-generation-json-export
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the feature you would like
There was an implementation under
mpt-witness-generator/trie/stacktrie.go
already, but still has some bugs. This issue is mainly to fix it.See Miha's doc for more details.
Additional context
No response
The text was updated successfully, but these errors were encountered: