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 stop-slot schedule is published and is compiled into the releases below. Announced in the 3.5.0 Mainnet Stop Slot Release and the 4.0.0 Mainnet Automode Upgrade Release.
| Field | Value |
|---|---|
| Pre-fork (stop-slot) release | 3.5.0-mainnet-stop-slot — mina-mainnet=3.5.0-mainnet-stop-slot-5e100ee |
| Automode release | 4.0.0-mainnet — mina-mainnet-automode=4.0.0-mainnet-893c877 |
| Mesa release (manual mode only) | Published after the stop-network-slot |
stop-transaction-slot (slot_tx_end) | Slot 393800 — 2026-09-03 10:00 UTC |
stop-network-slot (slot_chain_end) | Slot 393900 — 2026-09-03 15:00 UTC |
| Mesa genesis timestamp (UTC) | 2026-09-03 18:00 (hard_fork_genesis_slot_delta = 60 slots = 3 hours) |
| State Finalization window | Exactly 100 slots = exactly 5 hours between slot_tx_end and slot_chain_end |
Both mainnet packages come from the stable channel on packages.o1test.net. Run one of the two releases:
- Automode — install
mina-mainnet-automode=4.0.0-mainnet-893c877before the stop-transaction-slot. The dispatcher swaps to the Mesa binary by itself. No second upgrade. - Manual — install
mina-mainnet=3.5.0-mainnet-stop-slot-5e100eebefore the stop-transaction-slot, keep it running until the stop-network-slot, then install the Mesa release when it is published. See Upgrade Modes.
The archive package for both paths is mina-archive=3.5.0-mainnet-stop-slot-5e100ee.
Devnet
Devnet is on Mesa. The values below are historical; they will not change.
| Field | Value |
|---|---|
| Pre-fork (stop-slot) release | 3.5.0-devnet-stop-slot — mina-devnet=3.5.0-devnet-stop-slot-849edfa |
| Automode release | 4.0.0-devnet — mina-devnet-automode=4.0.0-devnet-2dc9218 |
| Mesa release (manual mode only) | 4.0.0-devnet-mesa — mina-devnet=4.0.0-6965b50 |
stop-transaction-slot (slot_tx_end) | Slot 413540 — 2026-08-19 10:00 UTC |
stop-network-slot (slot_chain_end) | Slot 413640 — 2026-08-19 15:00 UTC |
| Mesa genesis timestamp (UTC) | 2026-08-19 18:00 |
| State Finalization window | Exactly 100 slots = exactly 5 hours between slot_tx_end and slot_chain_end |
Devnet packages come from the alpha channel on packages.o1test.net. A node that joins devnet now must use mina-devnet=4.0.0-6965b50; the two pre-fork releases can no longer connect.
Preflight (archived)
The Mesa preflight network is archived — it is no longer running and its builds are no longer supported. 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 |
The MUT network (mesa-mut), which ran the same sequence on 4.0.0-rc1 builds, is also archived. For the full context on both archived networks, see Archived Networks.
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.