Ambient networks are chain-Specific Gas and Liquidity Domains
Ambient networks are separate deployments of the Ambient decentralized exchange, each with its own gas market, smart-contract state, token inventory, and pool depth. Selecting Ethereum, Scroll, Blast, Swell, or Plume fixes where a swap settles and which liquidity it can reach. A low transaction fee does not compensate for thin reserves, while deep liquidity can justify a higher gas bill. Compare the chain-local quote, route, native gas asset, and transfer requirement before authorizing a trade.
Jump to a section
Treating Identical Tickers as Interchangeable Assets
The most common network mistake is reading a ticker without checking its chain and contract.
Chain IDs remove that ambiguity. Ethereum uses chain ID 1, Scroll uses 534352, Blast uses 81457, Swell uses 1923, and Plume uses 98866. MetaMask exposes the selected chain before signing, while WalletConnect sessions carry the requested network context. The token contract matters too: USDC, USDT, and DAI balances exist on specific networks, and a bridge representation remains a separate on-chain asset. Match the ticker, contract, chain ID, and intended pool before comparing execution. Otherwise, a familiar symbol can lead to a balance the selected Ambient deployment cannot use.
ETH pays gas on Ethereum, Scroll, Blast, and Swell; Plume uses PLUME for direct transactions.
Moving a token to a new chain requires a bridge or chain-specific withdrawal before Ambient sees the asset. That move adds a separate fee, waiting period, and settlement path. Compare destination pool depth before transferring funds. An already funded chain with slightly higher gas may beat a cheaper destination requiring another network transfer.
Network Choice Sets the Cost Boundary
Network choice fixes the gas market and pool inventory available to an Ambient transaction.
Native Gas Follows the Selected Chain
On Ethereum, a type 2 EIP-1559 transaction carries maximum-fee and maximum-priority-fee fields. Scroll, Blast, and Swell also meter execution in ETH, while Plume meters direct execution in PLUME. Layer 2 quotes incorporate local execution and network-specific data costs. An EIP-712 relayer changes the paying account, not the existence of a network cost.
Liquidity Ends at the Deployment Boundary
Each Ambient deployment holds independent CrocSwapDex state. The same ETH/USDC label on Ethereum and Scroll points to separate reserves, price curves, fees, and LP positions. Price impact follows the trade size relative to active liquidity at that moment. Concentrated positions count only where their ranges overlap the pool price, so displayed total value does not describe the complete execution path.
Bridge Overhead Rewrites the Comparison
A bridge adds another transaction path before the trade begins. Its fee, arrival asset, finality process, and destination gas balance all belong in the route comparison. A low-gas deployment wins only when its quote remains better after those additions. An exchange withdrawal provides a different destination-funding path, while staying on the funded origin chain avoids cross-chain overhead.
One Contract Keeps Each Deployment Local
Ambient's CrocSwapDex contract keeps every pool on a selected network inside one deployment. A 1-hop route touches 1 pool, while a 2-hop route touches 2 pools. Ambient nets intermediate token debits and credits before settlement, so temporary legs do not create separate ERC-20 transfers. That architecture reduces token-transfer calls inside one deployment. It does not expose an Ethereum pool to Scroll or Plume; a cross-chain aggregator remains a separate alternative.
How Should You Compare a Route Before Signing?
A useful route comparison follows the transaction from network selection through final on-chain settlement.
Request comparable quotes for the same input amount on every funded candidate chain. Record expected output, minimum received, route pools, and network cost in a common unit. Add each required funding step before ranking the routes.
| Stage | Visible Evidence | Decision | Custody or Control Model |
|---|---|---|---|
| Select Network | Wallet network and chain ID | Choose the chain holding usable funds and gas | The wallet controls the active network context |
| Fund Destination | Chain-local token and gas balances | Use existing funds, a withdrawal, or a bridge | The origin wallet controls initiation; the transfer mechanism controls transit |
| Verify Pair | Token addresses and pool identifier | Match the exact assets to the intended pool | The user retains tokens before authorization |
| Retrieve Quote | Output, fee, price impact, and hop count | Compare the same input amount across candidates | The read-only quote changes no balances |
| Choose Settlement | Wallet transfer or surplus balance | Select direct or internal settlement for each side | CrocSwapDex holds surplus tokens and records the user's credit |
| Sign Authorization | Chain ID, allowance, calldata, or EIP-712 message | Authorize the selected route and limits | The wallet key controls authorization |
| Reconcile On-Chain State | Transaction receipt, output balance, or LP position | Confirm the state on the selected chain | CrocSwapDex settles atomically; the user controls the resulting wallet balance or position |
Across Ambient networks, use one measurement window because pool state and gas conditions move independently. Convert each network fee into the output asset using the same reference price, then subtract it from expected output. Include a bridge or withdrawal charge only for routes requiring destination funding. Preserve the quote's minimum received amount as the execution boundary rather than treating expected output as guaranteed. If two routes finish close together, prefer the chain already holding the desired asset and gas; it removes an extra settlement path without assuming future pool depth.
This ranking favors net delivered value over the lowest standalone gas estimate.
Gasless Settlement Moves Payment, Not Cost
Gasless Ambient settlement changes who submits the transaction and which asset pays its cost.
With EIP-712, the wallet signs structured data off-chain. A relayer sends the on-chain call, pays the chain's native gas asset, and receives an optional tip in an accepted token or surplus balance. The action still executes against the selected CrocSwapDex deployment. This route serves a wallet without ETH or PLUME, while relayer availability and the quoted tip remain part of the transaction cost.
Surplus collateral is an internal balance recorded by one Ambient deployment, not a balance shared across networks. Ambient represents settlement choices in an 8-bit mask: 0x1 selects surplus on the base side, 0x2 selects surplus on the quote side, and unused bits stay zero. Direct ERC-20 settlement puts tokens in the wallet after each action. Surplus settlement reduces repeated token transfers, making it stronger for recurring activity than isolated trades.
Pool Encoding Explains Quote Precision
On the same footing, Ambient's field encoding explains how pools, prices, quantities, and fee settings remain chain-specific, as documented in practice.
Pool and Quantity Fields
Importantly, Ambient identifies pool types with a 256-bit index, and its standard pool type uses index 420. Permissioned pools encode their oracle address in the leading 160 bits. Token quantities use signed or unsigned 128-bit integers and retain raw ERC-20 decimals. An integration must therefore combine chain ID, token address, and pool type instead of caching a pair symbol alone.
Prices and Ticks
Curve prices use Q64.64 fixed-point square roots, allocating 64 bits to each side of the radix point. Signed 24-bit ticks map prices through a 1.0001 ratio base. Raw token quantities do not normalize ERC-20 decimals, so an interface or SDK must apply each token's decimal scale before displaying a human price. A cross-network comparison built from raw fields alone will misstate the quote.
Fee Units and Dynamic Policy
Before any of that matters, Ambient encodes each pool liquidity fee in an unsigned 16-bit field whose unit is 0.0001%. The field provides precision, not a fixed fee tier. A policy oracle updates a pool's fee, and the fee policy samples returns in 60-minute windows. Read the live quote for the selected network and pool.
Uniswap V3 separates fixed tiers into different pools; Ambient adjusts one standard pool type through policy, so cached fee assumptions age quickly.
Edge Cases That Change the Winning Network
Three network edge cases frequently overturn an Ambient route chosen from gas estimates alone.
Native Assets and the Zero Address
EVM token addresses are 160 bits, or 20 bytes. Ambient represents the selected chain's native asset with zero address 0x0 instead of an ERC-20 wrapper. On Ethereum, Scroll, Blast, and Swell, that native leg is ETH; on Plume, it is PLUME. Substituting WETH for the native leg changes the asset and contract path, even when the symbols look related.
Active Depth and Position Portability
Whatever the setup, Ambient pools combine three liquidity forms on one curve: full-range ambient liquidity, concentrated ranges, and knockout liquidity. Only liquidity active at the quoted price supports immediate execution. LP positions also stay on their origin deployment, whether stored as a lightweight CrocSwapDex entry or represented by an ERC-20 LP token. Moving a position requires removing liquidity, transferring both resulting assets, and minting against a different destination pool. That sequence suits a strategic relocation; a one-time trade is cheaper on the funded origin chain when its quote remains competitive.
Useful questions about Ambient networks
-
Does switching networks in MetaMask move my Ambient balances?
- No, switching networks in MetaMask changes the chain the wallet reads and signs against; it does not transfer assets. A USDC balance on Ethereum remains on Ethereum when the interface switches to Scroll. To trade on the destination deployment, fund that network through a supported withdrawal or bridge, then retain its native gas asset unless a relayer handles gas. Reopen the quote after the balance arrives because destination liquidity has its own state.
-
Can one ERC-20 approval cover Ambient on Ethereum and Scroll?
- No, an ERC-20 approval belongs to one chain, token contract, owner, and spender. Ambient deploys a separate CrocSwapDex contract on each supported network, so an Ethereum allowance does not authorize the Scroll deployment. The token contract may also differ across chains. The wallet must approve the intended deployment on the selected network before a direct token transfer, while surplus collateral recorded there follows the DEX's internal settlement path.
-
When is direct wallet settlement preferable to Ambient surplus collateral?
- Direct wallet settlement is preferable for isolated swaps when the user wants output visible in the wallet immediately. Surplus collateral fits repeated Ambient actions because the deployment records an internal balance and nets token transfers. The choice applies separately to the base and quote sides through settlement flags. Surplus on Ethereum stays on Ethereum, so it offers no gas advantage after switching to Scroll, Blast, Swell, or Plume.
-
Will a reverted Ambient swap consume gas?
- Yes, a reverted on-chain Ambient transaction consumes gas already spent on validation and execution. A slippage boundary protects the token exchange by reverting the state change when the quoted limit fails, yet the selected network still charges for computation. With an EIP-712 relayed action, the relayer submits the transaction and handles the native gas payment under its quoted terms. The user's swap or liquidity state remains unchanged after the revert.
-
Why can an Ambient quote change after funds cross a bridge?
- An Ambient quote changes after bridging because the destination pool and gas market keep evolving during the transfer. The bridge also determines which token representation arrives, and that contract must match the intended pool. Once funds settle, request a fresh quote for the exact input amount, inspect the route and minimum received amount, and include destination gas or relayer cost. A pre-bridge quote is a snapshot, not a reservation.
-
Is PLUME required for an Ambient transaction on Plume?
- PLUME is required for a direct wallet transaction on Plume because it is the network's native gas asset. Ambient's EIP-712 flow provides another path: a relayer pays native gas and accepts a quoted tip in an allowed asset or surplus balance. The wallet still needs the intended trade token on Plume, and the relayer must support the action. Holding ETH on another chain does not pay Plume execution directly.
-
Where do Ambient LP fees remain after I switch networks?
- Ambient LP fees stay with the liquidity position on its origin deployment. Concentrated-position fees are reinvested as ambient liquidity inside the same pool, while wallet network switching changes only the displayed chain context. To use the assets elsewhere, remove liquidity on the origin chain, settle the resulting pair to the wallet or surplus balance, and transfer the assets separately. The destination position starts with a new pool state and range choice.
-
Does higher total pool liquidity guarantee a better Ambient quote?
- No, a higher headline liquidity total does not guarantee a better Ambient quote. Immediate execution uses liquidity active near the current price, including full-range ambient liquidity and in-range concentrated liquidity. Trade size, dynamic pool fee, hop count, and token-transfer path also affect delivered output. Compare equal input amounts at the same time, then subtract network and funding costs; the quote's minimum received amount defines the executable boundary.