Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cli): support protocol version 24 #40

Merged
merged 5 commits into from
May 3, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2,030 changes: 900 additions & 1,130 deletions Cargo.lock

Large diffs are not rendered by default.

10 changes: 3 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,20 +21,16 @@ It also generates the test, that can be inserted in unittests for Verifier.sol.
#
This is an experimental command line tool to verify the proofs for zkSync Era's updated proof system, Boojum [https://github.com/matter-labs/era-boojum](https://github.com/matter-labs/era-boojum).

The CLI fetches Boojum proofs for a given batch, public inputs, and aux input all from L1 and verifies the proof off chain. For testnet and sepolia chains, there may not be proofs submitted on chian for batches.
The CLI fetches Boojum proofs for a given batch, public inputs, and aux input all from L1 and verifies the proof off chain. For sepolia chains, there may not be proofs submitted on chian for batches.

Learn more about the Boojum proof system in our blog post: [https://zksync.mirror.xyz/HJ2Pj45EJkRdt5Pau-ZXwkV2ctPx8qFL19STM5jdYhc](https://zksync.mirror.xyz/HJ2Pj45EJkRdt5Pau-ZXwkV2ctPx8qFL19STM5jdYhc)

# Proof generation limitation

We are currently generating boojum proofs for all batches on sepolia, so at the moment this is the only chain supported. For mainnet and testnet, these will be updated once supported.

# Running the CLI

You can verify that committed proofs are valid by running:

```shell
cargo run -- --batch <batch_number> --l1-rpc <your L1 rpc https endpoint>
cargo run -- --batch <batch_number> --network <network> --l1-rpc <your L1 rpc https endpoint>
```

Full example
Expand All @@ -52,7 +48,7 @@ cargo run -- --batch 109939 --network mainnet --l1-rpc https://rpc.ankr.com/eth

```shell
--batch - The L1 batch number you want to verify the generated proof
--network - Along with batch number, defines if you want to verify a proof for Era testnet or mainnet. It defaults to mainnet. Accepts "mainnet" or "testnet"
--network - Along with batch number, defines if you want to verify a proof for Era testnet or mainnet. It defaults to mainnet. Accepts "mainnet" or "sepolia"
--l1-rpc - The RPC url required to pull data from L1.
--json - Flag to specify if the output should be in json. Note that all the usual std out prints are silenced.
```
Expand Down
Loading
Loading