What Is Maintained
The software and services the network depends on, each built and documented in public.
Core-Geth
Execution client
The recommended client for Ethereum Classic, a go-ethereum derivative that implements the network's consensus rules and its Proof-of-Work chain selection. Upstream go-ethereum no longer supports Ethereum Classic, so those rules are maintained here rather than inherited. Each release is built by the repository's own workflow, with a checksum and a build attestation beside every file.
Peer discovery lists
DNS discovery
Signed lists of Ethereum Classic and Mordor nodes, published in DNS so that a client finds its first peers. The lists are rebuilt every night from a crawl of the network, and every published list is committed to the repository, so the record of what clients were given is public.
Bootnodes
Network entry points
The fixed entry points a node contacts when it has no peers yet, for Ethereum Classic and for Mordor. They are run by the Core-Geth maintainers and built into the client, so a new node reaches the network without configuration.
Public JSON-RPC
Public endpoints
Public endpoints for Ethereum Classic and Mordor under ethereumclassic.net, run from the organization's repositories so that more than one maintainer can rebuild or move the service and anyone can read how it is run. ChainList carries the endpoints other operators publish.
Network dashboard
Network status
A public view of Ethereum Classic's network health, served from the organization's own infrastructure alongside the public endpoints, so operators and integrators can read the state of the network and its peers without standing up their own indexer.
Block explorer
Chain explorer
A public explorer for Ethereum Classic and Mordor, served from the organization's own infrastructure, so anyone can look up blocks, transactions, addresses and contracts without depending on a third-party service.
One Home, Whoever Maintains It
The ethereumclassic organization has held the Ethereum Classic community’s shared resources since July 2016: the website from the start, the ECIPs since 2018 and, since December 2024, Core-Geth. Keeping a reference client in the project’s own organization is ordinary practice, as with Bitcoin Core at bitcoin/bitcoin and go-ethereum at ethereum/go-ethereum.
Before that, this work moved each time the organization carrying it closed or left. The client changed repositories, and the bootnodes and discovery lists changed operators. A repository in the community’s organization stays where it is no matter who maintains or funds it, which is what makes it a fixed place for the network to point at.
Where it lives
ethereumclassic
The community's organization since July 2016
Who can change it
More than one maintainer
Each repository has more than one admin
How a change lands
Reviewed pull request
Approved by a reviewer other than its author
Running a Node
Core-Geth is the recommended client for Ethereum Classic. Take the current release from ethereumclassic/core-geth; the latest-release link always resolves to it. Releases from the v1.13 series onward are published only from that repository, so a node that follows the previous one does not see them. The installation guide covers each platform, and how to verify that a download was built by the repository’s own release workflow.
Security and Operator Contact
Mining pools, exchanges and service providers reach the people who maintain this work at one address. A person answers it: one of the core developers who maintain the client. It also takes private vulnerability reports, and subscriptions to release and security announcements.
security@ethereumclassic.netFrequently Asked Questions
The shared software and services the network depends on: the Core-Geth client, the network's bootnodes, the peer discovery lists, public JSON-RPC endpoints, a network dashboard, and a block explorer. They are maintained in the ethereumclassic organization on GitHub.
Core-Geth is the recommended client: run its v1.13 line, which closes all six client CVEs the audits found in the v1.12 client code. Take the current release from github.com/ethereumclassic/core-geth/releases/latest, which always resolves to it. Fukuii, a native Ethereum Classic client, is listed as an alternative on the clients page.
In ethereumclassic/core-geth, the community's repository. Releases from the v1.13 series onward are published only there, so a node tracking the previous repository, etclabscore/core-geth, does not see them.
Through the bootnodes built into the client and through signed DNS discovery lists, which are rebuilt every night from a crawl of the network and published under ethereumclassic.net, ethclassic.net and ethereumclassic.network. Every published list is committed to a public repository.
ChainList lists the public endpoints Ethereum Classic operators publish, for chain 61 and for Mordor, chain 63. A public endpoint is another operator's node: it can rate limit, fall behind or stop, so anything you depend on should run against a node you control.
security@ethereumclassic.net. A person answers it: one of the core developers who maintain this work. The same address takes private vulnerability reports and subscriptions to release and security announcements.
Ethereum Classic's core developers and community contributors do the day-to-day work. Ethereum Classic DAO LLC is the standing legal entity that maintains and funds them today as the funder of last resort. The stewardship page covers the arrangement and how to sponsor it.