Merge #10608: Add a comment explaining the use of MAX_BLOCK_BASE_SIZE.

1887337 Add a comment explaining the use of MAX_BLOCK_BASE_SIZE. (Gregory Maxwell)

Tree-SHA512: 4c643a3696241fbf4eac8d58bb26586f319338b28ee86d20394a8ea362911b467853eb40c43487ede753209a3c7bee2e576d2ca80627e9fc924fabefbcaea34b
This commit is contained in:
Wladimir J. van der Laan 2017-06-24 15:43:50 +02:00
commit eee398fa12
No known key found for this signature in database
GPG Key ID: 1E4AED62986CD25D

View File

@ -12,7 +12,13 @@
static const unsigned int MAX_BLOCK_SERIALIZED_SIZE = 4000000;
/** The maximum allowed weight for a block, see BIP 141 (network rule) */
static const unsigned int MAX_BLOCK_WEIGHT = 4000000;
/** The maximum allowed size for a block excluding witness data, in bytes (network rule) */
/**
* The maximum allowed size for a block excluding witness data, in bytes (network rule).
* This parameter is largely superfluous because it is directly implied by the above block
* weight limit, even when BIP 141 is not active. It continues to exist for use in
* various early tests that run before the witness data has been checked.
* All tests related to it could be removed without breaking consensus compatibility.
*/
static const unsigned int MAX_BLOCK_BASE_SIZE = 1000000;
/** The maximum allowed number of signature check operations in a block (network rule) */
static const int64_t MAX_BLOCK_SIGOPS_COST = 80000;