Back to Bitwise Onchain Solutions
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 Celestia's proposals BitBasic recorded, newest first. 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 votes recorded yet: BitBasic started recording Celestia votes on Nov 6, 2026
Every proposal recorded
- #9 Recover IBC clients with KYVE Before our records
- #8 Increase max square size to 256 and block size to 32 MiB Before our records
- #7 Set min_signed_per_window to .001 Before our records
- #5 Increase the Max Block Size to 8MB Before our records
- #4 Parameter Change: Increase SignedBlocksWindow Slashing Parameter for Celestia Mainnet Before our records
- #3 Modify ICA host allow messages Before our records
- #2 Pay for IBC Middleware Audits Before our records
Before our records: voting ended before BitBasic started recording Celestia votes on Nov 6, 2026. The chain deletes votes when voting ends, so BitBasic has no record of how this validator voted.
