1. Add the necessary repository

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

2. Install the necessary dependencies

sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release -y

3. Install Docker

sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli docker-compose containerd.io -y
sudo apt install gnome-keyring

4. Add your user to the Docker group

sudo usermod -aG docker $USER
sudo chmod 666 /var/run/docker.sock
sudo service docker restart

5. Testing the installation

docker version
docker pull hello-world

6.fix "System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down"

sudo apt-get update && sudo apt-get install -yqq daemonize dbus-user-session fontconfig

sudo daemonize /usr/bin/unshare --fork --pid --mount-proc /lib/systemd/systemd --system-unit=basic.target

exec sudo nsenter -t $(pidof systemd) -a su - $LOGNAME

snap version

参考文档

https://www.zdnet.com/article/docker-101-how-to-install-docker-on-ubuntu-server-22-04/
https://gist.github.com/alyleite/ca8b10581dbecd722d9dcc35b50d9b2b
https://docs.docker.com/engine/install/ubuntu/

Awesome zkEVM

zkEVM is a Fully EVM equivalent and zk friendly virtual machine.

Contents

• Awesome zkEVM
  • Contents
  • Article - Video
    • Rollup
    • zkEVM
    • zk-hardware
    • Zero-Knowledge-Proofs
      • zk-SNARK
      • Plonk
      • Halo2
  • Resources - libraries, tools
    • Early Rollup
    • Scroll and Appliedzkp(PSE)
    • Polygon Hermez
    • Polygon Zero
    • zkSync
    • StarkWare
    • Zero-Knowledge-Proofs
    • Halo2
    • zkp Acceleration
  • Different Solutions
    • Native zkEVM
    • Compiler-Based zkEVM
    • Transpiler-Based zkEVM
    • Other
• Contributing

Article - Video

Rollup

• An Incomplete Guide to Rollups - vitalik, Introducing Rollup.
• A rollup-centric ethereum roadmap - vitalik, rollup-centric ethereum roadmap.
• How Zk-Rollups Work - How barry whiteHat's rollup works.

zkEVM

• zkEVM - Scroll zkEVM.
• zkEVM Architecture - Scroll & EF zkEVM Architecture.
• ZKVerse: Deep Dive Into Polygon Hermez 2.0 - Deep into zkEVM of polygon hermez.
• zkEVM circuit arithmetization - zkEVM circuits and EVM circuit, yezhang.
• The different types of ZK-EVMs

zk-hardware

• Hardware Acceleration for Zero Knowledge Proofs - Hardware for ZKPs.

Zero-Knowledge-Proofs

zk-SNARK

• Introduction to zk-SNARKs with Examples - Get started to learn zk-SNARK by example.
• Why and How zk-SNARK Works - In-depth SNARK mechanism and understanding.

Plonk

• Understanding PLONK
• ZK Study Club - Plonk with Zac Williamson
• Multiset checks in PLONK and Plookup

Halo2

• Halo and more: exploring incremental verification and SNARKs without pairings

Resources - libraries, tools

Early Rollup

• idn3 rollup - iden3 rollup implement.
• barryWhiteHat rollup - First rollup implemented by barryWhiteHat.

Scroll and Appliedzkp(PSE)

• zkEVM-spec
• zkEVM-circuit
• zkEVM-document
• Scroll's architecture

Polygon Hermez

• Polygon Hermez zkEVM
• Hermez document

Polygon Zero

• Plonky2

zkSync

• zksync v1 - zksync v1 source code.
• compiler-solidity - zkSync v2 compiler.
• zksync v2 portal - zksync v2 faucet, Goerli network.

StarkWare

• Awesome-starknet - A curated list of starkNet resources.
• Warp:transpile solidity to cairo

Zero-Knowledge-Proofs

• Awesome-zkps - A curated list of zkps resources.

Halo2

• Halo2 repo
• Halo2 document
• Halo2 for PSE and Scroll

zkp Acceleration

• supranational
• supranational - sppark

Different Solutions

Native zkEVM

• PSE (formerly appliedzkp)
• Scroll
• Polygon Hermez
• Polygon Zero

Compiler-Based zkEVM

• zkSync v2

Transpiler-Based zkEVM

• StarkNet
• Miden

Other

• Consensys zkEVM
• Consensys zkEVM 2.0

Contributing

Contributions are very welcome!

Please have a look at contributing.md for guidelines.

英文原文：https://github.com/LuozhuZhang/awesome-zkevm

测试硬件环境

OS: Mac Pro {cpu intel} v11.7.5
注意：目前，Executor/Prover 不能在 ARM 驱动的 Mac 上运行。对于 Windows 用户，不建议使用 WSL/WSL2。

测试环境搭建

先按官方的测试环境进行部署，熟悉下部署细节，然后再做针对性补充
主要参考文章如下

• Running locally
• Running on production
• setup-local-node
• setup-production-node

官方是已Docker环境进行演示介绍的，我们精简下，主要说下关键操作

安装基础环境

自行安装go,docker和docker-compose
可以参考以下官方文档，查看对应平台的安装方法：
https://go.dev/doc/install
https://www.docker.com/get-started
https://docs.docker.com/compose/install/

克隆代码

git clone https://github.com/0xPolygonHermez/zkevm-node.git

构建Docker镜像

cd zkevm-node/
make build-docker

运行 zkNode 环境

cd test/
make run

其他操作

make stop // 停止 zkNode
make restart // 重启整个 zkNode 环境

执行后，会创建和启动如下容器

• zkevm-state-db
• zkevm-pool-db
• zkevm-mock-l1-network
• zkevm-prover
• zkevm-approve
• zkevm-sync
• zkevm-eth-tx-manager
• zkevm-sequencer
• zkevm-l2gaspricer
• zkevm-aggregator
• zkevm-json-rpc

根据Docker环境抽离各个模块配置

//TODO

L1网络配置

• Network Name: Geth - Local
• New RPC URL: http://localhost:8545
• ChainID: 1337
• Currency Symbol: ETH

L2网络配置

• Network Name: Polygon zkEVM - Local
• New RPC URL: http://localhost:8123
• ChainID: 1001
• Currency Symbol: ETH
• Block Explorer URL: http://localhost:4000

访问环境

• Databases:
  • zkEVM Node State Database
    • Type: Postgres DB
    • User: state_user
    • Password: state_password
    • Database: state-db
    • Host: localhost
    • Port: 5432
    • Url: postgres://state_user:srare_password@localhost:5432/state-db
  • zkEVM Node Pool Database
    • Type: Postgres DB
    • User: pool_user
    • Password: pool_password
    • Database: pool_db
    • Host: localhost
    • Port: 5433
    • Url: postgres://pool_user:pool_password@localhost:5433/pool_db
  • zkEVM Node JSON-RPC Database
    • Type: Postgres DB
    • User: rpc_user
    • Password: rpc_password
    • Database: rpc_db
    • Host: localhost
    • Port: 5434
    • Url: postgres://rpc_user:rpc_password@localhost:5434/rpc_db
  • Explorer L1 Database
    • Type: Postgres DB
    • User: l1_explorer_user
    • Password: l1_explorer_password
    • Database: l1_explorer_db
    • Host: localhost
    • Port: 5435
    • Url: postgres://l1_explorer_user:l1_explorer_password@localhost:5435/l1_explorer_db
  • Explorer L2 Database
    • Type: Postgres DB
    • User: l2_explorer_user
    • Password: l2_explorer_password
    • Database: l2_explorer_db
    • Host: localhost
    • Port: 5436
    • Url: postgres://l2_explorer_user:l2_explorer_password@localhost:5436/l2_explorer_db
• Networks:
  • L1 Network
    • Type: Geth
    • Host: localhost
    • Port: 8545
    • Url: http://localhost:8545
  • zkEVM Node
    • Type: JSON RPC
    • Host: localhost
    • Port: 8123
    • Url: http://localhost:8123
• Explorers:
  • Explorer L1
    • Type: Web
    • Host: localhost
    • Port: 4000
    • Url: http://localhost:4000
  • Explorer L2
    • Type: Web
    • Host: localhost
    • Port: 4001
    • Url: http://localhost:4000
• Prover
  • Type: Mock
  • Host: localhost
  • Port: Depending on the prover image, if it's mock or not:
    • Prod prover: 50052 for Prover, 50061 for Merkle Tree, 50071 for Executor
    • Mock prover: 43061 for MT, 43071 for Executor
  • Url: http://localhost:50001

关键地址私钥

L1 Addresses

Deployer Account

Sequencer Account

Accounts

1. 引言

源代码：https://github.com/0xPolygonHermez/zkevm-node （Go语言）

Polygon zkEVM节点提供的主要服务模块有：

• 1）JSON-RPC服务
• 2）Sequencer服务
• 3）Aggregator服务
• 4）Synchronizer服务
• 5）Broadcast服务

2. JSON-RPC服务

以太坊JSON-RPC接口 与 Polygon zkEVM中的JSON-RPC接口 对比情况为：

Hermez 2.0（zkEVM）除实现了以上与以太坊兼容的RPC接口之外，还额外实现了一些与state交互、与pool交互的接口：

// jsonRPCTxPool contains the methods required to interact with the tx pool.
type jsonRPCTxPool interface {
    AddTx(ctx context.Context, tx types.Transaction) error
    GetPendingTxs(ctx context.Context, isClaims bool, limit uint64) ([]pool.Transaction, error)
    GetGasPrice(ctx context.Context) (uint64, error)
    GetPendingTxHashesSince(ctx context.Context, since time.Time) ([]common.Hash, error)
}

// gasPriceEstimator contains the methods required to interact with gas price estimator
type gasPriceEstimator interface {
    GetAvgGasPrice(ctx context.Context) (*big.Int, error)
}

// stateInterface gathers the methods required to interact with the state.
type stateInterface interface {
    BeginStateTransaction(ctx context.Context) (pgx.Tx, error)

    GetLastConsolidatedL2BlockNumber(ctx context.Context, dbTx pgx.Tx) (uint64, error)
    GetTransactionByHash(ctx context.Context, transactionHash common.Hash, dbTx pgx.Tx) (*types.Transaction, error)
    GetTransactionReceipt(ctx context.Context, transactionHash common.Hash, dbTx pgx.Tx) (*types.Receipt, error)
    GetLastL2BlockNumber(ctx context.Context, dbTx pgx.Tx) (uint64, error)
    GetLastL2Block(ctx context.Context, dbTx pgx.Tx) (*types.Block, error)
    GetLastL2BlockHeader(ctx context.Context, dbTx pgx.Tx) (*types.Header, error)
    EstimateGas(transaction *types.Transaction, senderAddress common.Address) (uint64, error)
    GetBalance(ctx context.Context, address common.Address, blockNumber uint64, dbTx pgx.Tx) (*big.Int, error)
    GetL2BlockByHash(ctx context.Context, hash common.Hash, dbTx pgx.Tx) (*types.Block, error)
    GetL2BlockByNumber(ctx context.Context, blockNumber uint64, dbTx pgx.Tx) (*types.Block, error)
    GetCode(ctx context.Context, address common.Address, blockNumber uint64, dbTx pgx.Tx) ([]byte, error)
    GetStorageAt(ctx context.Context, address common.Address, position *big.Int, blockNumber uint64, dbTx pgx.Tx) (*big.Int, error)
    GetSyncingInfo(ctx context.Context, dbTx pgx.Tx) (state.SyncingInfo, error)
    GetTransactionByL2BlockHashAndIndex(ctx context.Context, blockHash common.Hash, index uint64, dbTx pgx.Tx) (*types.Transaction, error)
    GetTransactionByL2BlockNumberAndIndex(ctx context.Context, blockNumber uint64, index uint64, dbTx pgx.Tx) (*types.Transaction, error)
    GetNonce(ctx context.Context, address common.Address, blockNumber uint64, dbTx pgx.Tx) (uint64, error)
    GetL2BlockHeaderByNumber(ctx context.Context, blockNumber uint64, dbTx pgx.Tx) (*types.Header, error)
    GetL2BlockTransactionCountByHash(ctx context.Context, hash common.Hash, dbTx pgx.Tx) (uint64, error)
    GetL2BlockTransactionCountByNumber(ctx context.Context, blockNumber uint64, dbTx pgx.Tx) (uint64, error)
    GetLogs(ctx context.Context, fromBlock uint64, toBlock uint64, addresses []common.Address, topics [][]common.Hash, blockHash *common.Hash, since *time.Time, dbTx pgx.Tx) ([]*types.Log, error)
    GetL2BlockHashesSince(ctx context.Context, since time.Time, dbTx pgx.Tx) ([]common.Hash, error)
    DebugTransaction(ctx context.Context, transactionHash common.Hash, tracer string) (*runtime.ExecutionResult, error)
    ProcessUnsignedTransaction(ctx context.Context, tx *types.Transaction, senderAddress common.Address, blockNumber uint64, dbTx pgx.Tx) *runtime.ExecutionResult
    IsL2BlockConsolidated(ctx context.Context, blockNumber int, dbTx pgx.Tx) (bool, error)
    IsL2BlockVirtualized(ctx context.Context, blockNumber int, dbTx pgx.Tx) (bool, error)
}

type storageInterface interface {
    NewLogFilter(filter LogFilter) (uint64, error)
    NewBlockFilter() (uint64, error)
    NewPendingTransactionFilter() (uint64, error)
    GetFilter(filterID uint64) (*Filter, error)
    UpdateFilterLastPoll(filterID uint64) error
    UninstallFilter(filterID uint64) (bool, error)
}

3. Sequencer服务

当前代码库中，暂未实现permissionless sequencer功能，ProofOfEfficiency.sol合约中也暂未实现registerSequencer等接口。

参考资料

[1] Ethereum JSON-RPC Specification
[2] PoE
[3] zkProver debugging
[4] Hermez 1.5 - Merkle Tree spec
[5] PoE - 1.5

附录：Polygon Hermez 2.0 zkEVM系列博客

• ZK-Rollups工作原理
• Polygon zkEVM——Hermez 2.0简介
• Polygon zkEVM网络节点
• Polygon zkEVM 基本概念
• Polygon zkEVM Prover
• Polygon zkEVM工具——PIL和CIRCOM

转载：https://blog.csdn.net/mutourend/article/details/126409344

Polygon zkEVM架构组成-思路梳理

• zkNode

  • Synchronizer
    • 获取Sequencers提交的transactions
    • 获取Aggregators提交的validity proofs
    • 监听以太坊链上事件，包括new batches{events中读取的信息->存储database}
    • 处理可能的reorgs {检查last ethBlockNum 和 last ethBlockHash 是否已同步}
  • State子模块
    • 实现了Merkle Tree并连接到DB后台
      • 在block level检查integrity（即，关于gas、block size等相关信息）
      • 检查某些交易相关信息（如签名、足够的balance等）
      • 将smart contract（SC）代码存储到Merkle tree中，并使用EVM来处理交易
  • Sequencer
    • 支持模式：Trusted/Permissionless
    • 处理流程：接收L2交易+L2用户支付的交易手续费 -> 对L2交易进行排序 ->生成batches -> send tx{sequences形式}（为Aggregator验证支付费用） -> L1合约 {PolygonZkEVM.sol} -> 存储storage slots
    • 经济模型：向L1提交有效交易，以获利
      • 根据利润对pool中交易排序
      • 向L1提交batches，支付L1系统代币
  • Aggregator
    • 处理流程：L1合约 {PolygonZkEVM.sol} -> 获取Sequencer提交的L2 batches -> zkProver{特殊链下EVM解析器} -> 生成ZK proof{证明该batch的完整性}-> send tx -> L1合约 {PolygonZkEVM.sol} -> 更新 L2 State root
    • 经济模型:Sequencers提交L1 batch时支付的手续费
    • 开支
      • 向L1提交validity proof交易成本
      • 运行aggregator和zkProver服务器成本

• Consensus Contract（PolygonZkEVM.sol）

  • 存储Sequencers提交的L2 batches
  • 对Aggregator新提交的L2 State root进行validity proof验证

• zkProver

  • 本质：zk virtual machine来仿真EVM
  • 功能：为Aggregator使用，来验证batches并提供validity proofs
  • 生成proof：以多项式和汇编语言形式
  • 功能包含如下
    • Main State Machine Executor：处理zkEVM的执行
      • 使用zkASM解析EVM Bytecodes
      • 为每个transaction batch设置多项式约束
      • 对多项式约束使用PIL进行编码
    • secondary State Machines : zkEVM中证明交易正确性的每一步计算
      • zkProver是整个项目中最复杂的部分，包含了多个state machines：
        • 一些执行bitwise function的state machines（如XOR/Padding等等）
        • 执行哈希运算的的state machines（如Keccak、Poseidon等等）
        • 执行验签的state machines（如ECDSA等等）
      • 二级状态机有:
        • Binary SM
        • Memory SM
        • Storage SM
        • Poseidon SM
        • Keccak SM
        • Arithmetic SM
    • STARK-proof builder
      • State machines负责生成多项式约束，zk-STARKs用于证明batches满足这些多项式约束条件
      • zkProver使用FRI对zk-STARK证明加速
    • SNARK-proof builder
      • size: STARK-proof > SNARK-proof
        • SNARK-proof来证明STARK-proof的正确性
        • SNARK-proof做为validity proof
        • 更便宜地在L1上验证该validity proof

• L1-to-L2 Bridge

  • L1 Contract：部署在以太坊，管理rollups之间的资产转移

    负责2个操作

    • bridge：将资产由一个rollup转移到另一个rollup

    • claim：当合约从任意rollup claim时，使用claim操作

    需要有2棵Merkle tree

    • globalExitTree：包括了所有rollups的exit trees的所有信息

    • mainnet exit tree：包含了用户与主网交互的交易信息

    global exit root manager L1的合约负责管理跨越多个网络的exit roots

  • L2 Contract：部署在某特定的rollup上，负责主网与该rollup之间的资产转移

    • 处理rollup端的bridge和claim操作
    • 与globalExitTree和rollup exit tree交互以更新exit roots

共识算法PoE

Hermez 1.0 PoD共识缺点

• 特定时间，网络由单一actor控制，可能作弊
• 竞价协议，预测复杂性高
• 参与竞争运营门槛高，导致运营集中，抗审查

Proof-of-Efficiency（PoE）实现

• Sequencer：负责将L2的交易打包为batches并添加到L1的PoE智能合约
• Aggregator：之间竞争，负责检查transaction batches的有效性，并提供validity proofs

PoE智能合约基本接口

• sendBatch：用于接收Sequencer的batches
• validateBatch：用于接收Aggregator的validity proof，进行validate batches

batch fee

根据网络负载情况，batch fee将是可变的，可根据protocol合约中的某个参数来计算

PoE的经济模型

• Sequencer赚L2的交易手续费{相应的validity proof提交后}
• Aggregator赚取Sequencer支付的batch MATIC手续费