3 ms·
the segwit2x contentious fork failed due to an "off-by-one" block height issue in the codebase for miners. Even if all the miners were running it, it would neve
by warboat 9y ago
the segwit2x contentious fork failed due to an "off-by-one" block height issue in the codebase for miners. Even if all the miners were running it, it would never have activated. Did you even know that?
Also, most of the segwit2x node signalling were indeed done by Amazon AWS instances of non-mining nodes. It was not miner nodes. Did you even know that?
- Frogolocalypse 9y agoAnd here you are, with you still trying to fight a battle you've already lost. Four times. Losing exactly the same way every time. Because even after all of those losses, you still can't figure out why you always lose. Because even after all of those failures, you still don't understand why you lost, because you still don't understand how bitcoin works.