Reorganization Risk

Overview

Reorganization risk is the broader form of reorg risk affecting systems that treat recently observed ledger state as settled. A branch change can alter transaction inclusion, ordering, balances, contract events, or the source data consumed by applications.

Benign races, network partitions, software differences, validator behavior, or deliberate attacks may trigger reorganizations. Operational impact depends on depth, application assumptions, confirmation policy, indexer behavior, and whether external actions were already performed.

Teams should model branch changes, store block references, detect removed events, make processing idempotent, and support rollback or compensating actions. Deep or unusual reorganizations require escalation because they may indicate network instability or attack rather than routine consensus behavior.

Reorganization Risk is the full-name form of reorg risk; it should normally be consolidated with Reorg Risk unless a project deliberately distinguishes a non-blockchain meaning.

Reorganization risk is exposure to changed transaction history when a distributed ledger replaces one accepted branch with another. Reorganization risk extends beyond payment reversal to every application state derived from ledger events that may later be removed or reordered.

For Reorganization Risk, the assessment should evaluate exposure to changed transaction history when a distributed ledger replaces one accepted branch with another. The assessment record should separate observed evidence supporting exposure to changed transaction history when a distributed ledger replaces one accepted branch with another from assumptions, state the time horizon and existing controls, and identify who owns any remaining exposure. Monitoring should test whether the conditions described in exposure to changed transaction history when a distributed ledger replaces one accepted branch with another have changed enough to require a new rating, treatment, or approval.