
Blockchains need to find a way to agree upon what is true. As many computers support the same ledger, they need to share rules that say which transactions are valid, which version of the chain is the one they will follow, and which transactions will be discarded.
The first exposure to most people in the area is that with proof of work, which requires miners to solve complex puzzles to add new blocks, or even the proof-of-stake mechanism, which chooses the node to add new blocks. Of all the consensus mechanisms that are used, proof of authority is different: it doesn’t depend on anonymous participants and economic incentives; instead, it uses validators whose reputations are on the line.
What is proof of authority?
In the proof of authority (PoA) model a small number of veritable authors establish blocks and confirm transactions. These authors are known. No hidden addresses. The message is simple: By connecting the real-world identity and accountability of block production, one can run a network quickly and dependably without the demand for free competition to buy each block.
While PoA is largely used in scenarios where the participants prize performance, governance, and compliance more highly than maximal decentralization, it is popular in private, consortium, test, and controlled public networks where different rules will define the membership of assigned validators.
What is a PoA chain?
A PoA chain is any blockchain that uses proof of authority as its method of reaching consensus. In practical terms, it usually means:
- A fixed or curated validator set
- Clear rules for adding and removing validators
- Faster block production than permissionless networks, because only a small group can sign blocks
- Greater reliance on social and legal accountability, because validators are identifiable
You can think of it as a blockchain that behaves more like a governed network than an open wilderness. It is still a distributed ledger, but it is not designed to be fully trustless.
How PoA compares with Proof of Work and Proof of Stake

- Proof of work. Proof of work relies on miners spending computing power to win the right to add blocks. This can be very resilient in open, adversarial conditions, but it is slow and resource heavy by design.
- Proof of stake. Proof of stake selects validators based on their staked capital. It usually improves energy efficiency and can scale better than proof of work, but it still aims to operate with many independent validators and a wide participation set.
- Proof of authority. Proof of authority replaces open participation with permissioned participation. Validators do not win blocks by burning electricity or locking up capital. They are granted the right to validate because the network accepts their identity and reputation as the “stake”.
Because fewer machines do the work and there is no competitive race each block, a PoA chain can offer low fees and consistent performance. The cost is that users must trust the validator set and the governance process behind it.
How proof of authority works in practice
1) Validator selection and onboarding
A PoA network starts by deciding who is allowed to validate. Depending on the chain, validators may be invited, elected by a council, voted in by existing validators, or admitted through an application process. What matters is that there is a defined gatekeeping step.
Ethereum tooling has also popularised PoA style implementations such as Clique, defined in Ethereum Improvement Proposal 225, where authorised signers produce blocks and can vote to add or remove other signers over time.
2) Transaction validation
Users send transactions to the network. Validators check them against the rules, such as signature validity, nonce ordering, and balance checks. Since validators are pre approved, this stage is typically fast because there is no competitive contest.
3) Block production on a schedule
In many PoA designs, validators take turns producing blocks in an orderly pattern. Ethereum documentation describes signers producing blocks in a round robin fashion within fixed time windows.
This predictable schedule is one reason PoA networks can maintain stable block times.
4) Consensus and finality
Once a validator proposes a block, other validators accept it according to the consensus rules. Depending on the implementation, acceptance may be immediate, may require a threshold of signatures, or may use a Byzantine fault tolerant style of voting.
The key theme stays the same: a small set of known validators coordinate to keep the chain moving, rather than thousands of anonymous nodes competing to decide the next block.
5) Accountability and penalties
PoA uses social and reputational pressure as a deterrent. If a validator censors transactions, signs invalid blocks, or repeatedly goes offline, the network can remove them. The consequences are not only technical. They can also be commercial, legal, and reputational.
Because validators are identifiable, attacks can shift from pure technical exploits to coercion and collusion attempts. That is a major design consideration, and it is part of the reason PoA is most suitable where participants already have aligned incentives and governance structures.
What makes someone eligible to be a PoA validator?
Every network sets its own standards, but most PoA systems revolve around four expectations.
- Identity verification. Validators must be verifiable entities. This can resemble know your customer checks or organisational vetting.
- Reputation and credibility. A validator is expected to have something to lose. In some systems, that might be a public brand, an operating licence, or a business relationship with other participants.
- Operational competence. Validators must maintain infrastructure, monitor uptime, patch software, and secure keys. If a validator cannot keep a reliable node running, the chain suffers.
- Commitment to governance. PoA networks change over time. Upgrades, validator rotation, and incident response all require coordination. A PoA validator is often expected to engage in governance, not just block signing.
Benefits of proof of authority
PoA is popular for good reasons, especially outside fully open crypto markets.
- Faster throughput and predictable performance. With fewer validators and no competition for blocks, PoA networks can process transactions quickly and keep block times stable.
- Lower energy use. There is no mining race. Resource consumption is closer to running conventional server infrastructure.
- Lower and more stable fees. Less congestion and more controlled capacity can lead to cheaper transaction costs, which is useful for high volume business workflows.
- Clear governance and easier upgrades. When a small group runs the chain, it is easier to coordinate changes, security responses, and protocol upgrades.
- Suitable for compliance focused use cases. Many organisations need accountability, auditability, and the option to restrict participation. PoA aligns well with those needs.
It is also worth noting that some PoA chains can operate without a native token because the consensus does not require mining rewards or staking mechanics.
Limitations and criticisms of PoA
The same features that make proof of authority efficient also attract criticism.
- Centralisation risk. A small validator set can become a single point of failure, even if it is distributed across multiple organisations. If validators collude, they can shape transaction ordering and policy.
- Trust assumptions. PoA is not designed to be maximally trustless. Users must trust that the validator set is honest and that governance cannot be captured.
- Censorship pressure. Identifiable validators can be pressured by regulators, competitors, or attackers. Even without coercion, a coordinated validator set could choose to censor transactions.
- Validator targeting. Publicly known validators can be targeted with legal threats, bribes, social engineering, or direct attacks on infrastructure.
- Perception in open crypto ecosystems. In communities that prioritise permissionless participation, PoA is often viewed as too close to traditional systems. That can limit its appeal for certain public applications.
Where proof of authority is used
Proof of authority fits best when a blockchain is needed, but full openness is not.
- Private and consortium blockchains. Groups of companies may want shared infrastructure without opening validation to the public.
- Supply chain and enterprise data sharing. Businesses often want traceability with strong control over who can write to the ledger.
- Regulated environments. Sectors like finance, healthcare, and government services may require identifiable operators and strict governance.
- Testnets and development networks. PoA is widely used for controlled testing because it offers fast blocks without needing mining economics.
Examples of PoA in the real world
Here are several well known networks and implementations that show how PoA is applied.
- VeChain. VeChain uses a proof of authority model where authority nodes disclose identity and go through vetting procedures, reflecting the design goal of preventing anonymous block producers.
- POA Network. POA Network launched its own blockchain in 2017 and used validators who were licensed public notaries in the United States, bringing legal identity directly into validator selection.
- Cronos. Cronos describes its consensus as proof of authority, derived from Tendermint proof of stake, and notes that the network is supported by a set of validators and currently operates on an invitation basis for new validators.
- BNB Smart Chain and PoSA. Some public networks use PoA style designs blended with staking. BNB Smart Chain documentation discusses a validator set size of 21 and references fast block times, illustrating how a smaller validator set can prioritise speed and lower fees.
- xDai and Gnosis Chain. Gnosis Chain began as a proof of authority sidechain and later transitioned away from PoA through its merge process, reflecting a broader trend where networks evolve their security model as adoption grows.
The future of proof of authority

Proof of authority is unlikely to replace permissionless consensus for open, global money. That is not its purpose. Its role is to power systems where participants prefer identifiable operators, controlled governance, and predictable performance.
As blockchain adoption expands in enterprise and regulated sectors, PoA is likely to remain a practical option. Improvements will probably focus on stronger validator standards, better hardware security for keys, clearer audit trails, and governance frameworks that reduce the risk of capture.
Final thoughts
Proof of authority is a consensus mechanism built for speed and accountability. A PoA chain runs efficiently because it restricts block production to a trusted validator set. If your priority is openness and maximum censorship resistance, PoA is not the best match. If your priority is reliable throughput, low overhead, and clear governance, proof of authority can be exactly the right tool.
FAQ
Is proof of authority secure?
It can be secure in environments where validators are reputable and governance is robust, but its security model is different from permissionless networks. It relies on the honesty and accountability of a smaller validator set rather than anonymous economic competition.
Is PoA decentralised?
PoA is usually less decentralised than proof of work or many proof of stake systems because validation is restricted. Some PoA networks spread validators across multiple organisations, but participation is still permissioned.
How are validators added or removed on a PoA chain?
It depends on the implementation. Some systems use voting by existing validators, which is part of how Clique style PoA can manage signer sets over time.
Does a PoA blockchain need its own coin?
Not always. Because validators do not need mining rewards or mandatory staking to secure consensus, some PoA networks can operate without a native asset, using other fee arrangements instead.
Why do companies choose proof of authority?
Because it offers predictable performance, lower operational cost, and clear accountability, which can matter more than permissionless participation in business and compliance oriented settings.