across bridge: the 24-hour limit that matters
The catch appears before speed: Across does not use one universal bridge minimum or maximum. Limits change by token pair, origin chain, destination chain, liquidity, and quote conditions. A transfer can therefore fail even when both chains appear supported.
Check the route before touching your wallet
Start with the exact origin and destination, then confirm the token on each side. Across currently lists 27 mainnet chains, but chain support does not mean every asset can travel between every pair. The safe path is to select the route first, enter the amount, and inspect the returned quote before approving anything.
Compare the figures that decide acceptance
| Figure | What it tells you | Why it matters |
|---|---|---|
| 27 mainnet chains | Broad network coverage | Not universal token-pair coverage |
| About 2 seconds | Typical fill speed for most transfers | Not a promise during congestion or poor relayer economics |
| Route-specific minimum | Smallest accepted transfer | Amounts below it may be rejected |
| Route-specific maximum | Largest accepted transfer | Large transfers may need splitting |
| 1,000,000 units | Example: 1 USDC with six decimals | API amounts are not always human-readable |
| 1,000,000,000,000,000,000 units | Example: 1 WETH with 18 decimals | A decimal error can produce the wrong amount |
| 24 hours | Lifetime of an Across deposit address | Applies to the deposit-address flow, not every wallet transfer |
The important omission is the one many summaries hide: there is no dependable “Across maximum” to memorize. The limits endpoint returns minDeposit and maxDeposit for the precise input token, output token, and chain pair. Treat those values as live route data, not permanent product specifications. The across bridge is where the route can be checked before the transaction is signed.
Send only after the quote survives inspection
- Choose the source chain, destination chain, input token, and output token.
- Enter the amount and verify the displayed minimum, maximum, fee, output amount, and expiry.
- Check that the wallet holds the input token and enough source-chain gas.
- Confirm the recipient address and the token contract on the destination chain.
- Approve and submit only when the quoted output is acceptable.
Fix the mistake people most often make
Most often wrong: sending before checking token decimals and route limits. “1” may mean 1 USDC in the app but one smallest unit in an API request. A wrong token, wrong chain, or amount outside the live range can leave the transfer pending, rejected, or requiring recovery. For deposit addresses, never send after the 24-hour window, and never reuse an address casually. A fast bridge is useful only when the route, units, and limits are right first.