Bitcoin app developers can now send funds to silent payment addresses through the Spark-based Breez SDK, reducing the need to build a separate Bitcoin-payment interface for every destination type. Version 0.28.0 of the SDK appeared in early November 2026, with subsequent maintenance releases in the 0.28 branch. Bitcoin Optech’s November 20 roundup highlighted the new BIP352 sending support. The addition is a wallet-software feature, not a change to Bitcoin consensus.
Silent payments address a longstanding weakness of on-chain transfers: publishing the same conventional receiving address repeatedly lets observers group deposits and inspect the resulting balance history. Under BIP352, a recipient can publish a reusable address while each sender derives a different on-chain output using cryptographic data. The recipient later scans the blockchain to identify their payments. Payments remain public transactions; the mechanism reduces address-linking rather than making Bitcoin invisible.
Video: Roy Sheinfeld of Breez moderates a Bitcoin 2026 discussion about Spark, Ark and Lightning interoperability. The panel predates the SDK update and provides architecture background. Watch directly on YouTube.
One wallet interface, several payment paths
Breez’s current sending documentation lists Lightning invoices, ordinary Bitcoin addresses, silent-payment addresses, Spark addresses and Spark invoices as recognized payment requests. Developers first prepare a payment, review the returned fees and then authorize sending. Providing several input formats through one interface can simplify apps that pay both Lightning merchants and people receiving Bitcoin on-chain.
Spark is a Bitcoin-native payment layer built around shared signing with operators, allowing quick transfers without every operation becoming an immediate Bitcoin mainnet transaction. A Spark wallet is not identical to an ordinary self-hosted Lightning node. Its trust, availability and exit assumptions need separate scrutiny. Breez describes unilateral Bitcoin exits, yet exit costs and practical recovery conditions still matter, particularly for small balances.
The earlier Wavelength alpha illustrates a different approach to consumer payment infrastructure. Our OpenSwap coverage describes coin swaps, which target a separate transaction-linkability problem. No one technique independently solves every Bitcoin privacy concern.
Silent sending is not silent receiving
BIP352 payees require software capable of locating incoming outputs. Support for sending a silent payment does not mean that every wallet or SDK automatically implements receiving and scanning. The distinction matters for developers building a two-way application or migrating an existing address book. A recipient who lacks scanning support may not recognize an arriving output even though the chain confirms it.
Video: April 2026 explainer of BIP352 silent-payment addresses, one-time outputs and privacy trade-offs. The recording is background education, not a Breez 0.28 product demonstration. Watch directly on YouTube.
Stablecoins and bridging add another layer
Breez also documents optional token conversion and cross-chain routes for USDC and USDT. Those workflows depend on supported providers, fees, destination networks, limits and route availability; they are not inherent Bitcoin consensus features. A route offering an attractive quote can carry counterparty or bridge risks absent from a simple on-chain transfer. Applications need to display the actual asset delivered, network fees and final settlement status rather than assume every request follows the same path.
Breez’s open-source SDK repository supports integrations across several programming languages. Public documentation describes API-key requirements and separate development configuration. Teams should pin dependency versions, run send-and-recovery tests in controlled environments, and verify each payment method against current SDK behavior before accepting user balances.
Recent BitcoinVersus reporting on a watch-only silent-payment scanner shows why receiver tooling is progressing alongside sender support. The Bull Bitcoin Payjoin integration addresses another privacy surface through collaboratively constructed transactions. Together, those projects point toward wallet features that give users more choices without requiring a Bitcoin rule change.
The confirmed development is support for sending to reusable BIP352 destinations in a modern payment SDK. Whether the combination is secure and useful at scale depends on audited implementations, transparent fees and realistic recovery procedures, not promotional claims about frictionless or fully private payments.

Leave a Reply