Open-source Bitcoin Funding is financial support for developers, code reviewers, researchers, maintainers, educators and public infrastructure around Bitcoin. It helps sustain work that a conventional product business model may not pay for. Funding terms, acceptance of a change into a project and adoption of network rules are distinct questions.
Open-source does not mean development and maintenance cost nothing. Bitcoin Core lists code, testing, documentation, translations and user interfaces among needed contributions; its contribution guidelines describe thorough review and testing as a bottleneck. Funding can therefore pay for work whose result is neither a new feature nor a separately sold product. [Bitcoin Core — How Can I Contribute?] [Bitcoin Core — Contributing]
Donations can fund an organization or individual, a grant defines supported work, and employment has its own obligations. Brink separates grants for experienced developers from its paid fellowship program with mentoring. For grants it expects independent work and public progress reports. These models are not interchangeable; specific terms determine duration, payments, expectations and renewal. [Brink — Programs]
OpenSats evaluates mission alignment, clarity of goals, feasibility, applicant ability and intended impact. It describes expert review, due diligence, majority board approval and an agreement covering scope, milestones and reporting. Support is therefore not an automatic reward for an open repository. One fund's selection rules should not be presented as rules for the entire ecosystem. [OpenSats — Grant Selection]
Spiral publishes Square Crypto's historical announcement dated 2019-09-14 of a 100000 USD grant to the BTCPay Foundation supporting BTCPay Server. The condition was free and open-source work improving Bitcoin; this is not a universal current rate. Human Rights Foundation also supports education, translation and usability alongside development within its mission. These examples show the breadth of work, not a complete list of funders. [Spiral — Grant #1: BTCPay Server] [Human Rights Foundation — Bitcoin Development Fund]
Bitcoin Core requires public change proposals, review and appropriate tests; maintainers decide on repository inclusion. This process is distinct from changing consensus across the network. Users choose the software they run. A funder can influence the focus of paid work, but a grant alone grants no right to force others to adopt a change. [Bitcoin Core — Contributing] [Bitcoin.org — Network control FAQ]
When evaluating funding, examine donors, duration, obligations, termination options and potential conflicts of interest. OpenSats publishes financial and governance documents and links to conflict-of-interest policies; disclosure alone does not guarantee neutrality. The number of companies paying developers is not a measure of protocol control. This is a framework for checking specific relationships, not an accusation against a particular fund. [OpenSats — Transparency] [Bitcoin.org — Network control FAQ]
A project's license, repository, reviews, tests, documentation and recipient reports can be checked. Bitcoin Core generally accepts contributions under the MIT license with stated exceptions. Sensitive vulnerabilities, however, are reported under project security rules and disclosed in a coordinated way; pressure for a public grant deliverable must not replace that process. Open code alone does not prove security or audit quality. [Bitcoin Core — Contributing] [Bitcoin Core — Security Advisories]
A budget should account for maintenance, review of others' changes, knowledge transfer and continuation after a grant ends. Brink explicitly includes testing, review and bug fixes among supported work. Commit counts and donation totals are therefore insufficient measures of results. Examine specific benefits, independent assessment and remaining needs; an announced grant is not a completed project. [Brink — Programs] [OpenSats — Grant Selection]
A change that is not accepted can still produce useful work
In a hypothetical example, a grant enables a reviewer to test a proposed wallet change. They find a bug, demonstrate it with a test, and the proposal returns to its author for correction before acceptance. The reviewer did not have to add a new feature, yet the work helped prevent a regression. The funder can assess documented work under the agreement, but paid time gives it no right to bypass project review.
For the clearest picture, read this entry together with Bitcoin Donations, Bitcoin education, Bitcoin Core, Bitcoin and Human Rights, Bitcoin. The reverse links also lead from Bitcoin Donations.
01Can a large donor decide to change Bitcoin's rules?+
Not through a donation alone. It can influence which work it funds, but code acceptance depends on the project's process and rule changes on adoption by network participants. These different levels must not be confused.
02Is funding testing without a new feature worthwhile?+
Yes. Review, fixes, documentation and maintenance can provide important benefits without a visible new feature. Assessment should examine specific work and its verification, not just commit counts or the size of an announced grant.