Network Upgrades
Mina Protocol evolves through network upgrades (hard forks). Each upgrade introduces new protocol features, performance improvements, or governance changes. Hard forks are not backward compatible — all node operators must upgrade before the fork activates.
The Mesa preflight network hard-forked at 2026-04-27 13:00 UTC. The post-fork chain is now running the Mesa release 4.0.0-preflight-3f038cb, which raises the transaction protocol version to 5.0.0.
Operators must run 4.0.0-preflight-3f038cb to remain on the preflight network. Earlier builds — including the stop-slot release 4.0.0-preflight-stop-2967b39 — are no longer compatible with the post-fork chain.
zkApp developers must update to o1js@3.0.0-mesa.698ca, which targets transaction protocol v5.0.0; earlier o1js releases will produce transactions that the post-fork network rejects.
See Preflight Network for the full upgrade path.
| Upgrade | Status | Date | Key Changes |
|---|---|---|---|
| Berkeley | Completed | June 2024 | zkApp programmability, recursive proofs, new transaction model, archive database migration |
| Mesa | Preflight hard fork completed | 2026-04-27 13:00 UTC (preflight) | Transaction protocol v5.0.0, automode upgrades, simplified archive migration |