TL:DR
The different types of ZK-EVMs
1. Layer 2 基础 | WTF Academy
Type |
Feature |
Pros |
Cons |
Project |
Type 1(Ethereum-equivalent) |
|
|
|
Scroll, Taiko |
Type 2(EVM-equivalent) |
removing parts of the Ethereum stack that rely on needlessly complicated and ZK-unfriendly cryptography |
|
- ZK-EVM change Ethereum's Keccak and RLP-based Merkle Patricia tree and perhaps the block and receipt structures |
|
- | \ |
| Type2.5(EVM-equivalent,except gas) | increase the gas costs of specific operations in the EVM that are very difficult to ZK-prove | \ | may reduce developer tooling compatibility and break a few applications, but it's generally considered less risky than "deeper" EVM changes | \ |
| Type 3(almost EVM-equivalent) | remove a few features that are exceptionally hard:
- precompile
- some may change how to deal with contract code | | | Scroll and Polygon are both Type 3 in their current forms |
| Type 4 (high-level-language equivalent) | | | | |
zkEVM v.s EVM
zkEVM Vs EVM: Full Equivalence? by Ignasi Ramos | Devcon Bogotá
RoadMap
Manta
Manta Pacific发布其模块化zkEVM路线图