Lumoz Docs
  • Introduction
    • Welcome to Lumoz
    • Understand Lumoz
      • Modular AI Computing Network
      • Nodes
    • Lumoz Chain
    • Bridge
  • Lumoz Decentralized AI
    • Overview
    • Architecture
    • Computational Resource Management
    • Use Cases
    • Chat with Lumoz Decentralized AI
      • Plan
  • AI Agents
    • Overview
    • How Lumoz TEE Works
    • The Core Architecture Design
    • Lumoz AI Agent Framework
  • Compute Node
    • Compute Node
      • Why Compute Node
      • How do Compute Nodes Work
      • Rewards
    • Setup Compute Node
  • Rollup as a Service
    • Overview
    • Lumoz RaaS Stack
    • Rollups Built with Lumoz
  • Verifier
    • Verifer Node Explained
      • Why Verifier Node
      • How do Verifier Node Work
      • License
      • Rewards
    • Purchase Verifier Node
      • Purchase License
        • Buyback Guarantee
      • License Tiers
      • Invitation
      • FAQ
    • Setup Verifier Node
      • Who can run a node?
      • Requirements
      • Setup Node
        • Node as a Service
        • Build your own
          • 1. Initialize a Node
          • 2. Run the Node
            • Run with CLI
            • Run with Docker(recommended for multiple nodes)
          • 3. Update Node Information(optional)
      • FAQ
      • Troubleshooting
    • Delegate Licenses
      • Claim License
      • Delegate Guide
      • Undelegate Guide
    • Staking
      • Staking Guide
      • Unstaking Guide
    • Node Tier
    • Time Cooldown
    • Risk Notice and Disclaimer of Lumoz Verifier Node Sale
  • Roadmap
  • Tokenomics
    • Utility
    • Allocation & Distributions
    • Redemption
  • Contracts
  • Technical Reference
    • Lumoz ZK-PoW
      • ZKP Two-Step Submission
    • Cross-Rollup Communication
      • Prerequisits and Compatibility
      • Process of Native Cross-Rollup Transactions
  • Glossary
  • Resources
Powered by GitBook
On this page
  • Motivation
  • Lumoz's Solution
  1. Technical Reference

Lumoz ZK-PoW

Motivation

Currently, there are multiple ZK-Rollups running on the Ethereum mainnet, including Polygon zkEVM and zkSync era. However, the majority of these ZK-Rollup projects have not implemented a decentralized prover. For example, in the beta mainnet of Polygon zkEVM, trusted aggregators are relied upon for submitting ZKPs, and zkSync era follows a similar approach.

While centralized provers are feasible when the number of ZK-Rollups is small, with the maturation of ZK scalability technologies, especially the gradual implementation of zkEVM in the next one to two years, the number of ZK-Rollups will experience significant growth. In the case of a massive number of ZK-Rollups, centralized provers will pose several problems:

  • Firstly, the cost of provers is high, and maintaining a centralized prover cluster requires specialized equipment and facilities. Not every ZK-Rollup operator has the capability to maintain such a centralized prover setup. Therefore, we need professional miners to fulfill the computing power demand of the future massive ZK-Rollup ecosystem.

  • Secondly, if there is only one prover, a single node failure could result in the inability to confirm transactions for the entire ZK-Rollup. We need a decentralized prover mechanism to encourage multiple miners to participate in the computation of a ZKP simultaneously and receive corresponding rewards.

  • Lastly, we require a standardized ZKP optimization algorithm to enhance overall hardware efficiency.

Lumoz's Solution

As a highly decentralized public blockchain, Ethereum has become congested, and gas fees have become extremely expensive. Many Web3 applications, especially financial derivatives, games, social networks, and others, want to migrate to layer 2 or other public chains.

Actually, providing a high-performance and low-gas execution environment alone is not difficult, as some centralized solutions can easily achieve this. The challenge lies in maintaining a high level of decentralization while ensuring high performance and low gas fees.

In Lumoz's design, each Web3 application can have its dedicated ZK-Rollup and the freedom to choose a base chain. Currently, Lumoz supports four base chains: Ethereum, Lumoz, BNB Chain, and Polygon. This means developers can choose to deploy their ZK-Rollup on any of these four public chains.

To support the demand for massive hardware resources resulting from a large number of ZK-Rollups, Lumoz also provides a unified ZKP computing power marketplace, encouraging miners to generate ZKPs for these ZK-Rollups.

PreviousTechnical ReferenceNextZKP Two-Step Submission

Last updated 1 year ago