Breez pushed Glow to production at 17:38 UTC on August 6, 2026, publishing the repository under an open-source license that lets any team clone the codebase, swap the branding, and deploy a Lightning-enabled wallet without writing the plumbing from scratch. The release landed on a day when bitcoin idled at $64,430, volume thinning to $20.1 billion across spot markets as traders digested the latest ETF flow data.
What separates Glow from prior SDK drops is the dual intent: the same binary serves retail users making Lightning payments and developers dissecting how those payments are constructed. Passkey authentication, Lightning address resolution, and stablecoin send/receive flows all expose their API calls in the open — a reference implementation rather than documentation. A social-app builder can copy the Lightning-address module, a marketplace can lift the stablecoin transfer logic, and neither touches user funds.
The custody model is the regulatory lever. Keys never hit the app server, Breez infrastructure, or Turnkey's enclaves. The backend holds a policy credential defining permitted actions; the user holds the signing authority. That architecture, finalized in the Turnkey integration announced last month, removes the money-transmitter classification that has blocked consumer platforms from embedding Bitcoin for years.
| Feature | Glow Implementation | Custody Status | Regulatory Footprint |
|---|---|---|---|
| --- | --- | --- | --- |
| Passkey login | WebAuthn + Turnkey enclaves | Non-custodial | Minimal |
|---|---|---|---|
| Lightning addresses | LNURL-pay + BOLT12 | Non-custodial | Minimal |
| Stablecoin transfers | Taproot Assets / RGB | Non-custodial | Minimal |
|---|---|---|---|
| Wallet fork/rebrand | Full source access | Developer choice | Developer choice |
The timing aligns with a broader infrastructure push. Lightning Network capacity held near 5,400 BTC through July, while stablecoin supply on Bitcoin layers crossed $400 million in June — both metrics suggesting the plumbing is finally reaching the throughput consumer apps require. Glow does not move those numbers directly, but it lowers the integration cost for the next wave of apps that might.
Bitcoin Magazine's Mathew Di Salvo reported the release under the byline "Breez Drops New Bitcoin App Which Doubles As Wallet and Developer Toolkit," noting the SDK's non-custodial design as the key unlock for platforms that have watched from the sidelines. The article published at 12:38 Eastern, minutes after the repository went public.
Why the Turnkey deal precedes the wallet
Breez's July agreement with Turnkey solved a structural problem: how to let a centralized app server coordinate Bitcoin transactions without ever holding keys. Turnkey's secure enclaves generate and store private keys; the app server receives a signed policy token authorizing specific actions — pay invoice, open channel, swap asset — but cannot extract the key material. Glow is the first consumer-facing product built on that stack.
For a fintech with 10 million users, the difference is existential. Prior to this architecture, adding Lightning meant either custodial risk (the company holds keys) or regulatory ambiguity (the company might be deemed a money transmitter). The Turnkey model pushes key authority to the user device; the company's backend becomes a policy engine, not a vault.
What developers actually get
The repository includes a React Native codebase with TypeScript SDK bindings for every wallet operation. A developer building a creator-tipping feature can import the `sendPayment` module, inspect the fee-estimation logic, and replace the UI layer without rewriting the Lightning negotiation. The stablecoin module abstracts Taproot Assets and RGB behind a single `transferAsset` call — the first time both protocols share a unified interface in a production wallet.
Breez claims zero runtime dependencies on its own infrastructure after the initial SDK fetch. The wallet connects directly to Lightning nodes via LDK, to Turnkey for signing, and to Bitcoin Core for on-chain verification. That independence matters for teams that cannot accept a third-party uptime dependency in their critical path.
Watchpoints for the next 30 days
The first fork to ship a rebranded Glow will signal whether the "reference implementation" thesis holds. Watch the SDK's GitHub stars and fork count — a climb past 500 forks in month one would indicate builder traction. Monitor Lightning address adoption metrics on Amboss and 1ML; a sustained uptick in LNURL-pay registrations would suggest Glow-powered apps are reaching users. Finally, track Turnkey's enclave attestation logs (published weekly) for any anomaly in signing latency or failure rates — the trust anchor for the entire non-custodial claim.