Lumoz explained: ZK proving and verification DePIN with RaaS
Post1,747 words33 likes
Explains verifiable computation and Lumoz's combined rollup-as-a-service and ZK proof network, with zkProver and zkVerifier nodes secured via EigenLayer restaking. Frames the capped node licenses as the opportunity.
Key claims
Only 100,000 zkVerifier node licenses available
Network uses hybrid PoS and PoW consensus
Rollups live with Lumoz include ZKFair and Merlin
365 days from now, there will be 1000s of rollups.
The infra providers that enable this & lay the foundation for a rollup-centric future will be worth billions of $$$.
Meet @LumozOrg, a DePIN that serves as a modular computing layer specialized on efficient ZK proof services.
Alpha-🧵 on tech & my strategy (for today!).
➊ Why Does This Even Matter?!
Recent advances in zero knowledge proof systems and the hardware technology it requires have given rise to a new concept.
Verifiable computation.
The idea is to perform resource-intensive and expensive computation off-chain, while leveraging a succinct, cryptographic proof to verify the correctness of said off-chain computation on a decentralized base layer.
Sounds familiar?
It should.
This is how conceptually any ZK rollup operates.
Developing ZK rollups has historically been a difficult endeavour though, since the complexity that comes with developing ZK proof systems and circuits to prove certain computations is very high.
To make matters worse, the cost of generating ZK proofs has remained significant, which poses an additional problem for builders that ideally don't want to subsidize their network in production.
The modularization of the ZK stack aims to solve this problem.
With highly optimized proving networks and equally specialized ZK proof verification layers, the cost is reduced and the need to build these components proprietarily on a rollup-level is eliminated (abstracting complexity).
However, verifiable computation as a concept goes far beyond the (zk)EVM rollups you are already familiar with.
While proving general-purpose VM computation is cool, there is also huge potential to power more app-specific logic and enable new use cases that due to their compute requirements can't feasibly be run on-chain today.
Just think about AI. 🤖 ✨
Training a LLM or running inference are computationally very expensive. These AI/ML workloads can't be handled by most blockchains and require specialized hardware such as GPUs.
Relying on the concept of (ZK-powered) verifiable computation, these use cases finally become feasible. As long as there is a ZK proof that mathematically proves the correctness of the computational process that takes place off-chain, the trust assumptions are not impaired.
➋ WTF is ZK-Powered RaaS?
@LumozOrg is a leading innovator in the modular space that combines a rollup-as-a-service (RaaS) framework with a powerful and highly flexible computing platform designed for ZK proof services.
The team is building cutting-edge ZK infrastructure that consists of:
☞ Universal ZK Proving Layer
☞ Universal ZK Verification Layer
With this infra (powered by a DePIN), @LumozOrg aims to become the market leader in enabling all sorts of ZK rollups and delivering robust computational power to AI protocols.
But wait, WTF is RaaS exactly?
RaaS is the final abstraction layer on top of open-source rollup stacks and modular infrastructure components.
It matters because it fully abstracts all the complexity that was historically associated with building and maintaining decentralized networks.
How?
By allowing anyone to piece together the puzzle of modular building blocks within a fully customizable framework and through a no-code, dropdown-style Web UI.
To understand why this is needed amid the modular expansion, let's briefly revisit the simplified, high level tech architecture of a rollup:
☞ Sequencing layer:
The sequencer receives user transactions and orders them into a block that is later submitted to the L1 in compressed form and alongside a ZK proof that ensures validity. The sequencer provides pre-confirmations, a.k.a. a promise that a tx will later be included in a L1 block.
☞ Execution Layer:
That's where the transactions are processed and can either be a general-purpose environment such as a (zk)EVM or app-specific logic. Thanks to pre-confirmations (from the sequencer), the execution layer can execute transactions quickly without waiting for confirmation from the main chain.
☞ Proving Layer:
Every state update to the L2 is ZK proven and the resulting proof is subsequently verified to ensure that the txs included in a block are correct. The prover generates these ZK proofs, based on the tx data provided by the sequencer.
☞ Settlement (and Verification) Layer:
Responsible for the finalization of the rollup state transitions. In most cases, this is Ethereum L1. It verifies the data submitted by the rollup and updates the results to the main chain, ensuring the security and mathematically proven accuracy (through the ZK proof verification).
☞ ZK Proof Verification Layer
As hinted at before, specialized proof verification layers that work as a complement to Ethereum L1 can significantly improve efficiency. If this is a specialized network (as it the case with @LumozOrg), it warrants to be mentioned as its own layer.
☞ Consensus Layer:
Ensures consensus on the status of each transaction, ensuring the legitimacy and security of transactions. It usually adopts efficient consensus algorithms such as Proof of Stake (Ethereum).
☞ Data Availability Layer:
Records all transaction data that occurs on the rollup and provides full data when updating asset status in the settlement layer. For a "true" rollup, this is also Ethereum L1, however many rollups have pivoted to using off-chain DA solutions, including modular DA layers like @CelestiaOrg, @AvailProject.
@LumozOrg with its RaaS framework provides a solution that integrates all sorts of modular building blocks across all these layers of the stack, enabling builders to fully customize the configuration of their modular rollups.
More specifically, this means that builders can build with:
☞ Rollup Stacks / SDKs:
@0xPolygon, @Starknet, @LineaBuild, @BuildWithScroll and @zksync
☞ Shared Sequencers:
@EspressoSys and @radius_xyz
☞ Settlement Layers:
Ethereum, Bitcoin, @solana, @0xPolygon and @BNBCHAIN
☞ DA Layers:
Ethereum, @CelestiaOrg and @AvailProject
That's not even everything, there is much more across Oracle services, APIs, bridges, nodes-as-a-service, etc.
Additionally, the proving & verification layers are proprietary infrastructure that @LumozOrg provides out-of-the-box. We will have a closer look at this in the next chapter.
Rollups that already deployed on mainnet with @LumozOrg include @ZKFCommunity and @MerlinLayer2.
➌ How Does This Even Work?!
The @LumozOrg network (a.k.a. computational layer) operates as a blockchain network, employing a hybrid consensus mechanism of Proof of Stake (PoS) and Proof of Work (PoW).
Comprised of thousands of GPUs/CPUs, @LumozOrg's network of nodes ensures not only the continuous computational capacity to power ZK proof generation (and verification), but also supports large-scale parallel computing required by AI, guaranteeing the efficient execution of computational tasks.
By integrating these powerful computing resources with @eigencloud's restaking mechanism, @LumozOrg has created an efficient and highly secure computing-as-a-service system.
The @LumozOrg Actively Validated Service (AVS) Oracle is responsible for retrieving and storing data from EVM-compatible chains, ensuring high data availability and integrity, thus providing a solid data foundation for the computational layer, a.k.a. the Lumoz chain.
The @LumozOrg chain serves as the coordination/management layer of the entire computate network, responsible for task scheduling, reward distribution, and the management of zkProver & zkVerifier nodes, including but not limited to the processes of node addition and removal.
☞ zkProver: Nodes that perform specific computational tasks.
☞ zkVerifier: Verification nodes that verify ZKPs from the zkProver.
These nodes power the above-mentioned ZK infra components:
☞ Universal ZK Proving Layer
☞ Universal ZK Verification Layer
Thanks to its modular design and by separating the different functions into different node types, @LumozOrg has managed to significantly reduce the barriers of entry & cost to participate in zero knowledge computing.
This opens the door for a wide range of users to engage with these cutting-edge computing technologies on an infra level.
Users can join the network as zkProver or zkVerifier nodes, with the latter having significantly lower hardware requirements.
➍ Your Opportunity to Be Early (+ Airdrops)!!!
Node operation has turned into a very attractive business opportunity.
Running nodes for rewards in PoS or PoW mechanisms can yield significant rewards.
Unsurprisingly, the demand to run nodes, especially on high-profile infra layers like @LumozOrg's ZK compute network, is huge.
Hence, node ownership on @LumozOrg is bound by a node license, with only 100,000 (zkVerifier nodes) available. If you don’t want to run the node yourself, you can also delegate your license to someone that does.
Node licenses have been selling very fast on their website in a tiered system that goes up in price.
What adds to the FOMO here, is that these nodes do not only give you access to block rewards on the @LumozOrg chain, but you also qualify for a $MOZ allocation in the form of Lumoz points before TGE and after TGE, the zkVerifier nodes will earn 25% of supply as rewards. On top of that, there might be ecosystem airdrops incoming too!
Node Tiers 1-6/10 are already sold out with the Tier 7 sale currently in progress.
However, 3,500 Tier 4 licenses are reserved for @FjordFoundry and can be purchased from July 28th - August 1st, 1600 UTC (TODAY!!!) at a fixed price of $304.
The $MOZ token will be the native asset of the @LumozOrg chain and play a crucial role in several key areas of the overall network:
☞ Transaction Fees: Transactions require $MOZ tokens as gas fees.
☞ Service Payments: Using $MOZ for resource usage fees.
☞ Reward Incentives: $esMOZ* is issues as a reward for nodes providing computational power, security, and stability.
* ) can be exchanged for $MOZ tokens at a 1:1 ratio.
➎ Conclusion
@LumozOrg is building essential infrastructure that will power the most promising use cases of the cycle.
Getting exposure on a node operator level could be a very attractive play.
Why?
Well anon, do the maths.
You buy a node license.
This license will always be valuable, as long as node operators can generate reward-based income on @LumozOrg.
With the high and ever-increasing demand for robust ZK infra arising from an exploding rollup ecosystem and an AI industry in hyper-growth, this will likely be the case for the forseeable future.
However, the license is not all you get. 👇
With a $MOZ token allocation (points + rewards) on top and potential ecosystem airdrops down the line, this could literally be a goldmine.
Not mentioning the validator rewards that you will accrue indefinitely.
🧠 NFA but definitely worth to DYOR anon.
3 more images on X