Bitcoin Dev Archive
The bitcoin-dev mailing list, readable
The mailing list is where changes to Bitcoin get proposed and argued over: the block size, SegWit, Taproot, covenants, the quantum question. This is a mirror of the public archive since 2011, one page per thread, with the messages as they were sent. It is refreshed every day.
- 24,698
- messages
- 3,292
- threads
- 1,419
- people posting
- 16
- years
Recently active
Threads with the newest messages. Feed.
- Bitcoin Core security policy update
1 message, 22 Oct 2026. Antoine Poinsot
- Exposure-aware transaction construction for wallets
1 message, 19 Oct 2026. Zeeshan Ali Khan
- btc-verified October Update: Connecting Map to Territory
1 message, 19 Oct 2026. Keagan McClelland
- P2P UTXO Set Sharing
30 messages, 5 May to 15 Oct 2026. Eric Voskuil (12), Fabian (8), Anthony Towns (3), Antoine Riard (2), Josie Baker (2), Saint Wenhao, sadiq Ismail, Sjors Provoost
- Lichen: L2s In CHannels ENforced on bitcoin
3 messages, 11 to 12 Oct 2026. waxwing/ AdamISZ (2), Dustin Ray
- Flame: confidential transactions with Bitcoin proof-of-burn consensus
3 messages, 30 Sep to 8 Oct 2026. Oleg Andreev OOO (2), waxwing/ AdamISZ
- RE BIP 300: 26% censoring attack
1 message, 6 Oct 2026. Ori Newman
- [bitcoindev]
1 message, 6 Oct 2026. Luke Carriere
- LN-GAP : Lightning governed by arbitrary programs
1 message, 4 Oct 2026. waxwing/ AdamISZ
- DropKick ⚽️ - A minimal commit/reveal PQ rescue protocol
5 messages, 20 Aug to 4 Oct 2026. conduition (3), Alex, Antoine Riard
- Getting BIP54 past the finish line
1 message, 2 Oct 2026. Antoine Riard
- MHFE: memory-hard encryption of BIP39 backups into 24 words — request for review
1 message, 1 Oct 2026. Sergei Semenov
- Convention for tagged hash tags in BIPs
2 messages, 22 to 29 Sep 2026. Fabian, Sjors Provoost
- A Post-Quantum Path for BIP 324
8 messages, 5 May to 24 Sep 2026. Olaoluwa Osuntokun (3), conduition (2), Ethan Heilman, Jonas Schnelli, Liam Gilligan
- BIP324 One-Byte Message Type ID Alias Assignment
3 messages, 20 to 24 Sep 2026. Anthony Towns (2), Peter Todd
- QSAVE post-quantum solution for non-migrated coins
1 message, 22 Sep 2026. James T
- Bitcoin Core 32.0rc2 release candidate is available
1 message, 22 Sep 2026. Sebastian Kung
- No burn, Quantum Migration Proposal, Quantum Secure Asset Verification & Escrow (QSAVE)
9 messages, 4 Aug 2025 to 21 Sep 2026. James T (4), conduition (3), Javier Mateos, Erik Aronesty
- SHRINCS: an efficient hash-based signature scheme for Bitcoin (first draft)
7 messages, 26 Aug to 19 Sep 2026. conduition (4), Murch (2), Antoine Riard
- Standardizing public key exposure classification for existing outputs
5 messages, 4 to 18 Sep 2026. duncan0k (4), conduition
The big debates
The longest threads in the archive.
- Block Size Increase 2015, 116
- moving the default display to mbtc 2013, 112
- Block size following technological growth 2015, 111
- Aliases 2011, 107
- Let's deploy BIP65 CHECKLOCKTIMEVERIFY! 2015, 101
- New BIP32 structure 2014, 100
- Adding New BIP Editors 2024, 100
- Fees and the block-finding process 2015, 93
- Presenting a BIP for Shamir's Secret Sharing of Bitcoin private keys 2014, 90
- Coinbase reallocation to discourage Finney attacks 2014, 90
- Stealth Addresses 2014, 88
- Payment Protocol Proposal: Invoices/Payments/Receipts 2012, 87
By topic
37 curated topics, each a timeline of its threads with the BIPs and chapters that go with it. All topics.
- The block size debate 138
- Segregated witness 186
- Taproot and Schnorr 270
- Covenants: CTV, OP_CAT and friends 167
- Replace-by-fee 99
- Mempool policy and package relay 85
- Fees and fee estimation 148
- Privacy: CoinJoin, stealth addresses, silent payments 171
- Network privacy: Dandelion, Tor, encrypted transport 36
- Quantum computing 71
- Time warp, timestamps and the consensus cleanup 57
- The BIP process 91
- Soft fork activation 118
- Hard forks 177
- Bitcoin Core releases 236
- Security disclosures and vulnerabilities 104
- Chain splits and consensus bugs 78
- Lightning and payment channels 132
- Timelocks 85
- HD wallets, seeds and derivation 125
- Descriptors, PSBT and Miniscript 91
- Address formats 155
- Payment requests, URIs and invoices 106
- Script and opcodes 192
- Multisig and threshold signatures 149
- Data on the chain: OP_RETURN, inscriptions and spam 107
- Mining and pools 223
- Sidechains, drivechains and other layers 74
- Light clients and SPV 176
- The peer-to-peer protocol 142
- The UTXO set, pruning and initial sync 143
- Governance, moderation and the list itself 77
- Supply, subsidy and halvings 57
- Signatures and cryptography 155
- Node software and alternative implementations 114
- Testnet, signet and regtest 89
- Wallet design and coin selection 54
The people who wrote it
The most prolific of 1,419 names, each with a page. All people. Every BIP the list discussed has one too.
Browse by year
2015 was the loudest year. All the numbers.
- 2026 698 messages 129 threads
- 2025 1,140 messages 164 threads
- 2024 633 messages 123 threads
- 2023 949 messages 150 threads
- 2022 1,581 messages 206 threads
- 2021 1,386 messages 205 threads
- 2020 780 messages 127 threads
- 2019 942 messages 137 threads
- 2018 1,115 messages 175 threads
- 2017 2,091 messages 274 threads
- 2016 1,209 messages 178 threads
- 2015 5,110 messages 517 threads
- 2014 3,093 messages 308 threads
- 2013 1,859 messages 248 threads
- 2012 1,098 messages 192 threads
- 2011 1,014 messages 159 threads
About this mirror
The list lives at groups.google.com/g/bitcoindev, where anyone can subscribe and post. Its archive of record is the public-inbox at gnusha.org, kept by Bryan Bishop, with a second copy at mirror.b10c.me. Both can be cloned with git, and that is where this mirror comes from. The oldest message here is from 12 Jun 2011; the newest from 22 Oct 2026.
Messages are reproduced as sent. For reading on a screen, quoted text is folded away, list footers and signatures are dropped, and email addresses are obscured. Every message links to its original on gnusha.org, where the raw mail is one click further.
To cite a thread or a message, link to it here. Thread addresses do not change, and every message has a permalink of the form /archive/m/<Message-ID> that will keep working. Each message links to its original on gnusha.org, where the Linux Foundation's old archive links still land.
If you wrote to the list and want a message removed from this copy, write to the address on our security page and name the Message-ID.