A new open-source tool is helping Bitcoin wallets find private payments without sending a recognizable receiving address to a lookup server. Developer Ali Sherief announced spscand on November 15, 2026, a watch-only scanner designed to work with an independent Silent Payments plugin for Electrum. It implements BIP352, a method of publishing one reusable payment code while receiving funds at different on-chain outputs.
The development fills a practical gap. In ordinary Bitcoin payments, repeatedly publishing the same address makes incoming transfers easy to group. Silent Payments let a sender mathematically derive a new destination from the recipient’s reusable sp1 address and the sender’s transaction inputs. The blockchain shows the resulting output, not the reusable code itself. The receiver must then identify which outputs belong to them, creating a scanning problem.
Archival tutorial by ForrestHODL, May 22, 2026, demonstrating Silent Payments with Sparrow and other wallets. Educational explanation of BIP352; not a test or demonstration of spscand. Watch on YouTube.
A scanner that can see coins but cannot spend them
According to the developer’s MIT-licensed repository, spscand holds a scan private key and a spend public key. Together, they let it recognize matching outputs without providing the private spending key. The companion Electrum plugin retains signing authority. A local JSON API can report balances, confirmed outputs, and chain reorganizations; a Bitcoin Core backend can also track unconfirmed payments in the mempool.
That separation matters for a computer left online all day. Compromising a scan-only server should not directly authorize coin transfers. However, stealing its scan key can disclose the recipient’s payment history, so the tool is not a privacy-free replacement for keeping sensitive material offline.
Three ways to search the blockchain
The scanner supports three data paths. A Bitcoin Core node can perform the scan locally. A BlindBit server can supply block data, while matching remains local. A third configuration combines BlindBit tweak information with BIP157/158 compact block filters obtained from Bitcoin peers, downloading full blocks mainly when filters match.
The developer’s benchmark on a single historical Bitcoin block reported about 135 KB downloaded using BlindBit versus 59 KB of tweaks and filters before any matching-block downloads. That is an approximately 56% reduction in initial data for the measured block, not a verified networkwide average. With many labeled addresses, false matches can erode the savings.
Lunaticoin’s May 27, 2026 discussion and signet demonstration of Silent Payments and scanner infrastructure. Archival context from a different wallet implementation, not spscand release footage. Watch on YouTube.
What privacy the software does not promise
The repository explicitly warns that spscand has not been professionally audited. A remote BlindBit server still sees network metadata such as a client’s IP address and scan start height, and could omit data to conceal a payment. Compact-filter peers may learn which blocks interest the scanner. Tor and multiple filter peers reduce some exposure but cannot eliminate dishonest-source or device-compromise risks.
The Electrum integration is also an independent third-party plugin, not functionality shipped by the Electrum maintainers. Its documented receiving setup currently targets standard single-signature desktop software wallets, excluding hardware, multisignature, and watch-only Electrum wallets. Readers should verify published releases and use small test amounts rather than treating a GitHub announcement as an audited security certification.
How privacy tools are spreading
Developers are attacking related privacy problems from different angles. BitcoinVersus.Tech has covered Bitcoin Core’s BIP352 building blocks, OpenSwap’s coin-swapping implementation, and Bull Bitcoin’s default payjoin workflow. Separately, Bitcoin Core’s Tor/I2P privacy patch illustrates the value of protecting network metadata as well as addresses.
The practical milestone is narrower than anonymous Bitcoin: a reusable receiving code now has another independently implemented scanning path. Wider adoption still depends on interoperable wallet support, rigorous testing, manageable scan costs, and clear operational guidance.
Sources and verification
Sherief’s November 15 developer announcement; spscand source, requirements and benchmarks; companion Electrum plugin; Bitcoin Optech Newsletter #432; BIP352 specification. Benchmarks are developer-reported, not independently replicated. Cover: original conceptual oil painting with previously approved secondary logo.
We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiative, please scan the QR code below.


Leave a Reply