You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an ABCI application storing IAVLProofs and one has to be able to validate these proofs outside of the application's context (and independently from the merkleeyes module). The application also store different kinds of merkle trees (using some other hashing algorithm), but all of them implementing the IAVL format to store merkle proofs :
type IAVLProof struct {
LeafHash []byte
InnerNodes []IAVLProofInnerNode
RootHash []byte
}
type IAVLProofInnerNode struct {
Height int8
Size int
Left []byte
Right []byte
}
The only information missing to independently validate a proof is the hsh function used to build the IAVL tree (ripemd160 in tendermint's case). My suggestion is to add a field hashFunction, either in IAVLProofInnerNode or directly in IAVLProof to make it possible for merkle proof validation systems to work with several kinds of merkle trees, including your IAVL+ implementation.
The text was updated successfully, but these errors were encountered:
I have an ABCI application storing IAVLProofs and one has to be able to validate these proofs outside of the application's context (and independently from the merkleeyes module). The application also store different kinds of merkle trees (using some other hashing algorithm), but all of them implementing the IAVL format to store merkle proofs :
The only information missing to independently validate a proof is the hsh function used to build the IAVL tree (
ripemd160
in tendermint's case). My suggestion is to add a fieldhashFunction
, either inIAVLProofInnerNode
or directly inIAVLProof
to make it possible for merkle proof validation systems to work with several kinds of merkle trees, including your IAVL+ implementation.The text was updated successfully, but these errors were encountered: