Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.99
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains Bitcoin Core sendmany 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 sendmany created one transaction paying multiple destination addresses. The required fromaccount was deprecated and should be the empty default.
- Why it matters: sendmany is efficient multi-recipient spending, but one fee and one transaction couple every output. Safe use requires exact amounts, explicit fee-subtraction consent, privacy review and complete decoded reconciliation.
- Current position: Bitcoin Core 0.16.0 sendmany created one transaction paying multiple destination addresses.
Bitcoin Core sendmany RPC in simple English
Bitcoin Core sendmany RPC: Every address-value pair becomes part of one transaction and one returned txid. Failure affects the batch. Deduplicate destinations, cap recipient count and preserve per-output business mapping for reconciliation.
Simple example
A miner is checking Bitcoin Core sendmany RPC. Get explicit commercial approval, calculate rounding and dust outcomes and display final decoded outputs before broadcast. Use explicit coin selection, wallet separation or reviewed PSBT workflows when source control matters.
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.
- 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.
One transaction, many outputs
Every address-value pair becomes part of one transaction and one returned txid. Failure affects the batch. Deduplicate destinations, cap recipient count and preserve per-output business mapping for reconciliation.
Deprecated source account
fromaccount is deprecated and should be empty. It is not reliable coin segregation. Use explicit coin selection, wallet separation or reviewed PSBT workflows when source control matters.
Exact amount map
Addresses are object keys and amounts may be numbers or strings in BTC. Validate unique network-correct addresses and convert each value to satoshis. Reject zero, negative, excessive and duplicate-key ambiguity before wallet mutation.
Fee subtraction
subtractfeefrom selects recipients that share the fee equally, so they receive less than the stated amounts. Get explicit commercial approval, calculate rounding and dust outcomes and display final decoded outputs before broadcast.
Replaceability and estimation
replaceable enables BIP 125 signalling. Conf_target is measured in blocks and estimate_mode is UNSET, ECONOMICAL or CONSERVATIVE. Record all settings and maximum fee; estimates are not guarantees.
Input confirmation and privacy
minconf defaults one for eligible wallet balance. Batching reduces overhead but publicly links recipients in one transaction. Apply coin-selection privacy and avoid combining unrelated sensitive payouts merely for convenience.
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 sendmany RPC?
Bitcoin Core sendmany RPC: Every address-value pair becomes part of one transaction and one returned txid.
For Bitcoin Core sendmany RPC, what should a beginner know about one transaction, many outputs?
Every address-value pair becomes part of one transaction and one returned txid.
For Bitcoin Core sendmany RPC, what should a beginner know about deprecated source account?
fromaccount is deprecated and should be empty. It is not reliable coin segregation.
For Bitcoin Core sendmany RPC, what should a beginner know about exact amount map?
Addresses are object keys and amounts may be numbers or strings in BTC.
Conclusion
sendmany is efficient multi-recipient spending, but one fee and one transaction couple every output. Safe use requires exact amounts, explicit fee-subtraction consent, privacy review and complete decoded reconciliation.
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.