# Why are we moving to Sonic

**CrossCurve is moving to Sonic**

We have made a strategic decision to migrate **CrossCurve'**s hub chain from **Fantom** (**FTM**) to **Sonic**. This is not just a network change - it’s a transition to a new level of speed, efficiency, and possibilities. Let's explore why Sonic is the optimal choice, what benefits it brings to users, and how this step will shape our future.

## Why are we moving to Sonic?

### 1. Game-changing speed

**Sonic** dramatically accelerates blockchain operations. The average transaction finalization time is just **720 milliseconds**.

For comparison:

* **Ethereum** — \~12 seconds
* **Fantom Opera** — \~1-2 seconds

This makes **Sonic** one of the fastest **EVM**-compatible blockchains. In **DeFi**, speed is critical: minimal latency reduces arbitrage risks, improves liquidity conditions, and enhances user experience.

**Sonic** brings blockchain interactions closer to **Web2** performance—transactions process instantly, while fees remain minimal.

### 2. An economic model that rewards projects

Most blockchains either burn fees or direct them to network funds. **Sonic** takes a different approach:

* **Up to 90% of fees are returned to developers**
* **Projects generate sustainable revenue without raising fees**
* **Liquidity is redistributed to benefit everyone**: users, developers, and token holders

The more activity in the network, the higher the protocol revenues and user incentives.

### 3. Simple migration and ecosystem support

**Sonic** is an evolution of **Fantom’**s technology but with enhanced features.

What does this mean for projects?

* **Easy migration** — smart contract code requires minimal changes
* **$120M support fund** — **Fantom** has allocated grants to migrate dApps to **Sonic**
* **Major centralized exchanges have integrated automatic FTM → Sonic (S) swaps**

We gain all the advantages of the new network without losing functionality or liquidity.

## Why is Sonic better than other blockchains?

### 1. ve(3,3) Flywheel: a powerful tokenomics model

**Sonic’**s economy is built on the **ve(3,3)** concept, which incentivizes staking, liquidity, and long-term token holding.

This model has already proven successful in **Curve**, **Solidly** and **Velodrome**, creating a sustainable **DeFi** cycle.

### 2. Leading DeFi projects are moving to Sonic

**Sonic** has already attracted top players, including:

* **AAVE** — a leading DeFi protocol managing $10B+ in assets
* **Curve** — the largest stablecoin exchange platform
* **Solidly and other major DeFi projects** — key players in the industry

This means liquidity and users are already migrating to **Sonic**, making participation in this ecosystem strategically important.

### 3. Full Ethereum compatibility

**Sonic** supports **EVM**, making it fully compatible with existing **Ethereum** and **Fantom** smart contracts.

А **Sonic Gateway** — a native bridge enabling secure asset transfers between **Ethereum** and **Sonic** without reliance on centralized solutions.

## Conclusion

**CrossCurve**’s transition to **Sonic** is not just an upgrade - it’s a leap forward in technology.

What are the key benefits?

* **720ms transactions** — faster than any other EVM blockchain
* **Up to 90% of fees returned to developers** — projects earn more
* **Seamless migration with $120M support** — transition risks minimized.
* **Top DeFi projects onboarded** — **Sonic’**s ecosystem is growing rapidly


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.crosscurve.fi/user-documentation/migration-to-sonic/why-are-we-moving-to-sonic.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.