BIP 23 getblocktemplate – Pooled Mining made simple. See what the proposal changes, its current status and what it means for Bitcoin users and operators.
BIP 23 getblocktemplate pooled mining: This guide explains BIP 23 getblocktemplate. Pooled Mining in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
BIP 23 getblocktemplate pooled mining: BIP 22 supplies the base JSON-RPC block-template contract, while BIP 23 adds pooled-mining extensions. Level-one and level-two support descriptions bundle particular optional features, but a production handshake should still inspect returned capabilities and fields.
A node operator wants to understand BIP 23 getblocktemplate pooled mining. A server name or version string is not proof of the supported subset. A miner can submit hex-encoded block data in proposal mode before proof of work is found.
BIP 22 supplies the base JSON-RPC block-template contract, while BIP 23 adds pooled-mining extensions. Level-one and level-two support descriptions bundle particular optional features, but a production handshake should still inspect returned capabilities and fields. A server name or version string is not proof of the supported subset.
A miner can submit hex-encoded block data in proposal mode before proof of work is found. The server validates the candidate against its normal rules except proof of work and returns null, a rejection reason, a delta template or a work identifier. This catches invalid construction before scarce hashing time is committed.
The mutable array tells the client which parts it may change, including coinbase data, time, transactions, previous block or version under defined labels. Permission must be explicit. A client that silently modifies fields outside the declared set can produce rejected shares or an invalid solved block even when the original template was sound.
noncerange can constrain the header nonce space, while mintime, maxtime and moving offsets bound timestamp updates. These values coordinate distributed workers and prevent stale or invalid header construction. Pools need careful integer, endianness and clock handling and should refresh immediately when the previous block changes.
The specification allows abbreviated results such as submitting coinbase-related data when the server can reconstruct the rest from a work identifier. This reduces transfer but introduces state coupling. A failover server cannot necessarily reconstruct another server’s abbreviation, and expired work must be rejected clearly rather than attached to a new template.
getblocktemplate lets a miner inspect transaction selection and block rules more directly than opaque work distribution, yet the node serving templates remains consensus-critical. Protect RPC authentication and network exposure, isolate proposal traffic, validate required transactions and monitor reject reasons without logging credentials or full sensitive payloads.
Against regtest, request the supported capabilities, propose valid and deliberately invalid candidates, exercise each permitted mutation and submit abbreviations with correct, wrong and expired work IDs. Simulate a tip change and pool failover. Record whether every backend rejects stale or unauthorised changes consistently.
BIP 23 getblocktemplate pooled mining: BIP 22 supplies the base JSON-RPC block-template contract, while BIP 23 adds pooled-mining extensions.
BIP 22 supplies the base JSON-RPC block-template contract, while BIP 23 adds pooled-mining extensions.
A miner can submit hex-encoded block data in proposal mode before proof of work is found.
The mutable array tells the client which parts it may change, including coinbase data, time, transactions, previous block or version under defined labels.
BIP 23 gives pooled miners a richer, testable getblocktemplate contract. Safe deployment depends on explicit capability negotiation, strict mutation boundaries, proposal validation and failover tests for work identifiers, time and stale templates.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
BIP 323 guide to the Draft proposal reserving block-header version bits 5 to 28 for mining nonce space, signalling masks, compatibility and firmware tests.
BIP 301 guide covering its Draft soft-fork status, sidechain block bids, BMM Accept and Request commitments, one-winner rule, miner incentives and risks.
BIP 310 version rolling explained: learn Stratum extension negotiation, masks, minimum bit counts, ASIC nonce space and pool safeguards.
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.