Bitcoin’s newest mobile privacy feature can make your incoming money completely invisible
Silent Payments promise a reusable Bitcoin deal with with out exposing an apparent chain of funds to that deal with. A sender makes use of the recipient’s public info to derive a contemporary Taproot vacation spot, and the recipient’s pockets later scans eligible transactions to search out the output that belongs to it.
That receiving scan has been the tough half for telephones. A September measurement project reviews that BlindBit Oracle v2’s full scanning feed would require about 8 MB per day close to the higher finish of its dataset. The quantity suggests mobile bandwidth could also be manageable. It additionally highlights a separate danger: a light-weight pockets is dependent upon an indexer to ship full scanning knowledge, and an omitted entry can go away an actual cost undiscovered.
The rising tradeoff is due to this fact much less about uncooked obtain measurement than about what a pockets can confirm. The knowledge can match via a telephone connection. The pockets nonetheless wants a dependable method to know that each related piece arrived.
What the measurements set up
The challenge processed each Bitcoin block from peak 709,656 via 965,089, an inclusive span of 255,434 blocks from shortly after Taproot activation to September 2026. Its per-block CSV accommodates the identical variety of rows, with these actual peak boundaries.
Across that historical past, the entire BlindBit v2 scanning payload totaled 15,079,946,729 bytes. The challenge reviews that as 15.08 GB, averaging 59.0 KB per block. That full-history complete describes a restore throughout the measured vary.
The day by day quantity solutions a special query. Using the typical from heights 900,000 via 965,089 and an assumed 144 blocks per day, the challenge calculates about 8.0 MB for a pockets following the chain close to the dataset’s higher finish. It doesn’t describe the preliminary historic obtain.
The repository was produced by one unbiased operator. Its knowledge and scripts are public, and the combination row depend and payload totals can be checked from the CSV, however a second operator has but to publish a full rerun. The outcome speaks to bandwidth quantity; it doesn’t measure telephone battery use, processor load, storage conduct or supply latency.
The challenge additionally estimates a lighter filter route. About 0.94 GB of modeled Taproot-only filters plus roughly 6.2 GB of uncooked tweaks yields a 7.14 GB subtotal. The 15.08 GB full feed is about 2.1 instances that subtotal. The filter route then provides a full-block obtain for each match, together with false positives, so its realized site visitors varies by pockets exercise and match fee.
| Route | Comparison foundation | Additional site visitors |
|---|---|---|
| BlindBit v2 full feed | 15.08 GB throughout the measured historical past; about 8 MB per day within the recent-era estimate | No matched-block fetch throughout scanning |
| Modeled Taproot filter plus tweaks | About 7.14 GB throughout the measured historical past | Full block for each filter match |
The filter element is a mannequin constructed from actual per-block merchandise counts. Its sizing formulation was checked in opposition to 21 actual filter encodings and landed inside about 0.5%, in line with the challenge. A Taproot-only Silent Payments filter has but to be deployed.

How an indexer can make a cost invisible
BIP-352 defines the reusable deal with and the receiver’s scan. For every eligible transaction, the pockets combines its non-public scan key with public knowledge derived from the transaction’s inputs. It makes use of the outcome to generate candidate output keys and checks whether or not one seems within the transaction.
A full node can derive that knowledge from the blockchain. A lightweight pockets wants one other supply. The work-in-progress index-server specification describes server-assisted fashions that transfer completely different quantities of labor and data away from the gadget.
One mannequin retains matching on the telephone and asks a server for public tweaks. That can keep away from sharing the non-public scan key, however the server’s response nonetheless must be full. If the one tweak wanted for an incoming cost is absent, the pockets generates no matching vacation spot and reveals no receipt.
A Cake Wallet issue opened in July 2025 analyzed how the miss may persist. The reporter wrote {that a} consumer might save a later native scan peak after receiving incomplete knowledge. If the pockets then treats the sooner vary as completed, connecting to a special server wouldn’t robotically make it ask for the lacking block once more. The problem web page doesn’t present a maintainer affirmation of that structure evaluation, and it doesn’t doc intentional withholding by any server.
The output itself stays legitimate on Bitcoin. The recipient’s keys nonetheless management it. Discovery can be recovered by rescanning from an earlier peak in opposition to a whole, sincere supply or through the use of a full-node-backed scan. The user-facing hazard is silence: the pockets might present a whole sync with out signaling that historic knowledge ought to be revisited.
The challenge proposes chained commitments to every block’s canonical tweak set. Two servers that publish commitments can be in contrast, and an externally anchored checkpoint can expose later rewriting or equivocation. This creates an audit path. A primary consumer counting on a single response can nonetheless obtain an incomplete set earlier than an unbiased comparability reveals the discrepancy.
The belief selection is already reaching wallets
The requirements image has two layers. BIP-352’s standing is Complete, which covers the core Silent Payments protocol. Its light-client appendix nonetheless describes privacy-preserving telephone assist as open analysis. The new converged light-client document labels itself pre-draft v0.1, with adoption and interoperability work nonetheless forward.
Wallet builders have in the meantime shipped completely different server relationships. Sparrow Wallet 2.5.0, launched in May 2026, added Silent Payments receiving and automated number of a public Frigate server. Frigate describes its design as a Remote Scanner, which performs the matching on server infrastructure with ephemeral consumer scan keys.
The WIP index specification maps Cake Esplora to Cake Wallet and lists Dana Wallet, BDK with Kyoto, and BlindBit Desktop as purchasers round BlindBit Oracle. Dana and Silentium describe their very own mobile tasks as experimental. Those implementation sources don’t declare adoption of the September pre-draft.
For a consumer, these designs outline greater than synchronization velocity. A distant scanner can be taught which transactions belong to a pockets. A tweak server can maintain the non-public matching work on the telephone whereas leaving the pockets depending on a whole feed. A private full-node-backed service shifts each computation and belief onto infrastructure the consumer controls.
The measurements make the bandwidth a part of that selection look much less forbidding. Wider adoption nonetheless is dependent upon a second property: a pockets should be capable of detect incomplete historical past earlier than an incoming cost disappears from its view. Silent Payments can cover deal with reuse on-chain, however telephone wallets want safeguards that maintain privacy from turning into a brand new type of server belief.
The submit Bitcoin’s newest mobile privacy feature can make your incoming money completely invisible appeared first on CryptoSlate.
