Token Migration

This page outlines token migration options from Fantom Opera to the upcoming Sonic chain.

It provides comprehensive guidance for both token holders and project owners regarding their migration options.

Token Holders

Instructions for Token Holders

The official Sonic Labs token migration contract will facilitate the FTM to S migration starting in December 2024. This contract allows users to convert FTM to S at a 1:1 ratio.

For the first 90 days, you'll be able to swap between the two tokens freely. After this period, swaps will only be possible in one direction, from FTM to S.

Official Migration Contract Timeline

Phase	Duration	Conversion Type	Notes
Initial Period	90 Days	Two-way FTM ↔ S	Full flexibility
Final Phase	Indefinite	One-way FTM → S	No reverse conversion

CEX-Held FTM

Most centralized exchanges will support the automatic conversion of FTM to S. You won't need to take any action — your FTM will be converted automatically.

If you prefer to handle the migration yourself, you can withdraw to a Web3 wallet and use the official migration contract.

Staked FTM

Users will be able to unlock their staked FTM and bridge immediately to Sonic. The new Sonic staking system features:

Parameter	Requirement
Lock Period	14 days
Withdrawal Period	7 days
Minimum Stake	1 S
Validator Requirement	50,000 S

LP Positions

If you hold liquidity positions, you'll need to:

1. Break existing LP positions on Fantom

2. Migrate each token individually following their specific processes

3. Recreate your positions on Sonic

Other Token Holders

Contact your token's project team to learn their specific migration plan. Each project will choose between migration options such as:

• Bridge migration through LayerZero or Axelar

• Airdrop migration based on snapshots

• Hybrid approach combining both methods

Project Owners

Instructions for Project Owners

Projects have several options to migrate tokens from Fantom to Sonic. There is no one-size-fits-all solution — choose based on your token's setup and requirements.

Option 1: Bridge Migration

Day-one token bridging will be available through two providers at the Sonic launch.

Provider	Implementation	User Interface	Documentation
LayerZero	Technical OFT setup	Stargate/Squid Router	OFT Standard
Axelar	Simple app integration	Direct cross-chain	Interchain app

Advantages

• Instantly available on Sonic

• Easy to use with Axelar

• Can fit many use cases with LayerZero

Limitations

• Burnt LP remains on Fantom

• If LP was sent to SCC, it can be bridged and recreated

• Original token contract stays on Fantom (generally not an issue)

---

Option 2: Airdrop Migration

Deploy new token contract on Sonic with snapshot-based airdrop distribution.

Special Cases Requirements

Case	Handling Required	Solution
Multisigs	Yes	Different addresses on Sonic
LP Tokens	Yes	Snapshot by LP weights
Burnt Tokens	Optional	Can redistribute on Sonic
Initial LP	Yes	Additional funds for pairing

Advantages

• Works for burnt tokens and LPs

• No bridge needed

Limitations

• Special handling for LP and multisig holders

• More preparation work needed

• Recreation of initial burnt LP requires additional funds

---

Option 3: Hybrid (Beethoven X Approach)

1. Deploy new token on Sonic

2. Enable bridging of original tokens

3. Create migration contract for 1:1 swaps

4. Allow two-way conversion initially

5. Switch to one-way later

Example Implementation

• New contract: sonicBeets

• Users bridge fantomBeets to Sonic

• Migration contract handles 1:1 exchange

• Two-way conversion for limited time

• Mirrors official FTM → S migration process

Credit: Franz from Beethoven X

Migration FAQ