Support this work¶
Core-Geth is maintained as a public good, and it is unfunded. This page is the one place this project publishes its funding routes. If you find them anywhere else, check them against this page first.
What the funding pays for¶
Keeping a consensus client fit to run a live network: tracking upstream security fixes and deciding which apply to Ethereum Classic, cutting and verifying releases across nine platforms, running the bootnodes and publishing the peer discovery lists the network bootstraps from, and measuring what the published binaries actually contain. The audits are the record of that work, including what was found broken and what it took to fix.
Who depends on it¶
Mining pools, centralized exchanges and custodians, issuers of Ethereum Classic financial products, Etchash mining hardware manufacturers, block explorers, RPC providers, and anyone holding ETC. Ethereum Classic has no protocol treasury, so no part of the network’s fee or issuance revenue funds this maintenance. If the client is maintained, someone with a stake in the chain pays for it.
How to fund it¶
Sponsor on GitHub. Recurring or one-off, handled by GitHub, with the usual receipts. Use the Sponsor button on the repository.
An invoiced agreement, for organizations. If your business depends on this client, a maintenance sponsorship can be invoiced against a purchase order like any other vendor relationship, which is usually what a finance department needs. Write to donations@ethereumclassic.com with what you run and the period you want to cover.
A direct transfer. For anyone who prefers to send funds directly, on any EVM-compatible chain:
1 | |
Check that address before you use it. It is published here, on a page served over TLS from docs.coregeth.com, which is built from this repository. An address shown in a screenshot, a fork, a mirror or a message is worth nothing until it matches this page. If a large transfer is planned, send a small one first and confirm receipt at donations@ethereumclassic.com.
What funding does not buy¶
No influence over consensus rules, release content, or what an audit reports. Chain configuration follows the ECIP process, and every finding this project publishes is measured and linked so it can be checked without trusting either the maintainers or anyone who funds them. A sponsor gets the same client as everyone else, on the same schedule.
Requests for a feature, a fix, or a supported configuration are welcome from anyone, funded or not, in the repository’s issues.