Home » Blockchain » Mina Mesa Hard Fork Targets 90-Second Blocks

Mina Mesa Hard Fork Targets 90-Second Blocks

Mina’s Mesa hard fork reportedly cut slot time from three minutes to 90 seconds and raised zkApp state limits. We could not confirm the activation date or details against Mina’s…

Close-up of a dark blue printed circuit board with gold finish, for the Mina Mesa hard fork

Mina’s Mesa hard fork was reported to have gone live on September 3, 2026. The reported headline change is a shorter slot time: 90 seconds instead of three minutes. Mina is a blockchain that keeps a small, fixed-size proof of its entire history, so any node can verify the chain without storing the full ledger.

One caution up front. Mina’s release notes, the Mesa upgrade proposals and an independent report could not be opened when this story was rechecked, so the details below are unconfirmed. Mina’s official documentation and the Mina Foundation blog are the places to check exact versions and activation status.

What Mesa reportedly changes

The slot time falls from three minutes to 90 seconds, so blocks can arrive about twice as often. Beyond speed, the reported changes are aimed at zkApp developers. On-chain state fields rise from 8 to 32, which lets apps store more data per account, and limits on events and actions are raised, so apps can do more work per transaction. These raise per-account zkApp state, not node storage, and Mina’s succinct proof design is unchanged as described. Changes to proof math mean old verification keys stop working against new transactions. A temporary fallback reportedly lets apps keep using signature-based approval while developers recompile keys. New hard fork automation is meant to make later upgrades easier.

Why the slot time was the sore point

Mina has long been slower than most layer-1 chains because of its three minute slot time. A shorter slot time reduces how long a transaction waits for inclusion. It does not change how many zero-knowledge proofs the chain can verify, and it does not make confirmation instant, since chains usually wait for several blocks before treating a payment as settled. For zkApp developers, the state-field increase and key migration matter more day to day than the headline speed.

Who Benefits and How

The people who feel this first are zkApp developers, who get more room per account and a fallback while they migrate keys. Ordinary users of Mina-based apps could see transactions get included sooner, if the reported 90 second slot time holds up in practice. Whether it does hasn’t been shown, and nothing here is a statement about MINA’s price or adoption.

What is confirmed and what is not

The 90 second figure is a protocol parameter, and no measured block intervals on mainnet after the fork were found. The exact Mesa release version, the activation block, and whether all node operators upgraded could not be confirmed. The state-field and event limits were not checked against the protocol source. Developers should test whether their verification keys work after the fork rather than rely on the fallback long term.

Quick answers

What is a hard fork?

A protocol change that older software cannot follow, so node operators must upgrade to stay on the main chain.

Do zkApp developers have to act?

Reportedly yes. Verification keys may need recompiling, with a temporary signature-based fallback while they do.

Where can I confirm the details?

Mina’s official documentation, GitHub releases, and Mina Foundation announcements.

Sources

Related Reading