PANews reported on November 4th that Vitalik Buterin tweeted that the modexp precompilation is extremely unfriendly to ZK-EVM, with worst-case computational overhead reaching 50 times the average block size. He called for an EIP to replace it with equivalent EVM code, even if it requires higher gas. He admitted that as the designer of modexp, he was "ashamed to admit defeat" and pointed out that its extremely low usage and increased risk of consensus failure should not sacrifice the efficiency of the entire Ethereum ecosystem for the needs of a very small number of people.PANews reported on November 4th that Vitalik Buterin tweeted that the modexp precompilation is extremely unfriendly to ZK-EVM, with worst-case computational overhead reaching 50 times the average block size. He called for an EIP to replace it with equivalent EVM code, even if it requires higher gas. He admitted that as the designer of modexp, he was "ashamed to admit defeat" and pointed out that its extremely low usage and increased risk of consensus failure should not sacrifice the efficiency of the entire Ethereum ecosystem for the needs of a very small number of people.

Vitalik called for the removal of the modexp pre-compilation, arguing that it severely hinders ZK-EVM efficiency.

2025/11/04 10:43

PANews reported on November 4th that Vitalik Buterin tweeted that the modexp precompilation is extremely unfriendly to ZK-EVM, with worst-case computational overhead reaching 50 times the average block size. He called for an EIP to replace it with equivalent EVM code, even if it requires higher gas. He admitted that as the designer of modexp, he was "ashamed to admit defeat" and pointed out that its extremely low usage and increased risk of consensus failure should not sacrifice the efficiency of the entire Ethereum ecosystem for the needs of a very small number of people.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.
Share Insights

You May Also Like