Network upgrades
Blockchain networks often need to upgrade with new features which require coordination work among the community of developers, validators, and node operators prior to activating the upgrades. This process is called a network upgrade, which can be breaking or non-breaking. During planned network upgrades the community will coordinate to prepare for the upcoming upgrade. Breaking network upgrades are not backward-compatible with older versions of the network software, which is why it is important that validators upgrade their software to continue validating on the network. Non-breaking network upgrades are backward-compatible and require less coordination.
Network upgrade coordination
As of the Lemongrass upgrade in September 2024, Celestia has implemented CIP-10 , which establishes two methods for coordinating network upgrades:
- Pre-programmed height: Used for the Lemongrass network upgrade (v2)
- In-protocol signaling: Used for all subsequent upgrades (v3+)
Under the in-protocol signaling mechanism, validators submit messages to signal their readiness and preference for the next version. The upgrade activates automatically once a quorum of 5/6 of validators have signaled for the same version.
Announcement channels
Follow the latest network upgrade announcements on:
- Telegram: Network-wide announcement channel
- Discord
Upgrade process
The upgrade process can be broken down into a few steps:
- Celestia Improvement Proposals (CIPs) are created for consensus-breaking changes and features that impact user experience. These CIPs are included in a meta-CIP, which define the scope of the upgrade.
- Celestia core developer teams implement the features defined in the CIPs.
- A new binary is released with the new features to be tested on testnets.
- Node operators upgrade to the new binary, on Arabica devnet, Mocha testnet, and finally on Celestia Mainnet Beta.
- Upgrades using pre-programmed height (v2) activate at a predetermined block number.
- Upgrades using in-protocol signaling (v3+) activate one week after 5/6 of the voting power has signaled for a particular version
Network upgrade history
v7 (Hibiscus) was skipped on Mainnet Beta due to a bug discovered after testnet activation; v8 (defined in CIP-49 ) was activated instead.
Version links point to Celenium upgrade status pages for signaling upgrades (v3+). v2 used a pre-programmed height and does not have a Celenium signaling page.
Arabica devnet
| Version | Name | CIP | Date and time | Upgrade height | Delay period | Parameters |
|---|---|---|---|---|---|---|
| v2 | Lemongrass | CIP-17 | 2024/08/19 14:00 UTC | 1751707 | — | v2 |
| v3 | Ginger | CIP-25 | 2024/11/05 21:55:13 UTC | 2348907 | — | v3 |
| v4 | Lotus | CIP-33 | 2025/05/16 07:51:35 UTC | 5975265 | 1 day | v4 |
| v5 | — | — | 2025/07/29 19:59:00 UTC | 7316464 | 1 block | v5 |
| v6 | Matcha | CIP-42 | 2025/09/09 06:08:11 UTC | 8105605 | 1 day | v6 |
| v7 | Hibiscus | CIP-47 | 2026/02/14 02:36:26 UTC | 10133989 | 1 day | v7 |
| v8 | — | CIP-49 | 2026/04/04 17:22:12 UTC | 10853352 | 1 day | v8 |
| v9 | — | CIP-50 | 2026/05/28 12:00:22 UTC | 11636100 | 1 day | v9 |
Mocha testnet
| Version | Name | CIP | Date and time | Upgrade height | Delay period | Parameters |
|---|---|---|---|---|---|---|
| v2 | Lemongrass | CIP-17 | 2024/08/28 14:00 UTC | 2585031 | — | v2 |
| v3 | Ginger | CIP-25 | 2024/11/14 18:31:11 UTC | 3140052 | — | v3 |
| v4 | Lotus | CIP-33 | 2025/07/01 11:51:58 UTC | 6915786 | 2 days | v4 |
| v5 | — | — | 2025/07/30 17:07:29 UTC | 7401191 | 1 block | v5 |
| v6 | Matcha | CIP-42 | 2025/10/03 01:25:02 UTC | 8236886 | 2 days | v6 |
| v7 | Hibiscus | CIP-47 | 2026/02/23 18:21:52 UTC | 10209986 | 2 days | v7 |
| v8 | — | CIP-49 | 2026/04/16 14:26:21 UTC | 10941526 | 2 days | v8 |
| v9 | — | CIP-50 | 2026/06/05 08:16:10 UTC | 11655991 | 2 days | v9 |
Mainnet Beta
| Version | Name | CIP | Date and time | Upgrade height | Delay period | Parameters |
|---|---|---|---|---|---|---|
| v2 | Lemongrass | CIP-17 | 2024/09/18 14:00 UTC | 2371495 | — | v2 |
| v3 | Ginger | CIP-25 | 2024/12/12 14:28:52 UTC | 2993219 | — | v3 |
| v4 | Lotus | CIP-33 | 2025/07/28 13:46:27 UTC | 6680339 | 7 days | v4 |
| v5 | — | — | 2025/08/01 14:30:29 UTC | 6748821 | 1 block | v5 |
| v6 | Matcha | CIP-42 | 2025/11/24 12:33:12 UTC | 8662012 | 7 days | v6 |
| v7 | Hibiscus | CIP-47 | N/A (skipped, see v8) | N/A | — | — |
| v8 | — | CIP-49 | 2026/05/05 16:37:35 UTC | 10960599 | 7 days | v8 |
| v9 | — | CIP-50 | Signaling began 2026/06/02 14:54:21 UTC | Monitor status | 7 days | v9 |
Upcoming upgrades
Warning: You do not need to use a tool like cosmovisor to upgrade the binary. Please upgrade your binary before signaling support for the new version.
Mainnet Beta v9, defined in CIP-50 , is in progress. Monitor the upgrade status on Celenium .