App Token Migration

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

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

App Token Holders

Instructions for Token Holders

The official Sonic Labs upgrade portal will facilitate the FTM to S upgrade on a 1:1 basis.

Official Migration Contract Timeline

Phase	Duration	Conversion Type	Notes
Initial period	December 18, 2024 – March 31, 2025	Two-way FTM ↔ S	Full flexibility
Final phase	Indefinite	One-way FTM → S	No reverse conversion

CEX-Held FTM

If you hold FTM on a centralized exchange, we’re collaborating with major exchanges to enable users to upgrade FTM to S directly on their platforms. Stay tuned for updates from the CEX where you hold your FTM.

Alternatively, you can withdraw your FTM to Fantom Opera and upgrade to S through our upgrade portal.

Staked FTM

Users will be able to unlock their staked FTM and bridge immediately to Sonic following a 24-hour withdrawal waiting period. The new Sonic staking system features:

Parameter	Requirement
Withdrawal period	14 days
Minimum stake	1 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

• Airdrop migration based on snapshots

• Hybrid approach combining both methods

Project Developers

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 LayerZero at the Sonic launch.

Provider	Implementation	User Interface	Documentation
LayerZero	Technical OFT setup	Stargate	OFT Standard

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