# Celestia v11 passes the 5/6 signalling threshold; activation waits on a try-upgrade transaction

About 89.6% of Celestia mainnet voting power has signalled for app version 11, above the 83.3% needed. Once a try-upgrade transaction is sent, v11 activates 7 days later.

- Published: 2026-11-20T17:04:49Z
- Updated: 2026-11-20T17:04:49Z
- Chains: Celestia
- Source: https://status.celestia.org/incidents/01M7T4VX6XKB3QERTA0AEYT02D
- Web page: https://bitbasic.com/news/51-celestia-v11-passes-the-56-signalling-threshold-activation-waits-on-a-try
- By: BitBasic (https://bitbasic.com), run by BitNordic

Validators on Celestia's mainnet have now signalled for **app version 11** with more than the 5/6 of voting power the upgrade needs. At about 17:00 UTC on 20 November 2026, the chain's tally for version 11 showed **421.8 million of 471.0 million** voting power signalled, about **89.6%**. The threshold is 392.5 million (83.3%), so the tally is about 29.3 million above it.

A day earlier the same tally stood at about 36.0% ([BitBasic's post on the v11 release](https://bitbasic.com/news/48-celestia-mainnet-gets-emergency-v11-release-validators-must-install-and-signal)).

## What happens next

Celestia upgrades by validator signalling rather than a governance vote. Reaching the threshold does not activate v11 by itself:

- Anyone can now submit a `try-upgrade` transaction. At the time of writing, the chain's upgrade query still returned no pending upgrade, so this had not happened yet.
- According to the Celestia Foundation's notice, the upgrade takes effect **7 days** after the threshold is met and the upgrade transaction is submitted. The upgrade height can then be read with `celestia-appd query signal upgrade`.
- The chain was still on app version 10 at block 16,073,237.

That puts the earliest possible activation at about 27 November 2026, later if the `try-upgrade` transaction comes later.

## What v11 does

The Foundation calls v11 an emergency release. It restricts a fixed list of 41,963 accounts whose keys were exposed in the Keplr/Web3Auth social-login incident: from activation, those accounts can only move funds to one recovery address. The limits apply only once v11 is active.

## What it means

- **Validators:** anyone who has not yet installed celestia-app and Fibre v11.0.0 should do so before activation. A validator still on v10 at the upgrade height stops following the chain. Validators that have not signalled can still do so.
- **Bridge, full and light node operators:** celestia-node v0.36.0 is required; the Foundation says older versions will stop working once v11 is active.
- **Delegators and token holders:** nothing to do, unless your account is on the restricted list.

The signalling share and upgrade status are on the [Celestia dashboard](https://bitbasic.com/celestia).

## Sources

- [Celestia status: celestia-app and Fibre v11.0.0 and celestia-node v0.36.0, Mainnet Beta upgrade](https://status.celestia.org/incidents/01M7T4VX6XKB3QERTA0AEYT02D)
- [Celestia mainnet REST: version 11 tally](https://celestia-rest.publicnode.com/signal/v1/tally/11)
- [Celestia mainnet REST: pending signalled upgrade](https://celestia-rest.publicnode.com/signal/v1/upgrade)
- [Celestia docs: network upgrades](https://docs.celestia.org/operate/maintenance/network-upgrades/)
- [BitBasic: Celestia mainnet gets emergency v11 release](https://bitbasic.com/news/48-celestia-mainnet-gets-emergency-v11-release-validators-must-install-and-signal)
- [BitBasic: Celestia dashboard](https://bitbasic.com/celestia)
