Skip to content

Log the real limit when a block is too far in the future - #459

Merged
minuszka merged 1 commit into
defcon-project:v22.1.xfrom
minuszka:fix/future-block-time-message
Nov 15, 2026
Merged

minuszka merged 1 commit into
defcon-project:v22.1.xfrom
minuszka:fix/future-block-time-message

Conversation

@minuszka

Copy link
Copy Markdown
Contributor

This fixes a log message that showed Bitcoin's two-hour limit for a block from the future; it now shows this chain's three minutes, as do three RPC help texts. Tested on our CI server; the rule stays the same.

A block refused as time-too-new was logged against the adjusted time
plus two hours, Bitcoin's window, while the rule here allows three
minutes. The log now shows the limit the rule applied, and the help of
importmulti, importdescriptors and pruneblockchain gives the window in
seconds. The USDT cache test expects this chain's block subsidy. The
rule does not change. Tested on our CI server.
@minuszka
minuszka marked this pull request as ready for review November 15, 2026 14:41
@minuszka
minuszka merged commit 2c21821 into defcon-project:v22.1.x Nov 15, 2026
11 checks passed
@minuszka
minuszka deleted the fix/future-block-time-message branch November 15, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant