With the Mesa Upgrade, o1Labs is introducing an automated hard fork mechanism that allows Mina nodes to upgrade themselves, independently and seamlessly, without manual intervention. It's a fundamental rethink of how protocol upgrades for Mina work, and is the result of months of engineering work.
Upgrading a live blockchain is one of the most complex and stressful operations in software engineering. Unlike a web app or a mobile update, you can't just push a patch and roll it back if something goes wrong. Every node on the network needs to upgrade in a coordinated window, critical data needs to be migrated without errors, and the margin for mistakes is essentially zero. Get it wrong and you risk a chain split, data loss, or hours of unplanned downtime. This coordination isn’t just operationally heavy — it introduces real risk, as success depends on many independent actors executing perfectly under time pressure.
For most networks, this means upgrades are rare, expensive, and treated as high-stakes events rather than a routine part of development.
How Upgrades Have Worked Until Now
When Mina upgraded to Berkeley in 2024, it was a landmark moment for the protocol — bringing zkApp programmability, an improved proof system, and a more mature network to mainnet. But the upgrade process itself was manual.
Node operators had to follow carefully timed steps, download ledger snapshots from external sources, and execute a precise sequence of commands during a narrow window of network downtime. The o1Labs team coordinated closely with operators, exchanges, and infrastructure providers to make sure everything happened in the right order. It went smoothly, but required enormous coordination effort, and left little room for error.
As Mina grows and its upgrade ambitions expand, that process doesn't scale.
What's Changing with Mesa
Rather than waiting for the fork window and then scrambling to migrate data and generate configuration in a short time window, nodes running in automated mode do the heavy work in advance.
In practice, this means that while the network is still running normally, a Mesa node is quietly maintaining both the current and migrated ledgers in parallel, keeping them in sync as new blocks arrive. When the fork point arrives, the node already has everything it needs. It generates its post-fork configuration locally, without relying on external snapshots or coordinated distribution, and restarts on the new chain automatically. Each node independently prepares and executes the upgrade, removing reliance on shared artifacts, external coordination, or trusted distribution points.
For node operators, this means a dramatically simpler upgrade experience. In practice, this reduces the upgrade process from a coordinated, manual operation to something much closer to a standard software update.
For the network, it means a more secure and decentralized process, one where the integrity of the upgrade doesn't rely on perfect coordination between dozens of independent parties under time pressure.
The automated mode will be available as an option from Mesa onwards, sitting alongside the existing manual process for operators who prefer it.
Building Infrastructure for the Future
The automated hard fork mechanism is a foundational investment in how Mina evolves as a protocol.
When an upgrade requires months of coordination, testing, and a high-stakes manual process, the upgrade process itself becomes a bottleneck to progress. By reducing coordination burden and operational risk of upgrades, the Mesa Upgrade makes protocol evolution more predictable and reliable.
Additionally, by having each node generate its own fork configuration locally rather than consuming it from an external source, the upgrade process becomes more decentralized. Each node operates independently, eliminating single points of failure and reducing dependence on external coordination.
Part of a Bigger Picture
The automated hard fork mechanism is one of five major improvements being delivered with the Mesa Upgrade.
- Slot times are being reduced from 3 minutes to 90 seconds.
- On-chain state limits are expanding, giving developers more room to build expressive zkApps.
- Event and action limits are increasing, unlocking richer application logic.
- zkApp account update limit is being raised, allowing more complex operations in a single transaction.
Together, these changes represent a major step forward in Mina’s performance, developer capabilities, and operational reliability. The o1Labs engineering team has spent months designing, testing, and iterating to get it right — delivering an upgrade that improves not just what Mina can do, but how it evolves as a protocol.
Follow the Mesa Upgrade progress, join the conversation, and stay tuned for more details in the Mina Protocol Discord server.