Read liquidity-pool state, follow token transfers, and send transactions on Cronos EVM with reliable, high-performance RPC infrastructure.
Connect to Cronos EVM Mainnet over HTTPS and WebSocket. Read contract state, subscribe to events, and submit signed transactions using familiar Ethereum libraries.
Build Cronos applications with archive state, contract debugging, and predictable RPC capacity.
Run Cronos 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 Cronos indexers, accounting, and DeFi analytics.
Inspect Cronos execution with debug_traceTransaction and debug_traceCall. Diagnose reverted calls without maintaining a debugging node.
Read liquidity-pool state, simulate contract calls, and submit signed swaps. Connect your application with ethers.js, viem, or web3.py.
Explore Cronos tooling
Collect contract events with eth_getLogs and subscribe to new logs over WebSocket. Track the assets and pools your application supports.
Explore Cronos methods
Read native CRO balances, query ERC-20 balances, and check transaction receipts. Keep gas estimates and transaction status close to the user flow.
Consigue endpoint
Use debug_traceTransaction and debug_traceCall to inspect execution. Cronos exposes debug APIs rather than the trace namespace.
Explore Cronos debug APIs
Use Ethereum development tools with Cronos EVM chain ID 25. Cronos EVM is a separate network from Cronos zkEVM and Cronos POS.
Explore Cronos toolingChoose Cronos mainnet or Sepolia and an available node configuration to estimate monthly infrastructure costs.
Choose an available Cronos network and node configuration to estimate monthly infrastructure costs.
Testimonios de clientes de equipos que utilizan « Chainstack » en las redes compatibles.
…the ecosystem is excited to welcome Chainstack to bring low friction, enterprise-grade node infrastructure to the Cronos developer community.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 contracts over HTTPS, collect trading events with eth_getLogs, and subscribe to new logs over WebSocket. Backfill historical data for the markets your application follows.
Consigue endpointRun Cronos EVM Mainnet or Testnet on infrastructure you control. Deploy cronosd with monitoring, automated updates, and self-healing operations through Chainstack Self-Hosted.
Read token-transfer events from the latest Cronos 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://cronos-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDwss://cronos-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDCreate a Cronos node. Copy your authenticated HTTPS URL from Acceso y credenciales y sustituir YOUR_ENDPOINT_ID en el ejemplo.
curl --request POST \
--url https://cronos-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 the token or pool contract address and bounded block ranges when collecting historical activity.
Start with free Cronos 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 Cronos RPC, application development, and infrastructure guides.
Explore managed RPC access and application development.
Leer el artículo
Follow a practical Solidity deployment walkthrough.
Leer el artículo
Learn the event-subscription pattern for EVM trading feeds.
Leer el artículo
Set access rules for production applications.
Leer el artículoExplora los proyectos de código abierto de nuestro equipo de experiencia en « developer ». Sigue las guías prácticas, mira los tutoriales y adapta el código a tu aplicación.
JavaScript · Smart contracts
Write a Solidity lottery contract, then deploy and verify it on Cronos Testnet with Hardhat. Follow the repository and guide for contract interaction and testing.
A Cronos RPC endpoint connects your application to Cronos EVM through Ethereum-compatible JSON-RPC. Use it to read balances and contract state, retrieve event logs, estimate gas, and send signed transactions. Cronos EVM is separate from Cronos POS and Cronos zkEVM. See the Cronos 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://cronos-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID.
Testnet: https://cronos-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 Cronos endpoint.
Cronos Mainnet uses chain ID 25. Cronos Testnet uses chain ID 338. These are Cronos EVM networks, not Cronos POS or Cronos zkEVM. See the Cronos tooling guide for connection examples.
Yes. Use the WebSocket URL in your node’s Access and credentials panel with eth_subscribe to follow new blocks and contract logs. Use HTTPS and eth_getLogs for historical backfills, and reconnect and catch up after a dropped subscription. See the Cronos connection examples.
Paid Cronos Global Nodes expose debug_traceTransaction, debug_traceCall, debug_traceBlockByNumber, y debug_traceBlockByHash. Cronos does not serve the trace_* namespace. On Cronos Mainnet archive nodes, debug_traceBlockByNumber is limited to 10 requests per second on all plans. See Cronos debug API availability.
Yes. Cronos 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. Chainstack Self-Hosted supports Cronos Mainnet and Testnet using cronosd. 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 Cronos 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. Cronos Mainnet uses chain ID 25. Cronos Testnet uses chain ID 338.
A Chainstack Cronos Mainnet endpoint follows the format https://cronos-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 wallet backends. WebSocket subscriptions can follow new blocks and contract logs; use bounded HTTPS log requests for historical backfills. See the Cronos tooling guide y Referencia de métodos RPC para obtener más información sobre la integración.
