Stable
GetBlock provides fast and reliable access to Stable nodes via JSON-RPC and REST APIs. Connect to the Stable network without running your own infrastructure.
Stable is a Layer-1 blockchain purpose-built for stablecoin payments: USDT0 is the native gas token, so fees are paid and denominated in a dollar-pegged asset. It pairs an EVM execution layer with StableBFT, a proof-of-stake consensus in the CometBFT (Tendermint) lineage. It exposes both the Ethereum eth_* JSON-RPC surface and the native Cosmos SDK / Tendermint interfaces. This reference documents all of them.
Key Features
USDT0 Gas: The native gas token is USDT0, a dollar-pegged asset — fees are stable in dollar terms
EVM + CometBFT: An EVM execution layer on StableBFT (CometBFT/Tendermint-lineage) consensus — the
eth_*surface runs alongside native Cosmos interfacesFive API Interfaces: EVM JSON-RPC (HTTP + WebSocket), Cosmos REST, Cosmos gRPC, and Tendermint RPC (HTTP + WebSocket)
Deterministic Finality: CometBFT gives single-block finality — a result read at
latestis already finalDual Decimals: USDT0 is 18 decimals as the native gas token and 6 decimals as the USDT0 ERC-20 token
Payments Focus: Optimized for high-volume stablecoin transfers and payments
Network Information
Network Name
Stable Mainnet
EVM Chain ID
988 (0x3dc)
Native Currency
USDT0 (18-decimal native gas; 6-decimal ERC-20)
Consensus
StableBFT (CometBFT / Tendermint lineage)
Finality
Deterministic (single block)
Fee Model
EIP-1559 + legacy
Base URL
Available Interfaces
Stable pairs an EVM execution layer with a CometBFT consensus engine, so a node exposes several API interfaces. GetBlock serves all of the following; 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 eth_* surface
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 — by bech32 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.
Interface Endpoints
Supported Networks
Mainnet
988
✅
✅
✅
✅
✅
✅
❌
❌
✅
APIs
EVM JSON-RPC API — the Ethereum-compatible
eth_*surface (HTTP + WebSocket)Cosmos REST API — Cosmos SDK module queries over HTTP/JSON
Cosmos gRPC API — the same query set over Protocol Buffers
Tendermint RPC API — CometBFT consensus, block, tx, and
abci_query(HTTP + WebSocket)
Quickstart
Support
For technical support and questions:
Support: support@getblock.io
See Also
Last updated
Was this helpful?