Read pool state, index trading activity, and submit transactions with reliable, high-performance Sonic RPC infrastructure.
Connect your DeFi application to Sonic Mainnet through an HTTPS endpoint. Read contract state, collect events, and submit signed transactions with familiar Ethereum tools.
Build Sonic trading and analytics applications with archive state, execution traces, and predictable RPC capacity.
Run Sonic indexers and application backends with unlimited requests within your selected RPS tier. Keep monthly RPC costs predictable as request volume grows.
Query historical contract state and backfill event logs for Sonic indexers, accounting, and DeFi analytics.
Inspect Sonic transaction execution, diagnose reverted calls, and investigate internal contract activity with debug APIs.
Read pool contracts, simulate calls, and submit signed swaps. Connect your strategy or interface through ethers.js, viem, or web3.py.
Explore Sonic tooling
Collect contract events with eth_getLogs. Build your own price, volume, and wallet-activity indexes for the Sonic markets you support.
Explore Sonic methods
Read collateral, debt, and protocol state from lending contracts. Combine current reads with historical queries for position dashboards and risk tools.
Consigue endpoint
Inspect execution with debug and trace APIs on a paid Global Node. Follow internal calls and diagnose reverted swaps or approvals.
Explore Sonic debug APIs
Read native S balances and ERC-20 balances, estimate gas, and track receipts. Configure Sonic Mainnet chain ID 146 in your signing tools.
Explore Sonic toolingChoose Sonic Mainnet or Testnet and an available node configuration to estimate monthly infrastructure costs.
Choose an available Sonic network and node configuration to estimate monthly infrastructure costs.
Testimonios de clientes de equipos que utilizan « Chainstack » en las redes compatibles.
ChainstackSu sólida infraestructura ha mejorado considerablemente nuestra capacidad para proteger de forma eficaz los entornos Web3.Chainstack ha sido fundamental para mejorar la funcionalidad multicadena y la experiencia de usuario de Brave Wallet.El modelo de tarifa plana «Unlimited» de Node nos ofrece previsibilidad en los costes, y el rendimiento es muy sólido.Hemos pasado de tener incidentes semanales a no tener ninguno.Colaborar con Chainstack nos ha ayudado a reducir nuestros costes de infraestructura en más de un 70 %, al tiempo que hemos abordado complejos retos en materia de seguridad de Web3.
Query pool state, collect swap and token-transfer logs, and track transaction receipts through one Sonic RPC endpoint. Use historical state and execution traces for DeFi analytics and debugging.
Consigue endpointRun Sonic Mainnet or Testnet on infrastructure you control. Deploy sonicd with monitoring, automated updates, and self-healing operations through Chainstack Self-Hosted.
Read token-transfer events from the latest Sonic block with eth_getLogs.
Infraestructura preparada para la IA
Recomiende y gane
Ethereum
Hyperliquid
Solana
Arbitrum
BNB Smart Chain
Base
Polygon
TRON
Sui
Robinhood
SOC 2 Tipo II
ISO 27001
99,99 %+ de tiempo de actividad
Más información
Ver la guía de instalaciónhttps://sonic-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDCreate a Sonic node. Copy your authenticated HTTPS URL from Acceso y credenciales y sustituir YOUR_ENDPOINT_ID en el ejemplo.
curl --request POST \
--url https://sonic-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_getLogs",
"params": [
{
"fromBlock": "latest",
"toBlock": "latest",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
]
}
]
}'The result is an array of matching logs. Add your token or pool contract address and paginate historical block ranges when building an indexer.
Start with free Sonic RPC. Scale your application with paid plans, higher throughput, and dedicated infrastructure.
Incluye:
Todas las funciones de « Developer », además de:
Los complementos y la infraestructura dedicada de Node se facturan por separado.
Asistencia excepcional en todos los planes de pagoAhorra más del 50 % con nuestro plan de élite de pago por uso
Chatea en Telegram (se abre en una nueva pestaña)Explore Sonic RPC, application development, and infrastructure guides.
Read the testnet development walkthrough.
Leer el artículo
Explore managed Sonic node infrastructure.
Leer el artículo
Learn historical contract reads for DeFi analytics.
Leer el artículo
Set access rules for production applications.
Leer el artículo
A Sonic RPC endpoint connects your application to Sonic through Ethereum-compatible JSON-RPC. Use it to read balances and contract state, query event logs, estimate gas, and send signed transactions. Sonic Mainnet uses chain ID 146 and S for gas. See the Sonic tooling guide.
Sí. El plan « Developer » de Chainstackincluye 3 millones de request units al mes, 25 solicitudes por segundo y un node, sin necesidad de tarjeta de crédito. El consumo de unidades de solicitud depende del método. Crea una cuenta gratuita o compara las características de los planes.
Mainnet: https://sonic-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID.
Testnet: https://sonic-testnet.core.chainstack.com/YOUR_ENDPOINT_ID.
Sustituir YOUR_ENDPOINT_ID con el identificador que encontrarás en el panel «Acceso y credenciales» de tu node. Mantén ese identificador en secreto y utiliza la URL completa que se te ha facilitado para tu red implementada. Get a Sonic endpoint.
Sonic Mainnet uses chain ID 146. The current Sonic Testnet uses chain ID 14601. Match the chain ID to the network selected for your RPC endpoint. See Sonic’s official network settings.
No. The current Sonic Testnet uses chain ID 14601, while legacy Blaze Testnet uses 57054. Do not reuse a Blaze chain ID or endpoint URL for the current Testnet. Check your deployed node’s network and use the matching connection details. See Sonic’s current Testnet settings.
Yes. Connect ethers.js, viem, web3.py, Hardhat, or Foundry to the HTTPS endpoint for your Sonic network. Use standard EVM methods such as eth_call, eth_getLogs, y eth_sendRawTransaction. Consulta el Sonic tooling guide for integration examples.
Yes. Sonic archive access is available on paid plans for historical contract-state reads. Event-log retrieval and historical state are different workloads: specify the block you need for state queries, and paginate log backfills. Available historical ranges depend on the node configuration and retained data. See supported networks and node modes.
Yes. On a paid plan, deploy a Sonic Global Node with debug and trace APIs enabled. Use execution traces to investigate reverted calls and internal contract activity. Check the supported methods and deployment requirements before choosing your node configuration.
Yes. Chainstack Self-Hosted supports Sonic Mainnet and the current Sonic Testnet using sonicd. Deploy on infrastructure you control and manage the node through the Chainstack Self-Hosted interface. Hosting resources remain your responsibility. See the installation guide y supported deployment catalog.
Connect your application to Chainstack’s Sonic HTTPS endpoint to read balances, call contracts, query event logs, and submit signed transactions. Use eth_call para la lectura de contratos, eth_getLogs Para consultas sobre eventos, eth_getTransactionReceipt para la comprobación de recibos, y eth_sendRawTransaction to broadcast a signed transaction. Sonic Mainnet uses chain ID 146. The current Sonic Testnet uses chain ID 14601.
A Chainstack Sonic Mainnet endpoint follows the format https://sonic-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID. Sustituye YOUR_ENDPOINT_ID with your own authenticated node identifier. Use ethers.js, viem, or web3.py to build DeFi interfaces, trading systems, and historical analytics. Filter event logs by contract address and topic, and keep historical block ranges bounded. See the Sonic tooling guide y Referencia de métodos RPC para obtener más información sobre la integración.
Legacy Blaze Testnet uses chain ID 57054 and is separate from the current Sonic Testnet. Match your node’s network, endpoint URL, and chain ID before submitting transactions.
