Difference between revisions of "Block hashing algorithm"

Line 6: Line 6:
  
 
Each field includes a counter parameter that is relatively small (32-bits). The hash function cycles through all values of the Nonce field then increments (or otherwise changes) the extraNonce field before going through all permutations of the Nonce again. Incrementing the extraNonce field entails recomputing the merkle tree root as it modifies the hash of the Coinbase transaction.
 
Each field includes a counter parameter that is relatively small (32-bits). The hash function cycles through all values of the Nonce field then increments (or otherwise changes) the extraNonce field before going through all permutations of the Nonce again. Incrementing the extraNonce field entails recomputing the merkle tree root as it modifies the hash of the Coinbase transaction.
 
==Endianess==
 
Note that the hash, which is a 256-bit number, has lots of leading zero bytes when stored or printed as a big-endian hexadecimal constant, but it has trailing zero bytes when stored or printed in little-endian. For example, if interpreted as a string and the lowest (or start of) the string address keeps lowest significant byte, it is little-endian.
 
 
Most block explorers display the hash values as big-endian numbers; notation for numbers is usual (leading digits are the most significant digits read from left to right).
 
  
 
==Attribution==
 
==Attribution==
 
This content is based on content sourced from https://en.bitcoin.it/wiki/Block_hashing_algorithm under [https://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0]. Although it may have been extensively revised and updated we acknowledge the original authors.
 
This content is based on content sourced from https://en.bitcoin.it/wiki/Block_hashing_algorithm under [https://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0]. Although it may have been extensively revised and updated we acknowledge the original authors.

Revision as of 01:14, 18 June 2020

Bitcoin mining uses a hash based Proof of Work function. The algorithm requires the following parameters: a service string, a nonce, and a counter. In Bitcoin the service string is encoded in the block header data structure, and includes a version field, the hash of the previous block, the root hash of the Merkle tree of all transactions in the block, the current time, and the target of the proof of work function.

Bitcoin miners commonly make use of two nonce fields:

  1. The Nonce field which is included in the block header
  2. The extraNonce field which is part of the Coinbase transaction

Each field includes a counter parameter that is relatively small (32-bits). The hash function cycles through all values of the Nonce field then increments (or otherwise changes) the extraNonce field before going through all permutations of the Nonce again. Incrementing the extraNonce field entails recomputing the merkle tree root as it modifies the hash of the Coinbase transaction.

Attribution

This content is based on content sourced from https://en.bitcoin.it/wiki/Block_hashing_algorithm under Creative Commons Attribution 3.0. Although it may have been extensively revised and updated we acknowledge the original authors.