Cronos (CRO)
GetBlock provides fast and reliable access to Cronos nodes via JSON-RPC API. Connect to the Cronos network without running your own infrastructure.
Cronos is an EVM-compatible Layer 1 blockchain built by Crypto.com on the Cosmos SDK with Ethermint, secured by CometBFT (Tendermint) BFT consensus for fast, deterministic finality. It runs a standard Ethereum execution layer, so Solidity contracts, the eth_* JSON-RPC surface, and tooling such as Foundry, Hardhat, Ethers.js, and Viem work unchanged, while IBC connectivity links it to the wider Cosmos ecosystem. The native gas token is CRO, and Cronos supports EIP-1559 fee-market pricing through Ethermint's feemarket module. This reference document describes the Ethereum-compatible eth_* surface of Cronos EVM (chain ID 25), which is distinct from Cronos zkEVM (chain ID 388).
Key Features
EVM Compatibility: Standard Ethereum contracts, JSON-RPC, and tooling run unchanged on the Ethermint execution layer
Cosmos SDK Foundation: Built on the Cosmos SDK with IBC connectivity to the broader Cosmos ecosystem
CometBFT Consensus: Tendermint BFT gives fast, deterministic single-block finality with no probabilistic reorgs
EIP-1559 Fees: Ethermint's feemarket module provides base-fee pricing;
eth_feeHistoryand priority fees applyCRO Gas Token: Native gas is paid in CRO (18 decimals), with low, sub-cent transaction costs
Ethereum Tooling: Compatible with MetaMask, Foundry, Hardhat, Remix, Ethers.js, and Viem
Network Information
Network Name
Cronos EVM
Chain ID
25
Native Currency
CRO
EVM Compatible
Yes (Ethermint)
Framework
Cosmos SDK + Ethermint
Consensus
CometBFT (Tendermint) BFT
Block Time
~5-6 seconds
Finality
Deterministic (single block)
Fee Model
EIP-1559 (feemarket)
Base URL
Available Interfaces
Cronos is a Cosmos SDK chain with an embedded Ethermint EVM, so a Cronos node exposes several API interfaces beyond the Ethereum one. GetBlock serves all of the following for Cronos; each is provisioned as its own endpoint, so choose the API interface when you create the endpoint in the GetBlock dashboard.
EVM JSON-RPC (HTTP)
Ethereum JSON-RPC 2.0 over HTTP
Contract calls, transactions, and reads — the surface this reference documents
EVM JSON-RPC (WS)
Ethereum JSON-RPC 2.0 over WebSocket
eth_subscribe streams (newHeads, logs) and live EVM data
Cosmos (REST)
RESTful gRPC-gateway (LCD) over HTTP
Cosmos SDK module queries — bank, staking, governance, IBC — by bech32 (crc1…) address
Cosmos (gRPC)
Protobuf gRPC services
Typed Cosmos SDK queries for production backends
Tendermint RPC (HTTP)
CometBFT JSON-RPC over HTTP
Consensus, block, and transaction data; transaction broadcast; abci_query for module state
Tendermint RPC (WS)
CometBFT JSON-RPC over WebSocket
Event subscriptions (new blocks, transactions) over WebSocket
The Cosmos REST and gRPC interfaces carry the same Cosmos SDK query set over different transports (REST is an HTTP/JSON gateway in front of gRPC). Tendermint RPC exposes the CometBFT consensus engine directly and is where transactions are broadcast and low-level block and abci_query data is read. All three use the bech32 crc1… address encoding; a Cronos account's 0x and crc1… addresses are two encodings of the same key.
Interface Endpoints
Supported Networks
Mainnet
25
✅
✅
✅
✅
✅
✅
✅
APIs
Cosmos REST API — Cosmos SDK module queries over HTTP/JSON
Cosmos gRPC — the same query set over Protocol Buffers
Tendermint RPC API — CometBFT consensus, block, tx, and
abci_queryEVM JSON-RPC API — the Ethereum-compatible
eth_*surface (documented separately)
Quickstart
Support
For technical support and questions:
Support: support@getblock.io
See Also
Last updated
Was this helpful?