Skip to content
ethereumclassicPublic

About

A list of observed nodes on the Ethereum Classic network

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

Repository files navigation

Ethereum Classic nodes

A public dashboard and network visual tooling for Ethereum Classic and its Mordor test network, and the deployment configuration for the hosts behind both networks' bootnodes and public RPC. It extends the discovery lists: the lists give clients their first peers, and the dashboard shows the network they join, built from the crawl the lists publish every night. It is maintained in the ethereumclassic organization by its core developers and community contributors.

Important

This supersedes etcnodes.org. etcnodes.org is the node census and explorer the ETC Cooperative maintained. The Cooperative entered maintenance mode at the end of 2024. Its board has communicated that the Cooperative will dissolve. The dashboard built here will take its place. Until it is published, etcnodes.org remains the place to read the network. The ETC Cooperative transition lists where the Cooperative's other services continue.

The bootnodes

Ethereum Classic

enode://5c1f4f1c8036879c3186f0632ce0fdf3514e67679f0b5e1814335f5093a21c6c2fda20266ca2b54aac3305085fa46d9711493da1b564489ecec7b37d1aebb5f6@178.104.220.119:30303
enode://82100619a51fed73bce973a5f7ead3a9468535bdd4c87488037f99bf53b741e4701c5909b7c92897c863c23e494e27c83470a2fcbcc51f8b49655ed377dbd962@135.148.46.64:30303
enode://d77bc6696fc2a1419871c8819baef44089cd1847b1b895266382892fd04571cc01a97c45d4df6cbe4c37004195a3c578a76e706d12548916ca5c4341768b1972@62.72.47.101:30303

Mordor

enode://d6f2e535a2d183f930bd780913d1d4169d3479f22c2941117d10184d65adbb614866db83049438c17657d1b24a53f3560280f563305426e93868a9a98a02c5fc@2.29.31.123:30303
enode://b0b8da5708a22a0bc92e993c6fb93801d1bc5956efaf3ef7cafcd3af2167f634a2147abb6913a719d61ed03e180aa2045ffea7bd2e367db589165e83058df487@40.160.140.180:30303

All five are built into Core-Geth from v1.13.0, in params/bootnodes_classic.go and params/bootnodes_mordor.go, which are the authority if this list ever differs. The discovery lists' nightly crawl walks the network from the same five. The trees are built from that crawl, and the dashboard will be too.

Quick start

Core-Geth v1.13 line: nothing to configure. Both networks use these bootnodes by default. Install Core-Geth has the steps for each platform, and a node then starts with:

# Check that it reports a 1.13 release, then start a node on Ethereum Classic
geth version
geth --classic

For the Mordor test network, run geth --mordor instead.

Core-Geth v1.12 line: every node still on a v1.12 release should move to the v1.13 line, which closes the known vulnerabilities the audits found in v1.12. What the audits found says which flaws each v1.12 release still carries. Migrate Core-Geth has the steps for each platform, including the required P2P node key rotation. From v1.12.17 on, your chain data carries over. Budget about twenty minutes for the steps; the node is down only between its stop and its start, and each of those takes seconds. A node on a release before v1.12.17 resyncs instead, as Migrate Core-Geth explains.

Until a node can move, add --bootnodes with the list for your network. It replaces the built-in list, and it closes none of those vulnerabilities.

geth --classic --bootnodes "enode://5c1f4f1c8036879c3186f0632ce0fdf3514e67679f0b5e1814335f5093a21c6c2fda20266ca2b54aac3305085fa46d9711493da1b564489ecec7b37d1aebb5f6@178.104.220.119:30303,enode://82100619a51fed73bce973a5f7ead3a9468535bdd4c87488037f99bf53b741e4701c5909b7c92897c863c23e494e27c83470a2fcbcc51f8b49655ed377dbd962@135.148.46.64:30303,enode://d77bc6696fc2a1419871c8819baef44089cd1847b1b895266382892fd04571cc01a97c45d4df6cbe4c37004195a3c578a76e706d12548916ca5c4341768b1972@62.72.47.101:30303"

For Mordor, use --mordor and the two Mordor enodes. Keep a v1.12 node finding peers points a node that cannot leave the v1.12 line yet at the peer discovery lists and bootnodes the v1.13 line ships, with the steps for each platform and a config file.

Documentation

Page What it covers
Downloads The archive for every platform with its checksum beside it
Install Core-Geth Walks through installing, starting and checking a node on Linux, macOS, Windows, in a container or from source
Migrate Core-Geth Moves a node on v1.12.17 or a later v1.12 release to the v1.13 line, including the required P2P node key rotation
Keep a v1.12 node finding peers Points a node that cannot leave the v1.12 line yet at the peer discovery lists and bootnodes the v1.13 line ships, until it moves
Node operators: start here What to do now, and what to read in what order
Security The audits, what each release fixes, and a count of which releases Ethereum Classic nodes are still running
Bootnodes and peer discovery How a node finds peers, and running your own bootnode
Using the trees Pointing any Core-Geth release at the discovery trees
How nodes are chosen What gets a node listed in the trees
The ETC Cooperative transition Where the services the Cooperative maintained continue

Status

The five bootnodes are running, as the transition page records. As of November 2, 2026, the dashboard and the deployment configuration are planned, and neither is in this repository. The dashboard will publish at etcnodes.com, and this section will link to it then.

Security

To report a security issue privately, email security@ethereumclassic.net. SECURITY.md has the details. Security issues are never reported as public issues.

Support this work

These bootnodes and this dashboard are a public good. The Ethereum Classic DAO is the legal entity that maintains them, together with Ethereum Classic's core developers and community contributors, and today it also pays for that work, as its funder of last resort. The repositories stay in the ethereumclassic organization no matter who maintains or funds them. Earlier, this work moved between ETCDEV, ETC Labs and the ETC Cooperative as each one closed or left. With the ETC Cooperative's dissolution, Ethereum Classic stakeholders such as mining pools, exchanges and service providers should use security@ethereumclassic.net as their point of contact.

If you are a stakeholder of Ethereum Classic, you rely on this infrastructure, and Ethereum Classic has no protocol-layer funding mechanism for its critical infrastructure or its core developers. Please consider sponsoring it. Support this work lists who has funded it, explains how sponsors are credited, and gives the routes: an invoiced maintenance agreement for organizations, or a direct transfer to an address provided on request.

License

Apache-2.0. See LICENSE and NOTICE.

About

A list of observed nodes on the Ethereum Classic network

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors