Road to Mesa: Performance Dialed Up for zkApps

MIP9 aims to boost zkApp performance by tripling account update limits per transaction, enabling more complex, efficient, and cost-effective applications.

image

The next MIP proposed for Mina’s Mesa Upgrade is about capacity. We have proposed reducing slot times to double throughput and increasing the action and events limit. In this MIP, we will discuss MIP 9, a protocol update that lets a single Mina zkApp transaction handle more actions (account updates) at once. All of this means that more actions enable more complex applications by removing some of the logic constraints on zkApp builders.

What are Account Updates?

A zkApp account update is the basic instruction bundle inside a Mina transaction that specifies which zkApp account is being changed, what exactly changes, and how that change is authorized (by a proof or signature). They matter because they safely carry the “what and why” of a zkApp’s state change from off-chain execution to on-chain verification, enabling secure, composable, and predictable smart contract behavior on Mina.

What’s Changing?

Previously, many real‑world actions had to be split into multiple transactions, each needing separate approval and an extra fee. The new limit roughly triples how much can be packed into one transaction, reducing splits and streamlining flows.

Why It Matters?

The Mina Protocol currently limits zkApp transactions to a maximum of 10 signature-based account updates or 5 proof-based account updates per transaction. While these limits were initially established to ensure low impact on performance, they have become increasingly restrictive as zkApp development progressed. After careful testing we are now confident we can increase the number without affecting performance.

This limitation creates the following problems:

  1. Development Constraints: Developers are forced to split complex logic across multiple transactions, increasing complexity and limiting capabilities
  2. Technical Complexity on User Experience: End users must approve multiple transactions to complete what is logically a single operation.
  3. Increased Cost: As a result of the previous point, end users must pay extra fees on transactions, as fees grow linearly with the number of transactions.

By increasing these limits, we can enable more sophisticated zkApps that better serve user needs while maintaining Mina’s commitment to succinct blockchain architecture.

Part of the Bigger Road to Mesa Story

  • Slot Reduction MIP → More speed.
  • Increasing Mina’s On-Chain State Limit → More expressive applications and simplify zkApp development.
  • Increase Events & Actions Limit → More expressive applications.
  • Increase zkApp Account Update Limit (this MIP) → More complex, efficient zkApps in fewer transactions.

We’ve got one more proposal on the way — keep your eye out for it!

How to Get Involved

The Mesa Upgrade is being proposed by o1Labs, but this is a community journey, and this Increased zkApp Limit is a proposal. We need your feedback. At the time of publication (October 9, 2025), this MIP is in the Review phase.

  • Join the conversation on Mina Research and leave comments with questions, concerns, or suggestions.