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 decodepsbt 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 decodepsbt converted a base64 PSBT into structured JSON. It exposed the unsigned transaction, global unknown fields, per-input UTXOs, signatures, sighash, scripts, derivation data and final scripts, plus output metadata.
- Why it matters: decodepsbt turns a packet into reviewable evidence, but not trusted evidence. Safe inspection authenticates transaction intent and UTXOs, protects metadata and treats fee calculation as conditional on complete inputs.
- 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 decodepsbt RPC in simple English
Bitcoin Core decodepsbt RPC: Start with the decoded tx object and review version, locktime, ordered inputs, sequences and outputs exactly as with decoderawtransaction.
Simple example
A miner is checking Bitcoin Core decodepsbt RPC. Bound the base64 PSBT by size and source before decoding. When present, calculate it independently in satoshis, derive fee rate from final virtual size estimates and apply absolute and rate limits.
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.
Untrusted parser input
Bound the base64 PSBT by size and source before decoding. Parse errors, duplicate keys and unsupported structures must fail closed. A diagnostic endpoint exposed to arbitrary users can consume resources and reveal version-specific behaviour, so authenticate and rate-limit it.
Unsigned transaction intent
Start with the decoded tx object and review version, locktime, ordered inputs, sequences and outputs exactly as with decoderawtransaction. Authenticate recipients, amounts and change. Rich metadata cannot make a wrong unsigned transaction safe.
Input evidence
Inspect non-witness or witness UTXO data, partial signatures, sighash, redeem and witness scripts, final scripts and unknown fields. Cross-check UTXOs against a trusted node. Reject incompatible scripts, amounts or signature policies rather than assuming contributors supplied accurate metadata.
Derivation privacy
BIP32 master fingerprints and paths can link wallets, signers and change. Output records can reveal wallet ownership even before broadcast. Minimise who can decode complete packets and redact operational records while retaining hashes needed for audit lineage.
Conditional fee
The fee is present only when all UTXO slots needed for calculation are filled. Its absence means unknown, not zero. When present, calculate it independently in satoshis, derive fee rate from final virtual size estimates and apply absolute and rate limits.
Unknown fields
Preserve unknown key-value fields across compliant PSBT roles but do not execute or trust proprietary semantics without an allow-list. Log their key identifiers and hashes rather than full possibly sensitive values. Reject collisions or unexpected critical workflow data.
Review fixtures
Decode creator-only, updated, partially signed, finalised and malformed PSBTs. Test missing UTXOs, conflicting amounts, unusual sighash, derivation paths, unknown fields and oversized data. Verify the reviewer distinguishes missing, incomplete, final and extractable states.
Frequently asked questions
What is the main point of Bitcoin Core decodepsbt RPC?
Bitcoin Core decodepsbt RPC: Start with the decoded tx object and review version, locktime, ordered inputs, sequences and outputs exactly as with decoderawtransaction.
For Bitcoin Core decodepsbt RPC, what should a beginner know about untrusted parser input?
Bound the base64 PSBT by size and source before decoding. Parse errors, duplicate keys and unsupported structures must fail closed.
For Bitcoin Core decodepsbt RPC, what should a beginner know about unsigned transaction intent?
Start with the decoded tx object and review version, locktime, ordered inputs, sequences and outputs exactly as with decoderawtransaction.
For Bitcoin Core decodepsbt RPC, what should a beginner know about input evidence?
Inspect non-witness or witness UTXO data, partial signatures, sighash, redeem and witness scripts, final scripts and unknown fields.
Conclusion
decodepsbt turns a packet into reviewable evidence, but not trusted evidence. Safe inspection authenticates transaction intent and UTXOs, protects metadata and treats fee calculation as conditional on complete inputs.
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.