New answers tagged block
1
Yes, in general node A will send the entire block with all transactions in entirety to other nodes for them to validate. The receiving nodes will receive an entire block with everything in the block header and every transaction in the order that is required by the merkle root and they will validate everything in that block.
There is a network optimization ...
1
Full nodes validate everything. A miner must be running a full node. Not all full nodes are miners, but all miners are full nodes.
A full node validates everything in a block; it validates the transactions, it checks the block header is correct, and checks the Proof of Work is correct. So in the validation process, full nodes (and thus miners) will verify ...
2
The cap on the block size excluding witness data is 1000000 bytes.
There is no cap on block size including witness data. Instead, there is a limit on the block weight at 4000000 weight units. Depending on the composition of the block, 4000000 WU can correspond to anything from 1000000 bytes to close to 4000000 bytes (including witness data).
But a block ...
0
The function is called GetBlockSubsidy now and it can be found in validation.cpp.
2
There are no real rules, per se, just various optimizations.
ASICs are fast. They can burn through the entire 2^32 possible nonces for a given block in seconds, which requires miners to use the extra nonce field in the coinbase transaction to generate a new block header (since altering the coinbase transaction changes the merkle root) and try again.
This ...
Top 50 recent answers are included
