This guide explains BIP 375 Sending Silent Payments with PSBTs in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 375 is a Draft specification extending PSBT version 2 so multiple devices can construct Silent Payment outputs safely. Those scripts cannot be calculated until all eligible transaction inputs are known.
- Why it matters: BIP 375 addresses the coordination gap between PSBTv2 and Silent Payments. Its safety comes from freezing transaction context, proving each ECDH contribution and verifying final output scripts before any signature or broadcast.
- Current position: BIP 375 is a Draft specification extending PSBT version 2 so multiple devices can construct Silent Payment outputs safely.
BIP 375 Sending Silent Payments with PSBTs in simple English
BIP 375 Sending Silent Payments with PSBTs: BIP 375 is Draft, Specification, version 0.1.1 and requires BIPs 352, 370 and 374. Its fields are for PSBTv2, not PSBTv0.
Simple example
A node operator is checking BIP 375 Sending Silent Payments with PSBTs. Only after required shares and proofs validate may the output scripts be computed and the transaction extracted.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- 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.
Status and versions
BIP 375 is Draft, Specification, version 0.1.1 and requires BIPs 352, 370 and 374. Its fields are for PSBTv2, not PSBTv0.
Construction order
The constructor supplies Silent Payment recipients but output scripts remain unresolved until all inputs and their eligibility data are fixed.
Global share
A global field keyed by a 33-byte scan key carries the combined ECDH share for that recipient scan key.
Global proof
A matching global field carries the 64-byte BIP 374 proof for the ECDH share. Both fields must identify the same scan key and transaction context.
Signer work
Each signer determines eligible inputs it controls, computes its share and proof, verifies other contributions and refuses changed inputs, recipients or amounts.
Change detection
Roles must distinguish Silent Payment recipients from wallet change so output construction cannot redirect change or conceal a substituted recipient.
Extraction
Only after required shares and proofs validate may the output scripts be computed and the transaction extracted. Test missing, duplicated, inconsistent and stale fields. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of BIP 375 Sending Silent Payments with PSBTs?
BIP 375 Sending Silent Payments with PSBTs: BIP 375 is Draft, Specification, version 0.1.1 and requires BIPs 352, 370 and 374.
For BIP 375 Sending Silent Payments with PSBTs, what should a beginner know about status and versions?
BIP 375 is Draft, Specification, version 0.1.1 and requires BIPs 352, 370 and 374.
For BIP 375 Sending Silent Payments with PSBTs, what should a beginner know about construction order?
The constructor supplies Silent Payment recipients but output scripts remain unresolved until all inputs and their eligibility data are fixed.
For BIP 375 Sending Silent Payments with PSBTs, what should a beginner know about global share?
A global field keyed by a 33-byte scan key carries the combined ECDH share for that recipient scan key.
Conclusion
BIP 375 addresses the coordination gap between PSBTv2 and Silent Payments. Its safety comes from freezing transaction context, proving each ECDH contribution and verifying final output scripts before any signature or broadcast.
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.