⚠️ Sent the wrong asset

Use this page if you deposited a token the widget did not list, picked the wrong network, or sent to an old address.

Do not send a second transfer

A second send almost never fixes the first. It usually creates two cases to unwind. Wait until you know where the first one landed.

Check what actually went out

Compare the widget with the transaction your wallet or exchange broadcast:

1. Token contract or mint (not just the ticker)
2. Network
3. Recipient address
4. Amount versus the minimum

If the hash went to a different address than the one on screen, treat that as a possible paste or malware issue. We can inspect addresses Unifold issued. We cannot reverse a send to an attacker.

Correct asset, below the minimum

Send more of the same asset on the same network to the same address until you clear the floor. See Size limits and minimums.

Unsupported token or wrong network

This is the usual case: the ticker looks right, but the token or chain was not in the widget.

Open the support form and include:

• Destination app
• Token and network you meant to send
• Token and network you actually sent
• Transaction hash
• The deposit address as shown in the widget

The team will check whether a recovery path exists. There is no guarantee. Some assets on some chains cannot be moved without keys or liquidity we do not have.

Old or reused address

Addresses can be specific to a token, network, user, and destination. An address from last week, or from a different app, may not credit the account you are looking at. Still send the hash to support. Do not assume the funds are gone. Do not assume they will reroute on their own.

Clipboard swap or clickjacking

If the address you pasted does not match the widget character for character, do not send. If you already sent, that transaction is on someone else's address. File a report with the hash for our records. Recovery in that case is usually impossible.