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
Leaves are sent in the multiproof slightly different than how they are actually stored in the trie. The difference lies in the key. In the multiproof the first part of a leaf is the full path from root to leaf, instead of the partial path from previous node to leaf. The LEAF opcode has an operand digit which specifies how to get this partial path by cutting a prefix of the full path.
This incurs some overhead on the verifier. If the leaf was sent "normally" verifier could simply hash it without any modifications. But now, they have to decode the leaf, decode hex prefix of key, split it, encode via hex prefix, encode RLP and then hash.
My question is what's the trade-off here? what will we lose if we send leaves "normally" and not send the full path as their keys?
The text was updated successfully, but these errors were encountered:
Leaves are sent in the multiproof slightly different than how they are actually stored in the trie. The difference lies in the key. In the multiproof the first part of a leaf is the full path from root to leaf, instead of the partial path from previous node to leaf. The
LEAF
opcode has an operanddigit
which specifies how to get this partial path by cutting a prefix of the full path.This incurs some overhead on the verifier. If the leaf was sent "normally" verifier could simply hash it without any modifications. But now, they have to decode the leaf, decode hex prefix of key, split it, encode via hex prefix, encode RLP and then hash.
My question is what's the trade-off here? what will we lose if we send leaves "normally" and not send the full path as their keys?
The text was updated successfully, but these errors were encountered: