Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£858.42
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains Bitcoin Core submitblock 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 0.16.0 submitblock accepted a hex-encoded candidate block and attempted to submit it to the network. Its second optional value existed for BIP 22 compatibility and was ignored.
- Why it matters: submitblock is the hand-off from mining work to consensus validation. Safe operation preserves exact candidate identity, handles ambiguous responses idempotently and verifies propagation beyond the submitting node.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core submitblock RPC in simple English
Bitcoin Core submitblock RPC: Parse the exact hex before submission and compute block header hash independently. Confirm network, previous block, height context, version, time, difficulty target, nonce and transaction Merkle root.
Simple example
A miner is checking Bitcoin Core submitblock RPC. Do not let transport encoding or stale job identifiers substitute for candidate identity. Query the block hash and active chain before deciding whether a retry is necessary.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- 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.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Candidate identity
Parse the exact hex before submission and compute block header hash independently. Confirm network, previous block, height context, version, time, difficulty target, nonce and transaction Merkle root. Do not let transport encoding or stale job identifiers substitute for candidate identity.
Coinbase and commitments
Inspect the coinbase value, payout script, height commitment and witness commitment where applicable. Recalculate transaction fees and subsidy against the intended height. A block that solves proof of work can still fail consensus because its transactions or commitments are wrong.
BIP 22 interface
The required argument is block hex. The optional dummy parameter is compatibility baggage and is ignored, so it cannot carry policy or authentication. Keep job metadata in an external ledger keyed to the computed block hash rather than relying on that field.
Response classification
Interpret null, textual rejection information, RPC errors and timeouts using the documented BIP 22 and node-version behaviour. A timeout is unknown, not a safe instruction to mutate and resubmit. Query the block hash and active chain before deciding whether a retry is necessary.
Stale and duplicate work
The network tip may change between template creation and submission. Preserve the candidate bytes and job lineage, permit idempotent duplicate handling and distinguish stale-parent rejection from invalid proof or transaction rules. Never alter a solved header while attempting a retry.
Propagation evidence
Local acceptance does not prove broad relay or durable active-chain membership. Observe the block by hash through independent nodes, peers and pool accounting, then track competing tips and confirmations. Keep miner reward accounting provisional through the required maturity period.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core submitblock RPC?
Bitcoin Core submitblock RPC: Parse the exact hex before submission and compute block header hash independently.
For Bitcoin Core submitblock RPC, what should a beginner know about candidate identity?
Parse the exact hex before submission and compute block header hash independently.
For Bitcoin Core submitblock RPC, what should a beginner know about coinbase and commitments?
Inspect the coinbase value, payout script, height commitment and witness commitment where applicable.
For Bitcoin Core submitblock RPC, what should a beginner know about bip 22 interface?
The required argument is block hex. The optional dummy parameter is compatibility baggage and is ignored, so it cannot carry policy or authentication.
Conclusion
submitblock is the hand-off from mining work to consensus validation. Safe operation preserves exact candidate identity, handles ambiguous responses idempotently and verifies propagation beyond the submitting node.
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.
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.