Skip to content

BLOCKCHAIN LAB BRIEFING · ETHEREUM

Faster Contracts Are Not a Faster Market.

Aptos says MonoMove executes selected financial transactions up to 55 times faster in internal replays, and up to 11 times more sequential throughput end to end. Mainnet is a 2027 question, after a vote.

Internal replay, DecibelTrade mainnet transactions

Fig. 01

Maximum reported execution speed-up. Not network throughput.

“Up to” is the project’s own qualifier. These bars are the ceiling of selected operations in Aptos’s tests, not a measured confirmation time for users.

Aptos, as reported with the 6 October 2026 announcement. Not an independent re-run.

01

What happened

On 6 October 2026 Aptos introduced MonoMove, a rebuild of the Move virtual machine and the execution stack around it. The project replayed real mainnet transactions from DecibelTrade and reported maximum execution gains of 55 times on collateral withdrawals, 40 times on vault requests, 38 times on perpetual-market requests, and 22 times on order placement.

A separate internal benchmark, covering order books, liquidity, lending, oracle updates and payments, reported up to 11 times higher end-to-end sequential throughput, before further optimisation and before Block-STM. Feature completeness is expected by the end of 2026. Mainnet is planned for 2027, after a governance vote.

02

Why it matters

The workloads are the right ones to care about. Collateral, vaults, perpetual markets and order entry are the loop of an on-chain venue, not a toy transfer. If the gains survive production, an application can do more inside the same execution budget, or attempt logic it currently cannot afford.

The sentence that does not follow is “every on-chain market runs 55 times faster.” Execution is one stage. Propagation, consensus, storage and the application’s own responses sit outside that stage. Aptos itself says the bottleneck has moved toward the path between execution and storage.

A second metric, and a calendar

Fig. 02

The number in the headline is not the number in the path.
  • 11×Maximum reported end-to-end sequential throughput
  • 2026Feature completeness, expected, not shipped
  • 2027Mainnet, planned, after a governance vote
  • 0Independent production measurements in hand

End-to-end sequential throughput is a different test from the single-operation ceilings above. The rollout is still a development programme.

Aptos announcement, 6 October 2026.

03

The operating layer

A user’s wait is the whole path. Cutting one contract step from a hypothetical 55 milliseconds to 1 millisecond is a 55-times execution change and a barely visible confirmation change if the rest of the path is still long. Headroom is not the experience.

The safety claim has to be read apart from the speed claim. MonoMove keeps Move’s rules on creating, copying and transferring assets, and Aptos describes extra runtime checks plus differential testing against the current engine. Performance numbers do not prove those checks. Formal verification of critical components is described as still to come.

04

What is verified

The figures above are Aptos’s reported internal results, published with the announcement and repeated in contemporaneous coverage. They are replays and simulations. They are not a live mainnet upgrade, and they have not been independently reproduced for this article.

The timetable is also the project’s: feature-complete around the end of 2026, mainnet in 2027 if governance agrees. That is a plan, not an activation.

05

What remains unclear

Results with every production safeguard switched on, on representative validator hardware, over a sustained period. Whether the 11-times path holds once parallel execution and storage limits are in the measurement.

Fees, liquidity and product safety. None of those are implied by a faster virtual machine.

06

The catch

Faster contract execution creates room. End-to-end performance is what a trader feels. Aptos has published a serious execution programme aimed at real financial workloads, with a benchmark table that is more careful than the slogan wrapped around it.

Until the vote, the mainnet, and a number someone else can rerun, “55 times” belongs on the operation it was measured against. It does not belong on the network.

WATCH

What builders should watch

  1. 01A reproducible benchmark with production checks enabled.
  2. 02The governance vote, and what exactly it activates.
  3. 03User-visible confirmation time, not only virtual-machine time.

BOTTOM LINE

MonoMove is a proposed execution upgrade with large internal numbers and a 2027 mainnet plan. It is not a live 55-times market.

Sources

The documents are below. A chart is a reading of those documents, not a recommendation to buy or sell anything.

Continue