What is Proof of Staked Authority (PoSA)
What is Proof of Staked Authority (PoSA)
Proof of Staked Authority (PoSA) is a consensus mechanism that combines elements of Proof of Stake (PoS) and Proof of Authority (PoA). In a PoSA system, a limited set of validators is pre-approved or permissioned (the Authority component), and each validator must also lock a significant token stake (the Stake component). PoSA is most prominently used by BNB Smart Chain (formerly Binance Smart Chain), where it enables fast block times and low transaction fees while maintaining a known, accountable validator set.
Unlike open Proof of Stake, where any participant meeting the minimum stake can join the validator set, PoSA restricts validation to a curated group of entities. Unlike pure Proof of Authority, where validators are simply whitelisted based on identity or reputation, PoSA adds an economic bond: validators have tokens at risk, which creates a financial incentive against misbehavior.
In short: PoSA is a hybrid consensus mechanism where a permissioned set of validators must also stake tokens, combining the speed of authority-based validation with the economic accountability of staking.
How PoSA works
Validator selection
In a PoSA network, becoming a validator is not open to anyone who stakes enough tokens. Candidates must meet both governance criteria (approval, reputation, operational track record) and economic criteria (staking a substantial number of tokens). On BNB Smart Chain, the active validator set is limited to a small number of nodes -- historically 21 active validators, later expanded -- selected from candidates who have both been elected by stakers and meet the operational requirements.
Authority component
Staking component
The "Staked" in PoSA means that validators must lock tokens as collateral. This economic bond aligns their incentives with honest behavior: validators who produce invalid blocks, go offline, or attempt double-signing risk losing their staked tokens through slashing. Regular token holders can also delegate their stake to validator candidates, influencing which validators enter the active set.
Block production
Active validators take turns producing blocks in a scheduled rotation, similar to DPoS. Because the validator set is small and known, consensus is fast -- BNB Smart Chain produces blocks approximately every three seconds with near-instant finality. The small validator count means less communication overhead between nodes, which directly translates to higher throughput.
Governance and validator rotation
PoSA networks typically include governance mechanisms for adding or removing validators. On BNB Smart Chain, validators are re-elected periodically based on a combination of staking weight and community votes. Validators who underperform (low uptime, missed blocks) can be voted out and replaced. This governance layer sits between fully open PoS (anyone can join) and static PoA (validators are fixed by the operator).
The role of delegated staking in PoSA
In PoSA networks like BNB Smart Chain, regular token holders participate through delegated staking. They select a validator candidate and delegate their tokens to that candidate, increasing the candidate's total stake and improving their chances of entering the active validator set. In return, delegators receive a share of the validator's block rewards, proportional to the amount they delegated.
Delegated staking serves two functions: it allows token holders who cannot operate validator infrastructure to earn staking rewards, and it provides a governance signal -- validators with more delegated stake are viewed as having broader community support. If a validator underperforms or misbehaves, delegators can withdraw their stake and redirect it to a different candidate, creating accountability pressure similar to voter-driven removal in DPoS.
The combination of permissioned validator entry and delegated staking creates a layered system: the protocol controls who can validate (authority), the economics control who actually validates (staking weight), and delegators control which validators succeed (community trust).
PoSA compared to other mechanisms
| Dimension | PoS | PoA | PoSA | DPoS |
|---|---|---|---|---|
| Validator access | Open (stake minimum) | Permissioned (identity-based) | Permissioned + staking | Elected by token holders |
| Validator accountability | Slashing | Reputation / identity | Slashing + identity | Voter-driven removal |
| Throughput | Moderate | High | High | High |
| Decentralization | Higher (many validators possible) | Low (fixed authority set) | Low-moderate (small curated set) | Low-moderate (small elected set) |
| Economic bond | Yes (staked tokens at risk) | No (identity only) | Yes (staked tokens at risk) | Yes (delegated stake) |
PoSA occupies a middle ground: it is more accountable than pure PoA because validators have tokens at risk, but more centralized than open PoS because the validator set is limited and permissioned.
Why PoSA matters for crypto AI projects
Several crypto AI projects deploy on BNB Smart Chain or other PoSA networks because of the combination of low fees and fast block times. For AI workloads that generate frequent on-chain transactions -- task assignments, payment settlements, data registrations, model version records -- the throughput characteristics of PoSA can be practically important.
However, the permissioned nature of the validator set means that the security assumptions differ from open PoS networks. A project building on a PoSA chain effectively trusts a curated set of validators to order transactions honestly. Understanding this tradeoff is relevant to evaluating the Onchain necessity and infrastructure assumptions of any crypto AI project built on such a network.
The practical implication for readers: when a project card shows Consensus: PoSA, the project benefits from fast and cheap transaction processing but depends on a small group of known validators. This is neither inherently good nor bad -- it is a design choice with specific strengths (speed, low cost, accountability through identity) and specific limitations (centralization risk, permissioned access, potential for coordinated censorship).
Where it appears in DecAIHub project cards
In a DecAIHub project card, PoSA appears in the Consensus field. When a card shows Consensus: PoSA, it indicates that the project's underlying network uses the Proof of Staked Authority mechanism to validate transactions and produce blocks.
This is most commonly seen in projects that operate on BNB Smart Chain, where PoSA is the native consensus mechanism. The consensus field helps readers understand the infrastructure layer a project depends on -- how blocks are produced, who validates them, and what security guarantees the chain provides.
The consensus field is one of several infrastructure-level descriptors alongside Main chain, Type, and Network status. Together, these fields paint a picture of the technical foundation beneath the project's application and AI layers.
What PoSA alone does not prove
- PoSA does not prove decentralization. A small, permissioned validator set is more centralized at the consensus layer than an open PoS network. The number of validators, their independence from each other, their geographic and organizational diversity, and the governance process for adding or removing them determine the practical level of decentralization. A PoSA network where all validators are operated by related entities is functionally centralized regardless of the consensus label.
- PoSA does not prove that a project has AI. Consensus is an infrastructure mechanism. A project on a PoSA chain may or may not have a real AI component -- the consensus field says nothing about AI capability.
- PoSA does not prove censorship resistance. A small validator set where validators are known entities can, in theory, be pressured to censor specific transactions or addresses. Whether this is a practical risk depends on the jurisdiction, governance design, and validator diversity.
- PoSA does not prove token necessity. The fact that a chain's consensus uses staked tokens does not automatically mean the project's own token is necessary for its AI or application functionality.
- Low fees do not mean low risk. PoSA chains often have very low transaction fees, which is a user experience feature, not evidence of security, quality, or decentralization.
Do not confuse with
- Proof of Stake (PoS) -- in standard PoS, validator participation is open to anyone who stakes sufficient tokens. PoSA adds a permissioning layer on top of staking. PoSA validators must be approved, not just sufficiently staked. The "Authority" component is what distinguishes PoSA from open PoS.
- Delegated Proof of Stake (DPoS) -- DPoS selects validators through open token-holder elections where any candidate can run. PoSA uses a combination of staking weight and authority approval. The distinction is in how validators enter the set: elected by votes (DPoS) vs. curated by governance and staking (PoSA). Both result in small validator sets, but the selection mechanism differs.
- Proof of Authority (PoA) -- in pure PoA, validators are whitelisted based on identity or reputation alone, with no token stake required. PoSA adds the staking requirement to create an economic penalty for misbehavior. PoA without staking relies entirely on reputational accountability.
- Consensus -- the general concept of how networks agree on the state of the ledger. PoSA is one specific consensus mechanism among many.
- BNB Smart Chain -- BNB Smart Chain is a specific blockchain network that uses PoSA. PoSA is the consensus mechanism; BNB Smart Chain is the network that implements it. Other networks could adopt PoSA as well.
Frequently asked questions
Why was PoSA created instead of using standard PoS?
PoSA was designed to achieve a specific set of tradeoffs: fast block times, low fees, and EVM compatibility, while maintaining a known and accountable validator set. Standard open PoS with a large validator set introduces more communication overhead and slower finality. By limiting the validator set to pre-approved entities who also stake tokens, PoSA achieves the throughput characteristics needed for a high-volume chain like BNB Smart Chain, at the cost of broader validator participation.
How many validators does a PoSA network have?
On BNB Smart Chain, the most prominent PoSA implementation, the active validator set has historically been 21 nodes, though the protocol has expanded this number over time to improve decentralization. The specific number is a protocol parameter -- fewer validators mean faster consensus but more concentration of power; more validators improve resilience but add coordination overhead.
Can anyone become a PoSA validator?
Not directly. Unlike open PoS systems, PoSA requires candidates to meet both operational and governance criteria in addition to staking tokens. On BNB Smart Chain, becoming a validator involves registering as a candidate, meeting technical and operational requirements, and receiving enough delegated stake from token holders to rank within the active set. The combination of permissioning and staking creates a higher entry barrier than open PoS.
Is PoSA more centralized than DPoS?
Both mechanisms result in a small active validator set, but they differ in how validators are selected. DPoS uses open token-holder elections -- any candidate can run and voters decide. PoSA combines staking weight with authority approval, which adds a gatekeeping layer. In practice, the degree of centralization depends on the specific implementation: how many validators are active, how diverse they are, and how the governance process for adding or removing validators actually functions.
External references
- BNB Chain Documentation -- Consensus -- official documentation covering the PoSA consensus mechanism as implemented on BNB Smart Chain.
- Proof of authority -- Wikipedia -- background on Proof of Authority, one of the two components that PoSA combines.
No comments to display
No comments to display