Four checks before moving a deprecated wrapped token

Before moving a deprecated wrapped token, verify the issuer’s notice, the exact contract address, the migration or redemption route, and any deadline. A deprecation notice can end support without automatically burning balances or stopping transfers.

What does “deprecated” mean for the contract?

It can mean the issuer has stopped supporting a token, bridge, or interface, and those changes have different effects. A proxy contract may keep its address while its underlying implementation changes; a replacement token deployed at a new address is a separate contract, even if it uses the same name and ticker.

Wrapped tokens represent assets issued on another chain, often through a system that locks or otherwise accounts for the original asset while minting tokens on the destination chain. The precise design determines who can redeem the underlying asset and how. For more on those mechanics, see zerofi’s explanation of how the XMR bridge works.

Which four checks matter before migration?

Check the token and its route against the issuer’s current instructions before signing a transaction. These four details help distinguish an official migration from a similarly named contract or an unsupported path.

• Network and address: Match the chain and full contract address in the notice to the token in your wallet or explorer. A familiar ticker alone does not identify a contract.
• Migration method: Confirm whether holders must burn old tokens, claim replacements, or use a bridge transaction. Check the conversion terms and destination address before confirming.
• Redemption terms: Find out whether the old token can still be redeemed, who processes redemption, and whether fees or a cutoff apply. Do not assume that a replacement token carries the same claim.
• Approvals and support: Check which contract a migration page asks you to approve, and whether your wallet or trading venue supports the replacement token. Revoke approvals you no longer need through a trusted wallet interface.

What should holders do before moving funds?

Compare the contract address and instructions with a notice published through the issuer’s established channels, then inspect the transaction details before signing. If the notice does not specify the chain, destination contract, conversion terms, and any deadline, wait for clarification rather than guessing.

Use the official migration route only after confirming its address independently; a search result or message can lead to a lookalike page. A small test transaction may help reveal whether the route behaves as expected, but it does not prove that the contract or issuer is safe.

Keep a record of the old balance, transaction hash, and any migration confirmation. The next step depends on the issuer’s terms: holders may need to migrate by a stated cutoff, while whether redemption remains available afterward can be unconfirmed until the issuer says so.