ZK

In ZK rollups, the operator may post the transaction batch and state root to a base layer for user availability, but the system doesn’t require it for verification. The operator simply demonstrates transaction execution through ZK technology and submits this validity proof to the rollup contract on the base layer.

The L1’s validator set verifies the proof by running the contract logic, eliminating the need for additional verifier nodes. Instead of relying on economic incentives like optimistic rollups, ZK rollups leverage cryptography and ZK proofs to secure the system.

However, ZK mechanisms are difficult to design. While proof verification may be efficient for validators, proof construction is resource-intensive for the operator.