What is the Sonic RPC URL?

The Sonic Mainnet RPC URL with BoltRPC is https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY. Replace YOUR_API_KEY with your API key from trial.boltrpc.io. The chain ID is 146.

What is the relationship between Sonic and Fantom?

Sonic is the rebranded and upgraded version of Fantom Opera. The Fantom Foundation migrated to Sonic with a new EVM execution engine and a new native token (S). Existing FTM holders can migrate to S tokens.

Can I migrate my Fantom (FTM) tokens to Sonic?

Yes. The Fantom Foundation provides an official migration path from FTM to S through the official Sonic upgrade portal. Deployed Fantom contracts can also be migrated to Sonic.

How do I add Sonic to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Sonic, RPC URL: https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY, Chain ID: 146, Currency Symbol: S, Block Explorer: https://sonicscan.org.

What is the Sonic native token?

The native gas token on Sonic is S (previously FTM on Fantom Opera). You need S tokens to pay transaction fees. Existing FTM holders can migrate to S through the official Sonic upgrade portal.

Does BoltRPC support WebSocket for Sonic?

Yes. BoltRPC provides WebSocket endpoints for Sonic at wss://eu.endpoints.matrixed.link/ws/sonic?auth=YOUR_API_KEY.

Why does Sonic's 1-second block time matter for RPC selection?

At 1-second block times, polling-based applications make 60 calls per minute for block number checks alone. This amplification makes provider reliability and pricing model more consequential on fast chains. WebSocket subscriptions avoid polling overhead entirely.

Sonic RPC Endpoint | Flat-Rate Pricing

Quick connect

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY

WebSocket

wss://eu.endpoints.matrixed.link/ws/sonic?auth=YOUR_API_KEY

Replace YOUR_API_KEY with your API key. Get a free key →

Connect

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY"
);

import { createPublicClient, http } from "viem";
import { sonic } from "viem/chains";

const client = createPublicClient({
  chain: sonic,
  transport: http("https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY"),
});

curl https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Why BoltRPC

Built for teams that ship on Sonic.

Speed-sensitive workloads need a reliable RPC provider

Sonic is built for fast finality and EVM compatibility, designed to handle high-throughput DeFi activity. When a chain produces blocks every second, your RPC endpoint becomes the remaining variable in your application's performance stack. Trading bots and yield automation scripts running on Sonic need an endpoint that keeps up with block production without introducing unnecessary delays.

Flat pricing for bot-heavy workloads

Sonic's fast blocks mean trading bots and yield optimizers poll frequently. At 1-second blocks, a bot polling every block makes 86,400 requests per day from block number checks alone, before any contract calls. Flat pricing means this polling pattern does not compound into billing surprises.

Migrating Fantom ecosystem with production requirements

Sonic is the upgraded successor to Fantom Opera. The Fantom DeFi ecosystem has migrated to Sonic. These are established protocols with production RPC requirements, not experimental deployments.

Full EVM compatibility

Any Ethereum code works on Sonic with a single endpoint change.

WebSocket for 1-second block subscriptions

At Sonic's block speed, polling is inefficient. WebSocket subscriptions deliver new block notifications as they happen, without the overhead of polling every second.

High-throughput infrastructure for trading systems

Dedicated infrastructure for production Sonic applications. Contact us for volume requirements above the Business plan.

Methods

Full JSON-RPC coverage.

Every standard Sonic method you'd expect. Archive-only methods are available on request for qualifying plans.

standard

eth_blockNumber eth_call eth_estimateGas eth_sendRawTransaction eth_getTransactionReceipt

FAQ

Sonic, explained.

Common questions about connecting to Sonic over BoltRPC.

Ask a question Read the docs

: The Sonic Mainnet RPC URL with BoltRPC is `https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY`. Replace `YOUR_API_KEY` with your API key from [trial.boltrpc.io](https://trial.boltrpc.io). The chain ID is 146.
: Sonic is the rebranded and upgraded version of the Fantom Opera network. The Fantom Foundation migrated to Sonic to introduce a new EVM execution engine and a new native token (S). Existing Fantom (FTM) holders can migrate to S tokens.
: Yes. The Fantom Foundation provides an official migration path from FTM to S (Sonic's native token). Existing FTM holders can convert their tokens through the official Sonic upgrade portal. Deployed Fantom contracts can also be migrated to Sonic.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Sonic, RPC URL: `https://eu.endpoints.matrixed.link/rpc/sonic?auth=YOUR_API_KEY`, Chain ID: 146, Currency Symbol: S, Block Explorer: https://sonicscan.org.
: The native gas token on Sonic is S (previously FTM on Fantom Opera). You need S tokens to pay transaction fees on Sonic. Existing FTM holders can migrate to S through the official Sonic upgrade portal.
: Yes. BoltRPC provides WebSocket endpoints for Sonic at `wss://eu.endpoints.matrixed.link/ws/sonic?auth=YOUR_API_KEY`. Use WebSocket for real-time Sonic event subscriptions: new blocks, pending transactions, contract events.
: At 1-second block times, applications that poll for new blocks make far more RPC calls per unit of time than on slower chains. An application that polls every block on Ethereum makes 5 calls per minute; the same pattern on Sonic makes 60 calls per minute. This amplification effect makes RPC provider reliability and pricing model more consequential on fast chains. WebSocket subscriptions avoid polling overhead entirely.

Sonic