How espressosystems/hyperplonk works
Main Components Identification
The project is structured as a Rust workspace with multiple crates:
• arithmetic: Core mathematical operations
• hyperplonk: Main SNARK implementation
• subroutines: Supporting algorithms and protocols
• transcript: Proof transcript handling
• util: Utility functions
┌─ Core Components ──────────────────────────────────┐
• ┌─────────────┐ ┌───────────────┐ │
• Arithmetic │◄─────┐ │ Hyperplonk │ │
• ┘ │ └───────────────┘ │
• ▲ │
• ┌─────────────┐ └─────────┤ │
• Subroutines │◄──────────────┤ │
• ┘ │ │
• ▲ │ │
• ┌─────────────┐ ┌─────┴─────┐ │
• Transcript │◄───────│ Util │ │
• ┘ └───────────┘ │
• ┘
Arithmetic Module
• Multilinear Polynomial
• Univariate Polynomial
• Virtual Polynomial
• Error Handling
Subroutines Module
• PCS (Polynomial Commitment Scheme)
• Multilinear KZG
• Univariate KZG
• Poly IOP
• Sum Check
• Zero Check
• Product Check
• Permutation Check
Hyperplonk Core
• Components for:
• SNARK Implementation
• Custom Gates
• Witness Handling
• Selectors
Supporting Components
• Transcript Management
• Utility Functions
• Error Handling
• Use blue for core cryptographic components
• Use green for mathematical/arithmetic components
• Use orange for utility and support functions
D. Important Elements to Include:
• How data moves between components during proof generation and verification
• Direction of dependency relationships
Interface Points
• Public APIs and entry points
• Interaction points between major components
Key Processes
• Proof Generation Flow
• Verification Flow
• Polynomial Commitment Operations
E. Technical Details to Note:
• A section showing the relationship with external dependencies
• FFT-free components (as this is a key feature)
• Parallel processing capabilities (based on bench_results directory)
• Integration points for custom gates and witness generation
• Any special symbols or notations used
• Abbreviations (e.g., PCS, KZG, IOP)
Remember to emphasize the linear-time, FFT-free nature of the system, as this is a key distinguishing feature of the Hyperplonk implementation.