Episode notes
In this episode of The Van Wirdum Sjorsnado, hosts Aaron van Wirdum and Sjors Provoost explain what Bitcoin Improvement Proposals (BIPs) are, and how the BIP process works. They discuss why the BIP process is a useful, yet non-binding convention within Bitcoin’s technical community.
Aaron and Sjors start off by explaining what a BIP is exactly— and what it is not. They also explain that only improvements to Bitcoin software that affects other projects require a BIP. The two go on to dive into the history of the BIP process a little bit, noting that the format was introduced by Libbitcoin developer Amir Taaki and later updated by Bitcoin Knots maintainer Luke-jr.
Finally, Aaron and Sjors explain how the BIP process itself works, that is, how a proposal can be turned into a BIP, and eventually be implemented in software. They also briefly explain how the BIP process could become corrupted, and why that wouldn’t be a very big deal.
Chapters
00:00:00 What Bitcoin Improvement Proposals are
00:04:25 The origins of the BIP process
00:06:29 Discussion, drafts and reference implementations
00:11:54 BIP numbers, review and voluntary adoption
00:14:54 BIP editors, hosting and author responsibility
00:18:00 BIP layers, implementations and final status
