Out of Band Address Exchange using Payment Protocol Encryption

The five-minute read

One action, walked through

1. Open BIP 75 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This BIP is an extension to BIP 70 that provides two enhancements to the existing Payment Protocol.
3. Name the object that changes: SSL, TLS, MUST.
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 75 at the status the text itself states: Deployed.
• The object that has to change is SSL, TLS, MUST. A neighbouring document with a similar name is not this one.
• Wallet support is not the same as consensus validity.

What happened after the paper

The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is covered by the signed bytes in Out of Band Address Exchange using Payment Protocol Encryption?
• Can the same signature be replayed on another chain, account, or message?
• Which primitive does the text require: SSL, TLS, MUST?

Terms

BIP 75

The public text titled Out of Band Address Exchange using Payment Protocol Encryption.

Deployed

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

The problem the paper names

A signature that does not commit to what the user saw can be replayed into a different spend, a different chain, or a different message.

What the design proposes

• This BIP is an extension to BIP 70 that provides two enhancements to the existing Payment Protocol.
• # It allows the requester (Sender) of a PaymentRequest to voluntarily sign the original request and provide a certificate to allow the payee to know the identity of who they are transacting with.
• # It encrypts the PaymentRequest that is returned, before handing it off to the SSL/TLS layer to prevent man in the middle viewing of the Payment Request details.

How the mechanism is specified

• Taken from the specification, the next constraint is: # It allows the requester (Sender) of a PaymentRequest to voluntarily sign the original request and provide a certificate to allow the payee to know the identity of who they are transacting with.
• Locate SSL, TLS, MUST in BIP 75 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

• A signature scheme is not a privacy system. It hides the signer only if the protocol says so.
• Wallet support is not the same as consensus validity.
• The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 75 when a pitch says 'Out of Band Address Exchange using Payment Protocol Encryption' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.