CryptoSlate
The Mina Mesa upgrade stopped transaction processing on the layer-1 blockchain for roughly eight hours on September 3, with the chain splitting into a five-hour stretch of empty blocks and a three-hour stretch with no blocks produced at all. Exchanges suspended MINA deposits and withdrawals from the 10:00 UTC stop-transaction slot until the first Mesa slot completed at 18:30 UTC, leaving archive-node and manual node upgrades still in progress the next morning. The harder compatibility burden has fallen on deployed zkApps, which cannot process proof-authorized transactions until their developers compile Mesa-compatible verification keys.
Why it matters
Mesa changes protocol constants and circuit constraints, so proofs generated against pre-upgrade verification keys no longer verify. A zkApp cannot resume proof-authorized activity until its developer compiles a Mesa-compatible key with o1js 3.0 and posts the update on-chain. The blast radius is large: any contract that locked itself behind proof authorization now depends on its developer shipping the update before functionality returns. Mina's migration path temporarily lets verification-key permissions set to proof or impossible fall back to signature authorization, but access permissions set to impossible remain locked. There is no fixed migration deadline.
Market impact
Beyond the halt, Mesa halves slot time from three minutes to 90 seconds and temporarily caps zkApp transactions at 12 per block after stress tests found memory spikes when the soft limit was removed. The wider question is how many deployed zkApps will ship the upgrade in time, and whether the temporary signature-authorization fallback opens a window developers did not anticipate when they locked their permission rules.
Frequently asked questions
-
What was the timeline of the Mina Mesa upgrade on September 3?
The 10:00 UTC stop-transaction slot triggered a five-hour stretch of empty blocks, followed by roughly three hours with no block production. The first Mesa slot completed at 18:30 UTC, though archive-node and manual node upgrades were still in progress the next morning.
-
Why do deployed zkApps need new verification keys after the Mesa upgrade?
Mesa changes protocol constants and circuit constraints, so proofs generated against pre-upgrade keys no longer verify. Developers must compile a new key with o1js 3.0 and post the update on-chain before proof-authorized transactions can resume.
-
Is there a deadline for zkApps to migrate to Mesa-compatible keys?
No. Mina's migration path keeps a temporary signature-authorization fallback active until each zkApp updates its key, but no fixed migration deadline has been set.
-
What other changes does the Mesa upgrade introduce beyond the halt?
Mesa halves slot time from three minutes to 90 seconds and temporarily caps zkApp transactions at 12 per block, after stress tests found memory spikes when the soft limit was removed.
-
Are MINA deposits and withdrawals still suspended on exchanges?
Exchanges were instructed to suspend MINA deposits and withdrawals from the 10:00 UTC stop-transaction slot until the first Mesa slot completed at 18:30 UTC, and each exchange controls when transfer support resumes.
Crypto News
CoinTelegraph
TheBlock
CoinDesk
WuBlockchain