-
Notifications
You must be signed in to change notification settings - Fork 3
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
Do we need to specify merkle value for closestDescendantMerkleValue
?
#88
Comments
The "Merkle value" is what is defined in the spec: https://spec.polkadot.network/chap-state#sect-merkl-proof It's either the node value if it's I don't really see the problem with making it well defined. It's not like we're going to change this aspect of the trie any time soon. Saying that the value is opaque instead of well-defined means that the value might change after |
I'm also in for making it non opaque. That was the main reason I created this issue, to get consensus on this. |
But then we should still specify it. I would assume return an encoded version of a SCALE encoded enum like this:
Does that makes sense to you? |
The Merkle value is:
https://spec.polkadot.network/chap-state#defn-merkle-value I don't see what more to specify |
The correct way is if the node value is |
Reading the spec it isn't clear to me if merkle value returned by
closestDescendantMerkleValue
is an opaque object or we need to specify it? I mean it probably makes 100% sense to keep it opaque, but then we should mention this and also mention that this can not be compared across different implementations (not sure someone would ever do this).The text was updated successfully, but these errors were encountered: