Ethereum Classic RPC Endpoint

Flat-rate Ethereum Classic RPC provider and Ethereum Classic RPC node access: free tier, no KYC, HTTP. Ethereum Classic mainnet chain ID 61.

Ethereum Classic is the continuation of the original Ethereum chain that did not adopt the 2016 DAO hard fork. It remains a proof-of-work, EVM-compatible Layer 1 that upholds transaction immutability under the principle that code is law.

About Ethereum Classic

Ethereum Classic originated in July 2016 when the Ethereum community split over whether to reverse the DAO hack. The chain that preserved the unaltered transaction history became Ethereum Classic (ETC), retaining proof-of-work after Ethereum moved to proof-of-stake in 2022. Block times average around 13 seconds.

ETC secures the network with the ETChash mining algorithm, a modified Ethash variant adopted to harden the chain against attacks. It is fully EVM-compatible, so Solidity contracts and standard Ethereum tooling work, and it positions itself as the leading proof-of-work smart contract platform with a fixed monetary policy.

Common Use Cases on Ethereum Classic

• Proof-of-work smart contracts
• Store-of-value with fixed supply policy
• DeFi and token issuance
• Immutable on-chain records
• Payments using ETC

Ethereum Classic Ecosystem

Ethereum Classic supports EVM dApps and DeFi deployments, with infrastructure and explorers such as Blockscout and a mining ecosystem secured by ETChash.

Ethereum Classic Mainnet RPC URL (HTTP)

Ethereum Classic WebSocket RPC URL

Not available for Ethereum Classic right now: none of its upstreams currently accepts a subscription in our health checks. Poll the HTTP endpoint above instead.

Quick Start: Connect to Ethereum Classic

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/etc?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/etc?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("Ethereum Classic block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/etc?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/etc?key=YOUR_API_KEY"))
print("Ethereum Classic block:", w3.eth.block_number)

Add Ethereum Classic to MetaMask

Bridging to Ethereum Classic

Assets bridge to and from other chains via third-party services such as ChainBridge-based bridges and cross-chain providers supporting ETC.

Features of SwiftNodes for Ethereum Classic

• Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
• Health-checked every 2 minutes with automatic failover
• Free tier available — no credit card or KYC required
• Flat-rate monthly pricing with no per-request fees
• HTTP support (WebSocket not available for this chain right now)
• One API key works across all 75+ supported chains, including Ethereum Classic

Rate Limits

Frequently Asked Questions: Ethereum Classic

Ethereum Classic guides from the blog

• Ethereum Classic RPC: A Developer's GuideHow to connect to Ethereum Classic over JSON-RPC — chain ID 61, proof-of-work still live, why blocks carry no baseFeePerGas, what carries over from Ethereum unchanged, and where historical reads stop working.

Related EVM chains

Explore RPC endpoints for other EVM networks on SwiftNodes: