SNARK Proofs Audit

Open
  • Is something wrong?
#2,530 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the SNARK proofs cryptography code in the repository and defining the audit scope, since the issue names no files or entry points. Review the relevant proof implementation and tests, then document an independent assessment of correctness, security, and robustness; the audit findings and any follow-up fixes would define done.

Written by the indexing model from the issue text.

Description

roadmap :compass:

Why

We need an external audit of the SNARK proofs cryptography code to independently verify its correctness, security, and robustness. Given the critical role this code plays in ensuring trust and integrity, the audit will help identify potential vulnerabilities. They will then be addressed to prevent security risks and ensure the system remains reliable.

Dominant language
Rust
Stars
155
Forks
52
Avg merge
2d 17h
Merged PRs (30d)
37

Getting set up

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 IntersectMBO/mithril

All issues in IntersectMBO/mithril

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.