DEV Community

OnFinality
OnFinality

Posted on • Originally published at onfinality.io

Sonic RPC: Endpoints, Chain Settings, and Provider Guide

#web3 #tutorial #devops #blockchain

Sonic RPC at a Glance

Sonic is a high-performance EVM Layer-1 blockchain designed for DeFi and high-throughput applications. It offers sub-second finality and full EVM compatibility, making it easy to port existing Ethereum tooling. For developers, the first step is understanding the network's chain settings and available RPC endpoints.

Chain Settings

Network Chain ID RPC URL Explorer
Sonic Mainnet 146 (0x92) https://rpc.soniclabs.com sonicscan.org
Sonic Testnet (check official docs) (check official docs) (check official docs)

Note: Always verify the latest testnet details from the official Sonic documentation, as they can change.

Quick Recommendation: Public vs Managed RPC

For development and testing, public endpoints like https://rpc.soniclabs.com are sufficient. For production applications, you need a managed RPC provider that offers reliability, scalability, and support. Consider factors like rate limits, uptime guarantees, archive data, WebSocket support, and pricing.

If you're evaluating providers, start with a free tier to test latency and reliability, then scale as your user base grows. OnFinality offers Sonic RPC as part of its supported networks with flexible pricing.

What Is Sonic?

Sonic is a Layer-1 blockchain that combines a novel consensus mechanism with EVM compatibility. It aims to deliver high throughput (10,000+ TPS) and sub-second finality, making it attractive for DeFi applications that require fast transaction confirmation. Its native token is S, and it uses a block gas limit of 200,000,000.

Why RPC Provider Choice Matters

The RPC provider is the bridge between your application and the Sonic blockchain. The right provider affects:

  • Latency: Lower latency improves user experience.
  • Uptime: Reliability keeps your dApp online.
  • Rate Limits: Limits can throttle your traffic.
  • Features: Archive nodes, WebSockets, and trace methods vary.
  • Cost: Pricing models differ significantly.

Sonic RPC Endpoint Options

You have several options for accessing Sonic:

  1. Public Endpoints: Free but often rate-limited and not suitable for production.
  2. Managed Providers: Offer reliable, low-latency access with support and SLAs.
  3. Self-Hosted Nodes: Full control but requires infrastructure management.

Public Endpoints

  • https://rpc.soniclabs.com (official)
  • https://sonic-rpc.publicnode.com
  • wss://sonic-rpc.publicnode.com (WebSocket)

Managed Providers

Providers like QuickNode, Alchemy, and OnFinality offer dedicated Sonic endpoints with features like archive data, WebSocket support, and global infrastructure.

How to Connect to Sonic RPC

You can interact with Sonic using standard Ethereum JSON-RPC methods. Here's a basic curl example:

curl https://rpc.soniclabs.com \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
Enter fullscreen mode Exit fullscreen mode

Using ethers.js 

const { ethers } = require("ethers");

const provider = new ethers.JsonRpcProvider("https://rpc.soniclabs.com");

async function getBlockNumber() {
  const blockNumber = await provider.getBlockNumber();
  console.log("Current block:", blockNumber);
}

getBlockNumber();
Enter fullscreen mode Exit fullscreen mode

Wallet Configuration

To add Sonic to MetaMask or other wallets, use the following settings:

  • Network Name: Sonic Mainnet
  • RPC URL: https://rpc.soniclabs.com
  • Chain ID: 146
  • Currency Symbol: S
  • Explorer URL: https://sonicscan.org

Evaluating Sonic RPC Providers

When choosing a provider, consider the following criteria:

Criterion What to Check Why It Matters
Uptime Historical uptime stats Downtime breaks your app
Latency Response times from your region Slow responses hurt UX
Rate Limits Requests per second/day Limits can throttle growth
Archive Data Availability of historical state Needed for analytics and debugging
WebSocket Support for real-time subscriptions Essential for live updates
Pricing Cost per request or subscription Must fit your budget
Support SLAs and customer service Critical for production issues

Common Pitfalls and Troubleshooting

  • Rate Limiting: Public endpoints often limit requests. Use a managed provider for production.
  • WebSocket Disconnects: Ensure your client handles reconnection logic.
  • Incorrect Chain ID: Double-check that you're using 146 for mainnet.
  • Transaction Failures: Verify gas limits and token balances.

Key Takeaways

  • Sonic is a fast EVM Layer-1 with chain ID 146.
  • Public RPC endpoints are fine for testing but not for production.
  • Choose a managed provider that offers reliability, scalability, and support.
  • Always verify chain settings and use proper error handling in your code.

Frequently Asked Questions

What is the Sonic RPC URL?

The official public RPC URL is https://rpc.soniclabs.com. For production, consider a managed provider.

What is the Sonic Chain ID?

The Sonic mainnet chain ID is 146 (0x92).

Does Sonic support WebSocket?

Yes, Sonic supports WebSocket for real-time subscriptions, e.g., wss://sonic-rpc.publicnode.com.

How do I get Sonic testnet tokens?

Check the official Sonic documentation for faucet details.

Can I use OnFinality for Sonic RPC?

OnFinality provides Sonic RPC as part of its supported networks. Visit RPC pricing for details.

Related resources

Originally published at OnFinality.

Top comments (0)