BPoS Staking Guide
This guide documents Bonded Proof of Stake (BPoS) on the Elastos main chain: emissions, reward distribution, pledge rules, and validator economics. Parameters below are verified from Elastos.ELA source (DPoS v2, activated at block height 1,405,000).
For a step-by-step walkthrough using Essentials (stake, vote, unstake), see Stake ELA.
BPoS replaces the earlier delegated model with bonded voting: you lock (stake) ELA, then pledge it to a validator (vote) for a pledge window you choose (within chain min/max). Rewards are earned from that vote (pledge), not from locking ELA alone; the pledge weights how rewards flow between you, validators, and the protocol.
What is BPoS?
Elastos upgraded consensus from DPoS to BPoS. Token holders lock (bond) ELA, then cast votes (pledges) toward block-producing validators (supernodes). Earning rewards requires an active vote (pledge); locking ELA without voting does not earn.
The active set currently includes 69 BPoS validators elected through bonded voting.
At a high level:
- Voters lock ELA (stake) and pledge it to eligible validators for a defined period—that pledge is what earns a share of emissions.
- Elected validators produce blocks and receive a protocol-defined share of emissions; voters (pledged stake) receive the remainder of the validator bucket per consensus rules.
BPoS ties voting power to pledged duration and stake, aligning long-term participation with network security and validator accountability.
Staking rules (from chain parameters)
| Rule | Detail |
|---|---|
| Minimum pledge | 10 days (7,200 blocks) |
| Maximum pledge | 1,000 days (720,000 blocks) |
| Voting weight | 1 staked ELA = 1 equity token for voting |
| Rewards | Accrue from active votes (pledged stake); depend on amount pledged, pledge duration, and validator performance |
| Pledge changes | Duration may be extended; it cannot be shortened |
| Unstake while voting | ELA committed to active votes cannot be unstaked until the pledge expires |
| Validator eligibility | Validators must meet registration and staking requirements to be eligible for election |
| After expiry | You must re-vote after pledge ends to keep earning |
Block time note: Elastos main chain targets a 2-minute block interval; 7,200 / 720,000 blocks correspond to about 10 / 1,000 days at steady cadence. Use on-chain height for exact timing.
Until the pledge period ends, you cannot free ELA that is still allocated to votes. Plan liquidity and unstaking around expiry and re-voting.
Reward structure
Block rewards split at the protocol level:
- 35%: miners (AuxPoW)
- 35%: BPoS validators and voters (pledged stake)
- 30%: Elastos DAO treasury
Of the 35% validator share, consensus allocates 25% to the node operator and 75% to voters (token holders with active pledges to validators). Rewards are distributed automatically in proportion to pledged stake and pledge-related weighting as defined by the chain.
The 30% treasury slice funds Elastos DAO operations and ecosystem programs; it is not part of the validator–voter split. The 35% AuxPoW allocation pays merged-mining participants securing the main chain’s proof-of-work anchor.
Compare uptime, commission, and total votes when selecting validators; poor performance can reduce effective returns for that node’s voters.
Staking rights formula
Staking rights determine your share of rewards relative to other voters on the same validator. The formula rewards longer commitments with a logarithmic multiplier:
N = E × log(T / 720)
Where E is the number of staked ELA and T is the pledge time in blocks (7,200 ≤ T ≤ 720,000).
The logarithmic scaling means the growth coefficient ranges from 1x to roughly 3x as pledge time increases from the minimum (10 days) to the maximum (1,000 days). Doubling your pledge duration does not double your rights — it provides a diminishing but meaningful boost that rewards patient participants.
When you extend an existing pledge, staking rights and yield rates are recalculated in real time.
Equity tokens
When you lock ELA for BPoS, the protocol converts it into equity tokens — purpose-specific voting units. One locked ELA produces equity tokens for each of these activities:
| Equity token | Used for |
|---|---|
| BPoS staking | Pledging to validators for block production rewards |
| CR election | Voting for Cyber Republic Council candidates |
| Proposal opposition | Voting against CRC proposals during the referendum period |
| Impeachment | Voting to impeach sitting CR Council members |
Each equity token can only be used for its designated purpose. A single BPoS equity token can be pledged to one validator at a time, but you can split tokens across multiple validators.
To convert equity tokens back to liquid ELA, all equity tokens must be free (not actively committed to any vote or pledge). If any equity token is still locked in an activity, you cannot convert back. Equity tokens are non-transferable — they cannot be traded or sent to other addresses.
Pledge duration and extensions
You may extend a pledge (longer commitment) where the protocol allows; you cannot shorten an existing pledge below what the chain has already recorded. Extensions recalculate staking rights using the formula above. Read the confirmation screen carefully before signing.
Validator requirements
To register as a BPoS validator:
| Requirement | Detail |
|---|---|
| Deposit | 2,000 ELA pledged at registration |
| Minimum deposit pledge | 72,000 blocks (~100 days) |
| Activation threshold | Total staking rights from all voters must reach 80,000 |
| Deposit expiry | When the deposit pledge expires, the node automatically becomes inactive |
| Max voter pledge | Voters pledging to a validator cannot set a pledge duration exceeding the node's deposit expiry |
After registration, the node starts in an inactive state. It cannot produce blocks but can begin accepting voter pledges. Once aggregate staking rights cross 80,000, the node activates and enters the consensus rotation.
12 CRC nodes are active by default as part of the Elastos Council validator set. Voters cannot stake on CRC nodes — all block rewards from CRC nodes go directly to their operators.
Consensus rotation
Every 36 block heights constitutes one arbitration cycle. At the start of each cycle, 36 nodes are randomly selected from all active validators to serve as arbitrators for that cycle. This random selection gives all active validators equal opportunity to participate in consensus, regardless of their total staking rights.
As a validator accumulates more staking rights, the per-token yield for its voters decreases — this natural dilution encourages voters to spread their pledges across validators with lower total rights rather than concentrating on a few popular nodes.
Penalties
Validator misbehavior triggers penalties that affect both the node operator and its voters:
| Violation | Description | Penalty |
|---|---|---|
| Negligence | Failing to produce a block for 3 consecutive assigned slots | Node and all stakers penalized; reduced future rewards |
| Malicious behavior | Double-signing blocks or other provably malicious acts | 2,000 ELA deposit confiscated and burned; node permanently marked invalid |
Confiscated tokens are sent to the burn address and removed from circulation permanently. When a node's deposit falls below 2,000 ELA or its aggregate staking rights drop below 80,000, it becomes inactive and stops earning rewards.
As a voter, you share in your validator's penalties. Choose nodes with strong uptime records and avoid validators close to the 80,000 staking rights threshold where a few withdrawals could deactivate the node.
Tips for choosing a validator
-
Reward optimization: Validators with relatively lower total staking rights offer higher per-ELA yields due to the dilution effect. Avoid over-concentrated validators.
-
Stability margin: If a validator's total staking rights are close to 80,000, a few voters withdrawing could deactivate it. Prefer nodes with a comfortable margin above the threshold.
-
Pledge time alignment: Check the distribution of pledge times on a validator. Choose nodes where most voters have pledge durations equal to or longer than yours — a wave of short-term pledge expirations could destabilize the node.
-
Operational quality: Mining rewards are not everything. Check the validator's block signature rate and block generation rate. A validator with poor uptime or a history of missed blocks will cost you rewards and may trigger negligence penalties.
Key parameters (from code)
These values come from Elastos.ELA consensus and chain configuration. Heights and block counts are exact on-chain; day estimates assume the ~2 minute main-chain block time. Use a block explorer for precise wall-clock estimates around upgrades or variance.
| Parameter | Value | Source |
|---|---|---|
| BPoS activation | Height 1,405,000 | config.go |
| Min pledge duration | 7,200 blocks (~10 days) | Chain params |
| Max pledge duration | 720,000 blocks (~1,000 days) | Chain params |
| Active validators | 69 BPoS validators | Consensus params |
| Backup candidates | Configurable pool | Consensus params |
| Inactive penalty | After 1,440 rounds (~2 days) | MaxInactiveRounds |
| Node reward share | 25% | Consensus rules |
| Voter (pledged stake) reward share | 75% | Consensus rules |
Inactive validators: After MaxInactiveRounds (1,440 rounds, roughly ~2 days at nominal round timing), penalty logic can apply per consensus; favor validators with strong uptime when voting.
Backup set: A configurable pool of backup nodes compete for promotion when elected seats turn over; as a voter you still pick among eligible validators presented in the wallet. The protocol manages rotation and arbitration.
BPoS cutover: Before height 1,405,000, legacy DPoS rules applied; BPoS behavior and parameters documented here apply at and after that activation height on networks that adopted the release containing BPoS (DPoS v2).
For operator setup, supernode deployment, and RPC details, see the docs for BPoS supernodes, full nodes, and main-chain configuration in this site’s Nodes section.
Quick reference
| You want to… | Action |
|---|---|
| Start earning BPoS rewards | Stake (lock ELA), then cast votes (pledge to a validator) with pledge in range |
| Keep earning after pledge expires | Re-vote with a new pledge—locking alone does not restart rewards |
| Free ELA for spending | Wait until no active vote lock, then Unstake |
| Choose validators carefully | Review uptime, commission, and total votes in the voting UI before casting |
Validators should consult operator runbooks for registration, keys, and penalty recovery. End-user wallet steps live in Stake ELA.
Terms used on this page
| Term | Meaning |
|---|---|
| BPoS | Bonded Proof of Stake: lock ELA (stake), then vote (pledge) for a duration on main chain; rewards follow the vote |
| Pledge | The period (in blocks/days) your vote commitment stays locked |
| Staking rights | Weighted voting power calculated as E × log(T / 720) from stake amount and pledge duration |
| Equity token | Purpose-specific voting unit created when ELA is locked (BPoS staking, CR election, proposal opposition, impeachment) |
| Supernode | A registered validator eligible to produce blocks when in the active or backup sets |
| Arbitration cycle | A 36-block period during which 36 randomly selected validators serve as arbitrators |
| CRC node | One of 12 Council-operated nodes that are always active and cannot accept voter pledges |
| Elastos DAO | The governance body funded by the 30% treasury allocation |
Official builds and release notes for Elastos.ELA remain the source of truth if consensus parameters change in a future fork; always verify activation height and params for the network you use.