Supported DEXes

Aqueducta currently routes across four Movement L1 DEX adapters.

What "supported" means in practice:

• the DEX is discovered into the live snapshot
• its pools can participate in route search
• the quote engine can price eligible hops for that adapter
• the on-chain execution path can execute hops for that adapter, with router_v3 as the intended public target

Deployments can still stage-gate any adapter with server configuration, but these are the integrations currently implemented in the codebase.

Yuzu

Type:

• concentrated liquidity (CLMM)

Behavior:

• quotes use pool state plus cached tick data
• best for direct CLMM liquidity and one-intermediate paths
• can degrade when tick coverage is incomplete

What to expect:

• high-quality quotes when ticks are present
• explicit diagnostics when tick coverage is missing or partial

Mosaic

Type:

• constant-product AMM

Behavior:

• reserve-based quoting
• straightforward direct-pair execution path

What to expect:

• simple, predictable quoting behavior
• useful for direct stable or paired liquidity where Mosaic has depth

Meridian

Type:

• multiple pool kinds, including stable, weighted, and metastable

Behavior:

• quote accuracy comes from pool-type-aware preview calls
• route search can include Meridian alongside other DEXes, but the final quote path still remains deterministic for a fixed snapshot

What to expect:

• good direct-pair pricing on pools where Meridian holds the best liquidity
• diagnostics if preview-based refinement is unavailable or capped

WarpGate

Type:

• Movement AMM integration with router-visible direct pairs

Behavior:

• participates in normal route search and quote ranking
• available in the public API surface when enabled by the operator

What to expect:

• direct-pair competition against the other integrated DEXes
• the same determinism guarantees as the rest of the router

Current Router Boundaries

Aqueducta does not yet do:

• split routing
• exact-out quoting
• cross-chain routing

Current quote scope is:

• exact-in requests
• single-route selection
• ranked alternatives for the same request
• deterministic output keyed by snapshot_id