Separate folders, receipts and a face-down phone representing the information boundaries around a payment, editorial illustration
BIP 352 / PAYMENTS

Receive without reusing an on-chain address.

Silent Payments lets a recipient publish static payment information while senders create distinct on-chain outputs.

Read the explanation
← All standards

Why it exists

BIP 352 lets a recipient publish one reusable Silent Payments identifier without placing that same address on every payment. Senders derive distinct Taproot outputs, and the recipient discovers them by scanning. Unlike BIP 47’s on-chain notification flow, the basic scheme needs no separate notification transaction.

How it works

The published identifier contains scan and spend public keys. A sender combines eligible input key material with the recipient’s scan key to derive a shared secret and a destination tweak. Because the calculation depends on the transaction inputs, separate payments can create different output keys.

The receiver uses its scan secret and the eligible transactions’ input information to reproduce candidate output keys. A match identifies a payment. The spend secret allows the recipient to construct the private key needed to spend it; a scanning role can be separated from spending authority.

PUT IT IN CONTEXT

A practical example

A charity could publish a Silent Payments identifier on a permanent poster. Two compatible wallets paying that identifier produce different on-chain destinations. The charity’s scanner recognises both, but an observer cannot simply search for one reused output address to total those donations.

What to keep in mind

Scanning and recovery are more demanding than watching a conventional address list. Support must include reliable restoration, not just sending. Combining received coins later can reveal relationships, and publishing an identifier alongside a name still reveals that public association.

Status & implementation

BIP 352 is Complete, with official send/receive test vectors and a reference implementation. It uses existing Taproot outputs rather than a new consensus activation. Sending, receiving and scanning support are separate capabilities to check in a wallet.

Specification status: Complete · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close