Anyswap Funds Stuck? What You Can Actually Do, and What You Probably Cannot

The uncomfortable part comes first: if funds are stuck because of the Anyswap to Multichain failure, there may not be a normal support path, a retry button, or a contract method that makes the bridge whole again. A cross-chain bridge is not a bank queue. It is a custody and messaging system, and when that custody layer fails, the user-facing symptom is often simple: your source-chain asset is gone from your wallet, your destination-chain asset never becomes usable, or the wrapped token you hold no longer has credible backing.

That does not mean you should do nothing. It means the job changes. You are no longer "speeding up a bridge." You are preserving evidence, identifying which asset state you are actually in, avoiding recovery scams, and deciding whether any remaining on-chain action is rational.

What actually made Anyswap funds get stuck?

There were ordinary bridge delays before the collapse, and then there was the larger failure around Multichain, the later name associated with the protocol. Those are different problems.

In a normal bridge delay, the source-chain transaction may be confirmed, but the destination-chain release or mint is pending. That can happen because of relayer delays, liquidity constraints, routing problems, gas issues, RPC indexing lag, or a temporary pause. Annoying, yes. Usually diagnosable.

The July 2023 incident was not a routine delay. A Chainalysis July 2023 analysis described unusually large unauthorized withdrawals from Multichain, with the bulk coming from the Fantom bridge, and discussed the possibility of a hack or insider rug pull. The same analysis noted that Multichain used multi-party computation, or MPC, for key management; if enough MPC key material is controlled or unavailable, the bridge's ability to secure and release assets changes completely.

That is why "stuck" can mean several different things:

• Your original asset was locked or custodied on the source chain.
• You received an anyToken or wrapped asset, such as anyUSDC or anyETH, whose backing became questionable.
• You started a bridge transaction while service was paused or degraded.
• You hold a token that still appears in your wallet, but the market treats it as impaired because redemption is not reliable.
• You are seeing a frozen asset, especially where a centralized issuer or exchange has blocked movement at a specific address.

The fix depends on which of those states applies. There is no single recovery recipe.

Can I just reverse the bridge transaction?

Usually, no. Once a source-chain transaction is confirmed, the chain will not unwind it because the bridge later failed. Ethereum-style settlement is deliberately hard to reverse; finality is a feature until you need an exception.

For a lock-and-mint bridge, the usual pattern is that assets are locked on the source chain and a representation is minted or released on the destination chain. The ethereum.org bridge documentation describes this lock-and-mint model and the systemic risk created by wrapped assets. If the bridge custodian, validator set, MPC system, or destination contract cannot complete its side of the bargain, the source-chain transaction being valid does not guarantee a useful destination-chain asset.

So the question is not "how do I undo it?" The better question is: "What proof do I have, what asset do I hold now, and is there any live contract or issuer path that recognizes that proof?"

What should I check first?

Start with the boring checks. They matter because they separate a bad UI from a dead route.

1. Confirm the source-chain transaction hash in a block explorer. Look for success/failure, token contract, amount, sender, recipient, and the bridge/router contract.
2. Confirm whether a destination-chain transaction exists. Do not rely only on a bridge history page; check the destination explorer directly.
3. Identify the token contract you received, if any. A symbol like USDC, ETH, or BTC is not enough. You need the contract address.
4. Check whether the token is a wrapped bridge asset. Names like anyUSDC, anyETH, multiUSDC, or other bridge-specific variants are not the same as native issuance.
5. Look for official pause, shutdown, or incident notices from the protocol, wallet, exchange, or issuer involved.
6. Save screenshots and raw transaction links before trying new actions. Evidence gets harder to assemble after you connect to random "recovery" sites.

If all you find is a source-chain debit and no credible destination-chain credit, treat the position as unresolved, not "almost fixed."

A practical stuck-funds checklist

Use this as a triage sheet, not as a promise that a fix exists.

• [ ] Source-chain transaction hash saved.
• [ ] Destination-chain transaction hash found, or confirmed absent.
• [ ] Source token contract address recorded.
• [ ] Destination token contract address recorded.
• [ ] Token type identified: native, canonical wrapped, bridge-issued anyToken, LP receipt, or unknown.
• [ ] Bridge route identified: source chain, destination chain, bridge contract, and UI used.
• [ ] Current contract status checked: paused, deprecated, inaccessible, or still callable.
• [ ] Issuer or exchange status checked for frozen / blocked assets, especially stablecoins.
• [ ] Wallet approvals reviewed and unnecessary approvals revoked.
• [ ] No seed phrase, private key, or signed "recovery authorization" shared with any third party.
• [ ] Tax/accounting note created if the position may need to be treated as impaired or lost.

That last line is not glamorous, but it is real. If the technical path is gone, documentation may be the only useful thing left.

What if I hold anyUSDC, anyETH, or another anyToken?

Treat it as a separate asset until proven otherwise.

Wrapped assets depend on redeemability. If you hold anyUSDC, the relevant question is not whether "USDC" has value in the abstract; it is whether that specific token contract can be redeemed, swapped, or honored by a credible route. Same for anyETH. A bridge-issued representation can trade away from the asset it names when confidence in the backing or redemption path disappears.

This is where many people make the position worse. They see a token symbol in a wallet, assume it is equivalent to the native asset, and route it into a thin pool, a fake support site, or a second bridge that cannot actually redeem it. Before moving it, check the contract address, liquidity venue, pool depth, route, and whether the receiving protocol treats it as the same asset you think it is.

If your current path depends on a dead interface, comparing live bridge assumptions is a separate task from recovery. Around Anyswap, a current alternative worth checking should be treated as a research reference, not as a way to reverse an old transaction. The useful question is whether a new route has transparent custody, sane limits, and an exit path before you send anything else.

Does frozen mean recoverable?

Not automatically.

"Frozen" can mean at least three things in this context. A bridge can be paused. A token issuer can block transfers from specific addresses. An exchange or application can disable deposits or withdrawals for a token. Those are operationally different.

For USDC specifically, Circle's legal terms state that USDC can be blocklisted under its policy, and that transfers to and from a blocked address may be restricted; see the Circle USDC terms. That kind of freeze may prevent movement, but it does not by itself create a user recovery process for every affected bridge user. It may preserve assets from further movement, support law-enforcement or compliance action, or simply leave a holder waiting with no direct claim path through the bridge.

So no: frozen does not mean safe, solved, or refundable. It means movement has been restricted somewhere.

Did MPC key management matter?

Yes, because MPC was part of the custody control plane.

MPC is often described as a way to split signing authority instead of leaving one private key in one place. That can be a useful design. But the security benefit depends on operational reality: who controls the key shares, where the servers run, who can revoke access, and what happens if a principal disappears.

Reports on the Multichain shutdown said the team lost effective access after CEO Zhaojun was taken by Chinese police and that access to MPC node servers was tied to his control environment. A report on the shutdown notice described the project's statement that the servers running the MPC setup were controlled through Zhaojun's personal cloud server account. A Decrypt report on the same notice similarly covered the team's claim that it could no longer maintain normal operations.

For a stuck user, the practical implication is blunt: if the signing and custody system is unavailable or compromised, your wallet cannot force the bridge to honor a release. You can prove what happened on-chain. You cannot make missing operators sign.

Should I contact support, law enforcement, or a recovery service?

Contacting legitimate support channels is reasonable if they still exist, but do not confuse a ticket with custody. A support agent cannot mint backed assets without the protocol's authority, liquidity, and signer access.

For meaningful losses, preserve records and consider professional advice. That may mean a lawyer, accountant, insurer, exchange compliance desk, or law-enforcement report, depending on the situation and jurisdiction. Keep it factual: transaction hashes, timestamps, wallet addresses, token contracts, amounts, chains, screenshots, and any communication you received.

Be very suspicious of "recovery" offers. The common scam pattern is familiar: someone says your funds are visible, asks you to connect a wallet, asks for a seed phrase, sends you to a cloned bridge page, or tells you to pay a fee to unlock an old transfer. A legitimate investigator does not need your seed phrase. A real issuer or exchange will not ask you to sign arbitrary approvals through a chat link.

Is there any on-chain action worth trying?

Sometimes, but only after you know what state you are in.

If the issue is merely a wallet display problem, adding the correct token contract or switching RPCs can make a received token visible. If the issue is a pending approval, revoking approvals may reduce future risk but will not complete the old bridge. If the issue is a live but deprecated contract, read-only calls and explorer data may show status, but writing to the contract without understanding the function can burn gas or worsen the position.

The highest-value on-chain actions are defensive:

• Revoke stale approvals to bridge routers and unknown spenders.
• Move unaffected assets out of wallets that interacted with suspicious recovery sites.
• Avoid sending additional gas, tokens, or approvals to "unstick" a transaction unless the mechanism is documented and independently verifiable.
• Keep impaired wrapped assets separate from normal portfolio balances so you do not accidentally route them as if they were native assets.

Do not average down into a broken bridge asset just because it is cheap. A discount can reflect impaired redemption, not opportunity.

What should I conclude if the evidence points to the July 2023 collapse?

Conclude that you are dealing with a custody failure, not a normal delayed transaction.

The facts that matter are the transaction path, the token contract, and whether any credible party still controls the machinery needed to redeem or release assets. Chainalysis described the July withdrawals as unauthorized and discussed compromised or unavailable administrator-level control as a plausible mechanism. Contemporary shutdown reporting described loss of operational access and the end of normal project operations. Those are not conditions where a user can simply resubmit a form and expect a bridge to finish.

That is an unsatisfying answer, but it is the honest one. Your best next step is to document the position cleanly, secure the rest of the wallet, check whether any issuer, exchange, or legal channel applies, and avoid turning a stuck bridge claim into a second loss through a recovery scam.