Ethereum Classic (ETC) continues to serve as a foundational blockchain in the decentralized ecosystem, supporting wallets, mining operations, dApps, and developer projects worldwide. A critical component of interacting with the ETC network is access to reliable public RPC endpoints—remote interfaces that allow users to send transactions, deploy smart contracts, and query blockchain data without running their own node.
This guide provides a comprehensive overview of Ethereum Classic’s public RPC infrastructure, including updated endpoint URLs for the ETC mainnet and Mordor testnet, trusted sources for endpoint lists, and best practices for secure integration. Whether you're a developer, miner, or dApp user, this resource ensures you stay connected with accurate and current information.
What Are Public RPC Endpoints?
Remote Procedure Call (RPC) endpoints are HTTP or WebSocket URLs that connect applications to blockchain nodes. When wallets, mining pools, decentralized apps (dApps), or developers interact with Ethereum Classic, they rely on these endpoints to:
- Broadcast transactions
- Deploy or interact with smart contracts
- Query account balances and transaction history
- Sync blockchain state
While running a full node offers maximum security and control, many users prefer convenience over self-hosting. Public RPC services fill this gap by providing free or low-cost access to pre-deployed nodes—similar to cloud computing for blockchains.
👉 Discover secure ways to connect to Ethereum Classic using trusted infrastructure.
However, public endpoints come with trade-offs:
- Reduced privacy: Your requests are visible to the service provider.
- Rate limiting: Free tiers may throttle high-frequency queries.
- Downtime risk: Third-party nodes can go offline unexpectedly.
Despite these limitations, public RPCs remain essential for rapid development, testing, and lightweight applications.
Ethereum Classic Mainnet & Mordor Testnet Endpoints (2025 Update)
As of July 24, 2023, the ETC Cooperative migrated its primary RPC endpoints from Ethercluster to Rivet. All users must now use the updated URLs to ensure uninterrupted access.
✅ Current Official Endpoints
ETC Mainnet: https://etc.rivet.link
Mordor Testnet: https://rpc.mordor.etccooperative.org
⚠️ Important: The previous ethercluster URLs are deprecated. Continued use may result in failed connections or data inconsistencies.The Mordor testnet serves as a parallel network for developers to test dApps, smart contracts, and wallet integrations before deploying on the live ETC chain. It mirrors mainnet behavior while using zero-value test ETC tokens.
These endpoints are maintained by the ETC Cooperative and Rivet, ensuring high availability and community trust.
Where to Find Verified RPC Endpoint Lists
To enhance redundancy and reliability, multiple third-party platforms curate and verify public RPC endpoints for Ethereum Classic. Below are two of the most widely used resources.
1. Ethereum Classic Community Website
The official Ethereum Classic network page hosts a regularly updated list of known public RPC endpoints. This includes:
- Provider names
- RPC and WebSocket URLs
- Network type (mainnet/testnet)
- Status indicators (when available)
This list is community-maintained and considered a canonical reference within the ETC ecosystem.
👉 Access real-time blockchain connectivity through reliable node services.
2. Chainlist.org
Chainlist aggregates RPC endpoints across numerous EVM-compatible chains, including Ethereum Classic (Chain ID: 61). It allows users to:
- View multiple public RPC URLs
- Filter by network stability and provider
- One-click import into MetaMask
Chainlist also supports the Mordor testnet at https://chainlist.org/chain/63, making it ideal for developers testing cross-chain functionality.
Both platforms update their listings frequently, helping users avoid outdated or compromised endpoints.
Core Keywords for Ethereum Classic RPC Access
To support search visibility and user discovery, the following core keywords have been naturally integrated throughout this guide:
- Ethereum Classic public RPC
- ETC mainnet endpoint
- Mordor testnet RPC
- Ethereum Classic node URL
- Public blockchain API
- Decentralized app infrastructure
- Smart contract deployment ETC
- Free RPC for Ethereum Classic
These terms reflect common search intents related to development, connectivity, and integration with the ETC network.
Frequently Asked Questions (FAQ)
Q: Why did the ETC Cooperative change its RPC provider?
The migration from Ethercluster to Rivet was part of an effort to improve reliability, scalability, and long-term sustainability of public node services. Rivet offers enhanced uptime guarantees and better support for growing network demand.
Q: Can I still use old Ethercluster URLs?
No. As of July 24, 2023, Ethercluster endpoints for ETC and Mordor were permanently decommissioned. Using them will result in connection errors.
Q: Are public RPC endpoints safe for sending transactions?
Public endpoints are generally safe for reading data and sending non-sensitive transactions. However, for high-value operations or enterprise use, consider running your own node or using a private RPC service to maintain full control over data flow.
Q: How do I add the ETC mainnet to MetaMask manually?
In MetaMask:
- Go to Networks > Add Network
Enter:
- Network Name: Ethereum Classic Mainnet
- New RPC URL:
https://etc.rivet.link - Chain ID:
61 - Currency Symbol:
ETC - Block Explorer URL:
https://blockscout.com/etc/mainnet
Q: Is there a WebSocket endpoint available for real-time updates?
Yes. While https://etc.rivet.link primarily supports HTTPS, some providers listed on Chainlist offer WebSocket (wss://) support for event listening and live dApp updates.
Q: What should I do if an RPC endpoint stops working?
Try switching to an alternative from the Ethereum Classic community list or Chainlist. You can also run your own Geth or Hyperledger Besu node for uninterrupted access.
Best Practices for Using Public RPC Endpoints
To maximize performance and security when using public endpoints:
- Always verify the latest URLs via official sources
- Use rate-limiting-aware code in dApps to avoid timeouts
- Implement fallback logic with multiple endpoint providers
- Monitor endpoint health through tools like BlockScout
- Prefer HTTPS over HTTP to prevent man-in-the-middle attacks
For production-grade applications, consider upgrading to dedicated node services or setting up your own infrastructure.
👉 Explore seamless blockchain integration with advanced node solutions.
Final Thoughts
Staying up-to-date with Ethereum Classic’s public RPC endpoints is crucial for developers, miners, and dApp users. With the official shift to Rivet-hosted endpoints, the network has strengthened its infrastructure foundation.
By leveraging trusted sources like the ETC Community website and Chainlist, users can easily find verified connections to both the mainnet and Mordor testnet. As the ecosystem evolves in 2025 and beyond, maintaining reliable node access ensures smooth interaction with one of blockchain’s longest-running networks.
Always ensure your tools point to current endpoints—and prioritize security when relying on third-party services.