|
| 1 | +--- |
| 2 | +sidebar_position: 3 |
| 3 | +--- |
| 4 | + |
| 5 | +# Mesa upgrade |
| 6 | + |
| 7 | +The Mesa upgrade is a hardfork of the Mina Protocol that introduces several |
| 8 | +enhancements to zkApp capabilities. This page tracks the implementation of these |
| 9 | +features in the Rust node. |
| 10 | + |
| 11 | +## Overview |
| 12 | + |
| 13 | +The Mesa upgrade consists of three main protocol improvements: |
| 14 | + |
| 15 | +### Account update limit increases |
| 16 | + |
| 17 | +Increases the number of account updates allowed per transaction from 10 |
| 18 | +signature-based and 5 proof-based updates to roughly triple those limits. This |
| 19 | +enables more complex zkApp logic to be executed in fewer transactions. |
| 20 | + |
| 21 | +- **Blog post**: |
| 22 | + [Road to Mesa: Performance Dialed Up for zkApps](https://www.o1labs.org/blog/account-update-limit) |
| 23 | +- **Implementation status**: To be tracked |
| 24 | + |
| 25 | +### Events and actions capacity expansion (MIP-8) |
| 26 | + |
| 27 | +Increases the field element limit from 100 to 1024 for both events and actions |
| 28 | +per transaction, and removes the per-event/per-action mini-cap of 16 field |
| 29 | +elements. This allows zkApps to carry more information and instructions in a |
| 30 | +single transaction. |
| 31 | + |
| 32 | +- **Blog post**: |
| 33 | + [Road to Mesa: Preparing for the Next Chapter with More Use Cases](https://www.o1labs.org/blog/mip-8-events-actions) |
| 34 | +- **Implementation tracking**: |
| 35 | + [#1261](https://github.com/o1-labs/mina-rust/issues/1261) |
| 36 | + |
| 37 | +### zkApp state expansion |
| 38 | + |
| 39 | +Expands zkApp account state from 8 to 32 fields, allowing developers to store |
| 40 | +more data directly on-chain and reducing the need for external storage |
| 41 | +workarounds. |
| 42 | + |
| 43 | +- **Blog post**: |
| 44 | + [Road to Mesa: Expanding zkApp State with Fewer Constraints](https://www.o1labs.org/blog/increasing-zkapp-state) |
| 45 | +- **Implementation status**: To be tracked |
| 46 | + |
| 47 | +## Implementation tracking |
| 48 | + |
| 49 | +All Mesa upgrade work is tracked in |
| 50 | +[#1259](https://github.com/o1-labs/mina-rust/issues/1259). Each feature has its |
| 51 | +own sub-issue that includes: |
| 52 | + |
| 53 | +- Links to relevant MIPs (Mina Improvement Proposals) |
| 54 | +- OCaml node patches implementing the feature |
| 55 | +- Rust node implementation PRs |
| 56 | +- Performance benchmarks and tests |
| 57 | + |
| 58 | +## Additional resources |
| 59 | + |
| 60 | +- [Mesa Hard Fork Project Board](https://www.notion.so/o1labs/Hard-Fork-MIPs-Project-1c9e79b1f910805fb44cdc2b9db2ee8e?p=1c9e79b1f910804da24ed4f96638ab2b&pm=s) |
| 61 | +- [Mina Protocol Website](https://minaprotocol.com/) |
0 commit comments