As we continue on the Road to Mesa Upgrade, each proposed MIP is about unlocking more of Mina’s potential while keeping its foundation secure and succinct. The Slot Reduction MIP (our first stop on the journey) was all about speed — faster slots, quicker confirmations, more throughput. The On-Chain State MIP focused on expanding the amount of data zkApps can store directly on Mina, making them more expressive and easier to build. This proposal builds on the last MIP and focuses on flexibility, providing zkApp developers with the breathing room to build richer, more useful applications, and preparing for Mina’s next chapter.
First, What Are “Events” and “Actions”?
If a zkApp is like a smart contract program running on Mina, then events and actions are how that program interacts with the blockchain world around it.
- Events: pieces of information a zkApp can publish to the chain — they’re like “logs” or breadcrumbs that apps (and users) can reference later.
- Actions: tasks that a zkApp expects the chain (or other parties) to eventually process — they’re how apps trigger or request follow‑up work.
Currently, Mina enforces strict limits — only 16 per account update, max 100 field elements in total for events and for actions. That restraint was set early on to keep performance safe while zkApps were still new.
But those limits are showing their age, it’s time to significantly raise these limits.
What’s Changing?
This MIP proposes:
- Over 10X Capacity
- Raise the cap from 100 to 1024 field elements for both events and actions, per transaction.
- No Small Caps Within
- Remove the per‑event / per‑action mini‑cap of 16 field elements. Developers can now design larger, more expressive events or actions when needed.
In other words: each zkApp transaction can now “carry” a lot more information and instructions, enabling richer applications.
Why Does This Matter?
- Better User Experience
Today, a single app interaction might require several separate approvals (and multiple transaction fees). With this change, more can happen inside one transaction. End users just click once — done. - More Powerful zkApps
Developers get headroom to design advanced apps — such as zk voting systems, decentralized identity tools, or integrations with off‑chain data — without splitting logic unnaturally across many pieces. - Staying Competitive
Other smart contract platforms already allow large, complex logic inside one transaction. Increasing Mina’s limits lets zkApps compete on capability while still offering unmatched succinctness.
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 (this MIP) → More expressive applications.
And more proposals on the way — each raising Mina’s capabilities while keeping it lightweight and succinct.
How to Get Involved
The Mesa Upgrade is a community journey, and this increased zkApp limit is a proposal—not a decree. Feedback is essential. At the time of publication (October 1, 2025), this MIP is in the Review phase.
- Join the conversation on Mina Research and share your thoughts, questions, concerns, or suggestions.