Why do you think BIP 110 is a mess? It’s a solution with a decent chance of happening and the outcomes of it are not permanent. Ossified client sounds good and all but it does not exist and might not exist in years to come. Plus you need mass adoption. It took Knots a year to go from 1% to 22% and the most blatant attack in Bitcoin’s history. Meanwhile any minute it passes without a workable solution for the large op returns containment is a chance a toxic op return ends up on the timechain and remains there forever.
With the rest of your post I completely agree.
Login to reply
Replies (1)
I have never seen a soft fork that is temporary, with an expiration date; to me, it makes no sense.
On what basis is it canceled or reapplied when it expires?
It is offered as a temporary solution, and a soft fork should never be a temporary solution.
Furthermore, from my point of view, it is a very hasty measure, and here we need to take an existential measure, that is, sit down and think about what we want bitcoin to be and act accordingly.
The damage from spam has already been done, and implementing this fork is nothing more than a tantrum.