A rollup that is EVM-compatible and protected by a ZKP is called a zkEVM. To put it another way, a zkEVM is made to accommodate both EVM and zero knowledge roll up technology. The ultimate objective is to guarantee that zk rollups can support main layer Ethereum dApps and process any transactions that happen on the mainnet of Ethereum and prioritizing performance over interoperability with the current Ethereum infrastructure. The capability (dApps and smart contracts) made possible by these new zkEVMs significantly reduces gas prices and boosts Ethereum network throughput.
In order for Zk-EVM to cause synchrony, the computation needs to take place in a way that affects both the ZKP and EVM states.
Zk-EVM first simulates an Ethereum environment via roll-ups. It will start with Ethereum in its initial state, calculate every transaction as reads, offer a validity check, and then output a new transaction as writes in order to do that. Consequently, Ethereum’s state may be updated instantly without requiring duplicate computation in the ZKP environment first and then simultaneously posting those proofs on the Ethereum Environment. Then, it performs the subsequent procedure to verify a state change that can occur concurrently on both the L2 and Ethereum (main layer).
