From 4333fbe1c9f4a7afff1eedf34342e96f046cf152 Mon Sep 17 00:00:00 2001 From: ChihChengLiang Date: Fri, 8 Dec 2023 18:19:18 +0800 Subject: [PATCH 1/4] first draft --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index db401c9f..6e2e7bc1 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,17 @@ # SNARK Verifier Generic (S)NARK verifier. + +## User Guide + +If you write a circuit in Halo2 and want to verify the generated proof on Ethereum, this project is for you. + +This repository also contains an example to verify an aggregated proof, which is a proof for multiple other proofs. Try it out with `cargo run --example evm-verifier-with-accumulator`. + +The effort has been under active developement, so there are variants of repositories to chose. + +- For production use, [axiom’s fork](https://github.com/axiom-crypto/snark-verifier) is audited and thus recommended. +- In the future, [halo2-solidity-verifier](https://github.com/privacy-scaling-explorations/halo2-solidity-verifier) is favored. Some notes: + - We plan to sunset snark-verifier and shift focus to halo2-solidity-verifier + - halo2-solidity-verifier is unaudited and has some limitations, see the project README for details. + - snark-verifier fails to generate Solidity code by hitting the contract size limit when the circuit is too large. halo2-solidity-verifier is written to solve this issue. \ No newline at end of file From c9cb89c09ed27a33d086b5dfdb9d852c581da794 Mon Sep 17 00:00:00 2001 From: ChihChengLiang Date: Fri, 8 Dec 2023 18:25:43 +0800 Subject: [PATCH 2/4] GPT editing --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 6e2e7bc1..84f40382 100644 --- a/README.md +++ b/README.md @@ -4,14 +4,14 @@ Generic (S)NARK verifier. ## User Guide -If you write a circuit in Halo2 and want to verify the generated proof on Ethereum, this project is for you. +This project is tailored for verifying [Halo2](https://github.com/privacy-scaling-explorations/halo2)-generated proofs on Ethereum. -This repository also contains an example to verify an aggregated proof, which is a proof for multiple other proofs. Try it out with `cargo run --example evm-verifier-with-accumulator`. +Additionally, within this repository, there is an example provided for verifying an aggregated proof, which serves as proof for multiple other proofs. You can test it by executing `cargo run --example evm-verifier-with-accumulator`. -The effort has been under active developement, so there are variants of repositories to chose. +As this effort is continuously evolving, there are multiple repository variants to choose from. For optimal results: -- For production use, [axiom’s fork](https://github.com/axiom-crypto/snark-verifier) is audited and thus recommended. -- In the future, [halo2-solidity-verifier](https://github.com/privacy-scaling-explorations/halo2-solidity-verifier) is favored. Some notes: - - We plan to sunset snark-verifier and shift focus to halo2-solidity-verifier - - halo2-solidity-verifier is unaudited and has some limitations, see the project README for details. - - snark-verifier fails to generate Solidity code by hitting the contract size limit when the circuit is too large. halo2-solidity-verifier is written to solve this issue. \ No newline at end of file +- For production use, it is recommended to use [axiom’s fork](https://github.com/axiom-crypto/snark-verifier), which has been audited. +- In the future, consider using [halo2-solidity-verifier](https://github.com/privacy-scaling-explorations/halo2-solidity-verifier). However, please note the following: + - The plan is to phase out snark-verifier and shift focus to halo2-solidity-verifier + - Keep in mind halo2-solidity-verifier is currently unaudited and has certain limitations, refer to the project README for details. + - snark-verifier may encounter issues generating Solidity code due to hitting the contract size limit with large circuits, a problem addressed by halo2-solidity-verifier. From d2cf14357bd435869b4bee42976210871019f39c Mon Sep 17 00:00:00 2001 From: Chih Cheng Liang Date: Tue, 12 Dec 2023 17:48:42 +0800 Subject: [PATCH 3/4] Update README.md Co-authored-by: Han --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 84f40382..8beb9f11 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ Additionally, within this repository, there is an example provided for verifying As this effort is continuously evolving, there are multiple repository variants to choose from. For optimal results: - For production use, it is recommended to use [axiom’s fork](https://github.com/axiom-crypto/snark-verifier), which has been audited. -- In the future, consider using [halo2-solidity-verifier](https://github.com/privacy-scaling-explorations/halo2-solidity-verifier). However, please note the following: +- In the future, consider using [halo2-solidity-verifier](https://github.com/privacy-scaling-explorations/halo2-solidity-verifier) for solidity verifier generation. However, please note the following: - The plan is to phase out snark-verifier and shift focus to halo2-solidity-verifier - Keep in mind halo2-solidity-verifier is currently unaudited and has certain limitations, refer to the project README for details. - snark-verifier may encounter issues generating Solidity code due to hitting the contract size limit with large circuits, a problem addressed by halo2-solidity-verifier. From ab8b79db4c47554f439e7fd2da76e3baf8607b2d Mon Sep 17 00:00:00 2001 From: ChihChengLiang Date: Tue, 12 Dec 2023 18:01:31 +0800 Subject: [PATCH 4/4] highlight proof aggregation --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8beb9f11..19c61186 100644 --- a/README.md +++ b/README.md @@ -10,8 +10,11 @@ Additionally, within this repository, there is an example provided for verifying As this effort is continuously evolving, there are multiple repository variants to choose from. For optimal results: -- For production use, it is recommended to use [axiom’s fork](https://github.com/axiom-crypto/snark-verifier), which has been audited. +- Use [Axiom’s fork](https://github.com/axiom-crypto/snark-verifier) of snark-verifier when + - You require production-grade quality; Axiom's fork has been audited. + - Proof aggregation is necessary. - In the future, consider using [halo2-solidity-verifier](https://github.com/privacy-scaling-explorations/halo2-solidity-verifier) for solidity verifier generation. However, please note the following: - The plan is to phase out snark-verifier and shift focus to halo2-solidity-verifier - Keep in mind halo2-solidity-verifier is currently unaudited and has certain limitations, refer to the project README for details. - snark-verifier may encounter issues generating Solidity code due to hitting the contract size limit with large circuits, a problem addressed by halo2-solidity-verifier. + - Proof aggregation is not supported in halo2-solidity-verifier at this time.