Majority Attack
Pronunciation: muh-JAW-ruh-tee uh-TAK
Definition
A majority attack occurs when one actor or coordinated group controls enough consensus influence to manipulate blockchain ordering or confirmation. Defenses against Majority Attack combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Overview
Meaning and scope
A majority attack occurs when one actor or coordinated group controls enough consensus influence to manipulate blockchain ordering or confirmation. Defenses against Majority Attack combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Mechanism and operation
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. 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.
Practical payment example
An entity gains substantial effective control of proof-of-work block production and attempts a reorganization; the merchant updates confirmation-risk controls.
Operational checks
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.
Distinctions and limits
Control of a majority usually does not reveal private keys or permit arbitrary creation of assets beyond protocol rules. Majority influence threatens ordering and settlement assumptions, so network concentration and finality design directly affect payment acceptance risk. 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.
Related reading
Related definitions: consensus, confirmation.
Example
An entity gains substantial effective control of proof-of-work block production and attempts a reorganization; the merchant updates confirmation-risk controls.
Comparison
Control of a majority usually does not reveal private keys or permit arbitrary creation of assets beyond protocol rules. Majority influence threatens ordering and settlement assumptions, so network concentration and finality design directly affect payment acceptance risk.
Key Takeaway
Majority influence threatens ordering and settlement assumptions, so network concentration and finality design directly affect payment acceptance risk.
Sources
- Bitcoin.org Documentation: Block Chain — Bitcoin.org (2026-07-30)
- NIST Documentation: Cyberframework — NIST (2026-07-30)