Which server does your scanning?<\/strong> Silent Payments scanning needs an Electrum server that serves the silent-payments Two things worth knowing about that fallback as the app behaves today. Your node setting is not<\/strong> changed \u2014 the rest of the wallet keeps using your selected node.<\/p>\n\n\n\n So if you run your own node specifically for privacy, confirm it is a tweak-capable https:\/\/docs.cakewallet.com\/features\/privacy-and-security\/silent-payments<\/a><\/p>\n\n\n Say goodbye to “send me a new address.” A Silent Payment address is a single Bitcoin address \u2014 starting with A normal Bitcoin address is public the moment you share it: anyone who sees it can look up every payment it ever receives. The usual fix is handing out a fresh address for every payment \u2014 fine for one-off transfers, painful for donations, tips, or anyone who pays you repeatedly.<\/p>\n\n\n\n Silent Payments remove the tradeoff. The sender’s wallet uses your Cake Wallet was the first wallet with with full Silent Payments support<\/strong> \u2014 both sending and receiving.<\/p>\n\n\n\n Nothing to learn: paste an Tap Silent Payments receive address<\/p>\n\n\n\n Because payments to you are hidden on-chain, your wallet has to scan for them. Open Silent Payments settings<\/p>\n\n\n\ntweaks<\/code> index \u2014 in practice an electrs<\/code> build with tweak support. When a scan starts, Cake Wallet asks the node you currently have selected whether it can serve that data:<\/p>\n\n\n\n\n
electrs.cakewallet.com:50001<\/code>, instead.<\/li>\n<\/ul>\n\n\n\nelectrs<\/code> build and that your wallet is connected to it. Otherwise your Silent Payments scanni<\/p>\n<\/blockquote>\n\n\n\nSilent Payments<\/h1>\n\n\n\n
sp1<\/code> \u2014 that you can post anywhere: your website, social media bio, a donation page. Every payment sent to it lands at a fresh, unique address on-chain that only you can find and spend.<\/p>\n\n\n\nWhy you’d want this<\/a><\/h2>\n\n\n\n
sp1<\/code> address to derive<\/em> a unique one-time address that only you can detect. On-chain, the payment looks like any ordinary Taproot transaction \u2014 observers can’t even tell a Silent Payment happened, and unlike older reusable-address schemes (BIP47), there’s no extra “notification” transaction leaking metadata.<\/p>\n\n\n\nSending to a Silent Payment address<\/a><\/h2>\n\n\n\n
sp1...<\/code> address into the Send screen<\/a> like any other address. Your wallet handles the rest, and the recipient’s privacy comes free.<\/p>\n\n\n\nReceiving with Silent Payments<\/a><\/h2>\n\n\n\n
Find your sp1 address<\/a><\/h3>\n\n\n\n
Receive<\/code>, tap the address type under the QR code, and choose Silent Payments<\/code>. This address never changes \u2014 that’s the point. Post it anywhere.<\/p>\n\n\n\n![\"\"](\"https:\/\/docs.cakewallet.com\/~gitbook\/image?url=https%3A%2F%2Fraw.githubusercontent.com%2Fcake-tech%2Fdocs-assets%2Fmain%2Fv6.3.1%2Ffund_btc-sp_carrot-cake_receive_hl.png&width=768&dpr=3&quality=100&sign=39e1d7682ed918267d7e9c36269c31a9&sv=3\")
<\/figure>\n\n\n\nTurn on scanning<\/a><\/h3>\n\n\n\n
Settings<\/code> \u2192 Privacy<\/code> \u2192 Silent Payments<\/code> and enable Set Silent Payments always scanning<\/code>.<\/p>\n\n\n\n![\"\"](\"https:\/\/docs.cakewallet.com\/~gitbook\/image?url=https%3A%2F%2Fraw.githubusercontent.com%2Fcake-tech%2Fdocs-assets%2Fmain%2Fv6.3.1%2Fsilentpayments_scan_01_menu_hl.png&width=768&dpr=3&quality=100&sign=1f8c155e5ec31e2885b5341558ed4d7f&sv=3\")
<\/figure>\n\n\n\nLet it catch up<\/a><\/h3>\n\n\n\n
![\"\"](\"https:\/\/docs.cakewallet.com\/~gitbook\/image?url=https%3A%2F%2Fraw.githubusercontent.com%2Fcake-tech%2Fdocs-assets%2Fmain%2Fv6.3.1%2Fsilentpayments_scan_03_scanning-page.png&width=768&dpr=3&quality=100&sign=db61c6f8db542d4c8d09e532eeb3d693&sv=3\")
<\/figure>\n\n\n\n