Majority Attack

Overview

A majority attack targets the consensus resources that determine canonical history, such as mining power, stake, voting weight, or committee control. Capabilities depend on protocol rules and may include reorganizing blocks, censoring transactions, or double spending.

Control of a majority usually does not reveal private keys or permit arbitrary creation of assets beyond protocol rules. Economic cost, finality mechanisms, slashing, checkpoints, social response, and exchange policies determine practical impact and duration.

Users should evaluate consensus concentration, delegation, pool coordination, historical incidents, and current participation. Services can reduce exposure through confirmation policies, reorganization monitoring, independent nodes, limits, and temporary suspension during abnormal consensus behavior. Contingency decisions should consider customer communication and temporary limits on irreversible delivery.

A majority attack occurs when one actor or coordinated group controls enough consensus influence to manipulate blockchain ordering or confirmation. Majority influence threatens ordering and settlement assumptions, so network concentration and finality design directly affect payment acceptance risk.

Assessment of Majority Attack should trace majority attack occurs when one actor or coordinated group controls enough consensus influence to manipulate blockchain ordering or confirmation from prerequisite and entry point through observable impact on the affected service. A theoretical weakness or scanner result involving majority attack occurs when one actor, and confirmation should not be reported as exploitation without corroborating logs, transactions, or configuration evidence. Prevention, detection, containment, and recovery for the Majority attack path should be tested against the architecture associated with majority attack occurs when one actor, and confirmation.

Retesting for Majority Attack should reproduce the Majority attack path involving majority attack occurs when one actor, and confirmation, examine adjacent paths, and verify the conditions for safely returning the affected service to normal operation.