Validators & Staking
Proposer activity aggregated from the most recent — blocks, plus the live validator/observer counts from /v1/chain/info.
Active Validators
—
From chain-info
Observers
—
Read-only nodes
Distinct proposers (window)
—
Last — blocks
Avg Block Time
—
From window timestamps
Proposer activity (window)
Each row is one proposer the chain produced blocks with in the recent window. "First seen" is the earliest block in the window — not the on-chain registration height (no public endpoint yet).
| # | Proposer | Blocks | Share | First seen | Last seen |
|---|---|---|---|---|---|
| Loading… | |||||
First-seen timeline
When each proposer first produced a block within the recent window. The earliest entries are likely long-time validators; the latest are either new joiners or just had a quiet stretch before this window.
- Loading…
Not yet sourced
These all need a staking-module endpoint that is not yet public.
-
—Voting power / total stakeBonded MSK per validator and chain total.
-
—CommissionPer-validator delegator fee.
-
—Lifetime uptime / slashing historyRequires a signing-history endpoint, not just recent proposers.
-
—Registration / join transactionWhen each validator/observer was first onboarded — needs the staking module.
Delegate MSK
Once the staking endpoint ships, the form below will pre-populate with the live active set.
- Run
misaka-cli wallet createand fund your address from the faucet. - Pick a proposer from the list above, or wait for the staking endpoint to expose voting power.
- Submit
misaka-cli stake delegate <valoper> <amount>.
Run a Validator
Operate a node and produce blocks. Min self-bond and slashing parameters will be sourced from chain params once exposed.
- ✓Hardware: 8 vCPU / 16 GB RAM / 500 GB NVMe (recommended)
- ✓ML-DSA-65 consensus key (post-quantum)
- ✓Sentry topology recommended for prod