Ethereum Classic Public RPC Endpoints: A Complete Guide

·

Ethereum Classic (ETC) remains a cornerstone of decentralized blockchain infrastructure, supporting wallets, mining operations, dApps, and developer networks across the globe. As the ecosystem evolves, access to reliable and up-to-date public RPC endpoints becomes essential for seamless interaction with both the ETC mainnet and its test environments like Mordor. This guide provides a comprehensive overview of available endpoints, explains their function, and highlights trusted sources where users can find verified connection URLs.

Whether you're a developer deploying smart contracts, a miner submitting work, or a wallet provider enabling user transactions, understanding how to connect securely and efficiently to the Ethereum Classic network is crucial.

What Are Public RPC Endpoints?

Remote Procedure Call (RPC) endpoints are HTTP or WebSocket URLs that allow applications to communicate directly with a blockchain node. In the context of Ethereum Classic, these endpoints enable:

Users have two primary options: run their own full node—offering maximum security and control—or use a public RPC endpoint provided by third-party services. While running a private node is ideal for security-sensitive applications, many users opt for public endpoints due to lower operational overhead.

Public endpoints function similarly to cloud computing services. Organizations such as Rivet and the ETC Cooperative operate robust nodes and expose them via standardized URLs, allowing developers and end-users to interact with the ETC blockchain without maintaining infrastructure.

👉 Discover how blockchain networks power decentralized applications through reliable node access.

Updated Ethereum Classic Mainnet & Mordor Testnet Endpoints

As of July 24, 2023, the ETC Cooperative migrated the official Ethereum Classic mainnet RPC URL from Ethercluster to Rivet, enhancing reliability and performance. Additionally, the Mordor testnet endpoint was updated to a new dedicated address.

Here are the current official endpoints:

✅ Ethereum Classic Mainnet

https://etc.rivet.link

This is the recommended public RPC endpoint for production applications, wallets, and dApps interacting with real-value ETC transactions.

✅ Mordor Test Network

https://rpc.mordor.etccooperative.org

The Mordor network serves as a parallel testing environment for developers to experiment with smart contracts, transaction flows, and integrations before deploying on the mainnet.

⚠️ Important: If you're still using legacy endpoints such as ethereumclassic.network or deprecated Ethercluster URLs, update your configurations immediately to avoid service interruptions.

Where to Find Verified ETC Endpoint Lists

While official endpoints offer trusted access, multiple providers host public nodes to ensure redundancy and global availability. Below are two authoritative sources where users can discover up-to-date, community-verified RPC URLs.

1. Ethereum Classic Official Community Site

The Ethereum Classic website maintains an official, frequently updated list of public RPC endpoints at:
https://ethereumclassic.org/network/endpoints

This resource includes:

It's widely regarded as the most reliable starting point for developers integrating ETC into their platforms.

2. Chainlist.org – Multi-Network Endpoint Aggregator

Chainlist.org is a popular tool that aggregates RPC configurations for numerous EVM-compatible chains, including Ethereum Classic.

You can find ETC-specific endpoints here:

Chainlist allows one-click integration with popular wallets like MetaMask, making it especially useful for developers and non-technical users alike. The platform verifies provider authenticity and displays connection details such as block explorer links and native token symbols.

👉 Learn how developers use public nodes to build scalable blockchain solutions.

Core Keywords for Ethereum Classic Node Access

To ensure this guide aligns with user search intent and improves discoverability, the following core keywords have been naturally integrated throughout:

These terms reflect common queries from developers, miners, and dApp users seeking reliable connection methods to the ETC network.

Frequently Asked Questions (FAQ)

Q: Why did Ethereum Classic switch from Ethercluster to Rivet?

A: The migration to Rivet was initiated by the ETC Cooperative to improve node stability, reduce latency, and ensure long-term sustainability of public infrastructure. Rivet offers enhanced scalability and better global distribution compared to previous providers.

Q: Are public RPC endpoints safe to use?

A: Public endpoints are convenient but less secure than self-hosted nodes. They may log IP addresses or throttle requests under heavy load. For high-security applications—such as institutional wallets or large-scale dApps—running a private node is strongly recommended.

Q: Can I use multiple RPC endpoints for redundancy?

A: Yes. Many applications implement failover mechanisms that rotate between multiple trusted endpoints (e.g., Rivet, Chainlist-provided nodes) to maintain uptime during outages.

Q: Is the Mordor testnet still active?

A: Yes. The Mordor testnet remains operational for testing purposes. It uses a proof-of-work consensus model aligned with ETC’s philosophy and allows developers to simulate real-world conditions without financial risk.

Q: How do I add the ETC network to MetaMask manually?

A: Use these settings:

Q: What happens if a public endpoint goes down?

A: Service interruption may delay transaction broadcasting or balance updates. Always have backup endpoints configured or consider using load-balancing tools for mission-critical applications.

👉 Explore how modern crypto platforms ensure uninterrupted node connectivity.

Final Thoughts

Access to accurate and stable Ethereum Classic public RPC endpoints is fundamental for anyone building on or using the ETC ecosystem. With the official transition to Rivet and continued support from platforms like Chainlist and the ETC Cooperative, users now benefit from improved reliability and broader access options.

Whether you're testing on Mordor or deploying on the mainnet, staying informed about endpoint changes ensures uninterrupted service and optimal performance. Always verify your connection URLs regularly and consult trusted sources to maintain security and efficiency in your blockchain interactions.

By leveraging community-maintained lists and understanding the role of public nodes, developers and users alike can confidently engage with one of the longest-running proof-of-work blockchains in existence.