Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
hotfix: workaround gnark 0.10.0 unsoundness bug
A lot of time passed since gnark v0.10.0 unsoundness bug[0] was reported and fixed. We posponed the upgrade because the fixed release, v0.11.0, contains another vulnerability, an OOM[1], for which a fix has been in main since last November but no release appeared until now. Our options here are limited, and none quite happy: - We can `redirect` to a commit in `main`; - We can disable groth16 verifiers from the network, which we currently use; or - We can enforce that proofs have only one commitment, as the unsoundness can only be triggered with multiple commitments per proof. This implements the latter option, being the least invasive one. [0]: https://www.zellic.io/blog/gnark-bug-groth16-commitments [1]: GHSA-cph5-3pgr-c82g
- Loading branch information