I am pleased to announce v0.3 of the official BIP-110 activation client (link below).
This version contains some important bug fixes, so all users should update before activation occurs (still at least some weeks away).
A new draft of the BIP for the Reduced Data Temporary Softfork is available now.
All of the "legal" language has been removed, as well as the reactive deployment method.
All feedback welcome:
Just so you're aware, the official number for the Reduced Data Temporary Softfork has not been assigned yet, so "BIP-444" is actually not the correct way to refer to it.
For the moment, it's just "UASF-ReducedData" or RDTS.
I'm optimistic that a number will be assigned soon.
"Don't break userspace", while a nice idea, is not applicable to Bitcoin, if "userspace" means "stuffing blocks with arbitrary data".
@GrassFedBitcoin puts it very well here:
Bitcoiners have historically acted antagonistic towards spam, so much so that it is part of our culture. The recent removal of the OP_RETURN filter is a very recent development, and comes from a dev culture largely disconnected from Bitcoin maximalism.
Unfortunately, Taproot enabled more harm from arbitrary data storage than good from real monetary usage. The RDTS will fix it. Thankfully, very few people, if any, are using Taproot in ways that could be affected by the RDTS.