Bitcoin code: the repository, live
Live activity of Bitcoin Core on GitHub: commits, merged pull requests, releases, maintainers and contributors. Plus BIPs, Bitcoin Knots, Lightning implementations, where developers talk, how to contribute and how to verify a download.
🌱 Who writes Bitcoin's code, and how changes get in
- Bitcoin has no company or CEO. The most-used software, Bitcoin Core, is open source on GitHub: anyone can read every line and propose a change (a "pull request").
- Hundreds of volunteers and funded developers review each proposal publicly. Only after enough experienced reviewers agree ("ACK") does one of a handful of maintainers press merge. Maintainers don't decide what Bitcoin is; they apply what review agreed on.
- Big rule changes (soft forks) are written up as BIPs, debated for months or years on the mailing list and Delving Bitcoin, and only activate if node operators run the new software. Nobody can force an upgrade.
bitcoin/bitcoin right now
What it means: dozens of changes land every week, almost all tests, refactors and small fixes. Each one was reviewed in public before merging; consensus rules change very rarely.
GitHub data checked 11 Oct, 13:18 London · github.com/bitcoin/bitcoin · public GitHub REST API, refreshed every 3 hours.
Latest Bitcoin Core releases
Bitcoin Core ships a new major version roughly every six months and keeps releasing fixes for older branches for a while (see the release lifecycle on bitcoincore.org). Always verify a download (see below). Which versions nodes run →
Maintainers and top contributors
Maintainers are the people who press merge. Derived live from merge commits since 14 Aug 2026; the repo's contrib/verify-commits/trusted-keys lists 5 signing keys allowed to merge.
- 1.laanwj7,406
- 2.fanquake5,608
- 3.achow1012,578
- 4.sipa2,397
- 5.hebasto2,320
- 6.gavinandresen1,101
- 7.ryanofsky939
- 8.glozow795
- 9.jnewbery794
- 10.jonasschnelli774
- 11.theuni758
- 12.practicalswift715
Recently merged pull requests
- #36271Revert #36057 & document mingw-w64 requirementhebasto · 11 Oct, 08:04 London
- #36467test: Set socket timeout in interface_http.pyfanquake · 10 Oct, 01:52 London
- #36337fuzz: Cover block filter P2P messagessedited · 9 Oct, 17:07 London
- #36474ci: Run valgrind --exclude tests againfanquake · 9 Oct, 05:18 London
- #35989wallet: fix crash on importdescriptors with a range ending at 2^31-1achow101 · 9 Oct, 00:05 London
- #36450test: Use timeout_factor for drain timeout in check_slow_read_throttlesedited · 8 Oct, 16:24 London
- #34374kernel: use struct-based logging and simplify logging interfacesedited · 8 Oct, 16:01 London
- #35037ipc: support per-address max-connections options on -ipcbindsedited · 8 Oct, 15:10 London
- #36436ci: Derive CONTAINER_NAME from the ci config file namesedited · 8 Oct, 15:01 London
- #36471bitcoin-util: print genesis hash in display ordersedited · 8 Oct, 14:36 London
- #36416test: use ipaddress in addr_to_hexsedited · 8 Oct, 14:20 London
- #36462rpc: fix OpenRPC hex pattern to allow empty stringssedited · 8 Oct, 09:32 London
- #36418kernel: document that btck_WriteBytes may receive a null pointersedited · 7 Oct, 21:25 London
- #36447test: Misc fixes for pending validation events racessedited · 7 Oct, 13:54 London
- #36029cmake: Detect and log MinGW-w64 version when cross-compiling for Windowssedited · 7 Oct, 13:40 London
BIPs: latest proposals and BIP-110
Consensus (soft fork) · by Dathon Ohm. Proposes temporarily limiting arbitrary data at the consensus level for one year. Status in the BIPs repository: Closed. · Node signalling share →
- BIP 332Stale Tip RelayPeer Services · Draft · 2026-08-21
- BIP 461Deterministic ECDSA SignaturesApplications · Draft · 2026-08-12
- BIP 95Testnet 5Applications · Draft · 2026-06-22
- BIP 450Formosa—Seed encoding by themed mnemonic storiesApplications · Draft · 2026-05-15
- BIP 138Compact Encryption Scheme for Non-seed Wallet DataApplications · Draft · 2026-05-11
- BIP 451Dust UTXO Disposal ProtocolApplications · Draft · 2026-04-28
- BIP 440Varops Budget For Script Runtime ConstraintConsensus (soft fork) · Draft · 2026-03-25
- BIP 441Restoration of disabled script (Tapleaf 0xC2)Consensus (soft fork) · Draft · 2026-03-25
- BIP 393Output Script Descriptor AnnotationsApplications · Draft · 2026-03-17
- BIP 448Taproot-native (Re)bindable TransactionsConsensus (soft fork) · Draft · 2026-03-11
192 BIPs in github.com/bitcoin/bips README; statuses per BIP 3. Checked 11 Oct, 13:18 London.
Bitcoin Knots, GUI and BIPs repositories
Bitcoin Core derivative maintained by Luke Dashjr with extra options and stricter default relay policy.
Where pull requests for the Qt graphical interface of Bitcoin Core are opened and reviewed.
Bitcoin Improvement Proposals: design documents for protocol, P2P and wallet standards.
Lightning implementations
Lightning node by Lightning Labs (Go).
Lightning node by Blockstream (C).
Lightning node by ACINQ (Scala), powers Phoenix's LSP.
Lightning Dev Kit: a library to build Lightning into apps (Rust).
Where developers discuss
- [BIP Draft] Co-signer Spending Policies · 10 Oct
- Cassis, a new simple scheme for generic multi-layer multi-hop HTLC routing · 8 Oct
- Anchoring an SPV light client on another chain: checkpoint trust, retargeting and reorg handling · 7 Oct
- Disclosure: DoS vulnerabilities fixed in Eclair v0.14.1 · 6 Oct
- Descriptor syntax for hash preimages · 4 Oct
- Shielded Bitcoin: Private Transfers on the Bitcoin L1 · 2 Oct
The main list for protocol proposals and BIP announcements (hosted on Google Groups since 2024).
- Testing Bitcoin Core 31.0 Release Candidates · 08 Apr 2026 · svanstaa
- #33300 Compact block harness · 08 Oct 2025 · marcofleon
- #32489 wallet: Add exportwatchonlywallet RPC · 06 Aug 2025 · ryanofsky
- #31829 Improve TxOrphanage denial of service bounds · 18 Jun 2025 · glozow
How to contribute
CONTRIBUTING.md explains the PR workflow, commit style and how review (ACK/NACK) works. GUI changes go to bitcoin-core/gui.
Testing and reviewing open PRs is the most useful first contribution. The PR Review Club walks through one PR at a time.
Coding style, testing and debugging conventions for Bitcoin Core.
BIP 3 describes how BIPs are written, numbered and move through statuses (Draft → Complete → Deployed, or Closed).
- 5. Discuss
bitcoindev mailing list (Google Groups) for protocol proposals; Delving Bitcoin for technical research threads.
- 6. Get funded
bitcoincore.org lists ways to contribute, including funding organisations for open-source Bitcoin work.
Verify a Bitcoin Core release (GPG + Guix hashes)
- Download the release file and, from the same release folder, SHA256SUMS and SHA256SUMS.asc.
- Check the hash of your file is listed:
sha256sum --ignore-missing --check SHA256SUMS
- Import the builder keys from the guix.sigs repository (builder-keys folder) and verify the signatures:
gpg --verify SHA256SUMS.asc
- Look for several "Good signature" lines from builders you recognise. Releases are built reproducibly with Guix: independent builders get byte-identical binaries and publish their hashes in guix.sigs.
For v31.1: SHA256SUMS · SHA256SUMS.asc
Sources and method
- GitHub public REST API (unauthenticated): repository stats, commit counts, search for open/merged PRs, releases, contributors, weekly commit activity.
- Maintainers: GitHub accounts behind recent Merge bitcoin/bitcoin#… commits, cross-checked against the number of keys in contrib/verify-commits/trusted-keys.
- BIPs: README and BIP files from github.com/bitcoin/bips; Delving Bitcoin latest.json; bitcoincore.reviews.
- Refresh every 3 hours on our server. If a source fails, its last good data stays with a mark.
core ok · activity ok · repos ok · bips ok · delving ok · review_club ok · updated 11 Oct, 13:18 London