Metaswaps
Metaswaps lets traders exchange a token on one network for a token on another in a single transaction: one confirmation, no separate bridging step. It combines bridging, liquidity routing, and exchange into a single cross-network trade.
Most cross-network trading services rely on external solver networks or third-party bridges. Their pricing and security depend on the systems that carry the order. Metaswaps keeps the full trade within Aero: both legs execute against Aero's pools, Aero's routing picks the path, and Aero's interoperability layer, Metalane, carries the message between the networks.
Because Aero handles both sides of the trade, it can provide a single all-in quote. Order details stay hidden until execution because the transport and the trading venue are one system.
Why they exist
Cross-network trades historically have been fragmented: traders bridge tokens to the destination network in one step, then trade them in another, requiring multiple transactions and sets of fees. Worse, traders needed gas on the destination network to execute the trade, or pre-fund a relayer. Metaswaps collapse this into one transaction. Traders pick a source token and a destination token (on different networks), confirm once, and receive the output without intermediate steps or friction.
How they work
A Metaswap executes in three stages, all within a single confirmation:
- Quote stage. Aero quotes routes across pools on both source and destination networks, finding the best path for the input amount.
- Source network settlement. The source network receives the trader's input token, executes any required trade to a bridge-compatible asset, and hands the value off to Aero's cross-network transport layer (Metalane).
- Destination network settlement. The destination network receives the value via Metalane, executes any final trade, and delivers the output token directly to the trader's wallet.
What they unlock
For traders, any listed token on any network Aero serves is one confirmation away. There is no bridge tab, no destination-network gas, and no actions required on the destination network.
For token issuers, users can be reached in every network Aero serves, from day one. A trader does not need to be on the launch network, or know which network the token lives on, to trade for it.
For LPs and Token Operators, the cross-network trades settle against Aero's own pools on both legs, so volume otherwise routing through external bridges and aggregators generates trade fees in Aero pools instead. Those fees flow to Fee-earning liquidity deposits and to Token Operators as Exchange Revenue.
Cross-network mechanics
Quote and routing
Quotes update in real-time as prices change. Aero searches routes across all active pools on both networks to find the best execution for the input amount. A single Metaswap may use multiple pools on either network if the best path requires it.
Metalane transport
It is Aero's interoperability layer. Aero's Metalane infrastructure carries the cross-network message. The destination trade's parameters and recipient do not travel on the message until execution.
MEV protection
Order details stay hidden until the moment of execution. The trade is committed on the source network with its details concealed as a hash; once the message reaches the destination network, the full details are revealed and executed atomically. This two-phase approach ensures:
- Order details are not visible to MEV bots watching cross-network queues until the destination-network transaction executes.
- The destination trade's route, minimum output and recipient stay hidden until execution, which limits what MEV bots can see in advance. Protection against price movement between quote and execution comes from the slippage tolerance setting.
- If market conditions change significantly, the destination trade reverts on slippage tolerance rather than executing at a bad price.
Gas model
- Source network: The trader pays once, in the source token, when confirming the transaction that initiates the Metaswap. This covers the source-side trade and the cross-network message dispatch.
- Destination network: Gas for the destination-side trade and output delivery is estimated and deducted from the user's output. The quote reflects all fees and costs, and users receive the final amount after destination gas is accounted for.
- No destination gas pre-funding required. The trader does not need to hold gas on the destination network or pre-fund a relayer.
Metaswaps on Aero
Metaswaps automatically activate when tokens are on different networks. The following features and design principles shape how they work:
| Feature | What it means |
|---|---|
| One router, every network | Combines bridge and trade as one atomic flow, not separate steps. The path may route through multiple pools on either network as needed. |
| No dedicated liquidity or solver network | Aero's own Metalane cross-network infrastructure carries the message. Execution relies on existing onchain liquidity and Aero's routing, not external solvers. |
| MEV protection built in | Order details only land on the destination network at execution, preventing front-running from bots watching cross-network message queues. |
| TypeScript SDK for integrators | Wallets, aggregators, and AI agents can offer Metaswaps natively through Aero's SDK rather than building cross-network logic themselves. |
| Real-time quotes | Route quotes update as prices move. Slippage tolerance caps acceptable price movement and reverts if unmet. |
Configuration and behavior
The following settings control Metaswap execution:
| Setting | Description |
|---|---|
| Slippage Tolerance | AUTO by default; manual in settings to cap acceptable price movement. The trade reverts if the final route cannot meet the minimum output amount. Slippage is measured as the difference between the quoted route price and the actual execution price. |
| Finalization Time | Bounded by cross-network message latency over Aero's Metalane infrastructure, typically a couple of minutes between source-network confirmation and destination-network settlement. This includes quote finality on both networks and message dispatch. |
| Order Details Visibility | Details stay off-network during the quote phase (not visible to bots). They are hashed on the source network and revealed atomically on the destination network at execution. |
| Revert Conditions | The trade reverts if slippage tolerance is exceeded, if destination-network liquidity is insufficient, or if the Metalane message fails to deliver (rare, but the transaction is atomic on both networks). |
| Output Recipient | The trader's wallet address on the destination network. This can be a contract address as well; the trade delivers output directly to the specified recipient. |
Getting started
Open the Trade tab in the Aero app. Select a token on the source network and a destination token on a different network. Enter the amount to trade and (optionally) adjust slippage tolerance. Confirm the transaction on the source network. The destination network will finalize the trade automatically, and the output token will arrive in the wallet on that network.
For integrators and developers building Metaswap support into wallets, aggregators, or AI agents, the TypeScript SDK and technical documentation live in Aero's GitHub repositories. The SDK handles routing, quote fetching, and transaction construction.