Clarify Tx Update To Header Hashing I/O (closes #675)

Thanks darren-a and Saïvann.
This commit is contained in:
David A. Harding 2014-12-10 20:48:31 -05:00
parent 4722fe993e
commit 25acab7584
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7

View file

@ -139,8 +139,10 @@ transaction history (although, it should be noted, that even less than 50% of th
The block header provides several easy-to-modify fields, such as a The block header provides several easy-to-modify fields, such as a
dedicated nonce field, so obtaining new hashes doesn't require waiting dedicated nonce field, so obtaining new hashes doesn't require waiting
for new transactions. Also, only the 80-byte block header is hashed for for new transactions. Also, only the 80-byte block header is hashed for
proof-of-work, so adding more bytes of transaction data to proof-of-work, so including a large volume of transaction data in
a block does not slow down hashing with extra I/O. a block does not slow down hashing with extra I/O, and adding additional
transaction data only requires the recalculation of the ancestor hashes in
the merkle tree.
{% endautocrossref %} {% endautocrossref %}