APEX

APEX runs transactions in parallel. Every transaction that does not touch the same state executes at the same time, on its own core, with no coordinator deciding the order. Add cores, add throughput.

what it does

What APEX Does

Most chains run transactions one after another. APEX runs every non-colliding transaction at once, so the work spreads across cores instead of waiting in line.

composition not collision

Composition, Not Collision

Two transactions that never touch the same state reach the same result in any order. APEX proves which transactions are independent and runs them together, with no lock and no replay.

exact conflict detection

Exact Conflict Detection

APEX catches the exact moment two transactions touch the same state, and only those wait their turn. Everything else keeps moving.

linear scaling

Add a Core, Add Capacity

Throughput rises with the number of cores, not the speed of any one. The engine grows by widening, not by pushing a single core faster.

zero proving overhead

Zero Proving Overhead

Parallel execution adds nothing to the proof. The prover sees the same work whether it ran in parallel or in sequence, so the speedup is free.