Skip to main content

Provers

The Provers form the computational backbone of Lagrange's ZK Prover Network, consisting of a decentralized network of specialized hardware machines that generate zero-knowledge proofs on demand. This distributed architecture ensures high availability, censorship resistance, and scalable proof generation.

Network Architecture​

Decentralized Infrastructure​

The Prover Network is built on a foundation of geographic and operational diversity:

  • 85+ Institution-Grade Operators: Including Coinbase, OKX, P2P, Nethermind, and other leading blockchain infrastructure providers
  • Global Distribution: Provers located across multiple continents and time zones
  • Hardware Diversity: Support for various computational requirements and proof systems
  • Redundancy: Multiple provers per operator to ensure high availability

EigenLayer Integration​

The network leverages EigenLayer's restaking infrastructure for economic security:

  • Restaked assets: Operators stake tokens to participate in the network
  • Delegation: Holders of the allowlisted tokens can delegate their stake to trusted operators
  • Rewards Distribution: Provers will eventually earn fees for successful proof generation

Operational Model​

Job Assignment Process​

  1. Availability Announcement: Provers announce their availability and capabilities to the Gateway
  2. Job Classification: The Dispatcher categorizes incoming jobs based on computational requirements
  3. DARA Selection: The Double Auction Resource Allocation mechanism selects optimal provers
  4. Proof Generation: Selected provers generate proofs and submit results
  5. Verification: Gateway verifies proof correctness before aggregation

Performance Monitoring​

  • Real-Time Metrics: Continuous monitoring of prover performance and availability
  • Quality Scoring: Track success rates and response times
  • Resource Utilization: Monitor CPU, memory, and network usage
  • Reputation System: Historical performance influences future job assignments

Fault Tolerance​

  • Automatic Failover: Jobs are reassigned if provers fail or timeout
  • Redundant Processing: Critical jobs can be assigned to multiple provers
  • Recovery Mechanisms: Provers can resume from intermediate states
  • Health Checks: Continuous monitoring of prover health and connectivity

Performance Optimization​

  • Parallelization: Run multiple prover instances on suitable hardware
  • Memory Management: Efficient memory allocation for large circuits
  • CPU Optimization: Utilize all available cores for proof generation
  • Storage: Fast SSD storage for intermediate proof data

Security Model​

Cryptographic Security​

  • Proof Verification: All proofs are cryptographically verified before acceptance
  • Secure Communication: TLS encryption for all network communications
  • Key Management: Secure handling of cryptographic keys
  • Audit Trails: Comprehensive logging of all operations

Operational Security​

  • Access Controls: Multi-factor authentication and role-based access
  • Network Security: Firewalls and intrusion detection systems
  • Monitoring: 24/7 security monitoring and incident response
  • Compliance: Adherence to industry security standards

Economic Security​

  • Staking Mechanism: Economic incentives for honest behavior
  • Reputation System: Long-term consequences for poor performance

Joining the Network​

Operator Requirements​

  • EigenLayer Registration: Must be registered as an EigenLayer operator
  • Minimum Stake: Maintain minimum required stake
  • Hardware Compliance: Meet minimum hardware specifications

Onboarding Process​

  1. EigenLayer Setup: Register as an operator on EigenLayer
  2. Operator Allowlisting: Get operator allowlisted by contacting Lagrange team
  3. Hardware Provisioning: Set up qualifying hardware infrastructure
  4. Network Registration: Register with Lagrange's prover network
  5. Software Installation: Install and configure prover
  6. Go Live: Run the prover to start accepting and processing proof jobs

Ongoing Operations​

  • Monitoring: Continuous monitoring of prover performance
  • Maintenance: Regular updates and hardware maintenance
  • Compliance: Adherence to network rules and requirements
  • Optimization: Continuous improvement of performance and efficiency