Spending Silent Payment outputs with PSBTs

The five-minute read

One action, walked through

1. Open BIP 376 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: We use the following functions and conventions: ser 32 (i): serializes a 32-bit unsigned integer ''i'' as a 4-byte sequence, most significant byte first.
3. Name the object that changes: SEC1, SHA256.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 376 at the status the text itself states: Draft.
• The object that has to change is SEC1, SHA256. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

What happened after the paper

The source marks this draft. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What must an implementation of Spending Silent Payment outputs with PSBTs accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: SEC1, SHA256?

Terms

BIP 376

The public text titled Spending Silent Payment outputs with PSBTs.

Draft

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• We use the following functions and conventions: ser 32 (i): serializes a 32-bit unsigned integer ''i'' as a 4-byte sequence, most significant byte first.
• ser 256 (p): serializes the integer p as a 32-byte sequence, most significant byte first.
• ser P (P): serializes the coordinate pair P = (x,y) as a byte sequence using SEC1's compressed form: (0x02 or 0x03) || ser 256 (x), where the header byte depends on the parity of the omitted Y coordinate.

How the mechanism is specified

• Taken from the specification, the next constraint is: ser 256 (p): serializes the integer p as a 32-byte sequence, most significant byte first.
• Locate SEC1, SHA256 in BIP 376 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this draft. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use BIP 376 when a pitch says 'Spending Silent Payment outputs with PSBTs' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.