Mesa features

[cjjdespres]

I'm creating this issue to track the things we have already done in develop, or plan to do but haven't done, or will likely do (pending MIP voting, etc.), or features implemented in preparation for Mesa. A general tracking issue.

Stable changes

• Mina daemon tracks the planned genesis slot for upcoming hard forks in its runtime config.
• Mina daemon tracks the name of the chain it's currently running (berkeley) in its runtime config. (Doesn't necessarily have to be a runtime config option, I suppose).
• Mina daemon tracks the planned chain name for upcoming hard forks (e.g., mesa for the next one) somehow (maybe in runtime config?)
• Zkapp fallback logic applies to overall access too. See Resolve the possible zkApp fallback logic issue #17852. This is only relevant when hard forks happen, when the relevant version number increases.
• "Auto mode" option for scheduled hard forks

Mesa-Berkeley incompatibilities

• Mina daemon keeps its chain state in /chain-state/mesa-{network} in the mina config directory, and not / (the top level). The {network} will be mainnet or devnet. The mesa part will be the name of the chain the daemon thinks it's running (Set the chain name to Mesa in develop #18044).
• RPC versions increased. This will be done naturally as the relevant versioned types get updated; there may be more, but it shouldn't have to be tracked. Related: Increment versions for app state increase #17388, for state size increase (gossip messages, etc.) and Update SNARK worker & minimize data pased on wire - develop #17822 (for snark worker messages).
• Event/Actions limit increase. Reference: MIP Ref Impl: Increase events&actions limit #17573. Merge pending MIP voting. Will be in the mesa test branch.
• Zkapp state size increase. Reference: App state32 #17462. Merge pending MIP voting. Will be in the mesa test branch.
• Action update limit increase. Reference: MIP Ref Impl: Increase zkApp account update limit #17386. Merge pending MIP voting. Will be in the mesa test branch.
• Slot time reduction to 90s. Reference: MIP 6 (slot reduction to 90s) implementation #18069. Merge pending MIP voting. Will be in the mesa test branch.
• Coinbase decease to 90s. Included in MIP 6 (slot reduction to 90s) implementation #18069, for the slot time reduction MIP. Will be in the mesa test branch.
• Removing the zkapp soft limit. Included in MIP 6 (slot reduction to 90s) implementation #18069, for the slot time reduction MIP. Will be in the mesa test branch.
• Protocol version bump