Roadmap
This section presents the three-phase product roadmap.
Aporia's development unfolds in three phases, each unlocking a qualitatively new layer of capability. Phase 1 establishes Aporia as the primary liquidity venue in the Kaspa ecosystem and begins accumulating the data that powers Phase 2. Phase 2 activates the parallel-native execution model — the core architectural innovation — upon the launch of Kaspa vProg. Phase 3 scales with Kaspa's 100 BPS upgrade and builds the programmable liquidity layer for autonomous trading agents. Each phase is a necessary precondition for the next.
Phase 1 — Establish Liquidity (Q1–Q2 2026)
Phase 1 · Establish Liquidity Q1–Q2 2026
Goal: Become the primary liquidity venue in the Kaspa ecosystem while building the EigenFlow data foundation for Phase 2
Traditional linear order book DEX on igra L2 — full CLOB with price-time priority matching, spot and perpetual markets, zero maker fees, and 0.02% taker fees from day one
Professional MM infrastructure — REST and WebSocket APIs, co-location advisory, bilateral MM agreements with quoting obligations and enhanced rebates
Liquidity incentive programme — token distributions to market makers meeting time-at-quote and spread-width performance thresholds; insurance fund seeding
EigenFlow-lite data pipeline — continuous recording of Kaspa conflict-resolution events; execution class identification; spectral kernel pre-training begins
Security and compliance — pre-launch smart contract audits published; bug bounty programme live; KYC/AML hooks active for regulated market access
Ecosystem integration — KAS and KRC-20 token listings; cross-chain EVM deposit paths via L1 Deposit Contract and third-party bridge integrations
Phase 1 is not a placeholder. It is a production-grade trading venue competing for real volume in the Kaspa ecosystem from launch. The goal is not merely to be the first DEX on Kaspa — it is to be the best DEX on Kaspa, measured by order book depth, spread quality, and market maker participation. Everything in Phase 1 is designed to win that competition with a traditional linear CLOB before the parallel-native advantage activates.
Phase 1 EigenFlow note: EigenFlow-lite runs in passive data-collection mode throughout Phase 1. It does not influence execution, optimize spreads, or interact with the matching engine. Its sole function is to observe and record Kaspa network conflict-resolution events. The richer the dataset accumulated in Phase 1, the more accurate and immediately effective the full EigenFlow kernel will be when Phase 2 activates.
Phase 2 — Unlock Parallel Execution (Q4 2026 – Q1 2027)
Phase 2 · Unlock Parallel Execution Q4 2026 – Q1 2027
Goal: Activate the parallel-native execution model, achieve +35–75% MM Sharpe improvement, and attract top-tier professional market makers
Kaspa vProg migration — matching engine migrated from igra L2 to Kaspa's native programmability layer; multi-frontier execution environment activated
Multi-frontier quoting — simultaneous quote placement across parallel Kaspa frontier views; time-to-first-accepted-execution becomes an order statistic
Full EigenFlow deployment — spectral consensus kernel goes live: acceptance-probability optimization, fee-aware ordering, and staleness premium computation in real time
EigenFlow API outputs — acceptance probability vectors, EigenFlow weight queries, spectral gap stability indicators, and recommended fee schedules exposed to market makers
MEV-priced spreads — fee-aware entropy execution eliminates the information asymmetry between ordering advantage holders and market makers; spread pricing reflects true ordering costs
Institutional connectivity — FIX protocol support for institutional market makers; Phase 2 bilateral MM agreement programme with performance-based incentives
Phase 2 MM incentives — enhanced token distributions for market makers who successfully transition to multi-frontier quoting strategies
Phase 2 is the architectural event that distinguishes Aporia from every other order book DEX ever built. The transition from single-path to multi-frontier execution is not a feature upgrade — it is a change in execution physics. Market makers on Aporia in Phase 2 operate in a categorically different risk environment from those on any linear exchange. The 35–75% Sharpe improvement documented in the EigenFlow simulation is the expected outcome of this transition.
Phase 2 timing is contingent on the Kaspa vProg launch. Aporia's architecture is designed to activate Phase 2 as rapidly as possible following vProg availability — the matching engine interface, settlement infrastructure, and EigenFlow data pipeline are all built to support the transition without a full system rebuild.
Phase 3 — Scale with Kaspa (Q2–Q4 2027)
Phase 3 · Scale with Kaspa Q2–Q4 2027
Goal: Scale to 100 BPS execution, introduce EigenBatch, and establish Aporia as Kaspa's programmable liquidity layer for human and AI-agent trading
100 BPS execution scaling — multi-path execution engine scaled to Kaspa's 100 blocks-per-second upgrade; expected tip count increase produces further execution-time concentration (+60–120% Sharpe range)
AI-agent-optimized APIs — deterministic, programmable, multi-path execution APIs designed for autonomous trading agents; structured EigenFlow outputs as machine-readable market data
EigenBatch micro-auctions — vProg-native collective execution mechanism: competing quotes aggregated into single cryptographically proven clearing events; stale-tip routing attacks eliminated at the mechanism level
Advanced MM tooling — multi-frontier inventory management, automated spectral gap monitoring, and AI-assisted spread optimization for sophisticated market making strategies
Ecosystem expansion — additional instrument listings, cross-chain liquidity aggregation, and integration with emerging Kaspa DeFi infrastructure
Aporia as infrastructure — Aporia transitions from a trading venue to a programmable liquidity layer: open APIs enabling third-party protocols to route execution through Aporia's parallel-native order book
Phase 3 vision: At 100 BPS, Kaspa produces 100 parallel blocks per second — more simultaneous execution paths than any other network by an order of magnitude. At that scale, EigenFlow's time-concentration effect reaches its maximum simulated uplift of 60–120% Sharpe improvement over single-path strategies. Aporia at Phase 3 is not just a DEX — it is a execution-physics-native liquidity layer that will serve as infrastructure for the next generation of both human-operated and AI-driven trading strategies on Kaspa.
The Liquidity Flywheel
Each phase of the roadmap feeds a compounding flywheel that connects execution quality, market maker economics, liquidity depth, trading volume, and EigenFlow data quality in a self-reinforcing loop. The flywheel is the reason first-mover advantage on Kaspa is durable rather than transient.
Lower Exec Risk
→
Tighter Spreads
→
Higher MM Sharpe
→
Better Market Makers
↑
↓
Better Kernel Data
→
More Volume
→
Better Prices
→
Deeper Liquidity
The Aporia liquidity flywheel — each node feeds the next; the loop compounds with time and data
In Phase 1, the flywheel is powered by the liquidity incentive programme — artificial stimulus to bootstrap the cycle. In Phase 2, EigenFlow replaces the stimulus: the structural reduction in inventory risk drives real improvements in MM economics that sustain the flywheel without subsidies. In Phase 3, the flywheel's inputs grow in quality as Kaspa's block rate increases and EigenFlow's dataset deepens — compounding the advantage further with every additional block.
Last updated