Zero-Knowledge Virtual Machines (zkVMs) are specialized virtual machines designed to execute programs while preserving data privacy through zero-knowledge proofs.
A visual representation of zkVM’s main components and their interactions can be seen below.
Current zkVM designs prioritize SNARK compatibility, which in principle requires the minimization of the complexity of the circuit representation of their instructions.
Optimizing for SNARK compatibility does enhance the efficiency of the zero-knowledge proof process, but this often involves using a simplified instruction set. Such simplification inherently constrains the zkVM’s capabilities and expressiveness.
Yet, two recent innovations in zkVM optimization techniques are challenging the way we approach zkVM design; Jolt and Lasso.
Jolt (Just One Lookup Table): Introduces a new front-end technique that can be applied to a variety of instruction set architectures. Instead of converting each instruction directly into corresponding arithmetic circuits, Jolt represents these instructions as lookups into pre-determined tables. This provides a considerable efficiency boost because fetching a precomputed value from a table is usually much faster than performing a complex computation.
Lasso: Introduces a new lookup argument that uses a predefined table, enabling provers to commit to vectors and ensuring that each entry can be mapped back to this table. This provides an optimization for multiplications-based commitment schemes, creating a dramatically faster prover.
Jolt uses Lasso to offer a new framework for designing SNARKs for zkVMs, and together they can improve performance, developer experience, and auditability for SNARKs, thus expanding the horizon for zkVM design.
Thank you to the ZKM research team for valuable discussions.
I read the instruction but I did not understand why even zkEVM has the name EVM which is not running on ethereum.
Am I wrong ?
It sounds like you are talking about JVM here for me.
How to embed zkVM into ethereum ?
Or is there any milestone that EVM is going to be zkVM ?
Or are you proposing that EVM should be extended to zkVM in the future ?
Or do you have some contract zkVM on ethereum blockchain already ?
I am not asking the converse, i.e. how to embed EVM into zkVM.
Point out what is the wrong part if my understanding is wrong!
I do not see your motivations, how to use it “on ethereum”.
To connect zkMIPS with L2, users need to implement an L2-specific Communication Manager and a validation program for state transition. This program is then compiled to MIPS and executed by a MIPS VM. zkMIPS executes the program and generates ZK proof of execution. The proof can be sent to an on-chain proof verifier, which can trigger a state transition or allow withdrawals if the proof is valid. The main components of the integrated system are illustrated in Figure 3.
section 3.2 of the whitepaper seems to say that
A user Alice makes some program that compile into MIPS
Alice compiles the program using zkMIPS.
Then, zkMIPS publishes a zk-proof of the Alice’s program on some Ethereum Contract
There’s another good introduction.
It says zkEVM is a kind of zkRollup.
A user Alice write a contract and want to execute on zkEVM not on EVM
zkEVM compiles the code and publish its execution proof on the main zkEVM’s ethereum contract.
Alice can assure that zkEVM definitely executed Alice’s contract.
So, zkEVM is a kind of DApp on ethereum, and it can execute smart contracts “on zkEVM”.
The Contract executions are assured by ethereum.
Congratulations to the ZKM 4 research team for their groundbreaking work in zkVM optimization. The results speak volumes, not only in terms of advancing the efficiency of zero-knowledge proof processes but also in opening new horizons for zkVM design. The impact of this research is truly commendable. Well done!
