Band network
The cross-chain data oracle on Cosmos. Validators, uptime, oracle status, governance and jailing.
Typical fee 0.0005 BAND
Network
Updated-
Next day in
Cosmos chains have no epochs, so BitBasic uses the UTC day, midnight to midnight, as the dashboard's period and names it by its date.
- 11h 01m
-
Health
How fast the chain made its latest blocks, about 30 minutes' worth, compared with its normal block time (the average over the last 100,000 blocks, or fewer where nodes keep less history, measured hourly); 100 means it keeps its usual pace. It drops to 0 when no new block has arrived for 20 normal block times, and never sooner than a minute. Healthy at 90% or more, Degraded from 70% to under 90%, Unhealthy below 70%.
- Healthy
- 100.0% · 1,549 blocks in the last 29m 52s; 1,542 expected at the normal 1.162 s a block
-
Active validators
A node that stakes tokens, its own and its delegators', to sign and propose blocks. Only the validators with the most stake make the active set and earn rewards.
- 51
- 13 queued · 0 exiting
- All validators
-
Total stake
Tokens locked up to back a validator. Total stake includes tokens delegated by others.
- 91.14M BAND
-
Block height
The number of the latest block: how many blocks the chain has made so far.
- 76,807,903
-
Bonded ratio
Tokens locked up to back a validator. Total stake includes tokens delegated by others.
- 49.3%
- Of 184.69M BAND in supply
- Average block time
- 1.16 s
- Over the last 100,000 blocks
-
Signing window
The share of the last 86,400 blocks (about 28 hours) this validator signed. One that signs less than 5% of them is jailed.
- 86,400 blocks
- About 28 hours; signing under 5% of it gets a validator jailed
-
Oracle-active stake
Band validators also report outside data, such as prices, to the chain. While its oracle is active a validator shares in the 70% of block rewards set aside for that work; one that misses its oracle duties is deactivated and loses that share until its operator reactivates it, at the earliest 10 minutes later.
- 94.8%
- 39 of 51 active validators report oracle data
-
Oracle inactive
Band validators also report outside data, such as prices, to the chain. While its oracle is active a validator shares in the 70% of block rewards set aside for that work; one that misses its oracle duties is deactivated and loses that share until its operator reactivates it, at the earliest 10 minutes later.
- 12
- Active validators without the oracle share of rewards
Block production per day
Blocks made vs. what the normal block time would give, last 1 day
-
Average rate
Blocks the chain made as a share of what its normal block time (the average over the last 100,000 blocks, or fewer where nodes keep less history) would give over the time BitBasic counted. Cosmos has no slots, so under 100% means the chain ran slower than usual, not that blocks were skipped.
- —
- completed days only
- Blocks
- 0
- completed days only
-
Missed blocks
How many fewer blocks the chain made than its normal block time (the average over the last 100,000 blocks, or fewer where nodes keep less history) would give over the time BitBasic counted. Cosmos has no fixed slots, so this measures slowdowns rather than empty slots; a day the chain kept its usual pace shows none.
- 0
99% or more 95%–99% below 95% in progress
Latest blocks
Updated| Block | Producer | Age |
|---|---|---|
| #76,807,903 | Kruskal | |
| #76,807,902 | Dijkstra | |
| #76,807,901 | Forbole | |
| #76,807,900 | Hamming | |
| #76,807,899 | WeStaking | |
| #76,807,898 | Tarjan | |
| #76,807,897 | Knuth | |
| #76,807,896 | StakingCabin | |
| #76,807,895 | Wanchain | |
| #76,807,894 | Kruskal | |
| #76,807,893 | Dijkstra | |
| #76,807,892 | Hamming | |
| #76,807,891 | Tarjan | |
| #76,807,890 | Binance validator | |
| #76,807,889 | Knuth | |
| #76,807,888 | Fantom Foundation | |
| #76,807,887 | w3coins | |
| #76,807,886 | Kruskal | |
| #76,807,885 | Dijkstra | |
| #76,807,884 | sorawit |
Validators
Updated-
Active
In the active set: signs and proposes blocks, and earns rewards.
- 51
-
Queued
Outside the active set: not enough stake to be among the validators that sign blocks, so it earns nothing. It joins by itself once its stake ranks high enough.
- 13
-
Exited
Tombstoned (banned for good for double-signing), jailed more than 42 days ago and never unjailed, or fully unbonded and dropped from the chain's list of validators: gone for good or long abandoned.
- 164
Governance
How the chain decides upgrades and changes to its settings. Anyone can put up a proposal with a deposit; staked tokens then vote on it, and a validator's vote counts for its delegators unless they vote themselves.
Updated
How the chain decides upgrades and changes to its settings. Anyone can put up a proposal with a deposit; staked tokens then vote on it, and a validator's vote counts for its delegators unless they vote themselves.
- Open proposals
- 0
- None in voting now
- Proposals
- 21
- Latest vote: #22
-
Quorum
The share of all staked tokens that must vote on a proposal, any option counting, for its result to stand. A proposal that misses it fails, whatever the votes say.
- 40%
- Voting lasts 5 days (1 day if expedited)
Recent proposals
- #22 Recover expired Stride light client 07-tendermint-169 Passed · Yes 100%
- #21 BCIP-21: Governance-Gated Oracle Script & Data Source Approach Passed · Yes 100%
- #20 BCIP-20: Upgrade to v3.1.3 - Height Deadline Confirmation Passed · Yes 100%
- #19 BCIP-19: BandChain Upgrade v3.1.3 Approach Passed · Yes 100%
- #18 Recover IBC light client for Stride Passed · Yes 100%
- #17 BCIP-17: Strengthening Validator Operations for Band v3 Passed · Yes 99.6% · Abstain 0.4%
Jailing
A validator that signs too few blocks is jailed for downtime and loses 0.01% of its stake. One that signs two different blocks at the same height is tombstoned, banned for good, and loses 5%. Its delegators lose the same share. A validator whose operator withdraws its own stake below the minimum it set is jailed too, but loses nothing. BitBasic dates a jailing by when the validator left the active set, which the chain records for every kind of jailing.
Updated
A validator that signs too few blocks is jailed for downtime and loses 0.01% of its stake. One that signs two different blocks at the same height is tombstoned, banned for good, and loses 5%. Its delegators lose the same share. A validator whose operator withdraws its own stake below the minimum it set is jailed too, but loses nothing. BitBasic dates a jailing by when the validator left the active set, which the chain records for every kind of jailing.
-
Jailed recently
Removed from the active set: it earns nothing, and neither do its delegators, until its operator unjails it. Most jailings are for downtime, signing too few of the recent blocks; the operator can unjail it once the 10-minute jail period is over. A validator is also jailed when its operator withdraws its own stake below the minimum it set. BitBasic counts a validator as jailed for 42 days after the jailing (its 21-day unbonding, then 21 days more); after that it counts as exited.
- 0
- In the last 42 days; still jailed
-
Jailed long ago
Tombstoned (banned for good for double-signing), jailed more than 42 days ago and never unjailed, or fully unbonded and dropped from the chain's list of validators: gone for good or long abandoned.
- 160
- Over 42 days ago and never unjailed: counted as exited
-
Tombstoned
Tombstoned (banned for good for double-signing), jailed more than 42 days ago and never unjailed, or fully unbonded and dropped from the chain's list of validators: gone for good or long abandoned.
- 4
- Banned for good for double-signing
- Signing window
- 86,400 blocks
- About 28 hours
-
Minimum signed
The share of the last 86,400 blocks (about 28 hours) this validator signed. One that signs less than 5% of them is jailed.
- 5%
- Of the window; below it a validator is jailed for at least 10m 00s
Recently jailed
No validator has been jailed in the last 42 days.