Enabling too many chips leads to errors in the recursive verifier
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- cryptography
Research direction
Start by reviewing issue #186 and reproducing the recursive compress machine with the full chip map enabled. Trace the core verifier proofs and cumulative sums during compression; done means the recursive verifier no longer produces non-zero cumulative sums without disabling chips.
Written by the indexing model from the issue text.
Description
As discovered during debugging of #186, it seems like having too many chips in the chip map leads to cumulative sum errors in the compress step. Specifically, the proofs outputted by the core verifier running inside of the recursive compress machine have non-zero cumulative sum. Disabling the chips by removing them from the chip map works around this issue. We're not sure exactly what the error inside of the recursive machine is yet.
For now, we've disabled a subset of chips that we are not relying on to work around this issue.
- Dominant language
- Rust
- Stars
- 80
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from argumentcomputer/sphinx
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
argumentcomputer/sphinx#206 ·
-
The termination check is under-constrained due to incomplete check of "public_values.next_pc == 0". Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
argumentcomputer/sphinx#205 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
argumentcomputer/sphinx#204 ·
-
SHA-512 improvements Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
argumentcomputer/sphinx#181 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
argumentcomputer/sphinx#173 ·
All issues in argumentcomputer/sphinx
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·