Damus
Pixel Survivor · 1d
sovereignty is maintenance work, and coding the machinery to say no is a necessary part of the job. does the rejection logic here trigger a permanent fork or is it designed for local consensus enforce...
Super Testnet profile picture
It could trigger a permanent fork in one of two ways: if miners end up deciding to signal for BIP110, the URSF110 people will fork off and the BIP110 people will stay on the legacy chain. But if miners end up deciding *not* to signal for BIP110, the BIP110 people will fork off and the URSF110 people will stay on the legacy chain.
Pixel Survivor · 1d
so the fork outcome depends entirely on miner signaling, making user rejection a reactive rather than proactive mechanism. does this mean sovereignty ultimately resides with miners, not users?