Scan and spend keys
Your reusable code encodes two public keys. The scan key finds payments; the spend key authorizes moving them. Neither reveals a transaction history.
BIP-352
Live derivation
The reusable code below never changes. Watch a distinct Bitcoin output resolve for each payment, with no address published on-chain twice.
sp1qqgste7k9…juexzkBIP-352The mechanism
BIP-352 uses elliptic-curve Diffie–Hellman between the sender's inputs and your published scan and spend keys. The math happens off-chain; only ordinary-looking taproot outputs land on the ledger.
Your reusable code encodes two public keys. The scan key finds payments; the spend key authorizes moving them. Neither reveals a transaction history.
The sender combines their transaction inputs with your scan key to compute a shared secret, then derives a fresh output public key. Two payments never collide.
Your wallet recomputes the same secret from chain data and its scan key, recognising outputs meant for you—without a server learning which ones matched.
Detected outputs are standard taproot outputs. Observers see normal Bitcoin activity, not a labelled reusable address.
Receive
Your Silent Payment code can be presented repeatedly. Compatible senders create distinct outputs, reducing the address-reuse trail of conventional requests.

Send
ColdHarbor validates a BIP-352 destination, resolves the payment output, shows amount and fees, then asks for local approval.

Address formats
Product boundary
Bitcoin can be sent and received through BIP-352. Monero and other privacy assets are separate asset systems and are never labeled as Silent Payments.