Sparrow adds Silent Payment receiving

Sparrow Wallet has released version 2.5.0 with a concrete addition for private Bitcoin payments: the wallet can now receive Silent Payments, including when users rely on airgapped hardware wallet signers. Silent Payments are a reusable-address technique that avoids publishing a static address that is visibly reused. The sender derives a unique receiving output from the recipient’s public key and the transaction, reducing public linkage between incoming payments without requiring a central notification server.

The detail matters because Bitcoin privacy often advances at the wallet layer, not only through protocol proposals. If a user displays the same donation or payment address over and over, incoming payments can be clustered easily. Silent Payments aim to preserve the convenience of a reusable identifier while producing different on-chain outputs. Sparrow is adding the receiving side here, after send support had already appeared in earlier versions. The release notes also list a public Electrum server that supports Silent Payments and can be selected automatically when required.

This is still a wallet-level integration, not an ecosystem-wide switch. To receive a silent payment, software must scan the chain in a more specific way to find outputs that belong to the wallet. That can affect performance and explains why compatible servers matter. Support for airgapped hardware signers is also important: it lets users keep spending keys separated from an internet-connected computer while still trying this receiving mode in more cautious setups. In real use, privacy features become more credible when they do not force people to abandon basic security practices.

The useful signal is restrained. Bitcoin is not gaining a new consensus rule here, but a wallet tool that makes a privacy proposal more practical. For developers, this creates more surface to test: server compatibility, wallet recovery, fees, QR codes, hardware devices and scanning behavior. For users, the promise is simpler: reuse a receiving point with fewer obvious public traces. As with most privacy improvements, the final effect will depend on coordinated adoption by wallets, services and user habits.