📝Network Specifications

Mainnet and testnet chain specifications, explorer links, and public RPC endpoints.

Network Specifications and Public Endpoints

Chain ID

Cronos has different Chain IDs to distinguish between the devnet, testnet and mainnet. When running Cronos in your local environment, you will need to decide your own Chain ID.

For example, our testnet Chain ID is cronostestnet_338-3.

Cronos EVM Mainnet Specs

• Chain ID: 25

• JSON RPC API: https://evm.cronos.com

• Block explorer: https://explorer.cronos.com/

• Native token symbol: CRO

Cronos EVM Testnet Specs

• Chain ID: 338

• JSON RPC API: https://evm-t3.cronos.com/

• Block explorer: https://explorer.cronos.com/testnet

• Native token symbol: tCRO

Block Explorers

Cronos Mainnet

• Cronos Explorer: https://explorer.cronos.com/

Testnet

• Cronos Testnet Explorer: https://explorer.cronos.com/testnet

Cronos Explorer is the reference transaction and block explorer on Cronos https://explorer.cronos.com

Free RPC URLs for Cronos

Public RPCs URL Updates:

The Cronos RPC endpoints have been updated in March 2021 (shown as below) and it is recommended that all users update the endpoints. The old endpoints are still available for compatibility but maybe deprecated later.

Request Limits on Public RPCs:

To provide a stable experience to users, there is a request rate limit on the public RPCs to ensure fair usage. If your application requires a higher usage, please consider setting up your own nodes or using a commercial node provider. You can also reach out to us on Discord for assistance.

Public RPCs Integration Tips:

There are more than one machines serving the public RPC services. There is no guarantee that you are served by the same machine every time. For example, if you are broadcasting many transactions in a row, they will be sent to multiple machines that may not be perfectly in sync with respect to the account nonce, and this may cause your batch to fail.

If you are sending large numbers of transactions from your backend, consider setting up a single dedicated node.

Mainnet

• EVM HTTP JSON RPC (Web3 compatible)

  • https://evm.cronos.com/

• Block explorer

  • https://explorer.cronos.com/

• Tendermint RPC

  • https://rpc.cronos.com/

• Cosmos RESTful

  • https://rest.cronos.com/

• Cosmos gRPC Based

  • https://grpc.cronos.com/

• Swagger Rest API

  • https://rest.cronos.com/swagger/

Testnet

• EVM HTTP JSON RPC (Web3 compatible)

  • https://evm-t3.cronos.com/

• Block explorer

  • https://explorer.cronos.com/testnet

• Tendermint RPC

  • https://rpc-t3.cronos.com/

• Cosmos RESTful

  • https://rest-t3.cronos.com/

• Cosmos gRPC Based

  • https://grpc-t3.cronos.com/

Commercial node providers

Disclaimer:

The RPC endpoints below are provided by third-party services. Please conduct thorough independent research and testing before use. The use of these endpoints is at the user's sole risk.

• Moralis:

  • Moralis Nodes

  • Moralis YouTube Tutorials

• Blockdaemon:

  • Blockdaemon landing page

• RockX:

  • Guide to Cronos Free Access Node

  • Cronos Blockchain API for Web3 Builders

• Chainstack:

  • Cronos documentation

  • Get started with Cronos Node on Chainstack

  • Build lottery smart contract on Cronos blockchain with Chainstack

  • Chainstack announces support for Cronos

• GetBlock:

  • Cronos Shared Nodes

• Automata:

  • Automata 1RPC

• BlockPI:

  • Distributed RPC Service

• All That Node:

  • Cronos Nodes

• Allnodes:

  • RPC Gateway to Cronos

• Dwellir:

  • Connect your dApp or Web3 project with any blockchain

• dRPC NodeCloud:

  • Cronos Mainnet endpoints

  • Cronos Testnet endpoints

  • Service Status