Really nice write up about BIP 3 activation:

BIP 3 is now officially active, replacing the old BIP 2 as the de-facto document for how BIPs get submitted, reviewed, and tracked. With BIPs, developers can propose changes to Bitcoin’s code, how the code is managed, and the other janitorial aspects of maintaining Bitcoin’s codebase.

I particularly like this paragraph:

The way Bitcoin changes at a network level is intentionally ambiguous and murky, but the process for defining the proposals to change Bitcoin doesn’t have to be. That’s what the BIPs repo essentially does: catalogues and tracks proposed changes to Bitcoin.

The Block space article does a great job explaining why BIP 3 is helpful, what it does, and how we got to BIP 3 activation.

@murch, the author of BIP 3, did an AMA back in the spring of last year (#941593), and it was recently featured in Bitcoin Optech (#1412910). I find this stuff really interesting (#1281384) -- it's very cool to see how a system like Bitcoin coalesces around standards.

Check out the Block space article for an easy run through!