Learn · 07
Governance and staking
How BNB staking, govBNB voting power and on-chain proposals work on New L1.
Checked against official docs on 2026-10-29
StatusDevnet design. Uses the same governance engine as BNB Smart Chain.
Staking
- Users bridge BNB to New L1 and stake it through a system contract called
StakeHub. - Validators are backed by stake. Up to 64 are active, chosen once a day by stake.
- Validators caught signing conflicting blocks can be slashed, which means they lose part of their stake.
Voting power: govBNB
Staking mints govBNB one-to-one with the staked value. govBNB can't be transferred or traded. It exists only to record voting power.
Confirmed by official docsgovBNB only counts once it is delegated, either to yourself or to a validator. Holding it without delegating gives zero voting weight.
How a change happens
- Someone submits a proposal to change a protocol parameter.
- govBNB holders vote. It passes if it wins and reaches quorum.
- The change waits in a timelock for a mandatory delay.
- It then executes on-chain. Some changes, like Multi-Lane quotas, wait a little longer before they take effect.
Every governed contract only accepts changes through this flow.
What governance does not decide
The validator set itself is not voted on. It comes from the daily stake-based election.
Main system contracts
GovHub, Governor, Timelock, StakeHub and LaneRegistry. The addresses are listed on the official system contracts page.