A Taproot asset proposal enters the record
On April 5, 2022, Lightning Labs published Taro, a draft protocol intended to let issuers create assets on Bitcoin and eventually move them through the Lightning Network. The company simultaneously announced a $70 million Series B financing round to fund Lightning infrastructure and development of the proposal.
The distinction between proposal and product was central. Lightning Labs released draft Bitcoin Improvement Proposal material for developer review; it did not announce a live stablecoin, a production deployment or adoption by Bitcoin Core. Taro was infrastructure through which a separate issuer might create an asset. The issuer—not the protocol—would still determine how a dollar-linked token was backed, redeemed and governed.
That scope made the announcement consequential. Stablecoins had largely developed on other smart-contract networks, while Bitcoin’s Lightning Network primarily routed bitcoin. Taro proposed joining those two domains: Bitcoin would anchor asset commitments, while Lightning could provide off-chain payment paths. If implementations and liquidity followed, wallets could offer both BTC and fiat-denominated balances without requiring every routing node to support each asset.
How the draft was designed
The published specification described Taro as an application-layer, Taproot-native asset overlay. Its core design placed a nested asset tree inside Bitcoin’s Taproot structure. Transfers would carry proofs showing an asset’s history, while the Bitcoin chain would provide the ordering and double-spend protection for the underlying transaction outputs.
This did not mean Bitcoin’s base layer would understand or validate the asset’s business promises. Full nodes would see ordinary Taproot transactions; Taro-aware software would interpret the additional commitments and verify the asset-specific rules and proofs. That separation was meant to avoid putting each token’s state directly into Bitcoin’s consensus rules.
For Lightning payments, the proposal envisioned assets entering and leaving through asset-aware edges while bitcoin liquidity could connect portions of a route. Lightning Labs presented that as a way to reuse an existing payment network instead of building an isolated channel network for every issued asset. The design still depended on suitable wallet software, counterparties, exchange rates and liquidity at the route’s edges.
Funding met an unfinished roadmap
Contemporaneous reporting identified Valor Equity Partners as the lead investor in the $70 million Series B, with Baillie Gifford among the participants. The financing supplied institutional backing for the developer, but it was not evidence that Taro worked at production scale or that users wanted assets issued through it.
Lightning Labs’ own April 5 roadmap placed the work in three stages: circulate the draft protocol, build tooling for on-chain issuance and transfer, and then add Lightning functionality for Taro asset channels. That sequence is the clearest limitation on the event-day claim. On April 5, the specifications and financing were verifiable; throughput, fees, adoption and stablecoin safety were not.
The announcement also arrived after Bitcoin’s Taproot soft fork activated in November 2021. Taro was therefore an early attempt to turn Taproot’s more flexible commitment structure into an end-user asset system. It did not require the market to accept a new base-layer asset, but it did ask developers and users to adopt new software and proof-handling conventions above Bitcoin.
What could not yet be known
No event-day record established a market price effect attributable to Taro, so this reconstruction makes no such claim. It also reports no transaction count, capacity increase or fee reduction: none had been demonstrated by a production Taro network on April 5, 2022.
Later context confirms the boundary. On September 28, 2022, Lightning Labs released an alpha daemon for testnet use and said Lightning integration remained future work. That later milestone helps interpret the April announcement but does not change its original status: Taro was a funded, open technical proposal with a broad payments ambition, not a finished stablecoin rail.
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.