One way to do a URSF is to reject the block *after* BIP110's activation block unless it contains a tx that violates one of BIP110's restrictions. If enough people run it, miners have to choose: make the BIP110 people fork off or make the URSF people fork off. They can't keep both
Replies (3)
No miners are currently signaling support for BIP110, so investing time and effort in developing a URSF client seems like a waste of time and effort at this time (to me, anyways).
Much easier to just use the rejectblock command post-fork if a BIP110 block that forks the chain is ever mined.
What if they don't signal support for BIP110 but just stop mining txs that violate the BIP110 rules, to avoid losing 8% of their users? I don't want OP_IF in taproot to become "effectively invalid" just because miners opt to comply with a bad BIP out of economic interests
It will hurt my bags but I can’t help but be glad that noderunners will not be passive and hand the decision over to miners.
