EnglishEnglish中文中文اَلْعَرَبِيَّةُاَلْعَرَبِيَّةُDeutschDeutschEspañolEspañolΕλληνικάΕλληνικάFrançaisFrançaisעִבְרִיתעִבְרִיתहिन्दीहिन्दीHrvatskiHrvatskiItalianoItaliano日本語日本語한국어한국어MalayMalayNederlandsNederlandsPortuguêsPortuguêsрусскийрусскийภาษาไทยภาษาไทยTürkTürkTiếng ViệtTiếng Việt粵語粵語
Frequently asked questions by various stakeholders
Why Classic?
Start here to get the lowdown on Ethereum Classic's reason for being and unique value proposition
Further reading on the foundations that underpin ETC
A collection of videos and podcasts to keep you informed on ETC concepts and happenings
Support ETC by helping to translate this website!
Ethereum Classic Blog

ETC Core Devs Call 22: Proposed Rejection of Keccak256 ECIP-1049 Call Results

Announcements, Development, Education, Hard Forks, Media, Teams
ETC Core Devs Call 22 - Proposed Rejection of Keccak256 ECIP-1049
ETC Core Devs Call 22 - Proposed Rejection of Keccak256 ECIP-1049

ETC Core Devs Call 22 - Proposed Rejection of Keccak256 ECIP-1049 Call Results

ETC Core Devs Call 22: Conclusion

  • A new ECIP-1049 Champion was selected in Bob Summerwill. The old champion, Alexander Tsankov has stepped down from the proposal stating he is too busy to champion this proposal.
  • It was agreed by the ECIP Editor r0n1n and the new Champion of ECIP-1049, Bob Summerwill, that the ECIP-1049 proposal needs a material rewrite to meet ECIP-1000 compliance and remain in Draft status.
  • The new Champion vocalized intent to bring the ECIP-1049 proposal up to ECIP-1000 standards within the coming months during 2022.
  • The ECIP Editor and others on the call felt it was reasonable to afford the new champion time to clean up the ECIP-1049 proposal, as it was vocalized that undocumented technical work has been done by the champion's paid staff.
  • The ECIP editor vocalized intent to leave PR 465 open to push this proposal to Rejected status should this proposal continue to sit in a state that violates the ECIP-1000. This comes after the CDC 15 meeting where Alexander Tsankov, the old champion of this proposal, vocalized intent to update the proposal after a failed push to Accepted status in 2020 and did not follow through with the ECIP-1000 requirements regarding criticism and dissenting opinions to the ECIP-1049 proposal from the community.
  • It was recommended to split the ECIP to multiple ECIPs to align with ECIP-1000 guidelines; technical work, transition strategy, social consensus building, activation plan. These were some examples provided to the champion.
  • The elephant in the room on ECIP-1049 has been a documented lack of consensus. The ECIP-1049 proposal aims to displace the current mining ecosystem. This is a violation of the ECIP-1000 in itself.
  • Pushing contentious hard forks on the network is a violation of the ECIP-1000 process. It's unlikely the ETChash mining ecosystem will update nodes to this proposal should a hard fork be attempted. Many in the community; mining pools, miners, developers, core development teams, community members have vocalized support for the non-fork ETChash side of a contentious hard fork should the proponents of ECIP-1049 push a contentious hard fork on the Ethereum Classic network.
  • The ETChash mining ecosystem was assured continued support from community members should any centralized actor attempt a contentious hard fork on the Ethereum Classic network.
  • The opposition to ECIP-1049 has provided the new champion material criticism of ECIP-1049 to address during the champion's material redraft of the proposal.
  • The proposal will be reviewed at a later date for ECIP-1000 compliance. Should compliance not be met, this proposal will move to Rejected status. Note: the Champion can always revive a Rejected proposal when ECIP-1000 compliance is met.

Note: This ECIP appears to be contentious, as documented in all the previous threads and recordings. This proposal has a high-probability of a chain split between the Mining Ecosystem on ETCHash (GPUs and ETChash ASICs) and the proposed new mining ecosystem on Keccak256 (FPGA & KEC ASICs).

ETC Core Devs Call 22 - Proposed Rejection of Keccak256 ECIP-1049
ETC Core Devs Call 22 - Proposed Rejection of Keccak256 ECIP-1049

New Proposal Champion:

Given the new champion is active, Bob Summerwill is provided time to update the ECIP-1049 proposal to be ECIP-1000 compliant. This was recommended in October, 2020 to the previous champion after Core Developers Call 15, but did not happen. The hope is with a new champion we will see compliance with the ECIP process.

Some comments from Bob Summerwill on the undocumented technical work from his staff:

  • Support for Astor already integrated in Besu. There is a pull request for core-Geth (and blocks successfully mined on Astor), but some rearchitecting needed to make that clean enough to integrate.
  • The transition is where more client work is needed (ie. having a Testnet which goes through the transition versus being Keccak256 from Genesis). More work needed on mining side software too.
  • So not tons left to do, but probably needs a couple of months of focus to do it right. Note - this is the technical work.
  • Roll out via testnets, all the social layer etc etc is more time again, of course.
  • I was asked where June, 2022 was feasible (end to end). I think that is a pretty clear not really possible.

Here is the open PR to move 1049 to Rejected status if the new champion does NOT bring the ECIP-1049 proposal up to ECIP-1000 standards:

Thanks for everyone's participation. Please direct future commentary to the newest ECIP 1049 discussion thread. However, please review the historical threads. There has been plenty of technical discussion on this matter over the years.

Please review the issue thread to find the most up to date information.

Recording of Ethereum Classic Core Devs Call 22 - Proposed Rejection of Keccak256 ECIP-1049

Note: Issues with the ETC Discord server audio was reported by numerous call participants and observed on the recording. This led to talking over/interruptions during the call. Apologies to those listening after the fact from the organizer of the call and the third-party community member who recorded the call. Future CDC calls will be held on a platform with hand raising and the ability to mute interrupting parties during the call.

ETC Core Devs Call 22 - ECIP-1049 Proposed Rejection
ETC Core Devs Call 22 - ECIP-1049 Proposed Rejection
This page exists thanks in part to the following contributors:

  • EnglishEnglish
  • 中文中文
  • اَلْعَرَبِيَّةُاَلْعَرَبِيَّةُ
  • DeutschDeutsch
  • EspañolEspañol
  • ΕλληνικάΕλληνικά
  • FrançaisFrançais
  • עִבְרִיתעִבְרִית
  • हिन्दीहिन्दी
  • HrvatskiHrvatski
  • ItalianoItaliano
  • 日本語日本語
  • 한국어한국어
  • MalayMalay
  • NederlandsNederlands
  • PortuguêsPortuguês
  • русскийрусский
  • ภาษาไทยภาษาไทย
  • TürkTürk
  • Tiếng ViệtTiếng Việt
  • 粵語粵語
Add ETC to MetaMask
The ETC community is active on Discord
ETC Coop Discord
ETC Coop Discord
eth_classic Twitter
eth_classic Twitter
ETC_Network Twitter
ETC_Network Twitter
ETC Labs Github
ETC Labs Github
This site is powered by Netlify


  • FAQs
  • Why Classic?
  • Knowledge
  • Videos

Made with <3 for the Original Ethereum Vision

The content on this website is user-generated and solely for informational purposes. Do not interpret any content as an endorsement of any product or service. There's "no official anything" in Ethereum Classic. Always do your own research, and remember: don't trust, verify!