network

Re-org

A blockchain reorganization occurs when the network switches from one version of the chain to a competing version that has accumulated more proof-of-work.

A re-org happens when nodes on the Bitcoin network become aware of a competing chain that has more accumulated proof-of-work than the one they are currently following. Bitcoin's consensus rule is simple: always follow the chain with the most work. When a longer chain appears, nodes drop their current tip and reorganize to the new chain, reversing any blocks that were on the old branch. Transactions that were confirmed on the old branch but not included in the new chain return to the mempool as unconfirmed.

Small re-orgs of one or two blocks are a routine occurrence and essentially the same mechanism as orphan blocks: two competing blocks found at the same height, with the network briefly split before converging. Deeper re-orgs involving many blocks are far rarer and typically signal either a network partition (where nodes were unable to communicate for a period) or a deliberate attack. A sufficiently large re-org could theoretically reverse transactions that appeared finalized, which is why the common recommendation is to wait for six confirmations before treating a transaction as settled.

The six-confirmation convention comes from the probabilistic difficulty of executing a re-org. Each additional confirmation on top of a transaction means an attacker would need to redo that block's worth of proof-of-work plus produce future blocks faster than the honest network. With six confirmations, reversing a transaction would require an attacker to control a majority of the network's hashrate for an extended period, making the cost economically prohibitive under normal conditions.

Frequently asked questions

How often do re-orgs happen on Bitcoin?

One-block re-orgs happen occasionally, perhaps a handful of times per year, and are usually invisible to end users. Two-block re-orgs are rare. Re-orgs of three or more blocks are extremely uncommon on the main Bitcoin chain and have not occurred in many years. The deeper the re-org, the more hashrate and time an attacker would need, making large re-orgs effectively impractical.

Should I be worried about a re-org reversing my transaction?

For everyday transactions, waiting for one to three confirmations is sufficient. For large or high-value transfers, six confirmations is the widely accepted standard that makes a re-org attack economically unfeasible for any realistic attacker. Exchanges and services handling large amounts often require more confirmations for exactly this reason.

Is a re-org the same as a 51% attack?

A 51% attack is one way a re-org could be deliberately triggered. An attacker with more than half of the network's hashrate could mine a secret chain faster than the public chain and then release it to cause a deep re-org, potentially reversing their own confirmed transactions. Not all re-orgs are attacks, however; small re-orgs happen naturally as a result of normal network latency.