Atlas Staking (-- Auto compound rewards --)
Band validator
Typical fee 0.0006 BAND
Address
bandvaloper1xwgyl7dx7p68uxhl75m7rdr06jcvjpzsmcsfx8
View watchlist
Your Band watchlist is full (25). Remove one first.
-
Status
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.
- Exited
-
Stake
Tokens locked up to back a validator. Total stake includes tokens delegated by others.
- 0 BAND
-
Blocks produced
Blocks this validator proposed in the days BitBasic counted (see the date under the number). Validators take turns to propose, each in proportion to its voting power.
- 0
- Counted since Oct 29, 2026
- Account
- band1xwgyl7dx7p68uxhl75m7rdr06jcvjpzshw52rv
- Consensus address
- bandvalcons1kkeyzlxjme22ggkjp3yrjrky63ctja5q9l73lg
-
Commission
The share of rewards a validator keeps before paying its delegators. The validator sets it on-chain; it can raise it only a little each day, and never above the max rate it fixed when it started.
- 5%
- At most 20%; can rise by up to 1 percentage point a day
-
Jailed until
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.
- Oct 1, 2021
- Jailed for downtime on Oct 1, 2021; its operator can unjail it now
Get alerts
A message when this validator changes status, is jailed or slashed, or its oracle is deactivated. Free, no account needed.
Every message has a link to stop the alerts. How we handle your email or webhook.
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.
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.
How this validator voted on Band's latest proposals. Its vote counts for its delegators unless they vote themselves.
-
Participation
How many of the latest proposals it could vote on (while in the active set) this validator voted on; any option counts, abstain included. Delegators who don't vote themselves are counted with their validator's vote, so one that skips votes leaves them out.
- —
- No proposal it could vote on yet
Latest proposals
- #22 Recover expired Stride light client 07-tendermint-169 Not recorded
- #21 BCIP-21: Governance-Gated Oracle Script & Data Source Approach Not recorded
- #20 BCIP-20: Upgrade to v3.1.3 - Height Deadline Confirmation Not recorded
- #19 BCIP-19: BandChain Upgrade v3.1.3 Approach Not recorded
- #18 Recover IBC light client for Stride Not recorded
- #17 BCIP-17: Strengthening Validator Operations for Band v3 Not recorded
- #16 BCIP-16: Launching the First TSS Group on BandChain Not recorded
- #15 BCIP-15: Upgrade to v3.1 Not recorded
- #14 BCIP-14: Upgrade to v3 Not recorded
- #13 BCIP-12: Increase the maximum data size for oracle module Not recorded
Latest blocks
UpdatedNo blocks from this validator since Oct 29, 14:33 UTC. BitBasic keeps a rolling window of recent blocks.