Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Halo2 Soundness Bug Examples #63

Open
teddav opened this issue Jul 18, 2024 · 1 comment
Open

Proposal: Halo2 Soundness Bug Examples #63

teddav opened this issue Jul 18, 2024 · 1 comment
Assignees
Labels
Application Proposal Proposal submitted by applicants Grant Work in Progress Passed review and work in progress

Comments

@teddav
Copy link

teddav commented Jul 18, 2024

General Grant Proposal

Project Overview 📄

Overview

Write examples of Halo2 circuits presenting soundness bugs.
The goal is to educate users on recognizing and understanding Halo2 circuit bugs.

Team 👥

A one man team :)

  • Name: David
  • Telegram: teddav
  • Discord: teddav

Team's experience

Development Roadmap 🔩

Overview

  • Total Estimated Duration: 6 weeks
  • Total Estimated Working Hours: XXX hr
  • Full-time equivalent (FTE): 0.5
  • Expected Start Date: July 24th 2024
  • Expected End Date: September 4th 2024

For each vulnerability, the process will be:

  • explain the high level vulnerability: causes and consequences (real world examples)
  • write the vulnerable circuit
  • show the exploit
  • fix it

Milestone 1: High level overview + underconstrained

  • Estimated Duration: 2 weeks
  • FTE: 0.5
  • Estimated delivery date: August 7th 2024
  • Start with a blogpost
    • Halo2 global explainer
    • explanation of soundness
    • high level overview of circuit vulnerabilities
  • Write examples of the most common vulnerability: underconstrained circuits

Milestone 2: Circuits, circuits, circuits...

  • Estimated Duration: 2 weeks
  • FTE: 0.5
  • Estimated delivery date: August 21st 2024
  1. Write more vulnerable circuits:
    see https://github.com/0xPARC/zk-bug-tracker#common-vulnerabilities-header
  • more underconstrained:
    • "Nondeterministic Circuits"
    • “Assigned but not Constrained”
  • overflow/underflow
  1. Research other kind of vulnerabilities

Milestone 3: Tools + finish

  • Estimated Duration: 2 weeks
  • FTE: 0.5
  • Estimated delivery date: September 4th 2024
  1. Setup automated tools
    Which automated tools exist? How to use them to detect circuit vulnerabilities?
    These tools could be a great help to new developers (and more advanced as well)
  2. Write final blogpost
@NOOMA-42 NOOMA-42 added the Application Proposal Proposal submitted by applicants label Jul 18, 2024
@miha-stopar
Copy link

Looks cool!

@NOOMA-42 NOOMA-42 added the Grant Work in Progress Passed review and work in progress label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Application Proposal Proposal submitted by applicants Grant Work in Progress Passed review and work in progress
Projects
None yet
Development

No branches or pull requests

3 participants