paritytech / paritytech/ring-proof

remove RingVerifier::restore_challenges() in favor of PiopVerifier::evaluate_at_zeta()

Open
#74 0 comments 0 reactions 1 assignee View on GitHub

@swasilyev is already working on this.

Since Mar 5, 2026.

Dominant language
Rust
Stars
21
Forks
15
No merged PRs in 30d

Description

It had seemed just simpler to construct the evaluated piop when knowing zeta, but now i prefer to internalize it to have the verifier code in one place.

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.