ZK Stack components

What are the ZK Stack modules today?

zkEVM

Our execution machine: EVM compatible, tailored for ZK, and including enhancements like Native Account Abstraction.

• Virtual machine

  Repo:

  era-zk_evm

  The rust-based virtual machine is responsible for transaction validation and execution (including logic for rollbacks, history, etc).

Smart Contracts and System Contracts

All the smart contracts needed for the rollup, both on L1 and L2.

System contracts are important contracts with admin powers (could be compared to kernel modules), which define the behaviour of the system. The bytecodes of these contracts are set upon genesis and can be changed only by conducting upgrades. You can read more about system contracts here.

While the zkEVM does not know about the bytecodes of system contracts per se, it does rely on some of these for behaving correctly (for instance, it uses AccountCodeStorage system contract's storage to retrieve bytecodes of deployed zkEVM contracts, etc).

Server/Node (and its sub-components)

All the backend services needed to run a hyperchain, including:

• RPC services

  The main interface for users to interact with the server.

  • HttpApi - Public Web3 API running on HTTP.

  • WsApi - Public Web3 API (including PubSub) running on WebSocket server

• ETH Operator

  This module is responsible for interacting with the base layer, both as an observer, as well as executing transactions.

  • EthWatcher - Monitor the base layer for specific events, such as Deposits or System Upgrades.

  • EthTxAggregator - Aggregates L1 batches and prepare a base layer tx, such as
    commit_blocks , prove_blocks , execute_blocks.

  • EthTxManager - Signs and sends base layer txs, prepared by EthTxAggregator also responsible for resending txs if they are stuck for any reason (example, low gas price).

• Sequencer

  Component that takes a list of incoming transactions, and packs them into blocks and batches - so that each one fits within the multiple constraints that our proving system has. It takes these batches and executes them on the zkEVM.

  • Tree and TreeBackup - maintains a local RocksDB with the complete storage tree, computing the hash of the latest

  • StateKeeper - the component that executes the transactions and saves sealed blocks to the DB

• Contract verification API

  The service that receives smart contract verification requests, validates them and provides the code/ABIs for verified contracts.

Prover

The set of components that allows zkEVM instructions (and the state changes they cause) to be proven with zero knowledge cryptography.

• Circuits

  Repo:

  era-zkevm_circuits

  Based on the virtual machine zkEVM, but with added functionality that re-executes transactions generating special traces that are used to recreate a given computation as a set of arithmetic circuits, which are then used for zero-knowledge proofs. Currently we have 13 different circuits types, that are responsible for proving different elements of the execution.

• Witness generator

  Repo:

  zksync-era (Witness Generator)

  Based on the virtual machine zkEVM, but with added functionality that re-executes transactions generating special traces that are used to recreate a given computation as a set of arithmetic circuits, which are then used for zero-knowledge proofs.

• Boojum

  Repo:

  era-boojum

  Our STARK approach to proving zkEVM instructions. This module contains:

  • GPU implementation - Can be run on consumer-grade GPUs with as little as only 16GB of RAM.

  • CPU implementation - Mostly for testing purposes, but an alternative to enable anyone to generate proofs in case GPUs are not available.

• Fri compressor

  Repo:

  zksync-era (FRI compressor)

  Final stage of proof generation, wrapping the STARK proof generated by Boojum into a SNARK for cheaper verification on Ethereum.

• Verifier

  Repo:

  zksync-era (Verifier)

  Solidity smart contract that is responsible for verifying that the state changes that were committed are valid given some proof.

Fee withdrawer

A component that automates the withdrawal of the hyperchain collected fees to an address on the base layer. This helps ensure the ETH operator on the base layer side has a constant influx of the gas token to keep working properly.

Portal - Wallet + Bridge

A dApp that allows you (and your users) to easily interact with your hyperchain, including bridging assets from and to the base layer, sending them within your hyperchain, checking historical transactions, and managing contacts. You can also enhance its capabilities by running the Block Explorer Indexer/API.