Aptos unveils MonoMove engine for faster contract execution
Tech & Launches ·
The network's new execution engine aims to cut smart contract processing time dramatically, with mainnet deployment targeted for 2027 pending community approval.
Aptos Labs has introduced MonoMove, described as the most significant scalability overhaul the network has seen, with collateral withdrawals processing up to 55 times quicker than on the current virtual machine, according to an announcement posted on X. The upgrade also reported gains across other functions tested against real DecibelTrade transaction data: vault requests sped up by as much as 40x, perp market requests by up to 38x, and order placement by up to 22x.
The project is built around reworking the Move VM and its surrounding execution stack, a shift aimed at handling the kind of continuous, high-stakes activity that onchain markets require, from order books and collateral checks to price feeds and payouts. Early internal benchmarks modeling complex financial activity, including order book trades, lending platforms, and payment flows, showed throughput improving by up to 11x end-to-end compared to the existing VM, even before additional optimizations or Block-STM integration are applied.
That detail points to where Aptos Labs says the next bottleneck lies: not execution, but storage. The team has characterized the current results as a starting point rather than a ceiling, suggesting further gains may depend on separate infrastructure work still ahead.
On security, MonoMove keeps Move's existing asset-handling rules intact while introducing extra runtime checks meant to catch verifier or VM implementation bugs, an approach intended to eliminate certain categories of errors by design. Aptos Labs is also applying differential testing to compare outputs between the new and current engines, with formal verification of core components planned as the system moves toward production use.
The timeline calls for feature completeness by the end of 2026, with mainnet rollout in 2027 contingent on a governance vote, a schedule confirmed in coverage of the upgrade. What remains unclear is how the throughput figures will hold up once Block-STM and further storage optimizations are layered in, and whether the governance vote required for mainnet deployment will proceed on schedule.