Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£856.08
EST. MONTHLY
NO PAYBACK
EST. ROI
This guide explains Bitcoin Core send 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.21 introduced the experimental send RPC as a flexible transaction-construction interface. It accepts multiple address outputs or one data output, fee controls and detailed input, change, locking, replacement and PSBT options.
- Why it matters: The send RPC can consolidate several transaction-building workflows, but its flexible outcomes make explicit state handling essential. A production caller must know whether it received a proposal, signed transaction or broadcast result and verify each accordingly.
- 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 send RPC in simple English
Bitcoin Core send RPC: The 0.21 help explicitly labels send experimental. Pin request and response handling to the deployed version and keep a regression suite before upgrading Core.
Simple example
A miner is checking Bitcoin Core send RPC. Use idempotency outside Core, decode the candidate, reconcile recipients and fee, get approval, sign if needed, call testmempoolaccept where applicable, broadcast once and monitor replacement and confirmation.
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.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- PSBT:
- A portable format for passing an unsigned or partly signed Bitcoin transaction between tools and signers.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Experimental boundary
The 0.21 help explicitly labels send experimental. Pin request and response handling to the deployed version and keep a regression suite before upgrading Core.
Outputs
No output key may be duplicated: an address appears once and at most one data object is allowed. Parse BTC amounts exactly into satoshis and validate address network and encoded data policy.
Fees
Choose either estimator inputs or explicit sat/vB. If subtract_fee_from_outputs is used, recipients receive less than the entered amounts, so approvals must show final outputs rather than requested figures.
Inputs and change
Specified inputs include txid, vout and sequence; add_inputs controls whether Core may supplement them. Validate change address, type and position, coin locks, replaceability and privacy consequences.
Watch-only and signing
include_watching selects only solvable watch-only inputs. A wallet that cannot fully sign may return an incomplete PSBT; watch-only knowledge is never signing authority.
Broadcast control
add_to_wallet false prevents adding and broadcasting and returns transaction material. Psbt true forces a PSBT and implies that setting. Treat complete, txid, hex and psbt as conditional fields.
Production controls
Use idempotency outside Core, decode the candidate, reconcile recipients and fee, get approval, sign if needed, call testmempoolaccept where applicable, broadcast once and monitor replacement and confirmation. 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 the main point of Bitcoin Core send RPC?
Bitcoin Core send RPC: The 0.21 help explicitly labels send experimental. Pin request and response handling to the deployed version and keep a regression suite before upgrading Core.
For Bitcoin Core send RPC, what should a beginner know about experimental boundary?
The 0.21 help explicitly labels send experimental. Pin request and response handling to the deployed version and keep a regression suite before upgrading Core.
For Bitcoin Core send RPC, what should a beginner know about outputs?
No output key may be duplicated: an address appears once and at most one data object is allowed.
For Bitcoin Core send RPC, what should a beginner know about fees?
Choose either estimator inputs or explicit sat/vB. If subtract_fee_from_outputs is used, recipients receive less than the entered amounts, so approvals must show final outputs rather than requested figures.
Conclusion
The send RPC can consolidate several transaction-building workflows, but its flexible outcomes make explicit state handling essential. A production caller must know whether it received a proposal, signed transaction or broadcast result and verify each accordingly.
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.