Bitcoin Core waitforblockheight guide covering at-least height waits, timeout returns, response checks, reorganisations, client limits and reliable automation.
This guide explains Bitcoin Core waitforblockheight RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
Bitcoin Core waitforblockheight RPC: The condition is active-chain height at least the supplied integer. It is useful for coarse progress barriers but does not identify a particular block or guarantee a confirmation count for a transaction.
A miner is checking Bitcoin Core waitforblockheight RPC. Work tied to a particular transaction or block must test active-chain membership and confirmation depth after the wait.
The condition is active-chain height at least the supplied integer. It is useful for coarse progress barriers but does not identify a particular block or guarantee a confirmation count for a transaction.
The optional timeout is milliseconds and zero means wait indefinitely. Even a timed-out call returns the current tip object rather than a distinct success flag.
Continue only if returned height is at least the requested height. Preserve the returned hash too, because it identifies the chain view that satisfied or failed the condition.
A tip can cross the threshold and later reorganise. Work tied to a particular transaction or block must test active-chain membership and confirmation depth after the wait.
Set application and proxy timeouts consistently. On disconnection, fetch the current tip before retrying and avoid multiplying blocked workers.
Reject negative, implausibly large or stale targets before making the call. Derive heights from a trusted workflow rather than unauthenticated external input.
Log target, start, deadline and response; compare height; classify reached, timed out, node shutdown and transport failure; then perform the business-specific chain checks before committing state. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Bitcoin Core waitforblockheight RPC: The condition is active-chain height at least the supplied integer.
The condition is active-chain height at least the supplied integer. It is useful for coarse progress barriers but does not identify a particular block or guarantee a confirmation count for a transaction.
The optional timeout is milliseconds and zero means wait indefinitely. Even a timed-out call returns the current tip object rather than a distinct success flag.
Continue only if returned height is at least the requested height. Preserve the returned hash too, because it identifies the chain view that satisfied or failed the condition.
waitforblockheight provides an efficient at-least-height barrier, not finality. Reliable callers test the returned predicate explicitly and follow it with the transaction or block checks their workflow actually requires.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Bitcoin Core waitfornewblock RPC made simple. See what the feature does, where its limits sit and which checks node or wallet operators should make.
Bitcoin Core waitforblock RPC made simple. See what the feature does, where its limits sit and which checks node or wallet operators should make.
Bitcoin Core 26 submitpackage guide covering experimental child-with-parents packages, policy limits, fee results, replacements, propagation and safe submission.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.