> Yes, but primarily for a specific edge case.
As I said, 99.99% of users will never encounter such edge case. The other 0.01% had close to a year of prior notice to do something about it. If they are still impacted by this and that’s a big _IF_, they just wait 12 months until the soft fork expires and then they can again move funds. You can theoretically sabotage every BIP proposal by intentionally creating edge cases that violate checks to try and put a stick in the wheels. That doesn’t mean the rest of the network should be forced into a standstill because of this.
Login to reply
Replies (1)
Changing consensus should be very very hard.
Taproot upgrade was in retrospect probably not the right move.
BIP-110 or the version - post one year - will also likely be problematic for issues that are currently hard to see/unforeseen.
Default should be no change.
Pushing this as an *emergency* or even an *urgency* is not based in facts and IMHO will be why BIP-110 fails.