Ethereum Classic miners reverse Core Geth v1.13.0 migration after warning

Ethereum Classic node operators have been urged to avoid a disputed Core Geth v1.13.0 release after several mining pool nodes briefly adopted the software before returning to the maintained Argos client. Summary Several Ethereum Classic mining pool nodes briefly moved to the disputed Core Geth v1.13.0 release before returning to Argos v1.12.23. Classix said 96 commits were pushed within 56 hours without outside review before v1.13.0 was released and promoted as a security update. The disputed client reenabled MESS and changed node discovery infrastructure, while Classix said no blocks, funds or services were affected by the incident. Classix urged operators to avoid v1.13.0 and asked Ethereum Classic GitHub administrators to tighten repository and review controls. Classix said in a Sept. 16 incident report that the ethereumclassic/core-geth repository released v1.13.0 on Sept. 14 before the @ETC_Network account promoted it as an Ethereum Classic security update and told node operators to migrate. Similar messaging appeared on CoinMarketCap, while mining pools received emails from an ethereumclassic.com address. The report described the release as a rogue version because the existing Core Geth maintainers had not reviewed it and the maintained etclabscore/core-geth repository had not issued the update. Classix recommended that operators continue using Argos v1.12.23, the current release from the repository that has maintained Core Geth since 2020. Rogue Core Geth release reached some ETC mining nodes Development of the disputed version accelerated during the days before its release. According to Classix, 96 commits containing 13,422 added lines and 3,977 deleted lines were pushed within 56 hours directly to the fork’s main branch without pull requests or outside review. The ethereumclassic/core-geth repository itself had been forked from etclabscore/core-geth in December 2024. Activity increased on Sept. 12, 2026, when v1.13.0-rc1 was tagged. Six more release candidates followed before v1.13.0 was labeled stable at 15:06 UTC on Sept. 14. The @ETC_Network account published the migration request the following morning. The software reached part of Ethereum Classic’s mining infrastructure before operators reversed the migration. Four 2Miners nodes were running CoreGeth v1.13.0 at 12:09 UTC on Sept. 15, according to node status data cited by Classix. By 23:35 UTC, all four had returned to Argos v1.12.23. Other listed mining pools remained on versions in the 1.12 series. Some individual nodes continued running the disputed software. Etcnodes.org showed 11 v1.13.0 nodes at 07:33 UTC on Sept. 15, with the number falling to 10 by Sept. 16. Three of the remaining nodes matched bootnode IP addresses hardcoded into the new client, according to the report. You might also like: Ethereum price recovery hinges on $2,526 breakout No blocks were lost, no chain reorganizations occurred, no funds were affected and no service interruption was recorded during the incident, Classix said.