TL;DR: Bitcoin has no CEO, no company, and no foundation that controls its development. Hundreds of independent contributors worldwide write code, review proposals, and maintain the software through an open, consensus-driven process. Diverse funding from companies like Blockstream, Spiral, Chaincode Labs, Brink, and the Human Rights Foundation prevents any single entity from capturing the protocol.
Bitcoin development is the open, collaborative process by which independent contributors propose, review, test, and merge changes to Bitcoin's software. No one needs permission to participate, no single organization controls the codebase, and changes require overwhelming community consensus before activation. Hundreds of developers contribute to Bitcoin Core (the reference implementation), funded by a diverse mix of companies, nonprofits, and community grants so no single entity can capture the protocol.Bitcoin Has No CEO
Most software projects have a clear hierarchy. A company owns the code, a product manager sets the roadmap, and engineers build what they are told. Bitcoin operates differently. There is no company behind Bitcoin. There is no CEO, no board of directors, no product team, and no official foundation with authority over the protocol.
Satoshi Nakamoto published the Bitcoin whitepaper in 2008 and released the first software client in 2009. By 2011, Satoshi had stepped away entirely, handing commit access to a small group of early developers. Since then, Bitcoin development has been maintained by a loosely coordinated, global community of independent contributors.
This structure is intentional. Bitcoin is designed to be money that no single entity controls. If a company owned the codebase, that company could be pressured by regulators, acquired by competitors, or captured by internal politics. By distributing development across hundreds of independent contributors with no central authority, Bitcoin's governance mirrors its monetary policy: decentralized by design.
How Bitcoin Development Works
The Bitcoin Core Repository
The primary Bitcoin software implementation is Bitcoin Core, an open-source project hosted on GitHub. Anyone in the world can read the code, propose changes, or submit bug reports. The repository has accumulated contributions from over 900 individual developers since its creation.
Bitcoin Core is not the only implementation of the Bitcoin protocol, but it is by far the most widely used. The vast majority of Bitcoin nodes run Bitcoin Core, which makes it the reference implementation in practice. Other implementations exist (btcd, Bitcoin Knots, libbitcoin), but Bitcoin Core's dominance means that its development process has an outsized influence on the network.
The Bitcoin Core codebase is organized into several major areas, each with its own set of specialist contributors: consensus (the validation engine in src/consensus/ and src/validation.cpp), peer-to-peer networking (src/net.cpp, src/net_processing.cpp), wallet (src/wallet/, including descriptor wallets and coin selection), mempool and policy (src/txmempool.cpp, src/policy/), RPC and REST interfaces (src/rpc/), and build/testing infrastructure. Contributors often specialize in one or two areas, building deep expertise in the specific code paths they review and maintain.
The Pull Request Process
Changes to Bitcoin Core follow a structured process:
- Proposal: A developer writes code and submits a pull request (PR) to the Bitcoin Core repository on GitHub. The PR includes a description of what the change does, why it is needed, and how it was tested.
- Review: Other developers examine the code. They test it, look for bugs, check for security vulnerabilities, evaluate whether the change fits Bitcoin's design philosophy, and leave feedback. A single PR can undergo weeks or months of review.
- Revision: The original author responds to feedback, fixes issues, and updates the code. This back-and-forth often goes through multiple rounds.
- Merge: Once enough reviewers approve the change and no significant objections remain, a maintainer merges the PR into the codebase.
- Release: Merged changes are bundled into periodic Bitcoin Core releases. Node operators then choose whether to upgrade.
This process is deliberate by design. Bitcoin secures hundreds of billions of dollars in value. A bug in the consensus code could cause chain splits, loss of funds, or network-wide disruption.
Code Review: The Most Important Activity
Every change to Bitcoin Core must be examined by multiple independent reviewers before it can be merged. Reviewers check for correctness, security implications, backward compatibility, performance impact, and alignment with Bitcoin's design principles. A well-known saying in the Bitcoin development community captures this priority: "Bitcoin needs more reviewers, not more coders".
This emphasis on review creates a natural bottleneck. Many high-quality PRs sit open for months waiting for sufficient review. The bottleneck reflects a conscious trade-off: Bitcoin prioritizes safety over speed of development. A rushed change that introduces a consensus bug could be catastrophic.
Review quality varies. A quick "looks good to me" carries less weight than a detailed review that includes running the code, writing tests, and analyzing edge cases. The Bitcoin development community values thorough, rigorous review and treats it as the most important contribution anyone can make.
Bitcoin Core Maintainers
A small group of maintainers hold merge access to the Bitcoin Core repository. The number of maintainers has varied over the years, typically between four and seven, and the roster changes as contributors take on or step back from the role. The current holders of merge access are visible in the project's own repository rather than in any published roster.
Maintainers have a narrow, specific role: they merge code that has achieved sufficient review and community consensus. They do not have special power to change Bitcoin's rules. A maintainer cannot unilaterally add a feature, alter the supply cap, or modify the consensus rules. If a maintainer attempted to merge controversial code without community support, node operators would simply refuse to run it.
The maintainer role is closer to a janitor than a dictator. Maintainers keep the repository organized, ensure PRs meet quality standards, and press the merge button when the community has reached consensus. The position carries significant responsibility and almost no unilateral power.
How Maintainers Are Chosen
There is no formal election process. Maintainers emerge through sustained, high-quality contributions over years. A developer who consistently writes excellent code, provides thorough reviews, and demonstrates sound judgment earns the trust of the existing maintainers and the broader community. When a new maintainer is needed, the existing group identifies candidates based on track record.
Maintainers can also step down or have their access revoked. The role is not permanent, and the community expects maintainers to act as stewards, not authorities.
Who Funds Bitcoin Development?
Bitcoin developers need to eat. Since Bitcoin has no company generating revenue, development funding comes from a diverse ecosystem of companies, foundations, and community grants. This diversity is critical. If a single entity funded all Bitcoin development, that entity would have disproportionate influence over the protocol's direction.
Companies That Employ Bitcoin Developers
Several companies employ full-time developers who contribute to Bitcoin Core and related open-source projects:
- Blockstream: Employs and funds several Bitcoin Core contributors who work across consensus, cryptography, and protocol research. The company's engineers also maintain Core Lightning (CLN) (a major Lightning Network implementation), develop Elements (the open-source sidechain platform behind the Liquid Network), co-maintain libsecp256k1 (the cryptographic library used by Bitcoin Core for signature operations), and built Simplicity (a formally verifiable smart contract language created by Russell O'Connor within Blockstream Research, live on Liquid since July 2025). Blockstream's open-source contributions extend beyond its own products to the Bitcoin ecosystem broadly.
- Spiral: Block's (formerly Square) Bitcoin development arm. Spiral funds open-source Bitcoin projects including the Bitcoin Development Kit (BDK) and the Lightning Development Kit (LDK), which other companies use to build Bitcoin and Lightning applications.
- Chaincode Labs: A New York-based research and development center focused on Bitcoin and Lightning. Chaincode runs educational programs like the Chaincode Seminar series and employs Bitcoin Core contributors.
- Brink: A nonprofit that provides grants and mentorship to Bitcoin Core developers. Brink focuses specifically on funding the kind of unglamorous but essential work (code review, testing, maintenance) that keeps Bitcoin Core healthy.
Foundations and Grant Programs
- Human Rights Foundation (HRF): Funds Bitcoin development as part of its mission to protect human rights. HRF's Bitcoin Development Fund has supported dozens of developers working on privacy, Lightning, and Bitcoin Core.
- OpenSats: A nonprofit that distributes community donations to open-source Bitcoin and nostr contributors. OpenSats operates a grant program for both long-term support and smaller, project-specific grants.
- Bitcoin Foundation (historical): The Bitcoin Foundation funded some early development but declined in relevance. It no longer plays a significant role in funding.
Individual Grants and Community Funding
Many Bitcoin developers work independently, funded by grants from the organizations listed above, personal savings, or direct community support. Some use platforms like GitHub Sponsors or Geyser to receive donations from the Bitcoin community.
The diversity of funding sources is a security property of Bitcoin, not just an organizational detail. If Blockstream disappeared tomorrow, Bitcoin development would continue. If Spiral shut down its grants, other funders would fill the gap. No single funding source is a single point of failure. This redundancy is by design.
Beyond Bitcoin Core
Bitcoin Core is the most prominent development project, but the broader Bitcoin ecosystem includes thousands of contributors working on related software.
Lightning Network Implementations
Four independent implementations of the Lightning protocol maintain interoperability through the shared BOLT specification.
| Implementation | Maintainer | Language | Repository |
|---|---|---|---|
| Core Lightning (CLN) | Blockstream | C | ElementsProject/lightning |
| LND | Lightning Labs | Go | lightningnetwork/lnd |
| Eclair | ACINQ | Scala | ACINQ/eclair |
| LDK | Spiral (Block) | Rust | lightningdevkit/rust-lightning |
Other Ecosystem Areas
- Wallet software: Hundreds of developers build Bitcoin wallets, each with different priorities (privacy, simplicity, multisig, hardware integration).
- Mining software and firmware: Developers build and maintain the software that miners use to secure the network.
- Protocol research: Researchers propose new features, optimizations, and security improvements through Bitcoin Improvement Proposals (BIPs) and mailing list discussions.
- Layer-2 and sidechain development: Projects like the Liquid Network extend Bitcoin's capabilities for specific use cases (faster settlement, Confidential Transactions, asset issuance) without changing the base protocol.
- Developer tooling: Libraries like BDK, LDK, rust-bitcoin, and python-bitcoinlib make it easier for application developers to build on Bitcoin.
The Bitcoin development ecosystem is large and decentralized. No map captures all of it. Contributors range from full-time engineers at funded companies to weekend hobbyists fixing documentation typos, and both kinds of contribution matter to the network.
The Social Contract: Users Enforce the Rules
Code changes are only half the story. In Bitcoin, the ultimate authority rests with users who run full nodes.
When Bitcoin Core developers release a new version, no one is forced to upgrade. Each node operator independently decides whether to run the new software. If a release included changes that the community rejected, node operators would simply refuse to install it. The old rules would continue to apply on the network, and the controversial release would be irrelevant.
This dynamic was demonstrated dramatically during the 2017 block size war. A coalition of large companies and miners pushed for a hard fork to increase Bitcoin's block size. The proposal had backing from over 80% of mining hashrate and dozens of companies, including major exchanges and payment processors. By conventional power metrics, the change should have succeeded.
It failed. Individual users and node operators rejected the proposal. They ran software that enforced the existing rules and activated Segregated Witness (SegWit) as a soft fork instead. The companies' preferred fork (SegWit2x) was abandoned before it even launched because it lacked user support.
The block size war established a precedent that still defines Bitcoin governance: miners propose blocks, developers write code, but users enforce the rules. Neither hashrate nor corporate backing can override the distributed consensus of tens of thousands of independent node operators.
This social contract is what makes Bitcoin uniquely resistant to capture. A government can pressure a company. A regulator can threaten a foundation. But no entity can compel tens of thousands of independent node operators around the world to run software they do not want to run.
How Changes Get Activated
When the Bitcoin community does reach consensus on a protocol change, activation follows a careful process:
- Proposal and discussion: A developer publishes a BIP describing the change. Discussion happens on the bitcoin-dev mailing list, in GitHub issues, and at in-person developer meetings.
- Implementation: The change is coded, typically as a soft fork (backward-compatible) so that non-upgraded nodes continue to function.
- Review and testing: Months or years of review, testing on testnet and signet, and security analysis.
- Activation mechanism: A method for transitioning the network. Recent upgrades have used mechanisms like BIP 9 (miner signaling) or Speedy Trial (used for Taproot in 2021). The activation mechanism itself is often the most debated part of the process.
- Lock-in and activation: Once sufficient signaling or time-based criteria are met, the new rules activate on a specific block height. After activation, the network enforces the new rules.
Taproot, Bitcoin's most recent major upgrade, took over three years from initial proposal to activation. This timeline reflects the thoroughness required. Every consensus change carries risk, and the community demands extensive evidence that a change is safe, useful, and broadly supported before it goes live.
How to Contribute
Bitcoin development is permissionless. Anyone can participate without asking for approval from a company, foundation, or gatekeeper. The barrier to entry is skill and willingness to do the work, not credentials or connections.
Ways to Contribute
- Code review: The single highest-impact contribution. Pick a pull request on the Bitcoin Core GitHub repository, read the code, test it, and leave thoughtful feedback. No one will ask for your resume.
- Writing code: Fix bugs, implement features, or optimize existing code. Start with small issues labeled "good first issue" on GitHub.
- Testing: Run release candidates, test on signet or testnet, and report bugs. Testing is unglamorous work that prevents disasters.
- Documentation: Improve developer documentation, write tutorials, or translate existing resources. Good documentation lowers the barrier for new contributors.
- Research: Propose new ideas through BIPs, analyze existing proposals, or publish research on Bitcoin's security properties.
- Ecosystem development: Build wallets, tools, libraries, or applications that extend Bitcoin's usefulness. Not every contribution needs to touch Bitcoin Core directly.
- Education: Teach others about Bitcoin's technical properties. An educated user base strengthens the network's social layer.
Getting Started
The most common path into Bitcoin development starts with education. Programs like the Chaincode Seminar, Base58's courses, and Brink's fellowship provide structured learning paths for developers who want to contribute to Bitcoin Core. Reading the Bitcoin Core source code, following pull request discussions, and lurking on the bitcoin-dev mailing list are free ways to build context.
A practical starting point: pick one open pull request on the Bitcoin Core repository and try to understand what it does. Read the code, read the review comments, and run the tests. Understanding one PR in depth teaches more about Bitcoin development than reading ten overview articles.
Bitcoin's Open-Source Ecosystem
Why This Structure Matters
The criticism that Bitcoin's decentralized development process is slow and inefficient misunderstands what that process is optimizing for. Compared to a venture-funded startup that can ship features weekly, Bitcoin's multi-year upgrade cycles do look unhurried.
A startup can afford to move fast and break things because the worst outcome is a bug that costs users some convenience. Bitcoin cannot afford that trade-off. A consensus bug could split the network, destroy confidence in the monetary system, or enable theft of billions of dollars in value. The cost of a mistake is catastrophic, so the development process is built to minimize the probability of mistakes.
The decentralized funding model prevents capture, the open review process prevents backdoors, the social contract between users and developers prevents unilateral changes, and the deliberate pace prevents reckless experimentation with real money.
Every design choice in Bitcoin's development process serves the same goal: producing money that no single entity can control, alter, or corrupt. The development process itself is an extension of Bitcoin's monetary properties.
Why Doesn't Bitcoin Have More Features?
Frequently Asked Questions
Who is in charge of Bitcoin development?
No one. Bitcoin development is an open, collaborative process with no central authority. Maintainers merge code that has achieved community consensus, but they cannot unilaterally change Bitcoin's rules. Users who run full nodes are the ultimate enforcement mechanism.
Can a Bitcoin Core maintainer change the 21 million supply cap?
No. A maintainer could write code that changes the supply cap, but that code would only take effect if node operators chose to run it. Since the fixed supply is one of Bitcoin's core properties, such a change would be rejected by the overwhelming majority of the network. The code would be dead on arrival.
How many people work on Bitcoin Core?
Over 900 developers have contributed code to Bitcoin Core since its creation. In any given year, roughly 100 to 150 developers make meaningful contributions (code commits, reviews, testing). The active contributor base fluctuates, but it has grown steadily over time.
Do Bitcoin developers get paid?
Many do, but not by Bitcoin itself. Developers are funded through a mix of company employment (Blockstream, Spiral, Chaincode Labs), nonprofit grants (Brink, OpenSats, HRF), and community donations. Some work on a volunteer basis. The diversity of funding sources prevents any single funder from controlling development priorities.
Can anyone submit code to Bitcoin Core?
Yes. Bitcoin Core is open-source and accepts pull requests from anyone. Proposed changes go through extensive review by other developers before they can be merged. The barrier is quality, not permission.
What happened in the 2017 block size war?
A coalition of companies and miners with over 80% of mining hashrate attempted to force a block size increase through a hard fork (SegWit2x). Individual users and node operators rejected it, running software that enforced the existing rules while activating SegWit as a soft fork. The episode proved that users, not miners or companies, hold ultimate authority over Bitcoin's consensus rules.
Who created Bitcoin?
Bitcoin was created by Satoshi Nakamoto, a pseudonymous person or group who published the Bitcoin whitepaper in 2008 and released the first software in 2009. By 2011, Satoshi had stepped away and handed maintenance to early developers. Satoshi's identity remains unknown, and their absence is part of why no single person controls Bitcoin today.
Can a government shut down Bitcoin development?
No government can shut down Bitcoin development. The code is open-source and mirrored worldwide, the contributors are spread across many countries and are often pseudonymous, and the funding comes from many independent sources. A government could pressure one company or one developer, but the project would continue through the rest of the community. Ultimately, node operators decide which software defines the network.