Upcoming ·Starts in 3 days
Ethereum Classic Community Call #63
Mumbai
Friday, November 20, 2026 at 02:00 UTC (Thursday, November 19 in Americas)
Join Call
on Zoom
on Zoom
Green Room - Join one Hour Before
Join us at 01:00 UTC
Agenda
The call took a four-week break while we travelled to Mumbai for the Ethereum Cypherpunk Congress, our meetup and Devcon 8. This episode covers ETC news since Call 62, the ETC Cooperative wind-down, client updates, Besu plugin support, takeaways from Mumbai and Devcon 8, the first quantum-safe payment on ETC, and the 2026 community survey.
ETC News
- Community
- The 2026 Unofficial ETC Community Survey by Classix is open at survey.classix.dev. It is the first since 2019 and takes about ten minutes in nine languages.
- @eth_classic reported hashrate up about 46% between early September and late October. What is driving the growth?
- Website
- Kevin published Run Your Own ETC Node, Part 2: Run core-geth with Docker. What should Part 3 cover?
- SwiftNodes (public RPC) and GhostSwap (cross-chain swaps) were added.
ETC Cooperative
- The ETC Cooperative announced on 11 November that it is winding down, with most of the dissolution done by the end of 2026.
- It no longer accepts grant applications. Questions and outstanding matters go to the Cooperative by 6 December.
- It is arranging for the infrastructure it supports, including network nodes and the Blockscout explorer, to keep running for a transition period. Who should run this infrastructure in the long term?
- Diego’s role at the Cooperative ended on 7 November, after more than five years as its core developer. Thank you, Diego.
- What other services, accounts or responsibilities did the Cooperative hold that the community should know about?
Clients
- Diego will continue maintaining the ETC clients for at least another twelve months: Core-Geth, Go Ethereum Classic, and the Nethermind and Besu ETC plugins. A fifth client is under consideration for next year. Which one would be most useful?
- etclabscore core-geth
- No new release since Argos v1.12.23. A README and SECURITY.md now say how to report vulnerabilities.
- #704
miner_getWorkForis still open. Is it ready for a v1.12.24? - #685 would remove unresponsive bootnodes. With the Cooperative winding down, should the bootnode list be reviewed?
- Nethermind ETC plugin v2.2.2.0 brings the plugin onto Nethermind 2.2 and now releases with each Nethermind release.
- Fukuii has shipped many v0.11.x prereleases, with work on sync, a terminal UI and Chocolatey packages. Has anyone run it on mainnet?
- About 94% of reachable nodes run Core-Geth. In Mumbai, Diego called running a minority client “a cheap and easy insurance”. How can node operators and pools be encouraged to run one?
Besu Plugin Support
- Besu lead Gary Schulte opened besu#11887 on 7 November. It lets plugins change the protocol rules from a given block or timestamp, so a chain’s rules can live outside Besu. It is Part 1 of a series of plugin changes for chains other than Ethereum mainnet.
- It builds on Diego’s branch and credits him “for the design and most of the implementation”. Diego has reviewed the rebase and offered two fixes, one for fork ID handling.
- It targets Besu’s
plugin-api-refactorbranch, which the Besu team expects to merge intomainsoon.
- The last piece for full ETC support is a small change that lets the genesis config carry ETC-specific transitions.
- When both land, the Besu ETC plugin can run on unmodified upstream Besu, and ETC no longer needs its own Besu fork, as is already the case for Nethermind. What would it take for node operators and pools to run Besu on ETC?
Mumbai
- Reflections on Mumbai: the Ethereum Cypherpunk Congress, Devcon 8, and the Ethereum Classic meetup in Mumbai.
- Ideas from Mumbai. Which should come first?
- Kohaku privacy wallet SDK for ETC
- “Anonymining” pools that shield block rewards as miners earn them
- An AI upgrade pipeline that brings each upstream release into all four clients
- ETC on every hardware signer, with ERC-7730 clear signing, and fixing wallets that ignore chain ID 61
- Kleros arbitration as a default for “code is law” disputes
- ETC in the Ethereum Economic Zone
- AI-driven hackathons and ideathons in 2027
Quantum
- At Devcon 8, Justin Drake moved Ethereum’s post-quantum target forward to December 2028, with three hard forks after Glamsterdam. Ethereum plans leanXMSS for validators and leanSPHINCS for user accounts.
- The first payment using a quantum-safe signature on ETC was made on 16 November with skinnyCAT, an educational demo.
- The leanSPHINCS signature is checked by an ordinary contract with no owner, using only opcodes ETC has today. No fork was needed.
- Each signature is 7,740 bytes and costs about 123k gas of calldata plus 86k gas to verify. Ethereum’s answer is to aggregate signatures with EIP-8288. On ETC, miners would merge the proofs. Is that practical?
- Only funds held inside the demo are protected. Protecting the 132M ETC behind exposed keys needs an ECIP.
- A proposed ETC “Quantum Strawmap” would separate what ETC already has through proof of work from what it needs, sequenced as ECIPs. What should it include?
- A Safe with a leanSPHINCS owner contract works on ETC today. Would large holders use a post-quantum multisig?
- ECIPs #557 (ML-DSA precompile) has had no activity since July. With Ethereum choosing hash-based signatures, should it continue?
Community Survey
- The survey launched at the Mumbai meetup. Results will be published in 2027, and the prize draw is in January.
- What questions would you want answered? Please take part and share it.