Skip to main content
This page is for deposits that arrive somewhere the bridge cannot observe, or that contain a token the bridge is not programmed to credit. These are among the most painful mistakes in the space and the remedies are limited, so read before acting.
Do not try to “rescue” the funds yourself by sending more transactions on top. In several recovery paths the original transaction is what we need to work with, and additional traffic on the same address can make things harder, not easier.

​
The two situations, and what they mean

Situation A: you sent a supported asset on a chain the bridge does not support. Example: you sent USDC on a chain that Intention’s bridge does not yet index. The tokens exist on that chain, at the canonical bridge address (or some address that looks like it), but no validator is watching for them, so no attestation will ever be produced. In most cases the funds still belong to whoever controls the destination address on that chain. If the destination is an address under Intention Labs’ control on a chain we can operate on, recovery may be possible with manual help. If the destination is an address we do not control, recovery is at best unlikely. Situation B: you sent an unsupported asset to a supported chain’s bridge address. Example: you sent a random ERC-20 to the Intention bridge contract on a chain we do support. The contract received the transfer, but its deposit handler only credits the allowlisted assets. In this case the tokens are sitting in the contract and may be recoverable through a manual operator procedure, provided the contract exposes one and the asset is not itself broken (rebasing tokens, tokens with transfer fees, and tokens that reject transfers back can all complicate recovery). The most common unrecoverable case is when you send the native gas token of a chain the bridge does not support at all to an address derived from a public key on a chain we do support. The two chains use incompatible address schemes, and there is no key under our control that can spend on the source chain. Those funds are effectively gone.

​
What to do

  1. Stop. Do not move more funds. Do not attempt another deposit on the same transaction. Do not paste the transaction hash into any public channel.
  2. Write down exactly what happened — the chain you sent from, the destination address, the asset, the amount, the source-chain transaction hash, and the UTC time.
  3. Email support@intention.xyz with all of that information. Mark the subject as “Wrong network” or “Wrong asset” so we triage it to the right queue.
  4. Wait for a reply before doing anything else. We will tell you whether recovery is possible and what we need from you.

​
Supported chains and assets

The list of supported source chains and assets is TBD and will be published here when the bridge launches. Until then there are no supported deposit paths and any funds sent to addresses claiming to be Intention bridge contracts should be assumed fraudulent.

​
Prevention

  • Always verify the destination chain in your wallet, not just the address. An address string can look the same on multiple chains but lead to entirely different accounts.
  • Always test a new bridge path with a very small amount before moving a meaningful balance.
  • Never trust a contract address that you got from a private message, a screenshot, or a search result. Use the Bridge page on this site as the canonical source for the production addresses.