Nunchuk's BIP352 launch is the clearest signal yet that silent payments are crossing from cryptographic curiosity to production self-custody infrastructure. The advanced multisig wallet shipped support for sending to Silent Payment addresses in its latest release — confirmed in its iOS App Store changelog and on Stacker News approximately 16 hours before this brief was compiled — making it the first production-grade multisig platform to implement the standard. The timing is not coincidental: BIP392, authored by Craig Raw of Sparrow Wallet and merged via BIPs pull request #2047 in March 2026, has just formalised the sp() output script descriptor that gives silent payment outputs a standardised, wallet-portable representation. Two converging standards — BIP352 for the protocol itself and BIP392 for descriptor interoperability — have simultaneously reached maturity, and Nunchuk is the first major platform to act on both.
The arena for on-chain Bitcoin privacy tooling is structurally larger than the niche it currently occupies. Address reuse remains the single most common surveillance vector against self-custody users: when multiple payments land at the same scriptPubKey, chain-analysis firms can cluster UTXOs with high confidence and attribute transaction history to a single entity. The established mitigations — BIP47 reusable payment codes, CoinJoin coordination via Wasabi Wallet's WabiSabi protocol or JoinMarket, and manually requesting fresh addresses — all impose friction, interactivity costs, or trust assumptions. BIP352 silent payments eliminate interactivity entirely: the receiver publishes one static address offchain, and the sender's wallet derives a unique on-chain output for every payment using the sender's input public keys and the receiver's scan and spend keys. The competitive field entering 2026 consists of Dana Wallet, Cake Wallet, and now Nunchuk on the sending side, with BitBox02 having previously added support at the hardware signing layer. Sparrow Wallet, the dominant desktop self-custody platform, has not yet shipped sp() descriptor integration despite its creator authoring BIP392 — a gap that represents the most consequential near-term adoption milestone in the ecosystem.
The development itself is granular and worth unpacking precisely. Nunchuk's latest release changelog — confirmed on the iOS App Store for the Nunchuk Bitcoin Wallet application — lists 'Support sending to Silent Payment addresses' alongside a separate security enhancement: a two-hour delay for seed phrase viewing. The silent payments implementation covers the send path, meaning Nunchuk users can now pay any BIP352-compatible address without address reuse, but the receive path — which requires the wallet to continuously scan incoming transactions against the user's scan key — is not yet confirmed as part of this release. BIP352 itself was merged into the Bitcoin Improvement Proposals repository in 2024 and was subsequently updated via BIPs #2106 in 2026 to limit per-group recipients, tightening the specification. BIP392, the parallel descriptor standard, defines the sp() descriptor format: key expressions labelled 'spscan' and 'spspend' carry version and key material, while wallet birthday and additional labels are expressed as optional arguments within the descriptor string — a structure compatible with existing descriptor-based backup and recovery infrastructure. (For technical readers: sp() descriptors produce P2TR outputs, meaning silent payment outputs are indistinguishable from ordinary Taproot outputs at the blockchain level, which provides an additional anonymity-set benefit.)
The convergence of conditions making this moment possible rests on three structural forces. First, BIP352 spent approximately 18 months moving from draft to specification maturity after its 2024 merge, during which BIP375 — covering silent payments via PSBTs — was added, and the per-group recipient limit was tightened. That specification stabilisation is the prerequisite for wallet teams to commit engineering resources without risking obsolescence. Second, Bitcoin's fee environment as of late March 2026 sits at 1 sat/vB across all confirmation tiers, according to live Mempool.space data, reducing the on-chain cost burden of the additional outputs and scanning infrastructure that silent payments require. High-fee environments punish privacy features that increase transaction weight; the current ultra-low fee floor removes that disincentive entirely. Third, the Bitcoin network's hashrate of 1,041.7 EH/s signals a deeply secured base layer — operators building privacy tooling on top are doing so on infrastructure that shows no signs of systemic stress. The closest structural precedent is the BIP84 native SegWit adoption cycle of 2019–2021, where a standardised descriptor format (wpkh()) catalysed rapid multi-wallet interoperability once two or three major wallets shipped it simultaneously.
The competitive implications redistribute value within the Bitcoin privacy stack in a specific and directional way. Nunchuk's launch, combined with BIP392's formalisation, shifts the baseline privacy expectation upward for self-custody users — and that shift directly pressures CoinJoin coordinators. Wasabi Wallet's WabiSabi coordination service and JoinMarket's maker-taker model both derive value from the gap between what standard wallets offer (address reuse by default) and what privacy-conscious users require. If silent payments become a default send-path feature across the top five self-custody wallets, that gap narrows materially. The value chain after adoption looks as follows: hardware signers (BitBox02 already onboard, Ledger and Trezor not yet confirmed) capture send-side key material handling; descriptor-standard wallets (Sparrow, Nunchuk) capture the user-facing interface layer; and Bitcoin Core's scanning infrastructure — currently absent from the bitcoin/bitcoin codebase — becomes the critical missing link for node operators who want to self-verify receipt without delegating to a third-party indexer. The strategic miscalculation visible in the current data is Sparrow's: Craig Raw authored BIP392 but has not yet shipped sp() descriptor support in Sparrow itself, ceding first-mover positioning in the desktop wallet segment to a multisig-first competitor.
Our read: silent payments are on a BIP84-style adoption curve, and the 2026 window is the inflection point. The testable hypothesis is this — if Sparrow Wallet ships native sp() descriptor import/export within the next two quarters, and if Bitcoin Core receives a merged pull request targeting silent payment scanning, the three-wallet ecosystem of today will expand to cover a majority of active self-custody installations within 18 months. The confirming signals are specific: Sparrow shipping sp(), a bitcoin/bitcoin PR for scanning infrastructure attracting significant review activity, and cross-wallet interoperability proofs appearing on the Bitcoin-Dev mailing list. The disconfirming signal would be a sustained high-fee environment (above 20 sat/vB for more than 60 days) that makes the scanning overhead economically punishing for mobile wallets, or a critical vulnerability discovered in BIP352 implementations that forces a specification revision and resets the adoption clock. The structural logic favours confirmation: the interactivity problem that silent payments solve is real, the specification is stable, and the fee environment is permissive.
Decision-makers tracking this space should monitor four specific indicators over the next two to four quarters. First, Nunchuk's receive-path release: the current launch covers sending only; full scanning support would confirm that Nunchuk intends to own the complete silent payments user experience rather than treat this as a partial feature. Second, Sparrow Wallet's sp() descriptor integration: Craig Raw's authorship of BIP392 creates an implicit commitment that the market will price in — any delay beyond Q2 2026 signals internal resource constraints or a strategic pivot worth investigating. Third, a pull request in the bitcoin/bitcoin repository targeting native silent payment scanning infrastructure: the absence of this feature in Bitcoin Core is the single largest barrier to node-operator adoption, and its appearance would represent a definitive catalyst for the next adoption phase. Fourth, BIP392's status transition from Draft to Proposed: this requires confirmed implementation in at least two clients and one relay — with Nunchuk and Sparrow both engaged, the threshold may be met within this calendar year, and the formal status change would trigger coverage from wallet teams that track BIPs systematically as a product roadmap input.