# Celestia Mocha testnet activates v11 at block 2,760,281 on 19 November

Celestia's Mocha testnet moved to app version 11 at 10:11 UTC on 19 November and kept producing blocks. Nodes still on v10 software must upgrade; Celestia's mainnet is unaffected and has no v11 release yet.

- Published: 2026-11-19T11:04:33Z
- Updated: 2026-11-19T11:04:33Z
- Chains: Celestia Mocha
- Source: https://docs.celestia.org/operate/maintenance/network-upgrades/
- Web page: https://bitbasic.com/news/47-celestia-mocha-testnet-activates-v11-at-block-2760281-on-19-november
- By: BitBasic (https://bitbasic.com), run by BitNordic

Celestia's Mocha testnet switched to app version 11 on 19 November 2026. Block 2,760,280, the scheduled upgrade height, was produced at 10:11:52 UTC and was the last block on app version 10. The next block, 2,760,281, came at 10:11:55 UTC with app version 11, and blocks have kept coming since. This follows BitBasic's [earlier post on the upgrade height](https://bitbasic.com/news/40-celestia-mocha-testnet-v11-upgrade-set-for-block-2760280-around-19-november).

## What is now active

v11 is an emergency release cut from the v10 line. Its main change limits what a fixed list of accounts can do, accounts whose keys were exposed in the Keplr/Web3Auth social-login incident. According to Celestia's network upgrades page, listed accounts can only send funds to one recovery address, undelegate, withdraw rewards, or set their withdrawal address to the recovery address, with a fee of at most 1 TIA. These limits take effect when app version 11 activates, not when the software is installed. On Mocha the list holds three test accounts, so this was a rehearsal on test tokens.

Celestia's docs say block pacing and Fibre registration changes on the main development branch belong to v12, not v11.

## State of the network after activation

- Public Mocha REST endpoints now report celestia-app **v11.0.0-mocha**, and the signalling module shows no pending upgrade.
- At about 11:00 UTC, BitBasic counted 628 blocks in the previous 30 minutes and 41 seconds, against 643 expected at Mocha's usual 2.87-second block time. Health was rated Healthy (97.7).
- The active set is 86 validators.

## What operators need to do

- **Validators** still on a v10 binary no longer follow the chain and need celestia-app v11.0.0-mocha.
- **Bridge, full and light nodes** need celestia-node **v0.36.0-mocha** with a v11 core endpoint. Celestia's docs say older versions stop syncing once v11 is active.

## Mainnet

Celestia's mainnet is not affected. It still runs app version 10, and on 19 November Celestia's network upgrades page said v11 for Mainnet Beta "has not been released". The mainnet signalling tally for version 11 showed about 11.3 million of 470.1 million voting power (about 2.4%), well short of the 5/6 threshold. No mainnet date has been announced. Mainnet status is on the [Celestia dashboard](https://bitbasic.com/celestia), and Mocha's on the [Mocha dashboard](https://bitbasic.com/celestia-mocha).

## Sources

- [Celestia docs: network upgrades](https://docs.celestia.org/operate/maintenance/network-upgrades/)
- [Celestia docs: Mocha testnet](https://docs.celestia.org/operate/networks/mocha-testnet)
- [Celestia status: Mocha celestia-app fibre v11.0.0-mocha and celestia-node v0.36.0-mocha upgrade](https://status.celestia.org/incidents/01M7JJWSFYW5RCHF9XHKF688K5)
- [Mocha REST: block 2,760,281](https://api-mocha.pops.one/cosmos/base/tendermint/v1beta1/blocks/2760281)
- [Mocha REST: pending signal upgrade](https://api-mocha.pops.one/signal/v1/upgrade)
- [Celestia mainnet REST: version 11 tally](https://celestia-rest.publicnode.com/signal/v1/tally/11)
- [BitBasic: Celestia Mocha dashboard](https://bitbasic.com/celestia-mocha)
