Read player assets, track NFT transfers, and send transactions with reliable Ronin RPC infrastructure for game backends and marketplaces.
Connect your game or marketplace to Ronin Mainnet and Saigon over HTTPS and WebSocket. Read contract state, follow asset transfers, and submit signed transactions.
Build Ronin game backends with asset history, contract debugging, and predictable RPC capacity.
Run Ronin 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 Ronin indexers, accounting, and DeFi analytics.
Inspect Ronin transaction execution, diagnose reverted calls, and investigate internal contract activity with debug APIs.
Query NFT ownership and token balances from game contracts. Use indexed transfer history for player inventories and activity feeds.
Explore Ronin methods
Read collection data, follow asset transfers, and check transaction receipts. Connect your marketplace’s contract logic through standard EVM APIs.
Explore Ronin tooling
Collect ERC-20, ERC-721, and ERC-1155 contract events. Keep game-specific indexes for asset issuance, transfers, and marketplace interactions.
Explore event logs
Inspect failed purchases, token approvals, and contract calls. Enable debug and trace APIs on a Ronin Global Node for execution analysis.
Explore Ronin debug APIs
Exercise your contracts and transaction flows on Saigon before Mainnet. Configure the current Saigon chain ID, 202601, in your signing tools.
Explore Ronin toolingDiscuss Ronin infrastructure, available configurations, and pricing with the Chainstack team.
Customer stories from teams using Chainstack across supported networks.
Empowered by Chainstack’s fast, reliable, and cost-effective Web3 infrastructure, Ronin is now ready to enter the next phase of ecosystem expansion.Chainstack has been crucial in enhancing Brave Wallet’s multi-chain functionality and UX.The Unlimited Node flat-fee model gives us cost predictability, and the performance is rock-solidWe’ve gone from weekly incidents to zero incidents.Working with Chainstack helped us cut our infrastructure costs by over 70%, all while tackling intricate challenges in Web3 security.
Read token ownership, collect NFT transfer events, and track confirmed receipts. Build your own game and marketplace indexes around Ronin RPC instead of operating node infrastructure.
Get endpointRun Ronin Saigon on infrastructure you control. Deploy the OP Stack execution and rollup clients with an EigenDA proxy, monitoring, automated updates, and self-healing operations through Chainstack Self-Hosted.
Read token-transfer events from the latest Ronin block with eth_getLogs.
AI-ready infrastructure
Refer and earn
Ethereum
Hyperliquid
Solana
Arbitrum
BNB Smart Chain
Base
Polygon
TRON
Sui
Robinhood
SOC 2 Type II
ISO 27001
99.99%+ uptime
Learn more
View installation guidehttps://ronin-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDwss://ronin-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDCreate a Ronin node. Copy your authenticated HTTPS URL from Access and credentials and replace YOUR_ENDPOINT_ID in the example.
curl --request POST \
--url https://ronin-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 contains matching Transfer logs. For NFT inventories, filter by the collection contract and decode its ERC-721 or ERC-1155 events. Keep historical queries on one side of a network migration boundary.
Start with free Ronin RPC. Scale your application with paid plans, higher throughput, and dedicated infrastructure.
Includes:
All Developer features, plus:
Add-ons and Dedicated Node infrastructure are billed separately.
Exceptional support on every paid planSave over 50% on our elite Pay-as-you-go plan
Chat on Telegram (opens in a new tab)Explore Ronin RPC, application development, and infrastructure guides.
Explore Ronin RPC access for gaming applications.
Read article
Explore the OP Stack and EigenDA deployment option.
Read article
Compare infrastructure costs across supported networks.
Read article
Control access to your game’s backend infrastructure.
Read articleExplore open-source projects from our developer experience team. Follow practical guides, watch walkthroughs, and adapt the code for your application.
Solidity · Ronin gaming
Explore a Ronin game driven by block hashes. Use Foundry to build the contract and follow the guide’s game logic, deployment, and interaction examples.
Python · RPC performance
Run repeatable RPC load tests with Chainbench’s built-in profile for this network. Configure the method mix, concurrency, and test duration for your application.
A Ronin RPC endpoint connects your game, wallet, or marketplace to Ronin through Ethereum-compatible JSON-RPC. It lets you read contract state, query asset transfers, estimate gas, and submit signed transactions. Ronin Mainnet uses chain ID 2020 and RON for gas. See the Ronin tooling guide.
Yes. Chainstack’s Developer plan includes 3 million request units per month, 25 requests per second, and one node, with no credit card required. Request-unit consumption depends on the method. Create a free account or compare plan features.
Mainnet: https://ronin-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID.
Saigon Testnet: https://ronin-saigon.core.chainstack.com/YOUR_ENDPOINT_ID.
Replace YOUR_ENDPOINT_ID with the identifier from your node’s Access and credentials panel. Keep that identifier private and use the complete URL supplied for your deployed network. Get a Ronin endpoint.
Ronin Mainnet uses chain ID 2020. The current Saigon Testnet uses chain ID 202601. Saigon’s former chain ID, 2021, applies to its pre-migration network. Configure current Saigon transactions for 202601. See the Ronin network settings.
Ronin RPC can read NFT contracts and retrieve transfer logs. Your application can build an inventory index from ERC-721 and ERC-1155 events, then query current ownership where the contract supports it. A standard RPC endpoint is not a ready-made cross-collection inventory or NFT metadata API. See the Ronin event-log reference.
Split historical event queries at the relevant migration boundary instead of sending one eth_getLogs request across both backends. For Saigon, blocks below 45528550 belong to its previous L1 history; blocks from 45528550 onward belong to the L2 network. Query each range separately. See the Ronin tooling and migration notes for historical-query requirements.
Yes. Ronin 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. Network migrations and retained data can affect the available historical range. See supported networks and node modes.
Yes. Deploy a Ronin 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 Ronin Saigon using an OP Stack execution client, rollup client, and EigenDA proxy. Deploy on infrastructure you control and manage the node through the Chainstack Self-Hosted interface. Hosting resources remain your responsibility. See the installation guide and supported deployment catalog.
Connect your application to Chainstack’s Ronin HTTPS endpoint to read balances, call contracts, query event logs, and submit signed transactions. Use eth_call for contract reads, eth_getLogs for event queries, eth_getTransactionReceipt for receipt checks, and eth_sendRawTransaction to broadcast a signed transaction. Ronin Mainnet uses chain ID 2020. Saigon Testnet uses chain ID 202601.
A Chainstack Ronin Mainnet endpoint follows the format https://ronin-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID. Replace YOUR_ENDPOINT_ID with your own authenticated node identifier. Use ethers.js, viem, or web3.py to build game backends, NFT marketplaces, and asset-activity indexes. WebSocket subscriptions can follow new blocks and contract logs; use bounded HTTPS log requests for historical backfills. See the Ronin tooling guide and RPC method reference for integration details.
For historical event queries, split requests at the relevant network migration boundary. On Saigon, blocks below 45528550 are served by the previous L1 backend, while blocks from 45528550 onward are served by the L2 backend. A single event-log request must stay within one range.
