From ab8b79db4c47554f439e7fd2da76e3baf8607b2d Mon Sep 17 00:00:00 2001 From: ChihChengLiang Date: Tue, 12 Dec 2023 18:01:31 +0800 Subject: [PATCH] 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.