What Is Anyswap and How Did Its Bridge Work?

Anyswap is a cross-chain bridge protocol that coordinated a deposit or burn on one blockchain with a release or mint on another. For supported assets, Anyswap let users move value between networks through smart contracts and a signing network. The Anyswap cross-chain bridge stopped operating in 2023, so its old transfer instructions describe how it worked, not a live route to use.

Anyswap Moved Token Balances Between Networks

A bridge transfer gave you a corresponding balance on a destination blockchain; it did not move the original token contract off its source chain. That distinction matters because a token’s name and symbol can look identical on two networks while its contract address, issuer and redemption rights differ. The result was useful when you needed an asset on another network to hold, trade or use in an application there.

The method depended on the asset. For a token whose supply the bridge controlled, it could lock the original asset and mint a wrapped version elsewhere, then burn that version when someone returned it for the original. For a token already issued independently on both chains, the Anyswap Router relied on pools of that token: deposits replenished liquidity on one chain, while available liquidity paid recipients on another.

anyCall was a related cross-chain messaging feature for applications. It could pass instructions to a contract on the destination chain, and some routes combined a token transfer with such a call. A straightforward wallet-to-wallet transfer did not require a destination application call, so a user assessing one needed to focus first on the asset received and its backing.

How Anyswap Router Completed A Transfer

The Router coordinated two separate on-chain transactions through its contracts and an MPC signing network. Suppose a user historically sent 1,000 USDC from Ethereum to Fantom. The wallet first approved the source-chain Router to spend USDC, if it had not already done so, then signed the transfer specifying the token, amount, destination chain and recipient.

On a liquidity-pool route, the source contract took the USDC into its pool and emitted a transfer event. The signing network observed that event and, after its required source-chain confirmations, authorized the destination transaction. If the Fantom pool held enough USDC, the destination contract released USDC to the recipient; the user did not have to make a second transfer manually.

That final pool check was consequential. If the destination pool lacked enough underlying USDC, the recipient could instead receive anyUSDC, a pool-share token representing a claim for USDC. Under normal operation, its holder could redeem it when liquidity returned. A quoted 1:1 transfer therefore did not guarantee immediately spendable USDC on the destination chain.

For a bridged token controlled by the protocol, the path could burn a representation on the source chain and mint one on the destination chain instead of waiting for a pool payout. The Router’s contract functions reflected that difference: anySwapOutUnderlying accepted an underlying token, while anySwapOut burned a bridge-issued token. MPC signers were an essential trust point because destination issuance or release depended on their authorization; confirmation on Ethereum alone did not prove that Fantom had paid out.

Fees, Limits And Timing Depended On The Route

A transfer cost source-chain gas plus a cross-chain fee, and an ERC-20 approval could require another gas transaction. The protocol’s historical fee schedule listed roughly $0.90–$1.90 for mainstream tokens sent to non-Ethereum chains, while some other tokens used a 0.1% fee subject to minimums and maximums. Those figures describe the old service, not a current quote.

For the illustrative 1,000 USDC Ethereum-to-Fantom transfer, say the cross-chain fee was $1.50 and source-chain gas was $4. The expected payout would be about 998.50 USDC if the route paid the underlying token, while the $4 would come separately from the sender’s ETH balance. A first-time sender would also need ETH for approval gas and destination-chain gas tokens to use the received USDC afterward.

Historical minimum transfer amounts were around $12 in token value for mainstream assets going to non-Ethereum chains, with different thresholds for other routes. Ordinary transfers depended on source confirmations and destination execution, while large transfers could take hours under the old limits. The practical number to inspect was the destination amount and asset shown for the exact route, together with its minimum, maximum and available pool liquidity.

The Original Bridge Is No Longer A Route To Send Through

The service behind Anyswap ceased operations after a major bridge incident in July 2023, and normal completion of new transfers should not be assumed. An old interface, published contract address or successful source-chain transaction does not establish that the signing network will execute a destination payout. Do not submit funds to the original contracts on the strength of an archived walkthrough.

If you are deciding how to move an asset now, use the Anyswap route as a case study for what to check in any currently operating bridge. Verify the exact source and destination chain IDs, token contract addresses and recipient address; Ethereum mainnet is chain ID 1, while the historical Fantom network was chain ID 250. Confirm whether the destination asset is issuer-native, pool-backed or bridge-minted, because those forms can have different redemption and acceptance risks.

Then compare the quoted net output with the source gas, approval cost, transfer limit and available destination liquidity. Check that the route has a working destination transaction history and an active operator before signing. For a first transfer, an amount above the route’s minimum but small enough to test receipt is sensible; the decisive result is the asset arriving in the intended wallet on the intended chain.

Old Pending Transfers And AnyTokens Need Separate Checks

If an earlier Anyswap transfer appears unfinished, locate the source transaction hash and inspect the destination chain for a matching payout to the intended address. A successful source transaction only shows that the first leg happened. Record the token contract address and actual balance received, since a wallet may hide an anyToken or show it under a familiar symbol.

If the wallet holds anyUSDC or another anyToken, check whether its underlying pool still has assets and whether redemption is actually functioning before assigning it the face value of the original token. Pool shares are claims on available liquidity, and the 2023 incident makes an old promise of eventual redemption unreliable. The useful takeaway is the mechanism and its limits: a cross-chain transfer succeeds for the user only when the correct, usable asset arrives on the destination chain.