What changed in v10.6.0

Celestia Foundation’s official status notice records completion of Mainnet Beta maintenance for celestia-app and Fibre v10.6.0 on 9 November. The notice asks consensus-node and Fibre operators to upgrade for fixes covering consensus block propagation, the CAT mempool, peer-identity validation and the JSON-RPC server.

The signed release record, published on 5 November, describes the build as a minor update for nodes already running app version 10. It says no coordinated network upgrade or configuration change is required. That distinction matters: the maintenance event confirms deployment activity around the release, but it does not describe a new consensus-breaking fork.

Three verification changes stand out. Hyperlane’s Cosmos dependency moves to version 1.3.3, tightening ECDSA signature verification and interchain-security-module routing checks. ShareProof and RowProof verification now binds each proof to its claimed position in the data square. Fibre also rejects new escrow-deposit transactions from the mempool and block proposals when the signer address is non-canonical or the denomination is not utia.

The Fibre rule is forward-looking. Celestia’s notice says blocks that already contain such transactions remain valid. The release also rechecks payment-promise cache budgets when escrow balances fall and prevents a Fibre client crash when a state node returns an incomplete provider response.

Operators face an upgrade task; token claims remain separate

Validators and other node operators are the immediate audience. The release directs operators to replace celestia-app and, for validators, the matching Fibre binary, then confirm that syncing, signing and Fibre readiness resume. Source builds require Go 1.26.10. Prebuilt Linux multiplexer binaries require glibc 2.38, while the separate Fibre binary requires glibc 2.34.

For ordinary users, the official notices establish software changes rather than a token distribution, staking-rate promise, governance vote or new legal right attached to TIA. They also do not establish that every independent node upgraded at the same time. Mainnet Beta’s operator documentation continues to describe the production network as experimental and subject to occasional instability or reduced performance.

NetNapz assessment

Assessment: Binding proofs to positions and tightening signature and routing checks reduce ambiguity at verification boundaries. The release notes label several relevant changes high priority, but neither the status notice nor the release record characterizes a known exploit of Mainnet Beta. It would therefore be misleading to present v10.6.0 as a breach response without separate evidence.

The software-version trail also needs careful attribution. Celestia’s status service records the v10.6.0 Mainnet Beta maintenance as complete, while the general operator overview retrieved during this reporting still listed v10.5.0 for celestia-app. That page lag is a documentation inconsistency, not proof that the maintenance failed. Operators should use the specific status notice and signed release record, then verify their own binaries and network state.

Sources and limitations

NetNapz checked the Celestia Foundation status notice, Celestia operator documentation and the celestiaorg signed GitHub release on 12 November 2026. No independent binary audit, validator survey or live transaction test was performed. Numerical market-price claims are intentionally omitted because none is needed to explain the protocol maintenance.

• Celestia Network Status — Mainnet Beta v10.6.0 maintenance
• celestia-app v10.6.0 signed release record
• Celestia operator documentation — network overview