Network Fork

Overview

A network fork can arise from simultaneous block production, connectivity partitions, software bugs, malicious reorganization, or a coordinated rule change. Nodes may see competing branches until fork choice and finality select one canonical history. Temporary forks are expected in probabilistic consensus, while hard forks can create permanently incompatible networks when communities continue both rule sets. A finalized conflict indicates a more serious violation of the protocol’s assumptions. Payment systems should monitor canonical block hashes, confirmation depth, and finality rather than heights alone. During abnormal forks they may pause crediting or withdrawals and preserve all observations for reconciliation. Users must distinguish assets on split networks, because identical pre-fork keys and history do not guarantee equivalent post-fork value.

Credits, confirmations, balances, and callbacks must not be duplicated when the same transaction reappears in a different block. Applications affected by Network Fork should roll dependent state backward idempotently and then replay the new canonical history. The likelihood and impact of Network Fork depend on consensus design, network partitions, client faults, finality, and participant concentration. Finalized states may have stronger guarantees than merely included blocks, but exceptional recovery can still involve governance or software intervention.

High-value payment policies should choose thresholds that reflect network-specific reorganization risk. Production monitoring should retain old and new block references, affected transactions, confirmation depths, and the trigger for every business-state change. Network Fork should be tied to specific competing block hashes, heights, fork-choice rules, and the point at which the local canonical view changed. A height alone is insufficient because several valid or invalid branches can contain different transactions at the same position.