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
Currently, a node's Merkle structure is H(H(key, value), left_child, right_child). However, this means that in proofs we must always be sent both the key and the value together, whereas in absence proofs there are cases when we only care about the key.
This can be fixed by changing the structure to H(H(key, H(value)), left_child, right_child) to compress the value to a single hash at the cost of one more hash per value update. We could still choose to send the value in proofs if it is less than the hash length and we want to optimize for bandwidth rather than CPU.
The text was updated successfully, but these errors were encountered:
Currently, a node's Merkle structure is
H(H(key, value), left_child, right_child)
. However, this means that in proofs we must always be sent both the key and the value together, whereas in absence proofs there are cases when we only care about the key.This can be fixed by changing the structure to
H(H(key, H(value)), left_child, right_child)
to compress the value to a single hash at the cost of one more hash per value update. We could still choose to send the value in proofs if it is less than the hash length and we want to optimize for bandwidth rather than CPU.The text was updated successfully, but these errors were encountered: