• Mina Protocol’s Fall 2025 Hard Fork: Roadmap Explained
• 1 - Faster Blocks & Higher Throughput
• 2 - Expanded zkApp Capabilities
• 3 - Improved Staking and Governance
• 4 - Node Performance and Developer Tools
• Timeline for Launch?
• Explained: Benefits to Users, Builders, and Operators
• Working Together: Encapsulate x Mina Protocol
• More Blog Posts
• Subscribe to newsletter

Mina Protocol’s Fall 2025 Hard Fork: Roadmap Explained

The Mina team at O(1) Labs has outlined a detailed proposal for the next major network upgrade, targeted for Fall 2025. This hard fork builds on progress since the Berkeley upgrade, promising faster performance, expanded zkApp functionality, and smoother operations for developers and validators. Below we summarize and explain how they benefit end users, developers, and node operators.

1 - Faster Blocks & Higher Throughput

A headline feature of the hard fork is reducing the block slot time. Mina’s current slot length of 180 seconds slows down transaction finality and overall throughput. In testing, the team has already validated 90-second slots under heavy load with no issues. The formal MIP will specify the final value, but cutting slot time roughly in half will make blocks happen more frequently.

• Faster finality for users: Shorter slot times mean transactions and zkApp events confirm more quickly, improving the user experience.
• Increased network throughput: More frequent blocks increase the network’s capacity. In fact, the upgrade also raises block space to accommodate larger zkApp transactions. Combined with the shorter slots, this allows the chain to handle higher demand (for example, processing many staking payouts at epoch transitions) with less congestion.

These changes make Mina more scalable: users see faster confirmations, and validators benefit from higher transaction capacity with minimal impact on security.

2 - Expanded zkApp Capabilities

The hard fork greatly expands what zkApps (smart contracts) can do on Mina. In particular:

• Larger Transactions: Currently each zkApp transaction required a single SNARK, which limited its size and complexity. The new upgrade will enable splitting account-update SNARKs across multiple proofs, effectively removing that cap. Mina’s team expects at least a 2x increase in transaction size (with potential for even more improvements).
• More Events and Actions: Berkeley imposed a modest limit (∼16 field elements) on event and action data in each account update. The upgrade dramatically raises these limits, allowing zkApps to log larger events or queue more actions. This supports advanced features like including full Merkle tree proofs in on-chain events.
• Bigger zkApp State: The maximum state an account can hold is going from 8 field elements to 32. This fourfold increase lets developers store more data in an app’s on-chain state. It also helps remove race conditions in complex apps, since contracts no longer have to split their state awkwardly. Overall, this makes building rich dApps easier while preserving efficient proofs.
• Historical Preconditions: zkApps will gain the ability to “look back” at recent blocks when executing. This means a contract can reliably use chain-generated randomness or assert past state by reading the block history. For example, a lottery zkApp could draw a random number from a past block hash. This historical look-up feature unlocks many new use cases and verifiability by tying a contract’s logic to the recent past.

Together, these zkApp upgrades will empower developers to write more sophisticated and data-rich smart contracts. End users will benefit from richer applications (e.g. DeFi apps with larger states or complex logic), and contracts can interoperate with more powerful features (bigger events, full Merkle proofs, etc.).

3 - Improved Staking and Governance

• Automated Staking Payouts: Mina plans to introduce an automatic mechanism for distributing staking rewards. Currently, payouts occur via manual transactions; automating this will simplify the staking experience. The design is nearing completion and will be refined with community feedback, aiming to include it in the upgrade. This benefits stakers by reducing manual steps and ensures validators get reliably paid on schedule.
• On-Chain Governance: The developers are prototyping on-chain voting and decentralized treasury systems, but these are not included in the initial hard fork. They emphasize community input is needed for robust governance. For now, focus remains on the above improvements, with governance features to follow in future proposals after more consultation.

Overall, stakers and delegates can look forward to a smoother reward process, while broader governance changes will be planned through the community-driven MIP process.

4 - Node Performance and Developer Tools

• Partial Rust Node Integration: Mina has been developing a new Rust-based node client. Instead of waiting for a full release, the upgrade will embed well-tested Rust components into the existing OCaml node. This incremental approach yields performance and memory improvements right away, without delaying the fork. Node operators should see a leaner, faster node.
• API and SDK Enhancements: While many API redesigns are planned beyond this upgrade, the team is already working on a refined zkApp SDK/API to enhance security and composability. These improvements will make writing and auditing Mina smart contracts easier in the long run (for example, by improving state property assertions and communication between account updates).

In summary, developers will find the environment more powerful and user-friendly—larger transaction/state limits and improved tooling—while validators benefit from a more efficient node implementation and automated maintenance.

Timeline for Launch?

The improvements above will go through Mina’s MIP (Mina Improvement Proposal) process. In the coming weeks, the team will publish formal MIPs detailing each change. Based on initial feedback, they expect community review and voting to proceed smoothly. Once MIPs are approved, Mina will enter a thorough testing phase (several months long) before activating the fork. The current timeline targets mainnet deployment in Fall 2025.

Explained: Benefits to Users, Builders, and Operators

The Fall 2025 upgrade brings concrete benefits across the board:

• End Users: Faster block times mean quicker transaction confirmations and more responsive apps. New zkApp features (like on-chain randomness and richer contract state) will power more advanced dApps (e.g. gaming, DeFi). Smoother staking payouts will make earning rewards more user-friendly.
• Developers: Expanded limits (transactions, events, state) let developers build complex zkApps without hitting artificial caps. The improved API and larger data allowances make contracts easier to write and audit. More throughput and reduced congestion ensure apps run smoothly even under heavy use.
• Validators: Nodes will upgrade themselves and run with improved speed and efficiency. Faster finality (in future enhancements) further reduces risk and overhead for validators.

Working Together: Encapsulate x Mina Protocol

In summary, we at Encapsulate - being a validator on Mina, are excited to see the ecosystem grow in new directions with the new upgrade and looking forward to the enhancements to the staking infrastructure. We wish to keep supporting them in testing and feedback - to improve the overall blockchain infrastructure, like we have been doin so far - and being an active cheerleader in achieving the ambitious milestones they’ve set for themselves.

Subscribe to newsletter