How it works

Aqua0 routes traders through one of two execution venues, both settling against the same per-asset AssetVault on each chain. The vault tracks each strategy's backing in its own on-chain record, with its own idle/deployed balance, drawn from a shared pool of liquidity-provider principal, and adapters pull and push tokens against it only mid-swap.

How a trade fills

Locked liquidity from the shared pool fills a trade just-in-time, in one transaction, without the trader interacting with any liquidity provider directly.

No liquidity sits idle in a single pool, it's pulled in only when a real trade needs it, so the same locked-liquidity position can fill trades this way across many pools.

Your liquidity works across chains

You keep one locked-liquidity position, and it isn't confined to the chain where it was locked, it can back a strategy on a chain where you hold no local position at all. A local liquidity provider fills the trade there instantly, and your capital settles the difference behind the scenes, without you doing anything.

See Non-custodial design for the guarantees behind that settlement step.

The rest of this page goes one level deeper, into the two execution venues and how they route a trade against the vault.

1inch Aqua, single-chain

• LP locks liquidity into the vault, credited as principal.
• The operator ships the strategy into 1inch Aqua's virtual ledger, and the ship is authorized by that strategy's strategist signature, not the operator alone.
• A trader hits AquaSwapVMRouter.swap, and the router's maker hooks pull and push tokens against the vault mid-swap through the AquaAdapter.
• The router emits Swapped, and the backend attributes the delta pro-rata across the strategy's backers.

No on-chain attribution writeback happens beyond the settlement itself, since the vault's role ends at the swap.

Uniswap V4, single-chain

• The backend signs an EIP-712 JITPayload for the trade.
• The trader submits a V4 swap with the payload as hookData.
• The V4Adapter (itself the Uniswap V4 hook) injects a temporary range at beforeSwap, then removes it and settles the net deltas back to the vault at afterSwap.

Cross-chain

Capital in one chain's vault can also back a strategy or JIT fill that executes on another chain. The source vault carries that in-flight position under a bounded, monitored valuation until the destination settlement lands and reconciles it exactly, see Non-custodial design for the guarantee behind that step.