`provekit/backend/bn254/src/frontend/witness_generator`: Handling of the return value for the verifier.
Open
Nobody has claimed this yet.
to do
tracker
- Dominant language
- Noir
- Stars
- 138
- Forks
- 47
- Avg merge
- 1d 34m
- Merged PRs (30d)
- 6
Description
On 2026-07-06 in 05de18e “Merge pull request #458 from worldfnd/sl/goldilocks-field-abstraction”:
Handling of the return value for the verifier.
provekit_common::utils::serde_jsonify,
serde::{Deserialize, Serialize},
std::num::NonZeroU32,
};
// TODO: Handling of the return value for the verifier.
#[derive(Clone, Debug, Serialize, Deserialize)]
pub struct NoirWitnessGenerator {
// Note: Abi uses an [internally tagged] enum format in Serde, which is not compatible
// with some schemaless formats like Postcard.
From provekit/backend/bn254/src/frontend/witness_generator.rs:8
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.
Research direction
Start in provekit/backend/bn254/src/frontend/witness_generator.rs at the TODO near the NoirWitnessGenerator definition, then trace the verifier entry point and its callers to understand the expected return value. Done means the verifier’s return value is handled consistently, with the relevant behavior covered by the project’s existing tests if applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100