Aptos Foundation official logomark (aptos.dev)
Aptos unveils MonoMove, claiming up to 55x faster smart contract execution
The Move VM redesign posts big gains on replayed DecibelTrade transactions, but mainnet is not planned until 2027 and still needs governance approval
Aptos has introduced MonoMove, a new execution engine it says can run smart contracts up to 55 times faster for onchain markets.
Blockchains usually market speed through transactions-per-second figures. MonoMove targets a quieter bottleneck: how fast the virtual machine actually processes the code inside each transaction.
What MonoMove actually changes
MonoMove is a complete redesign of the Move virtual machine (VM) and the execution stack around it. Aptos is building a new one rather than tuning the old one.
The redesign has two goals. The first is better single-thread performance, meaning how fast one processor core gets through a job. The second is parallelism, meaning how many jobs can run side by side without stepping on each other.
Two technical choices drive the design. MonoMove uses monomorphized micro-ops and a register-based interpreter.
Monomorphization means generating specialized versions of code ahead of time. The engine then avoids figuring out data types on the fly while a transaction runs. A register-based interpreter works with values held in named slots instead of constantly pushing and popping them from a stack. Both approaches aim to cut wasted work from every instruction.
MonoMove has already been integrated into Aptos’s block executor, the component that processes transactions in each block. Development is moving through numerous GitHub pull requests over the course of 2026.
The benchmark numbers
The headline figures come from internal benchmarks. Aptos replayed real mainnet transactions from DecibelTrade and compared MonoMove against the previous VM.
The results, by transaction type:
- Collateral withdrawals: up to 55x faster
- Vault requests: up to 40x faster
- Perpetual market requests: up to 38x faster
- Order placements: up to 22x faster
End-to-end benchmarks showed throughput gains of 3-8x across workloads. Order-book matching improved approximately 7x. Liquidity-pool swaps improved 5-7x. Lending markets were also part of the tested workloads.
The gap between 55x and 3-8x is worth understanding. Execution is only one stage of processing a transaction.
AI, tech, and the markets they move—in one daily briefing.
Daily. Free. Join 34,000+ readers across crypto, finance, and policy.
A 3-8x throughput improvement also compares favorably with the roughly 2x gains Aptos got in 2025 from Loader V2, an earlier performance upgrade.
The road to mainnet
MonoMove is not live for users yet, and the timeline runs past this year.
The development plan moves in stages. It starts with sequential execution, where transactions run one after another. It then builds toward advanced parallel support.
Several features still have to be built along the way. These include native function ports, reentrancy checks, and gas instrumentation.
Reentrancy checks guard against a classic exploit in which a contract gets called back into before it finishes its first job. Gas instrumentation is the metering system that measures how much computation a transaction uses, so users pay for what they consume.
Aptos is targeting completion of the full feature set by the end of 2026. A mainnet rollout is planned for 2027, contingent on governance approval.
To make sure the new engine behaves exactly like the old one, Aptos has set out plans for differential testing and formal verification against the legacy AptosVM. Differential testing feeds identical inputs to both engines and flags any mismatch. Formal verification uses mathematical proofs to confirm the code does what it claims.
The redesign is also meant to stay within Move’s resource-oriented safety model while adding runtime checks. Move treats digital assets as resources that cannot be copied or accidentally destroyed.
What this means for Aptos and onchain trading
The benchmark choice says a lot about where Aptos is aiming. Collateral withdrawals, vault requests, perpetual market orders, and order placements are the core plumbing of onchain derivatives and trading venues.
Several risks deserve attention. The 55x figure is an upper bound from internal tests on one application’s replayed transactions, not an independent audit. Production conditions could look different once the full feature set, including gas metering and reentrancy protection, adds its own overhead.
Feature completeness by the end of 2026 is a target, not a guarantee.
Watchers have a few concrete milestones to track. One is the pace of MonoMove pull requests through 2026. Another is whether parallel execution support lands on schedule. A third is the results of differential testing against the legacy AptosVM. The final checkpoint is the governance proposal that would bring MonoMove to mainnet in 2027.