Open-source Bitcoin Funding supports people and projects that create, review and maintain publicly available Bitcoin software, education and infrastructure. Open-source means the source code is available to inspect, use and modify under its license; it does not mean the work has no cost. Funding pays for time and expertise, not the right to dictate the rules of the entire network.
Imagine a developer reviewing a proposed wallet change after her day job. She needs to understand the existing behavior, run tests and consider less common situations. She might add no visible feature and still protect others from a bug. The Bitcoin software project Bitcoin Core lists testing, documentation, translations and user interfaces among the contributions it needs. Its guidelines even identify in-depth review and testing as a development bottleneck. Funding makes room for precisely this often unnoticed work. [6] [7]
A donation can support a person or an organization, a grant sets a framework for funded work, and employment brings its own obligations. Brink, for example, distinguishes grants for experienced developers from a paid fellowship, a program in which people learn through work with mentors. Its grants expect independent work and public progress reports. Recipients therefore need to know more than the amount: what is expected, how long support lasts, when they will be paid and on what terms it can continue. [3]
A repository is where a project keeps its code and change history. Making it public does not automatically bring funding. OpenSats considers alignment with its mission, clear goals, feasibility, the applicant’s skills and expected impact. It describes expert assessment, applicant due diligence and majority approval by its board. The agreement then defines the scope, milestones and progress reports. These are one fund’s rules, not a single admissions process for all of Bitcoin. [1]
Spiral hosts a historical Square Crypto announcement dated 2019-09-14: a grant of 100000 USD to BTCPay Foundation in support of BTCPay Server. The funds could support free and open-source software improving Bitcoin, including usability or privacy. The amount describes that particular grant; it is not today’s price list for development. Human Rights Foundation also supports education, translations and usability alongside development within its mission. Funding therefore covers more than writing code, and these examples are not an exhaustive list of providers. [4] [5]
In Bitcoin Core, a change is proposed publicly, others review and test it, and maintainers decide whether to merge it into the shared repository. Even that does not by itself change the rules of the entire network. Users choose the software they run, and their nodes—the computers checking transactions and blocks—use it to enforce rules. A funder can influence what a paid developer works on. But a grant gives no power to bypass project review or order others to adopt the change. Funding work, accepting code and adopting network rules are separate steps. [7] [9]
It is reasonable to ask who pays for the work, for how long, with what obligations and what ability to end support. A conflict of interest can arise when a funder’s interests differ from users’ needs. OpenSats publishes financial and governance documents and links to conflict-of-interest rules. That openness helps people assess relationships, but does not guarantee neutrality. Likewise, counting companies that pay developers does not tell us how many entities control the protocol. This is about examining specific relationships, not accusing every fund in advance. [2] [9]
Evidence of funded work can be found in licenses, code, reviews, tests, documentation and recipient reports. Bitcoin Core generally accepts contributions under the MIT license, subject to stated exceptions. A license sets terms of use; it is not a safety certificate. Public code alone does not prove anyone has reviewed it thoroughly. If work reveals a sensitive vulnerability—a flaw that can be exploited—it should be reported under the project’s security policy and disclosed in a coordinated way. Pressure to show a grant result immediately must not come before protecting users. [7] [8]
A useful project also needs ongoing maintenance, review of other people’s changes and knowledge sharing. Brink explicitly includes these activities and bug fixes in the work it supports. Counting commits—records of changes in a repository—or adding up announced donations is therefore not enough. What matters more is what was solved, who checked it and who will look after it next. A grant announcement starts support; it does not prove a project is finished. Sustainable funding accounts for work that never makes the front page. [3] [1]
Good work sometimes prevents a release
In this fictional example, a grant lets a developer review a wallet change instead of fitting it into her evenings. She finds a situation where the new version would fail and writes a test that demonstrates the bug. The proposal goes back to its author for correction. Users see no new feature yet, but the funding has delivered value by helping prevent a faulty release. The provider can assess documented work against the agreement, but paying for time cannot buy a way around 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 Bitcoin’s rules?+
Not simply by donating. A donor can influence which work gets funded and what recipients spend time on. But code acceptance follows the project’s process, while network rules depend on what participants actually adopt and run. These levels must be kept distinct.
02Is work without a new feature worth funding?+
Yes. Reviewing someone else’s change, fixing a bug or writing clear documentation may help people more than another feature. What matters is evidence of the work and its verification. Neither commit counts nor the size of an announced grant tells the whole story.