Anyswap is a cross-chain protocol built to move supported tokens between blockchains through bridge and router routes, with anyCall for cross-chain messages. The key distinction is what arrives in your wallet: a wrapped anyToken or the underlying token. The original service ceased operations in 2023.
What is Anyswap and how does it work?
Anyswap worked by recording a deposit or burn on one chain, then arranging a matching mint or release on another. Its secure multiparty computation (SMPC) network coordinated the destination action after the source transaction was confirmed. Ethereum.org calls the basic bridge pattern “lock and mint”: the original asset stays locked while a wrapped representation circulates elsewhere.
Suppose a supported route moved 100 USDC from Ethereum to BNB Chain. Your wallet would first approve the token contract to spend up to the amount you chose; approval alone would move nothing. You would then submit the transfer, wait for source-chain confirmation, and check for a separate destination-chain transaction. Unlike an exchange withdrawal, these are on-chain steps you can inspect yourself.
A historical route quote could include a cross-chain fee, source-chain gas, a minimum transfer and a maximum transfer. For example, a 0.1% fee on 100 USDC is 0.10 USDC, but a quoted 1 USDC minimum fee would make the charge 1 USDC before gas. The wallet also needs the source chain’s gas token to submit the transaction; the displayed amount to receive is the useful figure to compare.
What is the difference between Anyswap's bridge and router?
The bridge created a wrapped token against an asset held on its origin chain, while the router tried to deliver the underlying token using destination-chain liquidity. The third option, anyCall, carried instructions for applications rather than serving as the ordinary wallet transfer path. Each solved a different problem:
- Bridge: Best for moving an asset to a chain where its wrapped anyToken was supported. It did not fit when the receiving application required the underlying token instead of that wrapped contract.
- Router: Best for receiving the underlying token when the destination pool held enough of it. If liquidity was short, a user could receive an anyToken claim and have to wait for liquidity before redeeming it.
- anyCall: Best for an application that needed to send a cross-chain message or trigger a destination contract call, sometimes alongside funds. It was unnecessary for a simple wallet-to-wallet token move.
The Anyswap cross-chain bridge illustrates why the output contract matters more than a familiar ticker. A route through Anyswap could show USDC on both sides, yet a router short of destination liquidity could leave the recipient holding anyUSDC. The destination token’s contract address would tell the wallet holder what actually arrived.
Is Anyswap still available?
No: the team announced that it was ceasing operations in July 2023, after abnormal asset withdrawals and loss of operational access. Chainalysis documented the announcement and the withdrawals. As of 20 October 2026, an old interface loading or a wallet approval succeeding should not be taken as evidence that a transfer can settle.
For a new transfer, check that a currently operating route supports the exact source and destination token contracts, has enough destination liquidity, and states its fees and limits before sending funds. If you already hold an anyToken, identify its contract and available redemption path first. A balance displayed as 100 anyUSDC is a claim on underlying USDC, not proof that 100 USDC can presently be redeemed.
How do I check an Anyswap transaction?
Check the transaction hash in the source chain’s block explorer first, then look for the matching destination transaction. A successful source transaction proves that the deposit or burn happened; it does not prove that the recipient received tokens. Compare the recipient address, token contract and amount on the destination chain rather than relying on the ticker shown in a wallet.
If the source transaction failed, the transfer did not begin, though gas may have been spent. If it succeeded but no destination transaction exists, record the source hash, chain, token contract and recipient address before investigating the route’s status. For an old transfer, those on-chain records remain useful even when a bridge status page is unavailable.
- Identify the output token contract before choosing a route.
- Check liquidity, quoted fees and limits before submitting.
- Verify both chain transactions and the token received.