fix: StorageTrie, ReceiptTrie and TransactionTrie shouldn't use TypedMpt
#446
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
crate: trace_decoder
0xaatif
changed the title
StorageTrie, ReceiptTrie and TransactionTrie shouldn't used TypedMptStorageTrie, ReceiptTrie and TransactionTrie shouldn't use TypedMpt
Nashtare
approved these changes
Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#413
Snippets from
0xaatif/typed-backend2that fix the bug.The basic change is
struct FooTrie { - typed: TypedMpt<Vec<u8>>, + untyped: HashedPartialTrie, }The following oracle passes
cargo build --release RUST_LOG=info ./target/release/leader \ --runtime in-memory \ --load-strategy on-demand rpc \ --rpc-type native \ --rpc-url "$RPC_URL" \ --block-interval 19807080..19807081 \ --backoff 1000 \ --max-retries 1000