fix(trie): proof generation shouldnt encode private bit#303
Open
fix(trie): proof generation shouldnt encode private bit#303
Conversation
This file contains hidden or 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
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.
Not 100% sure about this one, but it seems like a bug, so opening and keeping as a DRAFT for now.
StorageProof's verify function encodes using the U256 value without the is_private bit.
There trying to verify proofs that get returned from
eth_getProofendpoint currently fails for private slots. We want to completely disallow generating proofs for private slots anyways, but this the code semantics should be clearer/cleaner.Implementation Note
In the seismic-trie the is-private bool is actually encoded as part of the key! Which is why it doesn't need to be concatenated to the value. Either would work, but I personally would err on the side of putting it in the value, even at the cost of wasting 1 extra byte, since we probably could then use the stock mpt trie library without needing to fork it I think...
Reproducible test
Here's the test I was playing with to figure this out. That being said it's coming from an eth_getProof call that was returning a proof for a private slot, which we want to disallow... but still leaving here for now.