Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optimize for circuits that aren't used

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cryptography

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.

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.

Dominant language
Rust
Stars
5
Forks
1
Avg merge
3d 8h
Merged PRs (30d)
5

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from argumentcomputer/multi-stark

All issues in argumentcomputer/multi-stark

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.