Mesa Fork Schedule
This page collects the concrete fork-schedule values for the Mesa upgrade per network. If you are integrating with Mina (exchange, custodian, indexer, Rosetta consumer, monitoring), this is the single source of truth for when to act and which release to run.
The relevant moments are:
stop-transaction-slot(a.k.a.slot_tx_endin the daemon config) — the slot at which nodes stop accepting new user transactions. Block production continues with empty blocks until the network-slot. See the glossary entry.stop-network-slot(a.k.a.slot_chain_end) — the slot at which block production halts entirely. The network is offline between this slot and the Mesa genesis timestamp. See the glossary entry.- Mesa genesis timestamp — the wall-clock time at which the first block on the Mesa chain is produced. Exactly 3 hours after the stop-network-slot. See the glossary entry.
Mainnet
The mainnet Mesa fork schedule has not been announced. The values below are placeholders. They will be filled in once o1Labs publishes the stop-slot release and the Mesa genesis timestamp.
| Field | Value |
|---|---|
| Pre-fork (stop-slot) release | TBD — will be a 3.x.x tag |
| Mesa release | TBD — will be a 4.x.x tag |
stop-transaction-slot (slot_tx_end) | TBD |
stop-network-slot (slot_chain_end) | TBD |
| Mesa genesis timestamp (UTC) | TBD — exactly 3 hours after the stop-network-slot |
| State Finalization window | Exactly 100 slots = exactly 5 hours between slot_tx_end and slot_chain_end |
Subscribe to the MinaProtocol/mina releases and watch the Mina Foundation announcements channel for the schedule publication.
Devnet
Devnet typically forks ahead of mainnet to give integrators a final dress rehearsal. Schedule will be posted here once announced.
| Field | Value |
|---|---|
| Pre-fork (stop-slot) release | TBD |
| Mesa release | TBD |
stop-transaction-slot (slot_tx_end) | TBD |
stop-network-slot (slot_chain_end) | TBD |
| Mesa genesis timestamp (UTC) | TBD |
Preflight
The Mesa preflight network has already forked. The numbers below are historical; they will not change.
| Field | Value |
|---|---|
| Pre-fork release | 4.0.0-preflight1-b649c79 |
| Stop-slot release | 4.0.0-preflight-stop-2967b39 |
| Mesa release | 4.0.0-preflight-3f038cb |
| Mesa hard-fork time (UTC) | 2026-04-27 13:00 |
| Transaction protocol version after fork | 5.0.0 |
| o1js version targeting protocol v5.0.0 | o1js@3.0.0-mesa.698ca |
For the full preflight context, see Preflight Network.
How to use these values
- Exchanges: schedule your deposit/withdrawal freeze to begin before
stop-transaction-slotand re-enable after the Mesa genesis timestamp confirms block production. See the Exchanges tab on Post-Upgrade for the full checklist. - Block producers: install the stop-slot release any time before
stop-transaction-slot. If you are using automode, no further action is needed — the dispatcher will swap to the Mesa binary automatically after the Mesa release is published. - Archive operators: schedule the archive schema upgrade for any time on or after
stop-network-slot. The script is backward compatible and can also be run earlier. See Archive Upgrade. - Rosetta operators: follow the manual-mode timeline — Rosetta does not support automode. See Upgrade Modes.