Bitcoin Silent Payments Explained: How BIP-352 Works

Author logo
Tangem team
•
Post image

 

Bitcoin's blockchain is a public ledger. Every transaction is permanently recorded, and every address is pseudonymous rather than anonymous, meaning anyone can trace the full history of payments tied to a given address over time. Post one address publicly, and you've handed observers a window into every payment you receive.

 

Silent payments solve a specific version of this problem. They let you publish a single static identifier while each payment lands at a unique, unlinkable on-chain address. No coordination with the sender required. No notification transaction. Just privacy built into the protocol itself.

What are silent payments?

BIP-352 is a Bitcoin Improvement Proposal that defines a standard for static, reusable payment addresses where payments cannot be linked to the published address or to each other on-chain. The proposal was first dated March 9, 2023, and BIP-352 was formally added to the Bitcoin BIPs repository in May 2024.

 

A version-0 mainnet silent-payment address uses Bech32m encoding with the human-readable part sp. It begins sp1q, which is why you'll see these called sp1 addresses, and encodes two 33-byte compressed public keys: the scan public key followed by the spend public key.

 

Those two keys do different jobs. The scan key lets the recipient detect incoming payments by scanning the blockchain. The spend key controls the actual funds. Keeping them separate is a deliberate design choice, and it matters for hardware-wallet use cases explored later.

The address-reuse problem silent payments solve

Reusing a Bitcoin address links every payment to the same identifier. Anyone watching the blockchain can see the accumulated balance and the full transaction history. That's a real privacy cost, and it's why reusing addresses reduces privacy.

 

The standard workaround is HD wallet fresh addresses: your wallet automatically generates a new address for each transaction. It works well when the receiver and sender are in contact. But what if you want to post a donation address on a website, or accept payments without a back-and-forth exchange? Every visitor who wants to pay you needs a fresh address, which means you either reuse the same address (bad) or build an interactive system to hand out new ones (cumbersome).

 

Silent payments remove that interaction entirely. You publish one sp1 address. Each sender independently derives a unique unspent transaction output (UTXO)-producing output for you. No one watching the blockchain can connect those outputs to your published address or to each other.

How silent payments work, step by step

The mechanics look complex on paper but follow a clean logic. Here's the flow, without the equations:

  1. Publish your sp1 address. You generate a silent-payment address from your scan and spend public keys and share it publicly, on a website, in a profile, anywhere.
  2. The sender derives a shared secret. When someone wants to pay you, their wallet sums the private keys of the eligible inputs they're spending, then uses ECDH (Elliptic Curve Diffie-Hellman, a way for two parties to compute the same secret without exchanging it directly) with your spend public key to derive a shared secret unique to that transaction.
  3. The sender derives a Taproot output. Using that shared secret and your spend public key, the sender's wallet computes a fresh public key and encodes it as a Taproot output. This output looks like any ordinary Taproot output on-chain.
  4. The receiver scans eligible transactions. Your wallet uses your scan private key to check transactions that contain eligible inputs and at least one Taproot output. For each candidate, it recomputes the ECDH secret and derives the expected output key.
  5. Match found. Spend it. When a derived key matches an actual transaction output, your wallet knows it owns that output. It then computes the corresponding spend private key and can sign a transaction to move the funds.

Labels extend this further. A labeled silent-payment address embeds an extra value into the spend key, letting you distinguish payments by source (for example, separating donations from business payments) while using the same scan key. The zero value is reserved for change address outputs, so your own change returns to you without creating a detectable pattern.

Silent payments vs other ways to receive privately

MethodReusable public addressPayments linkable?Extra on-chain stepsReceiver scanning workWallet support
Reused addressYesYes, all linkedNoneNoneUniversal
HD fresh addressesNoNo, if used correctlyNoneNoneUniversal
BIP-47 / PayNymYesNotification visible1 notification txModerateLimited
BIP-352 Silent PaymentsYesNoNoneHigh (full scan)Growing

BIP-47 (PayNym) was an earlier attempt at the same problem. It requires a one-time on-chain notification transaction before payments can flow, making the sender-receiver relationship observable on-chain and adding a fee for that notification. This protocol skips the notification entirely: no extra transaction, no observable relationship, one standard Taproot output per payment.

 

Silent payments are also related to the stealth-address concept found in privacy-focused cryptocurrencies. If you want to compare Bitcoin's approach to the broader privacy coin landscape, see our overview of top privacy cryptocurrencies.

Benefits of silent payments

  • One public address, unlimited payments. You publish a single sp1 address and never need to update it or generate new ones for each payer.
  • Unlinkability on-chain. Each payment lands at a fresh Taproot output. No external observer can connect two payments to the same recipient by looking at the blockchain.
  • No notification transaction. Unlike BIP-47, silent payments create no observable on-chain relationship between sender and receiver before the payment itself.
  • Ordinary-looking transactions. Payments appear as standard Taproot outputs. There's no special marker that flags a transaction as a silent payment.
  • Separated scanning and spending keys. Because the scan key and spend key are distinct, a device or service can handle scanning without holding the keys that control funds. This separation also enables Schnorr signatures-compatible spending flows.

Limitations and trade-offs

The trade-offs are real, though. Understanding them is what separates informed adoption from disappointment.

  • Receiver scanning is the highest cost. Your wallet can't just watch for payments to a known address. It must scan eligible blockchain transactions, recompute ECDH secrets, and check for matches. Full nodes handle this more readily than light clients.

     

  • Light-client support remains open research. Privacy-preserving light-client infrastructure for silent payments is still being developed. The BIP estimates that serving tweak data requires roughly 33 bytes per eligible transaction, about 100 kB per 3,500-transaction block. That's manageable for a server, but non-trivial for a mobile wallet that tries to minimize data usage.

     

  • Sender compatibility is required. An sp1 address is useless if the sender's wallet doesn't support BIP-352. A sender using an incompatible wallet simply cannot pay you. This is the current practical ceiling on adoption.

     

  • Long addresses. Silent-payment addresses require at least 117 characters. That's longer than any standard Bitcoin address format and can cause display or input problems in older interfaces.

     

  • Collaborative transactions have limits. BIP-352 provides no formal security proof for collaborative transaction types such as CoinJoins, or transactions using MuSig or FROST inputs. Using silent payments in those contexts carries unresolved security questions.

     

  • Rescanning after restoration. If you restore a wallet from seed only, recovering unspent outputs requires scanning the UTXO set for relevant Taproot outputs. Recovering complete transaction history means rescanning the blockchain from your wallet's birthday. Wallets also need to scan from the last backup to catch any payments made since then.

Which wallets support silent payments (October 2026)

Support is growing but uneven. Sending is more widely available than receiving.

WalletSendingReceivingNotes
Cake WalletYesYesBoth sending and receiving supported
Sparrow WalletYes (v2.3.0)Yes (v2.5.0, May 2026)v2.5.0 includes air-gapped hardware-wallet signers
BitBox02YesNoSending only as of October 2026
NunchukYesYesReceiving added via server-assisted scanning
Bitcoin CoreNoNoPR #35301 merged Sept 23, 2026 adds primitives; wallet-level integration still in development

As of October 2026. Support changes quickly. Check each wallet's release notes before relying on these entries.

If you're interested in address rotation as a simpler privacy step that works today across more wallets, Tangem Wallet's Dynamic Addresses feature generates a fresh receiving address for each incoming transaction. That's address rotation, not silent payments. But it addresses the most common form of address reuse without requiring support for BIP-352 senders.

How to send or receive a silent payment

To receive:

  1. Generate a silent-payment address in a BIP-352-compatible wallet.
  2. Share your sp1 address publicly or with the sender.
  3. Your wallet scans eligible transactions using its scan key and detects outputs that belong to you.
  4. Matched outputs become spendable through the derived spend key.

 

To send:

  1. Open a BIP-352-compatible wallet and paste the recipient's sp1 address.
  2. The wallet selects eligible inputs (at least one is required; inputs with SegWit versions above 1 are excluded).
  3. It derives the recipient's unique Taproot output and constructs the transaction.
  4. Broadcast the transaction normally.

Start with a small test payment. Confirm the recipient wallet detects it before sending a larger amount. Keep backups current, because recovery requires rescanning transactions made since the last backup.

Silent payments and hardware wallets

Hardware wallets add a layer of complexity because the device must participate in ECDH derivation without exposing private keys to an online environment.

  • For sending, the computation can be split: the online application derives the recipient's fresh Taproot output using the recipient's public scan and spend keys, along with the eligible input keys. The hardware device provides or verifies its ECDH share through BIP375 PSBT fields, so the private key never leaves the device. BitBox02 firmware v9.21.0 (September 2024) added this sending capability. Sparrow 2.3.0 (October 2025) added sending support; Sparrow 2.4.0 (February 2026) added BIP375 hardware wallet support; and Sparrow 2.5.0 (May 2026) added receiving with air-gapped signers.

 

  • For receiving, the picture is harder. Scanning requires the scan private key to inspect transactions and derive matching output tweaks. An offline signer retaining only spending keys cannot scan on its own. A connected coordinator must supply verified tweaks for the hardware device to use when spending. This is why receiving support lags behind sending across the hardware-wallet ecosystem.

To understand the underlying address formats involved, see how Bitcoin addresses work. For background on extended public keys and wallet derivation, the xpub explainer covers the relevant concepts.

 

Dynamic Addresses in Tangem Wallet generate a new receiving address for each incoming transaction using standard BIP-44 derivation paths. This is address rotation, not silent payments. It is a useful distinction if you're evaluating privacy options across different wallet designs.

Final thoughts

Silent payments represent a meaningful step forward for Bitcoin privacy: a single reusable address, no notification transactions, and no on-chain links between payments. But support is not universal, and receiving requires scanning, either locally with a full node or through a service that can identify your payments.

 

Before relying on silent payments, verify that both your wallet and your senders' wallets implement BIP-352. For a broader look at cold-storage options that prioritize privacy alongside security, see our guide to the best Bitcoin cold storage wallets.

 


This article is for information only and is not financial advice. Wallet features change; check each wallet's documentation before relying on silent payments.

FAQ About Silent Payments

  • Silent payments are a Bitcoin protocol defined in BIP-352 that lets a recipient publish a single static address, with each payment going to a unique Taproot output, without address reuse or an on-chain notification transaction. The recipient must scan eligible blockchain transactions to detect payments. The proposal was dated March 9, 2023, and added to the Bitcoin BIPs repository in May 2024.

  • Silent payments do not add a separate protocol fee. The transaction still incurs normal Bitcoin network fees. Unlike BIP-47/PayNym, they avoid the notification transaction and its associated fee and on-chain footprint, while requiring more receiver-side scanning work.

  • Because silent payments use no notification transaction, the recipient's wallet cannot simply watch for payments to a known address. It must recompute the ECDH shared secret for eligible transactions and check whether any outputs match. This scanning burden is the main trade-off for the protocol's unlinkability guarantee.

  • Both let a recipient publish one reusable identifier. BIP-47 requires a one-time on-chain notification transaction before payments can flow, making the sender-receiver relationship observable and incurring an extra fee. BIP-352 skips the notification entirely, creates no observable on-chain relationship, and produces ordinary Taproot outputs, but shifts more work to the receiver's scanning process.

  • As of October 2026, Cake Wallet and Sparrow Wallet support both sending and receiving. BitBox02 supports sending only. Nunchuk supports both, using server-assisted scanning for receiving. Bitcoin Core merged foundational BIP-352 code in September 2026 but has not shipped wallet-level sending or receiving in a release. Support is evolving; check each wallet's release notes for the current status.

  • No. Sending to an sp1 address requires a wallet with BIP-352 support. A sender using an incompatible wallet cannot pay a silent-payment address. This sender-compatibility requirement is the current practical limit on how widely silent payments can be used.

Author logo
Author Tangem team

We are a team of Tangem Wallet users dedicated to simplifying self-custody for everyone.

Author logo
Reviewed by Patrick Dike-Ndulue

Senior editor covering crypto, onchain equities, and technology.