Skip to main content
Testnet

Band V3 network

Band's public testnet, where validators run the oracle and rehearse upgrades before mainnet. Validators, uptime, oracle status, governance and jailing.

Typical fee 0.0008 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.
13h 40m Day Nov 7 Hour 11 / 24
Health
Whether the chain made its latest blocks at its normal pace. BitBasic takes about 30 minutes' worth of the latest blocks and compares the time they took with the normal block time: the average over the last 100,000 blocks (or fewer where nodes keep less history), measured hourly. 100 means the 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,831 blocks in the last 29m 28s; 1,798 expected at the normal 0.983 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.
21
All validators
Total stake
Tokens locked up to back a validator. Total stake includes tokens delegated by others.
58.27M BAND
Block height
The number of the latest block: how many blocks the chain has made so far.
58,518,261
Bonded ratio
The share of all tokens in supply that is staked with validators. Staked (bonded) tokens earn rewards, can be slashed with their validator, and take 21 days to unstake.
35.9%
Of 162.1M BAND in supply
Average block time
0.98 s
Over the last 100,000 blocks
Signing window
How many recent blocks the chain checks to see if a validator is offline. A validator that signs too few of them (less than the minimum signed) is jailed for downtime.
86,400 blocks
About 24 hours; signing under 5% of it gets a validator jailed
Oracle-active stake
The share of the active set's stake held by validators whose oracle is active. Only they share in the 70% of block rewards set aside for oracle work.
95.7%
18 of 21 active validators have their oracle active
Oracle inactive
Validators in the active set whose oracle is deactivated. They still sign blocks but miss the 70% of rewards set aside for oracle work, until their operator reactivates the oracle.
3
Active validators without the oracle share of rewards
Full price coverage
Validators with an active oracle that report a price for every feed BitBasic counts. The others answer some feeds with "unavailable" or "unsupported" instead of a price, yet keep their oracle and its share of rewards.
13 of 18
Oracle-active validators reporting all 79 price feeds

Block production per day

Blocks made vs. what the normal block time would give, last 1 day

Updated
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
—
completed days only
Blocks behind pace
How many fewer blocks the chain made than its normal pace would give. BitBasic divides the time it counted by the normal block time (the average over the last 100,000 blocks, or fewer where nodes keep less history) and subtracts the blocks made. Cosmos chains have no fixed slots, so this shows the chain slowing down, not validators failing. A day at the usual pace shows 0. Blocks a validator did not sign are on its own page, as Missed blocks.
—

Counting started Nov 7, 10:08 UTC. The figures above appear once the first full day, Nov 8, ends at 00:00 UTC on Nov 9.

99% or more 95%–99% below 95% in progress

All days as a table

Latest blocks

Updated
Block Producer Transactions Age
#58,518,261 validator2 4
#58,518,260 node101 1
#58,518,259 validator4 1
#58,518,258 CosmosSpaces 1
#58,518,257 validator3 3
#58,518,256 validator1 0
#58,518,255 validator2 2
#58,518,254 B-Harvest 1

Validators

Updated
Active
In the active set: signs and proposes blocks, and earns rewards.
21
Exited
Left the validator set, permanently or for a long time. Tombstoned validators (banned forever for double-signing) count as exited, and so do those jailed more than 42 days ago and never unjailed, and those fully unbonded and removed from the chain's list of validators.
29

Top by stake

  1. validator1 10M BAND
  2. validator2 10M BAND
  3. validator3 10M BAND
  4. validator4 10M BAND
  5. Active Nodes 2M BAND

BitNordic on Band V3

Why is this here?

1 validator operated by BitNordic.

All validators

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
Open proposals
0
None in voting now
Proposals
16
Latest vote: #17
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.
33.4%
Voting lasts 2 days (1 day if expedited)

Recent proposals

All proposals

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 forever) 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
Jailed recently
Jailed in the last 42 days and not unjailed since. These validators show as Jailed: they earn nothing until their operator unjails them. After 42 days BitBasic counts them as exited.
0
In the last 42 days; still jailed
Jailed long ago
Jailed more than 42 days ago and never unjailed. BitBasic counts these validators as exited. Their delegators earn nothing until they move their stake to another validator.
29
Over 42 days ago and never unjailed: counted as exited
Tombstoned
Banned forever for signing two different blocks at the same height. This is called double-signing. The validator loses 5% of its stake, and its delegators lose the same share. It can never sign blocks again, so BitBasic counts it as exited.
0
Banned forever for double-signing
Signing window
How many recent blocks the chain checks to see if a validator is offline. A validator that signs too few of them (less than the minimum signed) is jailed for downtime.
86,400 blocks
About 24 hours
Minimum signed
The share of the signing window a validator must sign, or it is jailed. A validator below it is jailed for downtime: it loses 0.01% of its stake and earns nothing until its operator unjails it, at the earliest 10 minutes later.
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.

Lowest uptime first