Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core waitforblockheight RPC: Height Threshold Guide
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.
TL;DR
- What it is: Bitcoin Core 30.0 exposes waitforblockheight for automation that needs the active chain to reach at least a chosen height. The RPC returns the current tip when the threshold is reached, when the timeout expires or when the node exits.
- Why it matters: 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.
- Current position: The condition is active-chain height at least the supplied integer.
What this means in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of a mempool as one node’s waiting room for valid transactions that have not yet entered a block. Different nodes can have different waiting rooms, and the contents can change from one second to the next.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Threshold meaning
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.
Timeout semantics
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.
Correct predicate
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.
Reorganisation risk
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.
Client lifecycle
Set application and proxy timeouts consistently. On disconnection, fetch the current tip before retrying and avoid multiplying blocked workers.
Input safety
Reject negative, implausibly large or stale targets before making the call. Derive heights from a trusted workflow rather than unauthenticated external input.
Automation pattern
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.
Frequently asked questions
What is Bitcoin Core waitforblockheight RPC?
Bitcoin Core 30.0 exposes waitforblockheight for automation that needs the active chain to reach at least a chosen height. The RPC returns the current tip when the threshold is reached, when the timeout expires or when the node exits.
Is Bitcoin Core waitforblockheight RPC active or supported today?
The condition is active-chain height at least the supplied integer.
Why does Bitcoin Core matter?
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.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
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.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 Explained made simple. See the main facts, costs, risks and practical checks before you make a decision.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.