Update docs to reflect all MESA and o1js 3.0 changes#1166
Update docs to reflect all MESA and o1js 3.0 changes#1166Shigoto-dev19 wants to merge 6 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Nice job @Shigoto-dev19 ! |
| | ------------- | -------------------- | | ||
| | Slot duration | 90 seconds (1.5 min) | | ||
|
|
||
| The 50% reduction in slot time means blocks are produced twice as frequently, which roughly halves the time it takes for transactions to be included in a block. |
There was a problem hiding this comment.
According to Yasin's message on Telegram
During high-load stress tests, initial results revealed RAM spikes that could lead to "Out of Memory" (OOM) issues for some node operators. To ensure the Mesa Upgrade is a smooth experience for all operators regardless of hardware, we have made a temporary adjustment to the zkApp transaction limit, which will be lowered to 12 per block from the current 24.
Because Mesa halves slot time down to 90 seconds, keeping the limit at 12 results in the same total zkApp throughput as Berkeley supports with 24. This means zkApps have the same capacity, but with faster confirmations.
Should we say something about this here or because it is temporary there's no need?
I am referring to the "halving time" here concretely
There was a problem hiding this comment.
That's a valid point; because it's temporary I think we should keep it in mind as part of the changes to apply at merging time.
3 participants
Partly closes o1-labs/o1js#2639.
Summary
Documents all Mesa upgrade changes (MIPs 6-9) across the documentation.
Changes
New page added
Mesa upgrade overview: added a new page documenting all four MIPs with before/after comparison tables
MIP-6: Slot Time Reduction
180s→90s720→360MINA14days → ~7days2-4weeks →1-2weeksMIP-7: On-chain State Expansion
8→32MIP-8: Events/Actions Capacity
100→1,024field elementsMIP-9: Account Update Limits
Note
References