Proof of Authority (PoA) is a consensus mechanism in which a set of pre-approved validators, identified by their real-world identity or reputation, are authorized to produce blocks and validate transactions. Unlike PoW or PoS, where participation is open to anyone who meets computational or capital requirements, PoA restricts validation to known, vetted entities.
PoA prioritizes performance, predictability, and accountability over permissionless participation. It is widely used in enterprise blockchains, testnets, and networks where the validator set is intentionally curated.
How Proof of Authority Works
Identity as Stake
In PoA, validators do not compete with computational power (PoW) or risk financial capital (PoS). Instead, they stake their identity and reputation. Validators are typically organizations or individuals whose real-world identity has been verified and who have agreed to a set of governance rules.
The validation process is straightforward:
- A governing body or smart contract maintains a list of authorized validators.
- Validators take turns producing blocks according to a predetermined schedule (round-robin or similar).
- Blocks are signed with the validator's private key, making authorship verifiable.
- If a validator fails to produce a block or acts maliciously, they can be removed from the authorized set through a governance process.
Validator Requirements
PoA networks typically require validators to meet specific criteria before being admitted:
- Identity verification: Real-world identity must be established and publicly known (or known to the governing body).
- Reputation at stake: Validators are often established organizations whose reputation would suffer from malicious behavior.
- Technical capability: Validators must maintain high-uptime infrastructure meeting specified hardware and network requirements.
- Governance participation: Validators may be required to participate in network governance decisions.
The security model of PoA rests on a fundamentally different assumption than PoW or PoS: rather than making attacks economically irrational, PoA makes them socially and legally costly. A validator who acts maliciously risks not just protocol penalties but real-world reputational and legal consequences.
Enterprise Use Cases
PoA is particularly well-suited for enterprise and consortium blockchain deployments where the participants are known and trusted to varying degrees:
Supply Chain Management
Consortium blockchains tracking goods through supply chains benefit from PoA because participants (manufacturers, logistics providers, retailers) are known entities with existing business relationships. The permissioned nature of PoA aligns with enterprise requirements for access control and regulatory compliance.
Financial Services
Interbank settlement networks and trade finance platforms often use PoA or similar permissioned consensus because participants must meet regulatory requirements (KYC/AML) that are incompatible with anonymous, permissionless validation.
Identity and Credentials
Networks for managing digital identity, professional credentials, or academic certificates benefit from PoA's fast finality and the trust that comes from known validators.
Testing and Development
Most Ethereum testnets (such as Goerli and Sepolia) use PoA consensus, as there is no need for the security guarantees of PoW or PoS in a test environment, and PoA provides fast, predictable block production.
Notable Implementations
VeChain
VeChain is one of the most prominent public blockchains using PoA consensus. Its 101 Authority Masternodes are selected through an application process that evaluates the applicant's identity, track record, and infrastructure capabilities. VeChain targets enterprise supply chain and sustainability use cases, where the known validator set aligns with participants' need for accountability.
BNB Chain (Historical)
Binance Smart Chain (now BNB Chain) initially launched with a PoA-like consensus mechanism called Proof of Staked Authority (PoSA), combining elements of PoA and DPoS. A set of 21 validators was elected based on staking, but validators were required to meet identity and performance requirements set by the Binance ecosystem. While this enabled high throughput and low fees, it drew criticism for centralization given Binance's dominant influence over the validator set.
Clique (Ethereum PoA)
Clique is the PoA consensus engine used by several Ethereum testnets and private Ethereum networks. It implements a simple round-robin block production schedule among authorized signers, with an in-protocol voting mechanism for adding or removing signers. Clique's simplicity makes it a popular choice for development and testing environments.
Performance Characteristics
PoA networks achieve excellent performance metrics due to their small, coordinated validator sets:
| Metric | PoA (typical) | PoW (Bitcoin) | PoS (Ethereum) |
|---|---|---|---|
| Block time | 1–5 seconds | ~10 minutes | 12 seconds |
| Finality | Immediate or near-immediate | ~60 minutes (6 blocks) | ~13 minutes (2 epochs) |
| Throughput | Hundreds to thousands TPS | ~7 TPS | ~15–30 TPS |
| Energy consumption | Minimal | Very high | Low |
Comparison to Proof of Stake
PoA and PoS share surface similarities—both use a defined validator set and do not require energy-intensive mining. However, the differences are substantive:
- Entry mechanism: PoS validators self-select by depositing capital. PoA validators are selected through an approval process.
- Penalty mechanism: PoS uses automatic slashing (capital destruction). PoA relies on governance processes and social/legal consequences.
- Permissionlessness: PoS is open to any participant with sufficient capital. PoA is explicitly permissioned.
- Sybil resistance: PoS resists Sybil attacks through capital requirements. PoA resists them through identity verification.
The Decentralization Tradeoff
PoA's most significant limitation is its inherent centralization. The security of the network depends entirely on the honesty and availability of the authorized validator set. This creates several risks:
- Collusion: If validators collude, they can censor transactions, rewrite history, or extract value. The small validator set makes coordination easier.
- Single point of governance: The authority that approves validators represents a centralized governance function, even if the validation itself is distributed among multiple nodes.
- Regulatory risk: Known validators with real-world identities are subject to legal jurisdiction. Government action against validators can compromise the network.
- Censorship vulnerability: Unlike permissionless systems where censored transactions can find an honest miner/validator, PoA networks have no guarantee that censored transactions will ever be included if the validator set collectively decides to exclude them.