Concepts
The minimum vocabulary developers need (without internal details).
Virtual liquidity
Virtual liquidity is an accounting model where allocations and balances are tracked in a way that allows one balance to be used across multiple strategies (within constraints), without requiring a traditional “custody pool” per strategy.
Strategies
A strategy is a reusable configuration for how liquidity is deployed and how execution happens.
From an integrator’s perspective, you can treat strategies as:
- a set of available liquidity sources/options
- with user-facing metadata (risk, fees, performance history when available)
Cross-chain swaps
Cross-chain swaps require coordination. As an integrator, you should treat them as asynchronous operations with:
- a start request
- intermediate states
- a finalized outcome
Cross-chain LP vault movement
LP liquidity is moved between chains (e.g. Base ↔ Unichain) via Stargate and Composer. The home chain is Base. When funds are bridged to another chain, they are delivered to a VaultComposer contract, which forwards them to the user's Vault and triggers a deposit into Aqua so that the vault remains the maker on the destination chain. See the repo root doc ARCHITECTURE_CROSSCHAIN.md for the full design (contracts, flows, and security).