Sonic RPC Endpoint

Flat-rate Sonic RPC provider and Sonic RPC node access: free tier, no KYC, HTTP & WebSocket. Sonic mainnet chain ID 146.

Sonic is the rebranded and upgraded version of Fantom, launched in late 2024 with a new high-performance EVM execution layer (Sonic Engine). It offers sub-second finality and 10,000+ TPS targets, with an aggressive fee-sharing model that returns 90% of gas fees to dApp developers.

About Sonic

Sonic's core innovation is its custom EVM-compatible execution layer that maintains Solidity bytecode compatibility while achieving dramatically higher throughput than typical EVM chains. The S token is the native asset (1:1 with FTM via migration).

Sonic also introduced "FeeM" — fee monetization — where 90% of transaction fees paid in interaction with a dApp are returned to that dApp's developers. This creates strong incentive alignment between the chain and builders.

Common Use Cases on Sonic

• DeFi with sub-second finality
• GameFi and high-frequency dApps
• Developer revenue-sharing applications (FeeM)
• AI inference settlement (Sonic Labs has been positioning here)
• Migration target for existing Fantom dApps

Sonic Ecosystem

All major Fantom DeFi protocols (SpookySwap, Beethoven X, Equalizer) migrated to Sonic. New projects building specifically for the FeeM model. Sonic Labs has incentive programs running for builders.

Sonic Mainnet RPC URL (HTTP)

Sonic WebSocket RPC URL

Quick Start: Connect to Sonic

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/sonic?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/sonic?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("Sonic block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/sonic?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/sonic?key=YOUR_API_KEY"))
print("Sonic block:", w3.eth.block_number)

Add Sonic to MetaMask

Bridging to Sonic

Sonic Gateway (https://gateway.soniclabs.com) for Ethereum ↔ Sonic. Stargate, LayerZero for general cross-chain. Fantom Opera migration handled separately.

Features of SwiftNodes for Sonic

• Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
• Health-checked every 2 minutes with automatic failover
• Free tier available — no credit card or KYC required
• Flat-rate monthly pricing with no per-request fees
• HTTP and WebSocket support
• One API key works across all 75+ supported chains, including Sonic

Rate Limits

Frequently Asked Questions: Sonic

Sonic RPC methods

Measured weekly through this endpoint: what each method returns on Sonic, its limits, and an example request.

• eth_getLogssupported
• eth_getBlockReceiptssupported
• eth_feeHistorysupported
• eth_getProofsupported
• eth_createAccessListsupported
• debug_traceCallsupported
• trace_blocksupported
• trace_transactionsupported

Sonic guides from the blog

• Sonic RPC: Fantom's Successor, New Chain IDSonic is the high-performance L1 successor to Fantom Opera (chain ID 146, not 250) with sub-second finality and a 90%-fees-to-developers model. It's standard EVM (viem/ethers/foundry work), but if you're migrating from Fantom the new chain ID and S token are the first things to get right. Here's the developer map.
• Connecting MetaMask to Sonic, Berachain, and MonadThree of 2025's biggest EVM chain launches, three sets of MetaMask configuration values. The exact fields to paste, why the official public RPCs aren't enough for real use, and the errors to expect when you mistype something.

Related EVM chains

Explore RPC endpoints for other EVM networks on SwiftNodes: