Anyswap has no current transaction price: its former Multichain bridge ceased operations in July 2023, so no legitimate user should approve a transfer or calculate its old fee schedule at this time.
What inputs would Anyswap have needed to price a transfer?
A cross-chain quote was never one fixed “Anyswap fee.” It depended on the asset, the origin chain, the destination chain, the transfer route, the amount, and the moment the transaction was submitted. Missing any one of those inputs makes a quoted total meaningless.
- Source network: The wallet needed the chain’s native coin to submit an approval or transfer. On Ethereum, gas is the unit measuring the computation required for an operation; the fee depends on gas used and the price per unit.
- Destination network: A bridge may need liquidity, minting, release, or a relayer action on the receiving chain. Those mechanics affect the route and any amount withheld from the output.
- Token and route: Native assets, wrapped ERC-20 tokens, and liquidity-pool routes do not necessarily settle the same way. A route with thin liquidity can produce a worse effective result even if its visible platform charge is low.
- Amount: Network fees are not a simple percentage. A fixed on-chain cost takes a much larger share of a small transfer than a large one.
The useful diagnostic is to separate the costs before adding them: source-chain gas, any protocol or bridge charge, price impact or routing spread, and destination-side delivery costs. Calling all four “the fee” hides the reason a quote changed.
What would an Anyswap quote have shown as the expected output?
The expected output should have been the amount arriving on the destination chain, not merely the amount sent minus a displayed bridge fee. For a routed transfer, the practical calculation is:
expected output = input amount − route charge − liquidity effect − any delivery deduction
Gas normally sits beside that calculation because it is paid from the sender’s wallet in the source chain’s native asset. An ERC-20 transfer might therefore show a token output while still requiring ETH, FTM, BNB, or another native coin to authorize the transaction. A quote that ignores that wallet-side requirement is incomplete.
| What changes | What it changes in the total cost |
|---|---|
| Network congestion | Source-chain gas can rise before confirmation. |
| Contract approval | A first-time ERC-20 approval can add a separate on-chain transaction. |
| Route liquidity | The received amount can fall through price impact or a less favorable conversion path. |
| Transfer size | Fixed network costs become proportionally heavier on small transfers. |
| Destination handling | A route may reserve value for relaying, minting, or release on the receiving chain. |
The check I always do before confirming anything is to compare the wallet’s total native-coin spend with the exact destination amount, then verify that the destination token contract is the intended one. A token symbol alone is not enough: bridged and native versions can share a name.
How would an Anyswap bridge fee have been built?
Historically, Anyswap became Multichain, a cross-chain routing system that used bridge and liquidity mechanisms rather than a universal flat charge. That distinction matters because a bridge can lock an asset on one chain and release or mint a representation on another, while a router can use available liquidity to deliver an existing asset. The cost profile changes with the mechanism selected.
There is no defensible current percentage to publish for “Anyswap fees.” The Multichain team announced that it had ceased operations in July 2023 after unauthorized withdrawals; Chainalysis records the announcement and the surrounding incident in its Multichain incident analysis. An old interface, cached tutorial, or token approval does not turn that historical rate into a live price.
Which edge cases turn a plausible quote into the wrong answer?
The most common failure is mistaking an approval for the bridge transaction. The approval may succeed and consume gas while no asset has moved. The next failure is arriving with the transferred token but no native token on the destination chain to make a later transaction.
Other edge cases are more subtle: a transfer below a route’s minimum, an expired quote, insufficient pool liquidity, a token with transfer-tax logic, or a destination address on the wrong network. A transaction can also be confirmed on the source chain while the destination action never completes; source confirmation is evidence of submission, not proof of delivery.
What should someone do when an Anyswap screen offers a quote?
The right output is not a fee estimate but a stop condition: do not sign a new approval or send funds based on a screen using the former Anyswap/Multichain identity. The Anyswap site is the interface to inspect for its stated operator, contract addresses, and current documentation before treating any displayed route as actionable.
If a wallet already approved an old bridge contract, check the approval against the exact chain and token, revoke only the allowance that is no longer needed, and preserve transaction hashes for any unresolved transfer. That is how the cost question becomes answerable without confusing an old protocol name, a gas charge, and a live service.