Definition: Silent Payments is a Bitcoin payment protocol specified in BIP-352. It lets a recipient publish a reusable payment address while each payment creates a unique Taproot output. The sender does not need to contact the recipient, but the receiving wallet must scan the blockchain to detect payments.1
| Specification | BIP-352; the specification is marked Complete. That status describes the document, not support in every wallet. |
|---|---|
| Address format | Mainnet addresses begin sp1q; testnet and signet addresses begin tsp1q. |
| Payment output | A unique Taproot (P2TR) output is derived for each payment. |
| Directory | Bitcoin Directory |
How Silent Payments work
Bitcoin wallets commonly generate a fresh address for each payment because reusing one makes it easier for blockchain observers to connect transactions. Sharing a new address every time, however, requires the recipient to be available or to provide a batch of addresses in advance. Silent Payments aims to combine a reusable public address with a different on-chain destination for each payment.1
A Silent Payment address encodes two public keys: one for scanning and one for spending. When paying, a compatible wallet uses eligible transaction inputs and the recipient’s scan key to derive a shared secret. It combines that result with the recipient’s spend key to create a one-time Taproot output. The recipient’s wallet performs the corresponding scan and recognizes outputs it can spend. The recipient does not have to be online when the payment is made.
The protocol avoids a separate on-chain notification announcing the payment. BIP-352’s goals include unique outputs, no sender–recipient interaction, and transactions that blend in with ordinary Bitcoin activity. Its address format uses Bech32m: mainnet addresses start with sp1q, while testnet and signet addresses start with tsp1q.1
What happens during a payment
| Stage | What happens | Practical effect |
|---|---|---|
| 1. Share | The recipient shares one static Silent Payment address. | No fresh address exchange is needed for each payment. |
| 2. Derive | The sender’s wallet derives a payment-specific output from the address and eligible input data. | The sender can pay without an online handshake. |
| 3. Scan | The recipient’s wallet checks eligible transactions and outputs for a match. | Receiving requires wallet software that can scan for Silent Payments. |
| 4. Spend | The wallet uses the recipient’s spending key material for the detected output. | A standard-compatible wallet backup and recovery process still matters. |
Scanning, wallet support, and limitations
Scanning is the main trade-off. A recipient cannot identify incoming Silent Payments simply by searching for a conventional address in a block explorer; wallet software has to process the relevant transaction data and test outputs. Full nodes can perform that work, but lightweight-wallet support requires additional data and creates bandwidth and trust questions. BIP-352 discusses possible light-client approaches as an area for further research rather than a solved part of the specification.1
Silent Payments also do not make Bitcoin transactions fully anonymous. The blockchain remains public, and transaction amounts, timing, and other on-chain behavior can still reveal information. The protocol aims to reduce the direct link between a public receiving address and its payments; it does not hide every relationship or protect information shared outside the chain.
Implementation must follow the protocol’s input rules. BIP-352 recommends that the keys controlling a transaction’s inputs belong to the same entity, because the protocol has no formal security proof for collaborative use. Wallet compatibility therefore matters for both sending and receiving, especially when transactions involve coin selection, collaborative protocols, or light clients.1
A completed BIP is not proof that every wallet has implemented it. The libsecp256k1 0.8.0 release added a module for sending and receiving under BIP-352, while its changelog says the API needs full transaction data and does not implement light-client scanning. Bitcoin Core tracks protocol, sending, receiving, and light-client integration as separate work items. Check the documentation for the particular wallet before relying on it to create or detect Silent Payments.23
History
- March 2022: A public proposal for non-interactive private Bitcoin payments was discussed.
- March 9, 2023: BIP-352 was assigned as an application-layer specification.
- August 3, 2026: libsecp256k1 version 0.8.0 added a Silent Payments module implementing BIP-352; light-client scanning was not included in that API.
Related Terms
Related Articles
- Why Crypto Calls It a Wallet—and What the Metaphor Hides
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
- What Do Zero-Knowledge Proofs Actually Guarantee in Blockchain?
- Ethereum MEV Explained: Transaction Ordering, Block Builders, and User Risks
See Also
Page updated: November 10, 2026.
Sources
- Bitcoin Improvement Proposals. “BIP 352: Silent Payments.” Assigned March 9, 2023. Accessed November 10, 2026. https://github.com/bitcoin/bips/blob/master/bip-0352.mediawiki.
- Bitcoin Core. “Changelog.” libsecp256k1, version 0.8.0, August 3, 2026. Accessed November 10, 2026. https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md.
- Bitcoin Core. “BIP352 Tracking Issue #28536.” Opened September 26, 2023. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/issues/28536.