argumentcomputer / argumentcomputer/sphinx

Automated circuit artifact upload for release workflows

Open
#35 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
80
Forks
8
PR merge metrics
No merged PRs in 30d

Description

When running the full end-to-end groth16 flow, it looks like the default pre-built upstream SP1 circuit artifacts are no longer enough for verifying our proofs (verified with an aptos LC proof).

Either way, we may want to define a place to host these artifacts once we perform stable releases and make sure that we're using our own circuit artifacts by default instead of upstream's.

Contributor guide

Open the contributing guide

Research direction

Start with the full end-to-end groth16 flow and the release workflows that select pre-built SP1 circuit artifacts. Trace how the upstream artifacts are chosen, then define where release artifacts should be hosted and how the project will use its own artifacts by default; verify the result with the Aptos LC proof flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devops, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.