An N block reorg on Bitcoin with more proof-of-work appears out of nowhere with a double spend. How big does N have to be before you choose not to accept the reorg?
-
-
Replying to @neha
if it’s a deeeeep reorg, then either a/ you alone have been partitioned off of the main network, in which case the choice to HF & reject the heaviest chain is kinda suicidal since the fork only affects you
2 replies 0 retweets 4 likes -
Replying to @hugohanoi @neha
or b/ a malicious entity has taken over majority hash rate- you can confirm this by checking with other miners. Once confirmed, coordinating on a hard fork is a temporary solution, with the caveat that if the HF still uses the same hash algo, solution might not be sustainable.
2 replies 0 retweets 3 likes -
Replying to @hugohanoi @neha
... since whoever capable of taking over majority hash rate & caused a deep reorg like that can easily overwhelm your minority chain if they need to. You can also change the hash algo with the HF, which'd brick all mining hardware- might not be a safe position to be in either.
1 reply 0 retweets 0 likes
Although it would also depend on how much hash rate is behind the reorg
If it’s a clear majority, e.g. 90% chain A vs. 10% chain B, hardforking away while reusing the same hash algo is not a long term solution. But if its 55% vs 45%, better shot at survivability.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
