# Lumia

> Lumia is an Ethereum-compatible zkEVM layer-2 network designed to support real-world asset tokenization and lifecycle management

- Canonical URL: https://iq.wiki/wiki/lumia
- Categories: Projects & Protocols
- Tags: Ethereum, Layer2, Infrastructure, RWA
- Created: 2026-10-15T08:31:20.013Z
- Last updated: 2026-10-15T08:31:20.013Z
- Source: IQ.wiki — the world's largest blockchain and crypto encyclopedia (https://iq.wiki)

---

**Lumia** is a [blockchain](https://iq.wiki/wiki/blockchain) designed to support [real-world assets](https://iq.wiki/wiki/real-world-assets-rwas) (RWAs), including credit, real estate, commodities, and funds, across stages from issuance and distribution to settlement and trading.[\[1\]](#cite-id-oevcfymucx)​[\[2\]](#cite-id-0fdg7l26ir) It is a zero-knowledge Ethereum Virtual Machine ([zkEVM](https://iq.wiki/wiki/zkevm)) network built to run [Ethereum](https://iq.wiki/wiki/ethereum)-compatible applications alongside asset-specific services.[\[1\]](#cite-id-oevcfymucx)​[\[2\]](#cite-id-0fdg7l26ir)​

​

## Overview

In a June 24, 2025 announcement, [Avail](https://iq.wiki/wiki/avail-avail) said Lumia was using the Avail Stack, including Avail’s data-availability layer and [Nexus](https://iq.wiki/wiki/nexus), to develop infrastructure for [RWA](https://iq.wiki/wiki/real-world-assets-rwas) [tokenization](https://iq.wiki/wiki/tokenization). At that time, Avail reported that Lumia had tokenized more than $220 million in real estate, including two skyscrapers in Istanbul, and had a $1 billion framework agreement with Sen Group. The announcement also said Lumia had sold more than 25,000 HyperNodes and was working with issuers in private credit, U.S. Treasury bills, and real estate. Avail reported that Lumia forecast more than $1 billion in assets would be tokenized over the 12 months following the announcement, through June 2026; this was a forecast made in June 2025, not a reported completed total.[\[7\]](#cite-id-ydx6bnb43g)​

Lumia’s ecosystem backers have included Laser Digital, [DWF Labs](https://iq.wiki/wiki/dwf-labs), TRGC, [Binance](https://iq.wiki/wiki/binance), [Polygon](https://iq.wiki/wiki/polygon), and [Crypto.com](https://iq.wiki/wiki/cryptocom), among others, according to Lumia’s project account.[\[8\]](#cite-id-5j40srml4g)​

## Architecture

### Execution and Validity

Lumia is a [zkEVM](https://iq.wiki/wiki/zkevm) whose bytecode compatibility with [Ethereum](https://iq.wiki/wiki/ethereum) allows developers to deploy [Solidity](https://iq.wiki/wiki/solidity) [smart contracts](https://iq.wiki/wiki/smart-contract) and other general-purpose [Ethereum Virtual Machine (EVM)](https://iq.wiki/wiki/ethereum-virtual-machine-evm) applications.[\[1\]](#cite-id-oevcfymucx) Its state is secured through zero-knowledge validity proofs rather than an independent [validator](https://iq.wiki/wiki/validator) set. After transactions are executed, proof-generating systems called zkProvers produce proofs that batches followed EVM rules; a smart contract on Ethereum’s [layer 1](https://iq.wiki/wiki/layer-1) verifies those proofs. This design makes an invalid state transition impossible to prove valid.[\[1\]](#cite-id-oevcfymucx)​

Transaction ordering, execution proving, and data availability are handled as separate functions. A sequencer receives and orders transactions, then groups them into [layer 2](https://iq.wiki/wiki/layer-2) blocks. Block production is a single defined role rather than a validator-set voting process; correctness is checked separately through validity proofs. The arrangement supports fast, predictable ordering but makes transaction ordering and network liveness dependent on the sequencer remaining operational.[\[1\]](#cite-id-oevcfymucx)​

Lumia uses [Avail](https://iq.wiki/wiki/avail-avail) for data availability, placing transaction data on a dedicated network instead of publishing it in [Ethereum](https://iq.wiki/wiki/ethereum) calldata. Because execution proofs are verified on Ethereum while data availability is handled separately, the documentation classifies Lumia as a validium.[\[1\]](#cite-id-oevcfymucx)​

The announced Avail integration also described the use of [Avail](https://iq.wiki/wiki/avail-avail) light clients, which can sample data blocks and check them against KZG polynomial commitments. Avail said this design would let users verify data-availability guarantees from devices such as phones, browsers, and smartwatches, with a stated target of providing those guarantees to edge devices in under a minute.[\[7\]](#cite-id-ydx6bnb43g)​

### Development Networks and Interoperability

Lumia operates a [mainnet](https://iq.wiki/wiki/mainnet) and Lumia Beam, a public network for development and testing.[\[1\]](#cite-id-oevcfymucx)​

The Avail announcement described Lumia as preparing to interoperate across chains using Avail [Nexus](https://iq.wiki/wiki/nexus) for shared liquidity. [Avail](https://iq.wiki/wiki/avail-avail) characterized Nexus as supporting native connections among sovereign chains, cross-rollup messaging, trust-minimized infrastructure, and composable liquidity. The planned connections were intended to let Lumia assets, including assets routed through Lumia Stream, move across rollups and appchains.[\[7\]](#cite-id-ydx6bnb43g)​

### Network Upgrade and Operations

An article describing a Lumia [mainnet](https://iq.wiki/wiki/mainnet) upgrade reported [block](https://iq.wiki/wiki/block) times of roughly 300 milliseconds and finality of around 600 milliseconds. It said the network targeted sub-second execution and emphasized predictable end-to-end completion under uneven demand and infrastructure stress, rather than peak transactions per second.[\[9\]](#cite-id-owfrtqsogm)​

The article described Lumia’s execution layer as built on CDK-Erigon, a memory-efficient execution client intended to reduce hardware requirements and improve synchronization. It also described elastic [blocks](https://iq.wiki/wiki/block), which are produced and processed when there is activity, reducing unnecessary block production and idle computing. Other changes included transaction-processing improvements intended to reduce wasted allocation, improve transaction yielding, and address edge cases that could degrade [node](https://iq.wiki/wiki/node) performance.[\[9\]](#cite-id-owfrtqsogm)​

Reported upgrade changes included more resilient sequencer recovery and state-commit and unwind behavior; more accurate fee estimation and base-fee reporting; improved synchronization and correctness for layer-1-derived “info tree” data; and additional recovery stages for data-availability blobs. The upgrade also included safer remote procedure call (RPC) batching, clearer log-query errors, transaction-pool fixes for edge-case loops and improved prioritization, and more flexible flags and timing controls for [forks](https://iq.wiki/wiki/fork) and network configurations.[\[9\]](#cite-id-owfrtqsogm)​

The article also reported dependency and build-pipeline hardening, explicit remediation of known vulnerabilities identified by Common Vulnerabilities and Exposures (CVE), safer continuous integration and deployment practices, and more robust configuration and runtime modes. It said Lumia had applied SOC 2 security standards across its protocol and characterized this as the first integration of SOC 2-grade compliance standards throughout an [RWA](https://iq.wiki/wiki/real-world-assets-rwas) chain; these were claims made by the article.\[9]

## Asset Issuance and Compliance

Lumia’s base chain is permissionless: users can read its state, submit transactions, deploy contracts, and run [nodes](https://iq.wiki/wiki/node) without identity-based restrictions at the protocol layer.[\[1\]](#cite-id-oevcfymucx) Compliance requirements for regulated assets can instead be applied by the contracts chosen by issuers. Depending on the asset, those contracts may require know-your-customer checks for individual holders, know-your-business checks for institutional counterparties, transaction-level screening, or a combination of controls. These requirements apply to the relevant asset contracts rather than to the chain as a whole, allowing applications without such requirements to operate on the same base layer.[\[1\]](#cite-id-oevcfymucx)​

Avail described Lumia Stream as aggregating liquidity from [centralized](https://iq.wiki/wiki/cex-centralized-exchange) and [decentralized exchanges](https://iq.wiki/wiki/decentralized-exchange), market makers, and institutions. Avail’s announcement said Stream used [Polygon](https://iq.wiki/wiki/polygon) CDK-enabled [zkEVM](https://iq.wiki/wiki/zkevm) security and identity verification, and described Lumia’s services as spanning asset issuance and distribution.[\[7\]](#cite-id-ydx6bnb43g)​

## Tokenomics

LUMIA is Lumia’s native network token.[[1]](#cite-id-oevcfymucx) [CoinMarketCap](https://iq.wiki/wiki/coinmarketcap)’s overview describes it as a token for network [gas](https://iq.wiki/wiki/gas) fees, [staking](https://iq.wiki/wiki/staking), and governance.[[2]](#cite-id-0fdg7l26ir)

Lumia’s token documentation lists a total supply of 238,888,888 LUMIA following the ORN-to-LUMIA swap from 92,631,255 ORN, including 146,257,633 newly allocated tokens. Of that new supply, 73,439,930 LUMIA (50.21%) is allocated to [node](https://iq.wiki/wiki/node) rewards and vested over 20 years, while 72,817,703 LUMIA (49.79%) is allocated to ecosystem and community initiatives and vested over 10 years. The documentation allocates 0% of the new supply to the team. These are the token-documentation allocations and vesting schedules, not figures for current [circulating supply](https://iq.wiki/wiki/circulating-supply).[[10]](#cite-id-xewhnf43pn)

The CMC AI overview describes Lumia Power (LUMIAp) as a mechanism in which users lock LUMIA to receive EcoDrops, curated [airdrops](https://iq.wiki/wiki/airdrop) from projects launching in the Lumia ecosystem. It presents the arrangement as a way to connect community rewards with longer-term ecosystem participation rather than relying on inflationary token emissions.[[2]](#cite-id-0fdg7l26ir) The amount of LUMIAp depends on the amount of LUMIA locked and the lock duration; longer and larger locks receive more LUMIAp. Participation in EcoDrops requires at least a three-month lock, and campaigns may set additional eligibility conditions or participation steps. Shares are allocated according to eligible holders’ remaining LUMIAp power, and rewards are released linearly over three months.[[11]](#cite-id-t3d0a3time)

## Governance

Lumia Pulse is a platform for ecosystem access, participation, rewards, initiatives, and community voting.[\[8\]](#cite-id-5j40srml4g) Proposal LGP-01 passed on October 2, 2026, with 95% yes votes. It approved bringing forward approximately 18 years of remaining eligible HyperNode rewards for payment in USDT and established the Lumia Foundation Growth Initiative. The voting deadline was October 2, 2026, at 16:00 UTC.[\[12\]](#cite-id-99c6q6s91i)​[\[13\]](#cite-id-i9vi1nuaeo)​

In an October 1, 2026 update ahead of the LGP-01 deadline, Lumia said some HyperNode reward balances on Lumia Pulse could differ from those shown on the legacy platform.[\[14\]](#cite-id-gm25552oz3)​

## Security Reviews

The security firms [Hacken](https://iq.wiki/wiki/hacken) and Halborn have reviewed Lumia’s [Solidity](https://iq.wiki/wiki/solidity) token, [staking](https://iq.wiki/wiki/staking), governance, and migration contracts. Those reviews did not cover the chain’s protocol layer, including its sequencer, zkProvers, data-availability system, or bridge.[[1]](#cite-id-oevcfymucx)