ECIP (draft) - Quantum-resistance for Ethereum Classic: ML-DSA verification precompile#557
Conversation
|
Highlighting this comment so it doesn't appear that this wasn't looked at. Again, i think upstream EVM is the best place for this. They have the resources and bandwidth to implement this in a serious way. This project is currently in a funding crisis with its deprecated client in maintenance mode, so its unlikely this will get any attention atm. If this is adopted upstream it will make its way into ETC at some point should we figure out how to self-fund this project. https://github.com/orgs/ethereumclassic/discussions/556#discussioncomment-15686274 |
Thank you for the comment. I responded there. The tl;dr is that I think there are plenty of people available with which to do code review once the testing is complete and there is a successful test deployment with ample results to share. This would mean ETC can lead in the space. We like the idea of self-funding of projects and look forward to exploring that further with conversations about Elysium and how it relates to Olympia in this way. |
|
@GravityLabLLC, a numbering correction: the ECIP number in your title is being formalized for the Olympia network-security ECIP (referenced throughout client implementations and updated specs), and the 112x range is already the Olympia suite, with ECIP-1121 as the meta spec. Per ECIP-1000, ECIP numbers are assigned by editors at formal submission, not self-assigned, so I'm retitling this to the un-numbered draft format (matching your #568, #569, #570) until it's formally submitted. For post-quantum work, a dedicated range (1140s) makes sense as more QR proposals come in, your ML-DSA precompile would be the anchor as the first QR proposal submitted. We can assign the number at formal submission. |
WIP
Discussion: https://github.com/orgs/ethereumclassic/discussions/556
PR: ethereumclassic/core-geth#5