This guide explains Bitcoin Core sendrawtransaction 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 sendrawtransaction submitted a serialised, hex-encoded transaction to the local node and network and returned the transaction hash. The optional allowhighfees flag defaulted false and bypassed a historical fee-safety check when true.
- Why it matters: sendrawtransaction is the final irreversible exposure point for signed bytes. Safe broadcast requires exact transaction and fee verification, guarded retry and no casual use of the high-fee override.
- Current position: Bitcoin Core 0.16.0 sendrawtransaction submitted a serialised, hex-encoded transaction to the local node and network and returned the transaction hash.
Bitcoin Core sendrawtransaction RPC in simple English
Bitcoin Core sendrawtransaction RPC: Compute txid before broadcast and treat already-known responses as a state to inspect. Do not rebuild or re-sign blindly after timeout.
Simple example
A miner is checking Bitcoin Core sendrawtransaction RPC. Decode with a version-pinned parser and verify transaction structure and signatures or script satisfaction before exposing it to the node.
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.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Signed serialisation
Accept only bounded even-length hex from an authenticated workflow. Decode with a version-pinned parser and verify transaction structure and signatures or script satisfaction before exposing it to the node.
Inputs and outputs
Resolve every previous output, calculate input value, recipient outputs, change and fee in satoshis and verify locktime and sequence. A transaction can be valid yet pay the wrong address or fee.
High-fee override
allowhighfees false is the safe default. True disables an important historical check and requires exceptional independent approval with a hard computed fee and feerate limit. Never enable it globally to make an error disappear.
Local acceptance
The node applies consensus and policy, checking conflicts, fees and mempool conditions. A returned txid means local submission succeeded; it does not guarantee every peer accepted or that miners will include it.
Idempotent retries
Compute txid before broadcast and treat already-known responses as a state to inspect. Do not rebuild or re-sign blindly after timeout. Query local mempool and chain and compare exact serialisation before retrying.
Privacy and relay
Broadcast timing and peer topology can reveal transaction origin. Use approved node and network routing, restrict RPC and avoid logging raw hex that may contain sensitive wallet structure.
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 sendrawtransaction RPC?
Bitcoin Core sendrawtransaction RPC: Compute txid before broadcast and treat already-known responses as a state to inspect.
For Bitcoin Core sendrawtransaction RPC, what should a beginner know about signed serialisation?
Accept only bounded even-length hex from an authenticated workflow. Decode with a version-pinned parser and verify transaction structure and signatures or script satisfaction before exposing it to the node.
For Bitcoin Core sendrawtransaction RPC, what should a beginner know about inputs and outputs?
Resolve every previous output, calculate input value, recipient outputs, change and fee in satoshis and verify locktime and sequence.
For Bitcoin Core sendrawtransaction RPC, what should a beginner know about high-fee override?
allowhighfees false is the safe default. True disables an important historical check and requires exceptional independent approval with a hard computed fee and feerate limit.
Conclusion
sendrawtransaction is the final irreversible exposure point for signed bytes. Safe broadcast requires exact transaction and fee verification, guarded retry and no casual use of the high-fee override.
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.