Repository navigation
Log the real limit when a block is too far in the future - #459
Merged
minuszka merged 1 commit intoNov 15, 2026
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.