Documentation Index
Fetch the complete documentation index at: https://docs.binibit.com/llms.txt
Use this file to discover all available pages before exploring further.
Validator onboarding opens post-mainnet. The structure below describes the canonical model. Specific values (minimum stake, slashing percentages, performance bands) are TBD pending chain team final design.
What validators do
BiniChain validators:- Propose blocks in their assigned slots
- Attest to other validators’ blocks (vote on chain canonicality)
- Finalize blocks via the consensus protocol
- Earn rewards for honest participation
- Lose stake for misbehavior (slashing)
Becoming a validator
To become a validator:- Acquire the minimum self-stake in BINI (TBD value)
- Run a BiniChain validator node (hardware + uptime requirements TBD)
- Submit on-chain registration with bonded stake
- Wait for activation queue
- Begin attesting and proposing in your slots
Validator set size
The validator set has a soft cap to keep block finalization efficient:- Lower bound: enough to be decentralized (e.g., 64+ validators)
- Upper bound: enough that consensus rounds are fast (e.g., 256 validators)
Minimum stake
The minimum self-stake will be set high enough to be meaningful but low enough that mid-size holders can participate. Likely range: 100K–1M BINI (TBD). The minimum may decrease over time as the validator set matures and network value grows.Rewards
Validators earn:- Block rewards in BINI (when proposing or attesting)
- Priority fees from transactions in proposed blocks
- (Optional) MEV captured during block construction (subject to fairness rules)
Slashing
Validators lose stake for:| Offense | Slashing % |
|---|---|
| Double signing (proposing two blocks for the same slot) | High (e.g., 5-50% of stake) |
| Surround voting (voting that contradicts a previous vote) | High |
| Extended downtime | Low to moderate (per period) |
| Incorrect attestation | Low |
Withdrawal
Validators can voluntarily exit the active set:- Submit on-chain exit request
- Wait through the standard exit queue
- Stake unlocks after a withdrawal cooldown
- BINI returned to the validator’s address
Validator vs delegator
BiniChain (per chain team’s final design) may support delegation:- Holders without validator infrastructure can delegate their BINI to existing validators
- Delegators earn a pro-rata share of validator rewards (minus a commission)
- Delegators are slashed pro-rata if their validator misbehaves
Hardware requirements
Validator node requirements (TBD per chain team):- CPU: modern multi-core (e.g., 8 cores)
- RAM: 16-64 GB
- Storage: 1 TB+ SSD (for state and historical data)
- Network: stable connection, 100+ Mbps
- Uptime: 99.5%+ for non-trivial reward share
Validator onboarding timeline
- Pre-mainnet (now): planning + chain implementation
- Mainnet launch: initial validator set bootstrapped by team + early partners
- Post-mainnet (months 1-6): validator slot opens; first external validators onboard
- Mature: validator set grows to soft cap; delegation enabled
Related
Architecture
Consensus protocol underlying validators
Native BINI
What validators stake
BINI Emission
Where validator rewards come from
BINI Token
Where to acquire BINI
