Silent Payments let a recipient publish one reusable identifier while senders derive unique Taproot outputs non-interactively from transaction input keys and recipient scan/spend keys.
No notification server or prior sender-recipient interaction is required. [BIP 352 — Silent Payments] [Bitcoin Optech — Silent payments]
Recipients must scan eligible transactions and perform additional elliptic-curve work to detect outputs. [BIP 352 — Silent Payments] [Silent Payments reference]
They improve address-reuse privacy but do not hide transaction amounts, timing or all ownership heuristics. [Bitcoin Optech — Silent payments] [Silent Payments reference]
No notification server or prior sender-recipient interaction is required. [Silent Payments reference] [Bitcoin Core — wallet descriptors]
Recipients must scan eligible transactions and perform additional elliptic-curve work to detect outputs. [BIP 352 — Silent Payments] [Bitcoin Core — wallet implementation]
They improve address-reuse privacy but do not hide transaction amounts, timing or all ownership heuristics. [Bitcoin Core — wallet descriptors] [Bitcoin Core — wallet implementation]
No notification server or prior sender-recipient interaction is required. [Silent Payments reference] [BIP 340 — Schnorr Signatures]
Recipients must scan eligible transactions and perform additional elliptic-curve work to detect outputs. [Bitcoin Optech — Silent payments] [Bitcoin Core — wallet descriptors]
They improve address-reuse privacy but do not hide transaction amounts, timing or all ownership heuristics. [BIP 352 — Silent Payments] [BIP 340 — Schnorr Signatures]
No notification server or prior sender-recipient interaction is required. [Bitcoin Core — wallet implementation] [BIP 340 — Schnorr Signatures]
For the clearest picture, read this entry together with Bitcoin Privacy, Pseudonymity, Taproot, CoinJoin. The reverse links also lead from Bitcoin Privacy.