Lightspark made the beta version of Spark available on April 29, 2025, giving developers access to software kits for building self-custodial Bitcoin wallets and issuing Bitcoin-native assets, including stablecoins. The release moved Spark beyond the alpha-stage protocol introduction Lightspark had published on October 25, 2024.
The company described Spark as a trust-minimized payment and settlement protocol connected to Bitcoin and interoperable with the Lightning Network. Lightspark said transfers could occur instantly and at near-zero cost without wrapped assets or conventional cross-chain bridges. Those were contemporaneous company claims, not independently verified performance measurements.
Two development packages accompanied the beta: a wallet SDK for applications handling bitcoin and a separate issuer SDK for creating and managing assets. Lightspark explicitly warned that the beta was unfinished, that parts would break and that developers would encounter known and unknown limitations.
Why the beta mattered
Bitcoin’s base layer prioritizes decentralized settlement over high transaction throughput. Lightning can move bitcoin payments away from the base chain, but operating self-custodial Lightning wallets at large scale introduces channel, liquidity and online-availability challenges. Stablecoin activity, meanwhile, was concentrated on other blockchains rather than Bitcoin.
Spark attempted to address those constraints with a payment-focused layer in which ownership could change without recording every transfer directly in a new Bitcoin transaction. Its April 29 release therefore represented more than another wallet product: it was an attempt to make Bitcoin infrastructure support both rapid bitcoin transfers and issued assets through one developer stack.
Contemporaneous Axios reporting independently confirmed the launch and its stablecoin emphasis. The report described Spark as relying on Bitcoin for security guarantees while enabling applications and token issuance. Lightspark chief executive David Marcus presented the larger ambition as making Bitcoin a settlement medium for many stablecoins. That ambition did not establish that issuers, wallets or users had adopted the system on April 29.
The distinction between protocol availability and demonstrated adoption is essential. An accessible SDK can reduce integration work, but it does not prove transaction capacity, fee behavior under load, decentralization, resistance to operator failure or the legal status of assets issued through it. Lightspark published no independently audited throughput study, production-volume dataset or comprehensive security assessment with the launch announcement.
What was verified on April 29
The central verified event is narrow: Lightspark released Spark as a beta and offered wallet and asset-issuer tooling on April 29, 2025. The company’s announcement, its earlier protocol description and the public code repository substantiate that Spark was presented as open-source Bitcoin infrastructure rather than merely a future product proposal.
Descriptions such as “instant,” “near-zero cost,” “self-custodial” and “native” remain attributable product claims. They depend on Spark’s architecture, operator assumptions, Bitcoin transaction conditions and the precise path used to enter or leave the system. No event-day evidence established that Spark had reached mature production reliability.
Later context
On July 28, 2025, Lightspark announced that unilateral exit had become live, allowing a user to recover funds to Bitcoin through a pre-signed transaction after a timelock if an operator became unavailable or attempted censorship. That later milestone clarifies an important April 29 limitation: the beta launch should not be retroactively described as already containing every withdrawal safeguard delivered afterward.
The April 29 release was consequently a meaningful protocol checkpoint, not proof that Spark had solved Bitcoin scaling or stablecoin settlement. The next questions were whether independent reviewers would validate its security model, whether wallets and issuers would integrate it, and whether observed production costs and reliability would match the launch claims.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.