BIP 376 (Spending Silent Payment Outputs with PSBTs) — Glossary

TERM_DEF // UPGRADES_BIPS / BIP_376_SPENDING_SILENT_PAYMENT_OUTPUTS_WITH_PSBTS

BIP 376 (SPENDING SILENT
PAYMENT OUTPUTS WITH PSBTS)

BIP 376 (Spending Silent Payment Outputs with PSBTs). PSBT extensions for spending detected Silent Payment outputs.

This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.

WHAT_BIP_376_SPENDING_SILENT_PAYMENT_OUTPUTS_WITH_PSBTS_IS

BIP 376 (Spending Silent Payment Outputs with PSBTs) — at a glance

UPGRADES

BIP 376 — "Spending Silent Payment Outputs with PSBTs" is a Bitcoin Improvement Proposal. PSBT extensions for spending detected Silent Payment outputs. BIPs in this number range typically deal with recent (2020+) post-Taproot proposals and consensus upgrades.

Why it exists

DESIGN

BIP 376 (Spending Silent Payment Outputs with PSBTs) exists because Bitcoin has no central authority — every change to wallet, miner, or node behaviour has to be coordinated through written specs that everyone can read, critique, and implement. The BIP process is how the community arrives at a single answer to a specific protocol question without anyone being in charge of dictating it.

HOW_IT_WORKS

Mechanism

HOW IT WORKS

BIP-376 is implemented in source code that the proposer drafts alongside the text — typically against Bitcoin Core. Reviewers read both the spec and the code, and a BIP is only considered "real" once at least one independent implementation exists and is observed running on mainnet (or signet, for unactivated consensus changes).

1. Author drafts BIP-376 against the BIP-2 template — abstract, motivation, specification, rationale. 2. The text + a reference implementation are posted on the bitcoin-dev list and as a PR to bitcoin/bips. 3. Reviewers tear it apart: ambiguities, security concerns, edge cases, interaction with prior BIPs. 4. Once stable, the BIP editor merges it; it gets a number (BIP-376) and the status "draft" or "proposed". 5. Implementations land in Bitcoin Core / wallets / other clients. For consensus changes: activation parameters chosen. 6. After deployment + adoption, BIP-376 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".

WORKED_EXAMPLE

BIP-376 — open the source

EXAMPLE

Full text : https://github.com/bitcoin/bips/blob/master/bip-0376.mediawiki BIP repo : https://github.com/bitcoin/bips Every BIP carries its own metadata header (Status, Type, Created, Layer, License) before the abstract. Skim the abstract first, then jump to "Specification" for the normative requirements, and "Reference Implementation" for the canonical code.

KEY_PROPERTIES

OPT-IN

No authority can force a BIP on anyone. Adoption depends entirely on whether the change is genuinely useful.

NUMBERED

Stable numeric reference — BIP-376 means the same thing across every wallet, miner, and node that has read this spec.

NON-CONSENSUS

BIP-376 is not a consensus rule — clients can implement it without coordinating with the network at large.

IMPLEMENTATION-DRIVEN

A BIP without a working implementation is just an idea. Real adoption requires code, testing, and time.

COMMON_PITFALLS

Things that catch people out

PITFALLS

Don't confuse "draft" / "proposed" / "final" status — read the BIP header before relying on it in production.
The BIP number is just an editorial counter — it doesn't imply correctness or stability. Always cross-reference with the latest bitcoin/bips repo.

RELATED_CONCEPTS

Other terms from Upgrades & BIPs — click any to read its page:

TERMINOLOGY_INDEX

TERMINOLOGY

BIP 376 (Spending Silent Payment Outputs with PSBTs)

PSBT extensions for spending detected Silent Payment outputs.

Segregated Witness (SegWit, BIP 141)

The 2017 upgrade separating witness-data/">witness data, fixing tx malleability, and introducing weight units.

Taproot (BIP 341)

The 2021 upgrade introducing key-aggregable schnorr-signatures/">Schnorr signatures and Merkleized script trees.

Tapscript (BIP 342)

Script-language updates accompanying Taproot — new opcodes, removed limits.

Schnorr (BIP 340)

The Schnorr signature spec adopted by Taproot.

BIP Process

The community workflow for proposing, discussing, and tracking changes to Bitcoin.

Soft Fork Activation

The mechanism (versionbits, MASF, UASF, Speedy Trial) by which soft forks turn on.

MASF (Miner-Activated Soft Fork)

Activation triggered by miner signaling in block versions.