argumentcomputer / argumentcomputer/multi-stark
Optimize for circuits that aren't used
Open
- Dominant language
- Rust
- Stars
- 5
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Circuits that aren't used have no trace. We can filter them out when creating a proof.
But we also need to include some layout information in the proof object.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by tracing proof creation and the proof object, then determine how unused circuits and their layout information should be represented and validated.
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