Damus
Dathon Ohm profile picture
Dathon Ohm
After much discussion and consideration, I have decided to remove the reactive deployment method and the legal/moral motivations from the BIP document.

I still think those things are important and the reactive deployment may become necessary in an emergency, but I want to continue building consensus and those features were hampering progress.

I hope to have the new draft ready in the next day or two.

Thanks to everyone for your support so far.

11
nostrich · 15w
Thank you for your work. If a consensus builds around fixing the spam which abuses Bitcoin wouldn't it be possible to make the fix permanent? Because both sides actually state they are against spam.
Bitcoin Mechanic · 15w
Thanks for stepping up!
Luke Dashjr · 15w
The whole concept (as I originally designed it) was for an emergency/reactive UASF. I'm not sure it makes sense any other way. For a non-eventful softfork, you'd want to start it 1-1.5 years into the future. And then with a 1 year expiry still?
Léo · 15w
Thanks for all the good work!
Sly Fawkes · 14w
Shouldn't a reactive soft fork be the priority?