Mina is proposing a pragmatic upgrade: increase the number of on‑chain state fields a zkApp account can store from 8 to 32. In plain terms, this gives zkApp developers more room to keep important application data directly on-chain—simplifying designs, unlocking new use cases, and reducing workarounds—while preserving Mina’s hallmark succinctness.
Why 8 Fields Was a Problem?
With only 8 fields, developers often had to:
- Pack multiple values into a single field (hard to maintain and error‑prone).
- Split state across multiple accounts (complex and brittle).
- Move real data off‑chain and only store a root on‑chain (added infrastructure and code complexity).
This limited advanced patterns like on‑chain order books, multi‑step protocols, richer metadata, and general developer ergonomics. Moving to 32 fields relieves this pressure without compromising network performance.
What’s Changing?
Protocol limit: Maximum on‑chain state fields per zkApp account increases to 32.
- Node behavior: Validation, block production, and transaction size checks updated to accept and enforce 32 fields; transaction version incremented.
- o1js support: Account updates, accounts, and smart contracts all support up to 32 fields.
For developers, this means native, first‑class support across the stack—no custom tricks.
Why Does This Matter?
For developers
- More room, less potential bugs: Going from 8 to 32 state fields means developers can store data directly on-chain instead of cramming multiple values into one slot, splitting across extra accounts, or pushing real data off-chain. In practice, this cuts down on boilerplate code—the repetitive, extra code developers often have to write just to work around limitations. It will also reduce bugs and make codebases easier to reason about.
- Faster from idea to production: Common patterns—multisig wallets, games, attestations, rollup settlement—no longer require complex workarounds. That shortens development time, simplifies audits, and makes iteration safer.
- Better composability: When state is stored clearly and natively, other contracts and tools can integrate more easily—no need to decode packed fields or fetch off-chain data just to understand a contract’s state.
For users
- More capable apps: Expect richer features without slow, clunky workarounds. Examples include wallets with more signers, games that update state directly on-chain each move, and tokens with meaningful on-chain metadata.
- Better reliability: Fewer external systems involved means fewer points of failure. When more data is on-chain, apps are easier to verify and less likely to break because a server went down, for example.
- Clearer transparency: With more state on-chain, it’s simpler to inspect what an app is doing. Users and explorers can view meaningful data without having to chase off-chain references.
- Lower friction and costs over time: Simplified designs tend to be cheaper and more efficient to run. That can translate into better fees, faster confirmations, and smoother UX as projects optimize.
- Stronger security: Eliminating clever packing and complex off-chain dependencies reduces the chance of subtle bugs or data mismatches. A simpler system is easier to audit and trust.
Part of the Bigger Road to Mesa Story
- Slot Reduction MIP → More speed.
- Increasing Mina’s On-Chain State Limit (this MIP) → More expressive applications and simplify zkApp development.
And more proposals on the way — each raising Mina’s capabilities while keeping it lightweight and succinct.
How to Get Involved
Upgrades like this don’t just flip on overnight—they require a protocol-level change delivered through a hard fork. That means community participation isn’t optional background noise, it’s essential.
At the time of publication September 19, this proposal is in the Review phase, where developers, node operators, and community members can share feedback on Mina Research. Your input here helps ensure the design works well for a broad range of use cases.
Once all Mesa Upgrade proposals are finalized, they’ll move into an on-chain vote. That vote is what determines whether this change—and the rest of the Mesa Upgrade—actually goes live. If you care about how Mina evolves, staying informed and casting your vote is one of the most direct ways to shape the protocol’s future.
- Join the discussion: Share questions or suggestions on Mina Research.
- Stay tuned: We’ll post updates on X as the proposal moves through Review, Last Call, and toward voting.