A proposal signed by Jack Dorsey, Alex Morcos and Martin White announced the Bitcoin Legal Defense Fund on January 12, 2022, offering coordinated legal support to developers facing lawsuits over work in the Bitcoin ecosystem. The announcement, posted to the bitcoin-dev mailing list at 00:13:45 UTC, said the nonprofit would help find and retain counsel, shape litigation strategy and pay legal bills.
The intervention mattered because open-source maintainers could be named personally in litigation even though Bitcoin has no company, executive team or central operator responsible for the network. The fund framed that mismatch as a practical threat to development: independent contributors could abandon work or settle claims because defending a case was too expensive, regardless of the underlying merits.
A defense layer outside the protocol
The January 12 plan was deliberately modest. Assistance would be free and voluntary for developers, but not automatic. A board consisting of Dorsey, Morcos and White would decide which lawsuits and defendants the fund would support. The organization expected to begin with volunteer and part-time lawyers, and it said it was not then seeking additional money. Fundraising could follow if the board determined that litigation or staffing required it.
That structure did not alter Bitcoin's software, consensus rules or governance. It instead added an institutional resource around a project whose technical work is distributed among companies, grant recipients and unaffiliated contributors. In Coinburn's interpretation, the announcement treated legal defense as shared infrastructure: not a protocol upgrade, but a way to reduce the personal cost of participating in protocol maintenance.
The distinction was important. A defense fund could finance counsel and coordinate strategy, but it could not decide a case, immunize developers from suit or establish that any claim was unfounded. The board also retained discretion over support, leaving unanswered on January 12 how eligibility, conflicts and funding priorities would work in practice.
Tulip Trading became the first test
The fund identified the Tulip Trading litigation as its first activity. It said it would take over coordination of the existing defense for certain developers and fund outside counsel. The contemporaneous announcement described the action as alleging breach of fiduciary duty.
Tulip Trading's April 29, 2021 particulars of claim went further. The company alleged that developers associated with several Bitcoin-derived networks owed fiduciary and tortious duties after Tulip said access to digital assets had been lost. Among the remedies sought were orders requiring software steps that, in Tulip's theory, would enable it to regain control of the assets, or compensation if those steps were not taken. Those were allegations and requested remedies, not findings by a court as of January 12, 2022.
The case therefore raised a question extending beyond one claimant: whether people maintaining open-source network software could owe duties to an individual user that required them to change that software. It also exposed the difference between repository access and network control. Maintainers can review and merge code in a software repository, but users, miners and businesses independently choose which software and rules to run. The January 12 record did not resolve how a court would treat that distinction.
What was known on January 12
The verified development was the fund's announcement and stated operating plan, not a completed financing round or a court victory. No budget, endowment, roster of lawyers or list of future cases was disclosed. The announcement also made no claim that every Bitcoin developer would receive representation.
Contemporaneous coverage confirmed the mailing-list message and its focus on Tulip Trading. The durable significance was institutional: prominent Bitcoin backers were creating a mechanism to absorb legal costs that previously fell heavily on individual contributors.
Later context
A March 25, 2022 High Court judgment later described Tulip's claims and the developers' jurisdiction challenge in detail. That later record helps verify the litigation context, but it was not available on January 12 and does not change the narrower event-day fact: the fund had announced an intended defense role, while the underlying dispute remained unresolved.
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.