Skip to content

Commit 5f221c1

Browse files
committed
Improve MAX_FUTURE_BLOCK_TIME documentation
1 parent 2c1c06e commit 5f221c1

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/chain.h

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,12 @@
1919
* Maximum amount of time that a block timestamp is allowed to exceed the
2020
* current network-adjusted time before the block will be accepted.
2121
*
22-
* This constrains clock *drift*, not mining duration. A miner stamps the
23-
* block at template creation, then spends an arbitrary amount of time
24-
* factoring. By the time the solution is broadcast the timestamp is in the
25-
* past relative to peers, which is always accepted (subject to the
26-
* monotonic-timestamp rule). The only failure mode is a miner whose local
27-
* clock is more than 4 seconds ahead of the network at template creation.
22+
* A miner stamps the block at template creation, then spends an arbitrary amount
23+
* of time factoring (eg. 180s, which is extremely fast for mainnet diff). Normally by the time the solution is broadcast,
24+
* the timestamp, determined before factoring starts, is far in the past.
25+
* Assuming monotonic timestamp, the only failure mode is a miner whose local clock is so far ahead (eg. 185s ahead)
26+
* that template creation timestamp is still in the future by the time peer receives the mined block,
27+
* or if a normal node falls 185s behind.
2828
*/
2929
static constexpr int64_t MAX_FUTURE_BLOCK_TIME = 4;
3030

0 commit comments

Comments
 (0)