Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£865.50
EST. MONTHLY
204
DAYS
EST. ROI
This guide explains Bitcoin Core createpsbt 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.17.0 createpsbt implemented the BIP 174 Creator role. It accepted selected transaction inputs, payment or data outputs, optional locktime and an optional BIP 125 replaceable flag, then returned a base64 PSBT.
- Why it matters: createpsbt creates an unsigned transaction proposal, not a payment. Safety comes from exact input and output construction, explicit locktime and replacement policy and an immutable decoded intent for every later role.
- 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 createpsbt RPC in simple English
Bitcoin Core createpsbt RPC: Immediately decode the result and compare version, locktime, ordered inputs, sequences and outputs with the approved request. Compute a workflow identity for the unsigned transaction and prevent downstream participants from silently changing that intent.
Simple example
A miner is checking Bitcoin Core createpsbt RPC. Replaceable defaults false and marks the transaction as BIP 125 replaceable when true. Authenticate recipients separately and convert BTC values to integer satoshis before construction to avoid floating-point ambiguity.
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.
Explicit inputs
Each input requires a txid and vout and can carry a sequence. Authenticate every outpoint against the intended wallet or funding system and ensure it is available, unspent and approved. The Creator does not prove ownership or supply the UTXO amount needed for later fee review.
Ordered outputs
The output array can contain address-to-amount pairs and data-to-hex pairs. Preserve order deliberately and prohibit duplicate or unexpected change destinations. Authenticate recipients separately and convert BTC values to integer satoshis before construction to avoid floating-point ambiguity.
Locktime semantics
locktime defaults zero. A non-zero locktime also activates inputs through appropriate sequence handling unless explicit sequences govern them. Define whether the value is block height or time under transaction rules and test the intended spendability boundary.
Replacement policy
replaceable defaults false and marks the transaction as BIP 125 replaceable when true. Explicit sequences incompatible with the requested flag cause an error. Record the replacement decision and customer consequences; signalling does not guarantee that every later replacement will relay.
Creator-role limits
The result lacks the metadata, signatures and final scripts needed to spend. Pass it through authenticated updater and signer roles. Never present a created PSBT as funded, approved or fee-complete, and do not infer final fee until reliable UTXO values are present.
Decode and freeze
Immediately decode the result and compare version, locktime, ordered inputs, sequences and outputs with the approved request. Compute a workflow identity for the unsigned transaction and prevent downstream participants from silently changing that intent.
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 createpsbt RPC?
Bitcoin Core createpsbt RPC: Immediately decode the result and compare version, locktime, ordered inputs, sequences and outputs with the approved request.
For Bitcoin Core createpsbt RPC, what should a beginner know about explicit inputs?
Each input requires a txid and vout and can carry a sequence.
For Bitcoin Core createpsbt RPC, what should a beginner know about ordered outputs?
The output array can contain address-to-amount pairs and data-to-hex pairs.
For Bitcoin Core createpsbt RPC, what should a beginner know about locktime semantics?
locktime defaults zero. A non-zero locktime also activates inputs through appropriate sequence handling unless explicit sequences govern them.
Conclusion
createpsbt creates an unsigned transaction proposal, not a payment. Safety comes from exact input and output construction, explicit locktime and replacement policy and an immutable decoded intent for every later role.
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.