Addresses & networks
Canonical contract addresses and endpoints for Aquarius on mainnet and testnet.
Last updated
Canonical contract addresses and endpoints for Aquarius on mainnet and testnet.
The single source of truth for Aquarius deployment addresses. All values are verified against the production application configuration.
Provider-fee collector factory
AQUA asset
AQUA:GBNZILSTVQZ4R7IKQDGHYGY2QXL5QOFJYQMXPKWRRM5PAV7Y4M67AQUA
Backend API
https://amm-api.aqua.network/api/external/v2 (spec)
Soroban RPC
https://mainnet.sorobanrpc.com
Horizon
https://horizon.stellar.org
AMM router
CBCFTQSPDBAIZ6R6PJQKSQWKNKWH2QIV3I4J72SHWBIK3ADRRAM5A6GD
Test assets issuer (AQUA, USDC, USDT, …)
GAHPYWLK6YRN7CVYZOO4H3VDRZ7PVF5UJGLZCSPAEIKJE2XSWF5LAGER
Backend API
https://amm-api-testnet.aqua.network/api/external/v2
Soroban RPC
https://soroban-testnet.stellar.org:443
Horizon
https://horizon-testnet.stellar.org
Friendbot (account funding)
https://friendbot.stellar.org?addr=<PUBLIC_KEY>
Pool addresses are not listed here — pools are deployed permissionlessly and discovered at runtime: call get_pools(tokens) on the router, or query the Backend API /pools/ endpoint.
Stellar testnet is wiped 2–4 times per year, but Aquarius redeploys from a pinned deployer seed — the testnet addresses above are expected to persist across resets, and the test-asset issuer keeps its keys. State (pools, balances) is recreated each time; if a value here disagrees with the live deployment right after a reset, the rebuild may still be in progress — see Testing on testnet.
Last updated