non-uniform IVC
- Dominant language
- Rust
- Stars
- 285
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
Add a layer of abstraction to allow non-uniform IVC style on the various implemented folding schemes.
As it is specified at:
- SuperNova paper: https://eprint.iacr.org/2022/1758.pdf
- section 5 of the updated HyperNova paper: https://eprint.iacr.org/2023/573.pdf
Update:
- Nebula paper: https://eprint.iacr.org/2024/1605 outlines a new switchboard approach to achieve the non-uniform IVC which might be interesting
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the SuperNova paper and section 5 of the updated HyperNova paper, then compare them with the Nebula paper's switchboard approach. Inspect the implemented folding schemes to determine the abstraction boundary. Done means the schemes support non-uniform IVC through a consistent abstraction, with the intended behavior covered by the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100