Core-Geth guides
Guides to running a Core-Geth node
Install a node, move one off the v1.12 line, or keep one finding peers until it can move, one step at a time. Each guide runs its commands in order, and says what to decide and what to expect between them.
The Core-Geth guides
Start with the guide for your node
- For a machine with no node on it yetInstall Core-GethFrom the download to a node that has caught up with the Ethereum Classic network and holds peers, on Linux, macOS, Windows, in a container or built from the
mainbranch.Choosing a route, the install steps for your platform with a recording of the first start, checking the download, the first sync, keeping the node running, and where to ask. - For a node that runs
v1.12.17or a laterv1.12releaseMigrate Core-GethMoves the node to thev1.13line and gives it the new P2P node key the move requires. Fromv1.12.17on, 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.Checking what the node runs, what to decide before you stop it, each step with recordings of the clean stop and the start, rolling back for a while and deleting the old binary, what the move changes, and what to do if a step goes wrong. - For a
v1.12node that cannot move yetKeep a v1.12 node finding peersPoints the node at the peer discovery lists and bootnodes thev1.13line ships, so it keeps finding peers until it moves. It closes none of the flaws the audits found.Checking how the node starts, the steps for your platform with recordings of the clean stop and the starts, a config file, starting any node from the committed node records if the lists and bootnodes go dark, and what to take out when the node moves.
More guides in the Core-Geth documentation
A guide for every role
Running a node for an exchange, a mining pool, an RPC endpoint or an explorer starts in the documentation, which has a page for each role. Downloads has every file the latest release published, with its checksum.