Sonic Wallet: Send, Receive and Swap S, the Fantom Successor

Sonic addresses and the Fantom Opera mix-up

Sonic uses standard 0x addresses, so Keylo shows the same address for Sonic as for Ethereum and every other EVM network. There is no activation step, no memo and no minimum balance. The confusion comes from history: Fantom Opera, chain ID 250, also used 0x addresses, and plenty of exchanges, bridges and old tutorials still mention it. Opera and Sonic are separate chains, and Keylo supports Sonic, not Opera.

If someone sends FTM to your address on Opera, it really is yours, because the same key controls that address everywhere. But it will not appear in Keylo, and it is not S. Holders of old FTM can still upgrade to S through Sonic's official upgrade route; check the Sonic Labs website for the current process rather than trusting links shared in chats or search ads.

How to create a Sonic wallet with Keylo

Keylo never receives your password, phrase or private keys; it stores only the encrypted wallet, so it cannot move or recover your S. If you used MetaMask or Rabby with Fantom, you can import that 12- or 24-word phrase. Keylo uses the default Ethereum derivation path, so the first account matches. Funds still on Opera stay there, though, and need upgrading separately.

1. 1

   Go to create a wallet in a modern browser on phone, tablet or desktop. No extension is needed.

2. 2

   Enter your name, email, phone and a strong password, then confirm your email address from the link Keylo sends.

3. 3

   Keylo creates a 12-word recovery phrase on your device and encrypts it locally with a key derived from your password.

4. 4

   Choose Sonic in your network list to see your S balance and 0x address.

5. 5

   Reveal the phrase in Settings after re-entering your password, and copy it onto paper kept somewhere safe.

How to receive S on Sonic

Exchanges often keep their own deposit processing on top of network finality, so an exchange withdrawal can still take a few minutes even though Sonic itself is nearly instant. If the explorer shows the transfer to your address on Sonic, the funds have arrived; a delay in Keylo's balance is then just a refresh issue.

1. 1

   Open S in Keylo and tap Receive.

2. 2

   Copy your 0x address or show the QR code. Keylo labels it Sonic so the network is clear.

3. 3

   Ask the sender, or your exchange, to use the Sonic network. Do not accept S on Fantom or as a token on another chain.

4. 4

   Check Activity. Sonic finality is under a second, so incoming transfers appear almost immediately, with an explorer link.

How to send S

Because Sonic transactions finalise so quickly, there is very little window to notice a mistake. Read the full address on the review screen before you confirm, especially if you copied it from a chat or website, where clipboard malware can swap characters in the middle where people rarely look.

Sending to an exchange? Use the deposit address the exchange shows for the Sonic network specifically. Some platforms still group S under older Fantom branding, and others reuse one 0x deposit address across many networks but only credit the ones they list. No memo or tag is needed on Sonic, so an exchange asking for one is probably showing you a different network.

1. 1

   Open S, or a Sonic token, and tap Send.

2. 2

   Paste or scan the recipient's 0x address. Keylo validates the checksum and highlights contract addresses.

3. 3

   Enter an amount or tap Max, which keeps back enough S for the fee.

4. 4

   Pick slow, normal or fast, then review the exact amount and network fee.

5. 5

   Confirm to sign in your browser and broadcast to Sonic.

Sonic gas fees and Fee Monetization

Fees on Sonic are paid in S and use an EIP-1559 style base fee plus an optional tip. A simple transfer costs a small fraction of an S, and contract calls cost more in proportion to the gas they use. Keylo's slow, normal and fast choices adjust the tip and fee cap; with sub-second finality, the difference in confirmation time is usually tiny.

When you use a FeeM-registered app, most of the fee from your transaction can flow to that app's developer instead of only to the network. None of this is an extra charge on top of the fee. Keylo adds no fee of its own to a normal send, and the review screen always shows the total network fee in S before you sign.

Tokens and stablecoins on Sonic

Tokens on Sonic are ERC-20 contracts, and you need S for gas to move any of them. Stablecoins mostly arrive through bridges such as the Sonic Gateway, so you may see labels like USDC.e for bridged USDC. Wrapped S, staked S from liquid staking apps and many DeFi tokens live here too, often with similar names.

Symbols are not unique on any EVM chain. Before trading a token, look it up on the Sonic explorer and compare the contract address with the one the issuer publishes. Old FTM-era tokens did not automatically move to Sonic, so a token with a familiar Fantom name on Sonic may be a new deployment, a bridged copy or an impostor.

Liquid staking tokens deserve a word of their own. They represent S that an app has staked with Sonic validators on your behalf, and they move like any other token. Their value depends on the protocol behind them and on how quickly it lets you exit, so read its unbonding rules first. Keylo shows these balances like any token but does not stake S itself.

Swap S or bridge to Ethereum

Keylo supports swaps and bridges on Sonic through LI.FI, which searches DEXs and audited bridges for a route. You can swap S for stablecoins on Sonic or move value between Sonic and networks such as Ethereum, Base or Arbitrum. The quote shows the route, expected output, minimum received and every fee, including any small service fee, before you confirm. The swap and bridge page explains more.

Sonic's own canonical bridge, the Sonic Gateway, batches transfers: deposits from Ethereum are processed roughly every ten minutes and withdrawals about hourly, and it includes a fail-safe that lets users recover bridged assets on Ethereum if the Gateway stops working for 14 days. Third-party routes are often faster. Either way, if a route cannot complete, the protocol refunds the sending wallet.

Sonic safety tips

• Use only the official Sonic Labs site for FTM upgrades. Fake upgrade and migration portals are the most common Sonic scam.
• Pick the Sonic network, not Fantom, for S deposits and withdrawals.
• Check token contracts on the explorer before buying anything with a familiar Fantom name.
• Revoke or avoid unlimited token approvals for apps you no longer use.
• Keep your recovery phrase offline and never type it into a website. See how Keylo protects your funds.
• Turn on two-factor authentication and an anti-phishing code for Keylo emails.

Frequently asked questions