Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£869.43
EST. MONTHLY
203
DAYS
EST. ROI
This guide explains Bitcoin Core joinpsbts 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.18.0 joinpsbts combined multiple distinct base64 PSBTs into one PSBT containing every input and output. No input could appear in more than one source.
- Why it matters: joinpsbts constructs a new shared transaction from disjoint proposals. Safety depends on recognising that old signatures vanish and every fee, output and participant commitment must be reviewed again.
- 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 joinpsbts RPC in simple English
Bitcoin Core joinpsbts RPC: Decode every source and identify its unsigned transaction, inputs, outputs, metadata and owner. Joining is not the same as combinepsbt, which merges data for the same transaction.
Simple example
A miner is checking Bitcoin Core joinpsbts RPC. Joining can dilute fees or create dust even when each source looked acceptable. Reject duplicate outpoints across all sources before calling the RPC.
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.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- PSBT:
- A portable format for passing an unsigned or partly signed Bitcoin transaction between tools and signers.
Distinct proposals
Decode every source and identify its unsigned transaction, inputs, outputs, metadata and owner. Joining is not the same as combinepsbt, which merges data for the same transaction.
Disjoint inputs
Reject duplicate outpoints across all sources before calling the RPC. A repeated input makes the set invalid and may reveal a coordination or replay error.
All outputs retained
The result includes all outputs from all proposals. Confirm recipients, amounts, data outputs and permitted ordering, then recompute aggregate intent and change.
Signatures dropped
All signatures are discarded because the joined transaction has a different commitment. Every participant must review and sign the final joined artefact again.
Fees and policy
Authenticate UTXO values, total outputs and estimated size to calculate the new fee and rate. Joining can dilute fees or create dust even when each source looked acceptable.
Privacy
Joined PSBTs link participants, inputs, outputs and metadata. Minimise derivation paths and proprietary fields, use an authorised coordinator and define abort and retry handling.
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 joinpsbts RPC?
Bitcoin Core joinpsbts RPC: Decode every source and identify its unsigned transaction, inputs, outputs, metadata and owner.
For Bitcoin Core joinpsbts RPC, what should a beginner know about distinct proposals?
Decode every source and identify its unsigned transaction, inputs, outputs, metadata and owner.
For Bitcoin Core joinpsbts RPC, what should a beginner know about disjoint inputs?
Reject duplicate outpoints across all sources before calling the RPC. A repeated input makes the set invalid and may reveal a coordination or replay error.
For Bitcoin Core joinpsbts RPC, what should a beginner know about all outputs retained?
The result includes all outputs from all proposals. Confirm recipients, amounts, data outputs and permitted ordering, then recompute aggregate intent and change.
Conclusion
joinpsbts constructs a new shared transaction from disjoint proposals. Safety depends on recognising that old signatures vanish and every fee, output and participant commitment must be reviewed again.
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.