Docs · Roadmap
Path to mainnet
Atrium runs on two testnets today. This page is the honest, verified account of what each venue looks like on mainnet: which connect directly on Arbitrum One, and which live on other chains and are reached cross-chain. The split was verified against on-chain contracts and official deployment registries, not assumed. Six of nine are native on Arbitrum One; three are inherently cross-chain because they are literally other chains.
Six venues are native on Arbitrum One
The protocol is deployed on Arbitrum One mainnet, so the adapter calls it directly. No bridge. On mainnet the only change from testnet is binding the adapter to the real contract instead of the Atrium mock used on Sepolia.
| Venue | On Arbitrum One | Note |
|---|---|---|
| Aave V3 | Pool 0x794a61358D6845594F94dc1DB02A252b5b4814aD | Read on-chain (chainId 42161) |
| GMX V2 | ExchangeRouter 0x1C3fa76e6E1088bCE750f23a5BFcffa1efEF6A41 | Arbitrum-native; order-based + keeper execution |
| Curve | Native on Arbitrum One | Stable/crypto pools |
| Pendle V2 | Native on Arbitrum One | Yield / PT-YT markets |
| Morpho Blue | Native on Arbitrum One | Isolated lending markets |
| Synthetix V3 | Native on Arbitrum One | Perps / synths |
Three venues connect cross-chain
These protocols are not on Arbitrum One, so a native adapter cannot call them directly. They are reached through a verified cross-chain mechanism. This is by design, not a gap: they are different chains.
| Venue | Home chain | How Atrium reaches it |
|---|---|---|
| Hyperliquid | Hyperliquid L1 (its own chain) | Validator-signed attestation: a validator signs each action, the adapter verifies the signature on Arbitrum, the result is recorded on-chain. |
| Polymarket | Polygon | Chainlink CCIP message-passing from Arbitrum to the venue chain and back. |
| Trade.xyz | Hyperliquid L1 | Same path as Hyperliquid: validator-signed attestation. |
Honest caveats
- Aave V3, not Aave Horizon. The base Aave V3 lending protocol is live on Arbitrum One. The permissioned Horizon RWA / tokenized T-bill market the adapter is named after launched on Ethereum mainnet only. The adapter is a generic Aave V3 pool adapter, so on Arbitrum One it does generic Aave V3 USDC lending, not the Horizon RWA market. Earning real Horizon yield would need a separate cross-chain path to Ethereum.
- The adapters are still work to wire.The venues are real and verified, but today's adapters are testnet scaffolds and mocks. Mainnet means replacing each stub with the venue's real ABI (for example GMX V2 is order-based and asynchronous,
createOrderplus keeper execution, not a synchronous open/close call). The contracts are real; the integrations are the build. - Mainnet posture. Testnet runs a single deployer admin; the mainnet target is a 3-of-5 multisig plus a 48-hour timelock, stated on /security.
Live addresses for both testnets are on /architecture, and the per-venue testnet status is on /docs/honesty.