How to compute MAST commit bytes in bitcoin payment?
The hash digests used to create the commitments are each 32 bytes, so proving that a spend of Figure 7-6 is authorized (using a merkle tree and the particular conditions) and authenticated (using signatures) uses 383 bytes. By comparison, the same spend without a merkle tree (i.e., providing all possible authorization conditions) uses 412 bytes.
Can anyone explain how to compute 383 bytes and 412 bytes? Thanks!
from Recent Questions - Bitcoin Stack Exchange https://ift.tt/M2lri0K
via IFTTT