Exodus has ended support for Fantom (FTM).
It's no longer possible to send or receive FTM and assets on the Fantom network with Exodus.
To learn more, visit: Asset sunset FAQs.
Starting in December 2024, Fantom (FTM) began migrating to the new Sonic (S) token on the Sonic network.
What this means for you:
Exodus does not support the Sonic network or the new Sonic (S) token.
Exodus has ended support for the Fantom network.
Want to learn more about how this affects you? Read on for all the details.
In this article:
What is the Fantom (FTM) to Sonic (S) migration?
The Fantom Foundation is migrating the Fantom (FTM) token on the Fantom Opera network to the Sonic (S) token on the Sonic network.
Sonic Labs announced that the Fantom Opera network will remain operational through at least the end of 2026. See Sonic Labs' announcement on X.
If you hold Fantom (FTM), you can migrate it to Sonic (S) using Sonic Labs' upgrade tool. This tool allows you to swap FTM for S at a 1:1 rate.
For instructions on how to do this, visit the section: How do I migrate my Fantom (FTM) to Sonic (S)?
For more information about the Sonic network, the Sonic (S) token, and the token migration, please visit Sonic's website: Sonic FAQ.
What if I hold Fantom (FTM) in Exodus?
Exodus has ended support for Fantom (FTM), and Exodus does not support the new Sonic (S) token on the Sonic network.
Sonic Labs announced that the Fantom Opera network will remain operational at least through the end of 2026.
As Exodus no longer supports Fantom, you can manage your assets on Fantom with a supported wallet like MetaMask. Before support for the Fantom Opera network ends, move your assets on the Fantom network to a different network, swap them, or migrate Fantom (FTM) to Sonic (S).
To migrate your Fantom (FTM) to Sonic (S), see the section below: How do I migrate my Fantom (FTM) to Sonic (S)?
MetaMask is a third-party platform. As such, Exodus cannot guarantee the performance of its products/services or that the steps shown and the information provided will always be accurate.
How do I migrate my Fantom (FTM) to Sonic (S)?
Exodus does not support the new Vaulta (A) token. You can use a supported wallet, such as MetaMask, to migrate your FTM.
MetaMask is a third-party platform. As such, Exodus cannot guarantee the performance of its products/services or that the steps shown and the information provided will always be accurate.
Download the MetaMask wallet from their official website.
In MetaMask, add the Fantom Opera network. For a guide on adding custom networks, visit MetaMask's guide: How to add a custom network RPC.
Fantom Opera network details:
a) Network name: Fantom Opera
b) Default URL RPC: https://rpcapi.fantom.network
c) Chain ID: 250
d) Currency Symbol: FTM
e) Block explorer URL: https://ftmscan.com/
Next, import your FTM private key from Exodus into MetaMask.
In Exodus Desktop, you can view the private keys for some assets that are no longer supported in Exodus, including FTM. Here's a guide on how to find your FTM private key: How do I view my private keys for removed assets?Open MetaMask and import your Exodus FTM private key. For a full guide, see the MetaMask guide Importing an Account.
Once you see your FTM tokens in MetaMask, visit the Sonic Labs upgrade tool and connect your MetaMask wallet:
Once connected, a) choose the amount of FTM you want to upgrade to Sonic (S), then b) click Upgrade.
To see and interact with your S token in MetaMask, add the Sonic network. For a guide on adding custom networks, visit MetaMask's guide: How to add a custom network RPC.
Sonic network details:
a) Network name: Sonic Mainnet
b) Default RPC URL: https://rpc.soniclabs.com
c) Chain ID: 146
d) Currency Symbol: S
e) Block explorer URL: https://sonicscan.org
That's it! Your Fantom (FTM) on the Fantom Opera network has been migrated to Sonic (S) on the Sonic network.
What if my Fantom (FTM) isn't on the Fantom Opera Network?
If you hold FTM on Ethereum, you can use the MySonic upgrade portal to upgrade FTM on Ethereum to S on Sonic.
For more information, visit Sonic's help content: Migration FAQ.