Appearance
Reading the dashboard
The status view is read-only and needs no wallet. Anyone can open it.
It shows four things: the exchange rate, a notice if anything affects what you can do right now, and two or three headline figures. Everything else — the full accounting, the batch pipeline, the configuration, and the operator's checks — is under Protocol details, which is folded away by default and explained further down this page.
Exchange rate
The one headline figure: how much ATOM one vATOM is currently worth.
It starts at 1.000000 and rises as rewards compound. It is vesting-adjusted, meaning recently compounded rewards are only partly counted — see the exchange rate for why. Both minting and redeeming use this same number, so there is no spread between them.
Notices
Shown only when something changes what you can do — the protocol being paused, or a payout waiting to be finalized. When there is nothing to say, nothing appears; a green "all clear" badge on every visit is noise rather than information.
Conditions that matter to whoever runs the deployment rather than to a holder — a period drift, an unexplained balance, a validator count near the gas bound — appear under Protocol details instead.
Headline figures
Total staked is the ATOM backing every vATOM, and vATOM supply is how much of the receipt token exists. Together they are the exchange rate's numerator and denominator.
A third tile, Room for deposits, appears when a cap is set: how much more the pool will accept. With no cap there is no third tile.
The protocol fee is not shown here. It is fixed at zero and cannot be changed, so it is a constant rather than something to watch — it appears in the stake form's preview, in what it costs, and under Protocol details with the rest of the configuration.
Protocol details
Everything below is inside that disclosure. None of it is hidden — it is the same contract read in more depth, and most of it answers an operator's question rather than a holder's.
Pool
Six tiles describing where the ATOM is.
Pooled ATOM
The ATOM backing the vATOM supply — delegated, earning, and attributable to current holders. This is the numerator of the exchange rate.
vATOM supply
Total vATOM in existence. The denominator of the exchange rate.
Owed to redeemers
ATOM promised to people who have already redeemed but have not been paid yet. This covers every unsettled request: those still sitting in the open batch and those already unbonding.
This is deliberately excluded from the exchange rate. It is no longer backing the supply — it belongs to people on their way out.
Claim reserve
ATOM that has arrived, been finalized, and is sitting in the contract right now waiting to be claimed. If you have a finalized withdrawal, your payout is in here.
Vesting rewards
Recently compounded rewards not yet fully recognised in the exchange rate. Recognised in a straight line over 24 hours.
A non-zero value here is healthy — it means rewards were compounded recently. It is not locked-away or at-risk value; it is yours, being phased into the rate to prevent the reward sandwich described in the exchange rate.
Contract bank
The contract's actual liquid ATOM balance: unbonded proceeds plus the claim reserve.
Staking rewards are not in here — they go to the separate rewards vault. That separation is what makes the finalize measurement exact, so this balance should be explainable. When it is not, the runbook checks say so.
Deposit cap
Shown only when a cap is set. The bar is the pool against its ceiling.
When it is full, new deposits are refused. Redemptions and claims are never affected. The cap measures the pool, not cumulative deposits, so redemptions free up room again.
It is a gate on new deposits rather than a hard ceiling on everything the contract holds. Two consequences worth knowing: compounding rewards can push the pool past it (refusing would strand rewards and stall the exchange rate, which is worse), and the figure excludes ATOM owed to people who have already redeemed — so a large redemption frees the full headroom while that ATOM is still in the contract.
Runbook checks
Operational health. Each check is an icon, a label, and an explanation — never colour alone.
| Check | Severity | What it means | What to do |
|---|---|---|---|
| No action required | good | Everything is clear at this block | Nothing |
| Protocol paused | critical | Stake, redeem and claim are all frozen | Only the admin can unpause |
| Forecast maturity | critical | The chain stopped reporting unbonding completion times, so maturities are estimates | Investigate at the chain level. Do not rush settlement — a batch may simply be early rather than slashed |
| A matured batch awaiting finalization | warning | ATOM has arrived; claims are blocked until it is finalized | Anyone can finalize, including you |
| Several matured batches awaiting finalization | warning | More than one batch has arrived, so the permissionless finalize refuses | Needs a governed settlement covering all of them together |
| Unbonding period drift | serious | The chain's real unbonding period differs from what the contract was configured with by more than 5% | Re-check the batch window against the real period — the 7-entry safety bound assumes they match |
| Unexplained bank balance | serious | The contract holds more ATOM than the claim reserve plus arrived batches accounts for | Either a donation or an early arrival. It inflates the finalize measurement and should be accounted for before settling |
| More than 20 validators configured | warning | Unbonding gas scales with the set size | Fine up to 32, but watch the block-gas share |
Unbonding pipeline
Every batch that has been processed but not yet finalized — the work queue.
| Column | Meaning |
|---|---|
| Batch | Its id |
| Status | See below |
| Owed (ATOM) | What the batch was recorded as owing, at each request's rate |
| Undelegated | What was actually sent to the chain to unbond |
| Claimable at | When all of its ATOM will have arrived |
| Remaining | Countdown |
| Haircut | The slashing effect, once finalized. Below 100% means the batch was slashed |
Statuses:
- Awaiting replies — processed, but the chain has not yet reported completion times
- Unbonding — clock running, nothing to do
- Awaiting finalize — ATOM has arrived; claims are blocked until someone finalizes
- Finalized — settled, claims can be paid
- Forecast maturity — the date is an estimate, not chain-reported; needs governed settlement
An empty table is normal and good. It means nothing is in flight.
Validator set
Every configured validator and the share of new stake it takes — the weights, as percentages. They always total 100%.
This is where your deposit goes and how compounded rewards are split. It is not a picture of where the stake currently is: changing weights moves nothing already delegated, so after a rotation the live delegations and this table differ until batches drain the old ones. See how your deposit is spread.
Configuration
| Field | Meaning |
|---|---|
| Unbonding period (configured) | Fixed when the contract was deployed. Bounds the batch cadence only — it does not determine when your funds mature |
| Unbonding period (chain, observed) | What the staking module actually applied, most recently. This is the real one. "Not yet observed" until the first batch is processed |
| Batch window | How long a batch accumulates requests before it can be processed |
| Validators | Size of the configured set |
| Paused | Whether stake/redeem/claim are frozen |
| Protocol fee | Fixed at 0 bps, not adjustable |
The two unbonding period rows exist to be compared. If they diverge, the runbook raises drift — the configured value is a deployment-time assumption, while the observed value is the truth.
The header, and the line at the foot of the page
On the left, the network badge — which chain you are about to sign on. On the right, in order:
- Docs — this site
- Faucet — only on a test network, and only if it has one. Connect first and the link arrives at the faucet with your address already filled in
- The theme button — cycles: follow your device, light, dark. Its tooltip says which
- Connect, or your address once connected. Present on every view — see connecting an account
Everything else is diagnostics, in small print at the foot of the page:
- The RPC host — which node the page is reading. Hover it for the full URL
build <sha>— the exact commit this page was built from. If it is not what you expect, you are looking at a stale page or a different server.devmeans the build was not stampedrefreshed <time>— when the numbers above were last fetched. If it stops advancing, the page has lost its connection to the node