3 ms·
It's inherent in Bitcoin (like any other blockchain) being distributed; not every node is going to immediately recognize every transaction/block in the same ord
by yellowapple 4y ago
It's inherent in Bitcoin (like any other blockchain) being distributed; not every node is going to immediately recognize every transaction/block in the same order, and chains frequently diverge for a block or two. Usually they sort themselves out and regain consensus pretty quickly (via the so-called "longest chain rule"), which is why it ain't exactly newsworthy.
Also happens as a consequence of the node implementations being actively developed: any sufficiently-drastic change in a node's software produces such a split, wherein you end up with two chains calling themselves "Bitcoin": one consisting of the nodes which upgraded, and one consisting of the nodes which didn't. The latter is usually short-lived, but sometimes things get... messy: https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki https://github.com/bitcoin/bips/blob/master/bip-0050.mediawi...
- lisper 4y agoOh, right, I remember that now. That was essentially a rental attack that happened by accident, and it was mitigated by the fact that no one was actually trying to exploit it. I think Bitcoin dodged a bullet that day. But that was ten years ago. Has anything even remotely similar happens since then? (Other that the bitcoin-cash split, of course, which was done intentionally.)