argumentcomputer / argumentcomputer/sphinx
Defenses on multiplicity overflow
- Dominant language
- Rust
- Stars
- 80
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The SP1 audit highlights accounting for the max # of byte lookups per instruction as a way to defend against multiplicity overflow:
https://hackmd.io/wztOd455QKWf-K8LXh_Fqw#Defenses-on-Multiplicity-Overflow-in-mathbbF_p
We do have precompiles much larger than Sp1 (e.g. G2 ops), which may have more lookups per instructions, and invalidate this defense.
/cc @adr1anh
Contributor guide
Research direction
Start with the linked SP1 audit section on defenses against multiplicity overflow, then inspect how this repository accounts for byte lookups in its precompiles. No repository file, test, or entry point is named in the issue. Done means establishing a defense that remains valid for larger precompiles such as G2 operations, or documenting why the current accounting is sufficient.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100