[M19-IMPL-11] Proof composition architecture design
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- blockchain, cryptography
Research direction
No files, tests, or entry points are named. Start by mapping the Noir, Halo2, and Kimchi proof inputs and the proposed SIP Composer; done means the architecture document is complete, interfaces are finalized, and feasibility is confirmed.
Written by the indexing model from the issue text.
Description
Description
Design the overall architecture for composing proofs from multiple ZK systems.
Vision
┌─────────────────────────────────────────────────────────────────────────────┐
│ SIP PROOF COMPOSITION ARCHITECTURE │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ Input Proofs Composition Output │
│ ──────────── ─────────── ────── │
│ ┌─────────────┐ │
│ │ Noir Proof │──┐ │
│ │ (validity) │ │ ┌─────────────────┐ ┌─────────────┐ │
│ └─────────────┘ │ │ │ │ Composed │ │
│ ├─────────▶│ SIP Composer │─────▶│ Proof │ │
│ ┌─────────────┐ │ │ │ │ │ │
│ │ Halo2 Proof │──┤ └─────────────────┘ └─────────────┘ │
│ │ (privacy) │ │ │ │
│ └─────────────┘ │ │ │
│ │ ▼ │
│ ┌─────────────┐ │ ┌─────────────────┐ │
│ │Kimchi Proof │──┘ │ Verification: │ │
│ │ (succinct) │ │ • Privacy ✓ │ │
│ └─────────────┘ │ • Validity ✓ │ │
│ │ • Succinct ✓ │ │
│ └─────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Tasks
- Define proof interface abstraction
- Design composition algorithm
- Handle different curve families
- Implement proof aggregation
- Document architecture
Acceptance Criteria
- Architecture document complete
- Interface definitions finalized
- Feasibility confirmed
Parent
- Epic: #825
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from sip-protocol/sip-protocol
-
tech-debt
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sip-protocol/sip-protocol#1208 ·
-
tech-debt
Difficulty 4/5 3-5 days Newbie friendliness 52/100
sip-protocol/sip-protocol#1207 ·
-
tech-debt
Difficulty 4/5 3-5 days Newbie friendliness 52/100
sip-protocol/sip-protocol#1206 ·
-
dependencies tech-debt
Difficulty 5/5 Over a week Newbie friendliness 20/100
sip-protocol/sip-protocol#1186 ·
-
anchor chain:solana dependencies priority:medium tech-debt
Difficulty 5/5 Over a week Newbie friendliness 35/100
sip-protocol/sip-protocol#1161 · 2 comments ·
All issues in sip-protocol/sip-protocol
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·