How ingonyama-zk/icicle works
Main Components and Architecture
┌─────────────────────────────────────────────────────────────┐
• Language Bindings │
• ┬───────────────────────────┬─────────────────┤
• Rust │ Go │ C++ │
• ┬───────┴──────────────┬────────────┴────────┬────────┘
┌───────▼──────────────────────▼──────────────────────▼───────┐
• ICICLE Core │
• ┤
• Primitives │ Fields │ Curves │ Hash │ Runtime │ Device │
• ┬─────────────────────────────────────────────────────┘
┌───────▼─────────────────────────────────────────────────────┐
• Hardware Backends │
• ┬─────────────────────────┬─────────────────┤
• CPU │ CUDA │ Metal │
• ┴─────────────────────────┴─────────────────┘
Component Details
a) Core Components (Rectangles):
• Cryptographic Primitives (NTT, MSM, etc.)
• Field Operations
• Curve Operations
• Hash Functions
• Runtime Management
• Device Management
b) Hardware Backends (Hexagons):
• CPU Backend
• CUDA Backend
• Metal Backend
c) Language Bindings (Rounded Rectangles):
• Rust Wrappers
• Go Wrappers
• C++ Interface
Data Flow and Interactions
Application → Language Binding → Core → Backend → Hardware
Key Features to Highlight
Create subsections showing:
• Multi-device support
• Field/Curve implementations
• Cryptographic primitives
• Memory management
• Backend selection/configuration
Implementation Details
Technical details in notes:
• Supported curves (BLS12-381, BN254, etc.)
• Supported fields (babybear, stark252, etc.)
• Hardware requirements
• Performance characteristics
• Clear separation between frontend (bindings) and backend (hardware)
• Extensibility points for new backends
• Performance-critical paths
• Memory management and resource allocation flows
• Where configuration and runtime selection occurs