Reorganization (Reorg)
Definition
A reorganization (reorg) occurs when a node switches to a different chain branch that has more accumulated work. Previously confirmed blocks become orphaned, and transactions in them may need re-confirmation. Deep reorgs can reverse "finalized" transactions.
Technical Explanation
Reorgs happen when an alternative chain overtakes the current one. Nodes follow the "longest chain" (most work) rule. If a competing branch gains more cumulative proof-of-work, nodes reorganize: orphaning their current tip and adopting the heavier chain.
Shallow reorgs (1-2 blocks) are normal network behavior from propagation delays. Deep reorgs (6+ blocks) are concerning—either the network is unhealthy or an attack is underway. This is why exchanges require multiple confirmations.
SynX Relevance
SynX's consensus design minimizes reorg risk through hybrid proof mechanisms. Confirmation requirements balance usability with security. The explorer displays chain status, helping users understand when transactions have sufficient depth for finality.
Frequently Asked Questions
- Can reorgs steal my funds?
- Reorgs reverse recent transactions—always wait for sufficient confirmations for large amounts.
- How many confirmations prevent reorgs?
- More confirmations = more security. Six is common; high-value transfers may want more.
- Are reorgs attacks?
- Shallow reorgs are normal. Deep reorgs may indicate attacks or network issues.
Stable consensus, reliable finality. Trust SynX