The "filter fork" finally has code... ...and Bitcoin developers are ripping it apart because it's riddled with problems. Here's what is going on with the BIP-110 (BIP-444) activation client /🧵 👉👉👉NOOB FRIENDLY👈👈👈

First, what is an "activation client"? It's the code that coordinates the actual soft fork itself. A modified version of an existing Bitcoin client that enforces the new fork rules While an activation client normally undergoes several improvements, it is expected that the client works, passes all tests upon the first release.

What's broken? Basically, the stuff that matters. The client can't reliably execute a User Activated Soft Fork. Tests designed to verify fork logic are failing. Developers warn it could cause consensus bugs or accidentally fork users off the network (unintentionally) s/o @Rob1Ham of @AnchorWatch for explanations

The debacle echoes Segwit2x in 2017, another controversial fork led by a single developer with buggy software that failed on launch. Despite the technical red flags, some users report many of their peers are already running the flawed client.

What happens next? Developers will submit fixes and an updated version of the release client will (probably) come out. But you have to wonder....

Enjoy our work? Retweet the first tweet for more exposure of our work! Thanks!

@nobsbitcoin