How zkmopro/mopro works
Main Components Structure
A. Client Applications Layer (Top)
• Mobile Apps (iOS/Android)
• Web Applications
• Flutter Applications
• React Native Applications
B. Core Integration Layer (Middle)
• Mopro FFI (Foreign Function Interface)
• Mopro WASM (WebAssembly Interface)
C. ZK Proving Layer (Bottom)
• Circom Adapter
• Halo2 Adapter
Component Relationships
• Double lines: Data flow paths
Detailed Component Breakdown
Frontend Implementations:
┌─────────────────────────────────────────┐
• Client Applications │
• ┬─────────┬─────────┬─────────┤
• Android │ iOS │ Web │ Flutter │
• ┴─────────┴─────────┴─────────┘
Integration Layer:
┌─────────────────────────────────────────┐
• Integration Interfaces │
• ┬─────────────────┤
• Mopro FFI │ Mopro WASM │
• (Mobile Native) │ (Web Browser) │
• ┴─────────────────┘
ZK Proving Layer:
┌─────────────────────────────────────────┐
• ZK Proving Engines │
• ┬─────────────────┤
• Circom Adapter │ Halo2 Adapter │
• ┴─────────────────┘
Additional Elements
Supporting components:
• Test vectors repository
• Documentation system
• CLI tools
• Configuration management
Performance Indicators
A side panel showing performance metrics from the README:
• Circom performance comparisons
• Halo2 performance metrics
• Platform-specific benchmarks
Implementation Details
Technical aspects:
• Rust/FFI bindings
• WASM compilation pipeline
• Mobile platform integration points
• Test infrastructure