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?
No, a partitioning attack (or accident) can happen without having any hash rate at all.
-
-
Cool. Mind expanding on that, or suggesting a place for me to look?
-
Let’s say Neha’s scenario happens tomorrow, and it’s because you’re in scenario (a). What to make of the blocks that your node has been receiving over the past days/weeks/months? Their mere existence implies the expenditure of hashpower corresponding to their difficulty, right?
End of conversation
New conversation -
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.
