Quarters 1 through 40
Quarters 40 through 80
| Quarter | Node Emissions | Community Emissions | Total Emissions |
|---|---|---|---|
| 1 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 2 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 3 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 4 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 5 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 6 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 7 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 8 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 9 | 2,295,000.00 | 1,819,000.00 | 4,114,000.00 |
| 10 | 2,295,000.00 | 1,819,000.00 | 4,114,000.00 |
| 11 | 2,295,000.00 | 1,819,000.00 | 4,114,000.00 |
| 12 | 2,295,000.00 | 1,818,995.00 | 4,113,995.00 |
| 13 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 14 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 15 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 16 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 17 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 18 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 19 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 20 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 21 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 22 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 23 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 24 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 25 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 26 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 27 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 28 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 29 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 30 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 31 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 32 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 33 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 34 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 35 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 36 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 37 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 38 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 39 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 40 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 41 | 8,964.84 | 0 | 8,964.84 |
| 42 | 8,964.84 | 0 | 8,964.84 |
| 43 | 8,964.84 | 0 | 8,964.84 |
| 44 | 8,964.84 | 0 | 8,964.84 |
| 45 | 4,482.42 | 0 | 4,482.42 |
| 46 | 4,482.42 | 0 | 4,482.42 |
| 47 | 4,482.42 | 0 | 4,482.42 |
| 48 | 4,482.42 | 0 | 4,482.42 |
| 49 | 2,241.21 | 0 | 2,241.21 |
| 50 | 2,241.21 | 0 | 2,241.21 |
| 51 | 2,241.21 | 0 | 2,241.21 |
| 52 | 2,241.21 | 0 | 2,241.21 |
| 53 | 1,120.61 | 0 | 1,120.61 |
| 54 | 1,120.61 | 0 | 1,120.61 |
| 55 | 1,120.61 | 0 | 1,120.61 |
| 56 | 1,120.61 | 0 | 1,120.61 |
| 57 | 560.30 | 0 | 560.30 |
| 58 | 560.30 | 0 | 560.30 |
| 59 | 560.30 | 0 | 560.30 |
| 60 | 560.30 | 0 | 560.30 |
| 61 | 280.15 | 0 | 280.15 |
| 62 | 280.15 | 0 | 280.15 |
| 63 | 280.15 | 0 | 280.15 |
| 64 | 280.15 | 0 | 280.15 |
| 65 | 140.07 | 0 | 140.07 |
| 66 | 140.07 | 0 | 140.07 |
| 67 | 140.07 | 0 | 140.07 |
| 68 | 140.07 | 0 | 140.07 |
| 69 | 70.04 | 0 | 70.04 |
| 70 | 70.04 | 0 | 70.04 |
| 71 | 70.04 | 0 | 70.04 |
| 72 | 70.04 | 0 | 70.04 |
| 73 | 35.02 | 0 | 35.02 |
| 74 | 35.02 | 0 | 35.02 |
| 75 | 35.02 | 0 | 35.02 |
| 76 | 35.02 | 0 | 35.02 |
| 77 | 17.51 | 0 | 17.51 |
| 78 | 17.51 | 0 | 17.51 |
| 79 | 17.51 | 0 | 17.51 |
| 80 | 17.56 | 0 | 17.56 |
)
2. **Click "Connect wallet"**
)
3. **Click "BNB Chain" or "Ethereum"**
)
4. **Click "MetaMask"**
)
5. **Click "Max" to take your entire wallet balance**
)
6. **Click "Allow to use ORN" to approve contract usage**
)
7. **Click "Swap"**
)
The guide covered the necessary steps to swap ORN to LUMIA on the Lumia platform, including connecting your wallet, selecting the BNB Chain, confirming the amount, authorizing the use of ORN, and executing the swap
The guide covered how to swap tokens from ORN to LUMIA using Blockchain via ETH and BSC networks. For a technical flow, see below.
# Token Swap Guide (SmartContract)
## [Token swap via SmartContract (Explorer).](https://app.guidde.com/playbooks/qm2NW6TA2HffSa2a79iHE9)
{% embed url="第 1 至第 40 季度
第 40 至 80 季度
| 季度 | 节点释放 | 社区释放 | 总释放量 |
|---|---|---|---|
| 1 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 2 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 3 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 4 | 9,180,000.00 | 2,730,664.00 | 11,910,664.00 |
| 5 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 6 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 7 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 8 | 4,590,000.00 | 1,820,443.00 | 6,410,443.00 |
| 9 | 2,295,000.00 | 1,819,000.00 | 4,114,000.00 |
| 10 | 2,295,000.00 | 1,819,000.00 | 4,114,000.00 |
| 11 | 2,295,000.00 | 1,819,000.00 | 4,114,000.00 |
| 12 | 2,295,000.00 | 1,818,995.00 | 4,113,995.00 |
| 13 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 14 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 15 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 16 | 1,147,500.00 | 1,786,904.00 | 2,934,404.00 |
| 17 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 18 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 19 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 20 | 573,750.00 | 1,754,809.00 | 2,328,559.00 |
| 21 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 22 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 23 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 24 | 286,875.00 | 1,722,713.00 | 2,009,588.00 |
| 25 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 26 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 27 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 28 | 143,437.50 | 1,690,617.00 | 1,834,054.50 |
| 29 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 30 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 31 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 32 | 71,718.75 | 1,658,521.00 | 1,730,239.75 |
| 33 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 34 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 35 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 36 | 35,859.38 | 1,626,426.00 | 1,662,285.38 |
| 37 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 38 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 39 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 40 | 17,929.68 | 1,594,330.00 | 1,612,259.68 |
| 41 | 8,964.84 | 0 | 8,964.84 |
| 42 | 8,964.84 | 0 | 8,964.84 |
| 43 | 8,964.84 | 0 | 8,964.84 |
| 44 | 8,964.84 | 0 | 8,964.84 |
| 45 | 4,482.42 | 0 | 4,482.42 |
| 46 | 4,482.42 | 0 | 4,482.42 |
| 47 | 4,482.42 | 0 | 4,482.42 |
| 48 | 4,482.42 | 0 | 4,482.42 |
| 49 | 2,241.21 | 0 | 2,241.21 |
| 50 | 2,241.21 | 0 | 2,241.21 |
| 51 | 2,241.21 | 0 | 2,241.21 |
| 52 | 2,241.21 | 0 | 2,241.21 |
| 53 | 1,120.61 | 0 | 1,120.61 |
| 54 | 1,120.61 | 0 | 1,120.61 |
| 55 | 1,120.61 | 0 | 1,120.61 |
| 56 | 1,120.61 | 0 | 1,120.61 |
| 57 | 560.30 | 0 | 560.30 |
| 58 | 560.30 | 0 | 560.30 |
| 59 | 560.30 | 0 | 560.30 |
| 60 | 560.30 | 0 | 560.30 |
| 61 | 280.15 | 0 | 280.15 |
| 62 | 280.15 | 0 | 280.15 |
| 63 | 280.15 | 0 | 280.15 |
| 64 | 280.15 | 0 | 280.15 |
| 65 | 140.07 | 0 | 140.07 |
| 66 | 140.07 | 0 | 140.07 |
| 67 | 140.07 | 0 | 140.07 |
| 68 | 140.07 | 0 | 140.07 |
| 69 | 70.04 | 0 | 70.04 |
| 70 | 70.04 | 0 | 70.04 |
| 71 | 70.04 | 0 | 70.04 |
| 72 | 70.04 | 0 | 70.04 |
| 73 | 35.02 | 0 | 35.02 |
| 74 | 35.02 | 0 | 35.02 |
| 75 | 35.02 | 0 | 35.02 |
| 76 | 35.02 | 0 | 35.02 |
| 77 | 17.51 | 0 | 17.51 |
| 78 | 17.51 | 0 | 17.51 |
| 79 | 17.51 | 0 | 17.51 |
| 80 | 17.56 | 0 | 17.56 |
High level data flow in enhanced DAC
High Level: A type of validity proof that makes it simple for even a light client to independently generate their own mathematically verified data availability guarantees.
Analogy: A KZG commitment scheme is essentially a cryptographic envelope. When a sheet full of data is inserted into the envelope and sealed, a unique serial number is created and placed on top—we call this committing to the value. Once sealed, the data cannot be changed or tampered with but anyone can verify its existence by scanning the signature. If the data is changed, the digital signature changes and the previous signature is no longer valid.
| | [Data Availability Sampling](https://docs.availproject.org/docs/faqs#what-is-data-availability-sampling-das) | Data availability sampling is a method used by light clients to confirm the availability of data without downloading complete blocks, allowing them to verify with 99.99% certainty that all data in a block is available by sampling just \~1% of it. Through this method, light clients engage in several rounds of random sampling for small chunks of block data. With each successful round, confidence that the data is available grows. When the light client achieves a set confidence threshold, they recognize the block data as accessible. | | [Light Client](https://docs.availproject.org/docs/operate-a-node/run-a-light-client/Overview) | The Avail light client is a node that lets users access blockchains by downloading the bare minimum amount of data required to verify its existence. It plays a vital role in ensuring the availability and correctness of data within the Avail network. Avail LCs are suitable for low-resource environments like phones and smartwatches and offer roughly comparable security to full nodes. As the number of light clients grows and more data availability sampling (DAS) occurs, the coverage offered by the light client network expands, eventually becoming large enough to collectively sample larger blocks. Unlike monolithic blockchain designs which reduce the amount of blockspace available as demand increases, Avail’s LCs can help scale blockspace with demand, future-proofing appchains and rollups. | | [Consensus Mechanism](https://docs.availproject.org/docs/learn-about-avail/consensus) | Avail uses a hybrid consensus model based on Polkadot’s BABE and GRANDPA that produces high finality and liveness. This model equips Avail with network resilience and enables it to withstand temporary network partitions and a substantial number of node failures. | | [GRANDPA](https://docs.availproject.org/docs/learn-about-avail/consensus/grandpa) | GRANDPA functions as the finality gadget, ensuring transaction accuracy and security, and enables the simultaneous finalization of multiple blocks. GRANDPA validators vote on a block that they consider best and their votes are applied transitively to all previous blocks. After two-thirds of the GRANDPA authorities have voted for a particular block, it is considered final, greatly speeding up the finalization process, even after long-term network partitioning or other networking failures. As soon as more than 2/3 of validators attest to a chain containing a certain block, all blocks leading up to that one are finalized at once. | | [BABE](https://docs.availproject.org/docs/learn-about-avail/consensus/babe#introduction) | BABE serves as the block production engine, prioritizing quick transaction processing (liveness) by coordinating with validator nodes to identify new block producers. BABE assigns block production slots to validators according to stake and using a randomness cycle. BABE execution happens in sequential non-overlapping phases known as epochs. Each epoch is divided into a predefined number of slots. During each slot, only some of the validators can produce a block. Validators are selected based on a verifiable random function (VRF). | # Benefits of AvailDA | **Cost Efficient** | Securely transition data availability off-chain, significantly cutting costs, and boosting L2 scalability and efficiency. | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Improved UX** | Shifting data availability off-chain alleviates the burden on the Ethereum mainnet, leading to expedited transaction confirmation and reduced gas fees for users. | | **Scalability** | Designed to scale as user activity increases, allowing higher throughput without sacrificing performance or reliability. | | **Reliable** | Cutting-edge solution for encoding, committing to, and verifying the availability of data, ensuring that it remains accessible and reliable even in the face of node failures, network disruptions, or malicious actors. | | **Versatility** | Turn-key data availability base layer equipped with SDKs, an attestation bridge, and data availability guarantees from peer-to-peer light clients designed for ZK and Optimistic rollups, all built by a proven team. | # Lumia DA - Lightclient Nodes Lumia Chains Approach to Data Availability: DA Lightclients Lumia chain, being a state-of-the-art Layer 2 scaling solution, recognizes the importance of data availability and has developed its own approach to ensure the integrity and accessibility of transaction data while maintaining high level of decentralization. Lumia chain builds on the concept of lightclients introduced by the AvailDA team and brings forth innovation by allowing Node Sale Participants to stake their NFT licenses to run, verify and earn LUMIA via its bespoke Lightclient implementation. Lumia currently is actively developing the lightclient solution and development discussions as well as PRs can be viewed [here](https://github.com/availproject/avail-light/pull/764). ### DA Nodes and Node Licenses To become a DA (lightclient) node operator, participants must acquire a "node license" in the form of a non-fungible token (NFT). These node licenses grant the holders the right to operate a DA node and earn rewards in the form of LUMIA tokens for their services. Lumia chain with its goal to reach "***stage 2***" in mind will promote decentralization and community participation. Lumia chain allows "node sale" participants who have purchased a node license NFT to run their own lightclient nodes. By running their node, participants can earn a portion of the LUMIA rewards allocated to the DA nodes cluster. ### Technical Details of DA Nodes The DA nodes in Lumia operates as follows: 1. **Data Storage**: When a transaction is processed on the Lumia network, the transaction data is distributed across the DA nodes on AvailDA. Each DA node stores a portion of the data, ensuring that the data is replicated and readily available. 2. **Data Retrieval**: When a participant needs to access the transaction data for validation or other purposes, they can request the data from the DA nodes. The DA nodes work together to serve the requested data promptly. 3. **Data Integrity**: To ensure the integrity of the stored data, Lumia chain employs cryptographic techniques such as erasure coding and Merkle proofs. These techniques allow for the detection of any data corruption or tampering attempts. 4. **Reward Distribution**: The LUMIA rewards allocated to the DA nodes are distributed among the node operators based on their contribution and uptime. 5. **Scalability and Resilience**: The DA nodes is designed to scale horizontally, allowing for the addition of more nodes as the network grows. This scalability ensures that the data availability remains high even as the transaction volume increases. Additionally, the distributed nature of the cluster provides resilience against node failures or malicious actors. ### Pros and Cons of Lumia chains DA Approach vs. EigenDA When compared to other data availability solutions like EigenDA, Lumia chains DA approach has its own set of advantages and disadvantages: #### Pros: * **Community Participation**: Lumia chains DA approach allows for greater community participation through the node license NFT system. This promotes decentralization and incentivizes participants to actively contribute to the network's security and performance. * **Trusted Partners**: By partnering with trusted entities to serve as the initial DA nodes, Lumia chain ensures a high level of reliability and stability in the early stages of the network's development. * **Reward Distribution**: The DA approach enables a fair distribution of rewards among node operators and node license NFT holders, creating a more inclusive and attractive ecosystem for participants. * **Redundancy and Disaster Recovery:** Lumia chain will operate both AvailDA as decentralized DA layer but at the same time it will operate centralize DAC. In the event of recovery or disaster chain will switchover from one or the other to serve data and assure chain is operational at all times. #### Cons: * **Complexity**: Lumia chains DA approach introduces additional complexity compared to solutions like EigenDA. Managing the DA nodes cluster, node licenses, and reward distribution requires careful design and implementation. Lumia collaborates with Polygon and GatewayFM to streamline DAC implementation and management. ### Conclusion Lumia chains approach to data availability represents a unique and innovative solution that prioritizes community participation, decentralization, and reward distribution. While it may introduce some complexities compared to other solutions like EigenDA, the approach offers distinct advantages in terms of inclusivity and incentivization as well as promotion of true decentralization. As Lumia chain continues to refine and optimize its DA nodes, it has the potential to establish itself as a leading example of how data availability can be achieved in a decentralized and community-driven manner. Lumia is currently working on lightclients adjustments to ensure we can run on smartphones as we aim to optimize and decentralize every aspect of the chain. # Lumia Stream ## Welcome to Lumia Stream: Powering the Future of DeFi #### The Challenge of Spread-Out Liquidity In the world of blockchain, we're moving fast into a future with many chains - like L1 and L2 technologies. This is great for growth, but it makes liquidity spread thin across different chains and exchanges. Often, projects struggle to keep or attract this essential liquidity, making it hard for good ideas to take off because they can't get the financial backing they need. ### How Lumia Changes the Game Lumia Stream steps in as a game-changer. It’s natively built on Lumia L2 and on the main EVM blockchains, it's easy to integrate via guided SDKs to help developers focus on making their projects unique and engaging without worrying about attracting liquidity. Here's how: **Easy Access to Liquidity** Lumia Stream aggregate both centralized (CEXs) and decentralized exchanges (DEXs) to bring together the liquidity of the entire crypto market. This means developers can start their projects with the liquidity resources they need right from the start, whether they need Spot or Perpetuals liquidity. **MEV Protection** All trades using decentralized CEX liquidity will be protected from MEV and frontrunning, being decentralized p2p agreements between the trader and Lumia Stream's Liquidity Nodes. **Atomic Swap Bridge** Lumia Stream has built a bridge with Atomic Swaps with Hashed Time Lock Contracts (HTLCs), to allow trustless cross chain bridging of native assets. The cryptographic technology behind this bridge allow Lumia Stream to perform permissionless cross chain swaps without the risks of mint and burn mechanisms and without the need to rely on a multisig. **Transmuted AMM Price Curves and Virtual Order Books** Lumia Stream has included in its SDK the possibility for developers to create a virtual order book showing paths between multiple exchanges (DEXs and CEXs) and Transmuted AMM Price Curves, which allows the Virtual Order Book to show pools from AMMs of any kind as quotes on an order book. To learn more, read the Lumia Stream documentation at this link {% content-ref url="/spaces/23sOcZDOT0EJuHpwQzoU" %} [Lumia Stream](https://lumia.gitbook.io/lumia-stream/) {% endcontent-ref %} ### # Node Owned Liquidity ## Introduction Node Owned Liquidity is a pivotal concept in the Lumia ecosystem, particularly for the Lumia L2 DAC (Data Availability Committee) nodes. Unlike regular validator nodes which receive their rewards gradually over time, DAC nodes are granted these rewards from the beginning. This strategic allocation allows for immediate liquidity, which is essential for facilitating large trades on Lumia Stream. ## How It Works DAC nodes, which validate Lumia L2, receive their rewards in LUMIA tokens upfront. These rewards are subject to a vesting schedule, but the liquidity is available immediately for use on Lumia Stream. This system is designed to handle significant trade volumes efficiently. Here's a detailed explanation of the process: 1. **Trade Initiation**: * A trader on Lumia Stream intends to perform a trade to acquire XYZ tokens. * The available liquidity within the Liquidity Nodes on Lumia Stream is insufficient to facilitate the trade. 2. **Utilizing Node Owned Liquidity**: * In this scenario, the Liquidity Node will utilize the LUMIA tokens owned by DAC nodes. * These tokens are posted as collateral in a strongly overcollateralized position within the XYZ/LUMIA lending pool. * The Liquidity Node borrows XYZ tokens using the posted LUMIA tokens as collateral. 3. **Execution and Settlement**: * The borrowed XYZ tokens are sent to the Lumia Stream trader to complete the trade. * Subsequently, the Liquidity Node hedges the order, rebalances its portfolio, and repays the loan. * This entire process is carried out while maintaining a delta-neutral position for Liquidity Nodes and DAC Nodes. #### Benefits 1. **Instant Liquidity**: * DAC node delegators provide LUMIA tokens that are otherwise idle, enabling immediate liquidity for large trades. * This ensures that even trades worth millions of dollars can be settled instantly on Lumia Stream, with 1:1 CEX pricing. 2. **Real Yield for DAC Nodes**: * By leveraging Node Owned Liquidity, DAC nodes generate real yield. * This adds a significant value proposition for delegators who stake their LUMIA tokens with DAC nodes. 3. **Increased Capital Efficiency**: * Using node rewards liquidity to facilitate trades takes validator node capital efficiency to unprecedented heights. * The entire amount of delegated LUMIA, which is in the tens of millions, counts towards the TVL of Lumia Stream. #### Conclusion Node Owned Liquidity is a sophisticated mechanism that enhances the liquidity, efficiency, and security of the Lumia ecosystem. By leveraging the immediate availability of LUMIA tokens from DAC nodes, Lumia Stream can facilitate large trades seamlessly, providing real yield to DAC Nodes and boosting the platform's TVL. This innovative approach underscores the strategic advantage of DAC nodes within the Lumia network and their critical role in driving the ecosystem's growth and stability. # Liquidity Restaking Lumia Stream is developing innovative forms of yields for Liquidity Nodes and Liquidity Restakers, increasing capital efficiency to a scale never seen before in DeFi. More details TBA soon. # Lumia Passport ### Introduction to Lumia Passport Lumia Passport is your blockchain identity with infinite dencentralized possibilites. In essence, it is an Account Abstraction (AA) wallet that replaces traditional private key wallets with smart contracts. AA makes your crypto experience more secure, user-friendly and enabling features like social recovery, multi-factor authentication, bundled transactions, and spending limits. All of this is now handled by custom logic instead of just a single private key. At the core of Lumia Passport are both decentralized identity and account abstraction solution. It is based on the ERC-4337 account abstraction and Sumsub KYC and identity verification. While ERC-4337 standardized AA on Ethereum, allowing wallets to act like bank accounts with flexible rules, Sumsub handles the core KYC/AML compliance and issues verifiable attestations on-chain. Lumia Passport represents a paradigm shift in how users interact with blockchain applications, removing the complexity of traditional wallet management while maintaining the security and decentralization principles that define Web3. ### What is in Lumia Passport? Lumia Passport is a multi-layered identity and account management system that combines: 1. **ERC-4337 Smart Accounts**: Programmable wallet accounts that enable gasless transactions, batch operations, and custom authorization logic 2. **Sumsub Integration**: A combination of ZKPs for secure verification, document checks, biometrics, and transaction monitoring, aiming to balance user privacy with strict regulatory needs. 3. **Reusable Identity**: A single, portable identity that works across all dApps and services within the Lumia ecosystem 4. **Selective Disclosure**: Users control exactly what information they share with different applications. The Passport serves as both a Smart Account wallet and a verified credential container, allowing users to seamlessly interact with decentralized applications while maintaining complete control over their personal data. ### Core Components #### ERC-4337 Smart Account Architecture Lumia Passport leverages the ERC-4337 standard to transform traditional externally owned accounts (EOAs) into programmable smart contract accounts. This architecture provides several key advantages: **UserOperation Objects** Instead of traditional transactions signed by private keys, Lumia Passport uses UserOperations—pseudo-transaction objects that represent user intent. A UserOperation contains: * **sender**: The smart account address initiating the operation * **nonce**: Sequential number preventing replay attacks * **initCode**: Bytecode for deploying the account if it doesn't exist * **callData**: The actual function call and parameters to execute * **callGasLimit**: Maximum gas for the main execution * **verificationGasLimit**: Maximum gas for signature verification * **preVerificationGas**: Gas compensation for bundler operations * **maxFeePerGas**: Maximum total gas price willing to pay * **maxPriorityFeePerGas**: Maximum priority fee for miners * **paymasterAndData**: Information about third-party gas sponsorship * **signature**: Cryptographic proof authorizing the operation **Entry Point Contract** The Entry Point contract is the singleton smart contract that orchestrates all ERC-4337 operations on Lumia chain. It: * Validates UserOperations before execution * Manages the execution flow and gas accounting * Coordinates with Paymasters for gas sponsorship * Ensures security through standardized validation * Handles batch execution of multiple operations Lumia chain utilizes a deployed Entry Point contract compatible with the ERC-4337 v0.6 specification, ensuring broad compatibility with the account abstraction ecosystem. **Smart Account Contract** Each Lumia Passport is implemented as an ERC-4337-compliant smart contract that: * Stores all user assets (tokens, NFTs, etc.) * Implements custom validation logic before transaction execution * Supports multiple signers and authorization schemes * Enables modular functionality through plugins * Maintains upgrade paths while preserving security The Smart Account is signer-agnostic, meaning users can authenticate using various methods including traditional private keys, multi-signature schemes, hardware wallets, biometrics, or passkeys. #### Sumsub Integration Comprehensive Identity Verification Lumia Passport leverages Sumsub, a full-cycle verification platform that orchestrates the entire user lifecycle. Sumsub enables secure and compliant identity verification, allowing users to meet regulatory standards while ensuring their digital identity remains portable and secure. Advanced Verification & Fraud Prevention At the core of Sumsub is a robust compliance engine that validates user credentials with high accuracy and liveness detection. This technology allows for: * Non-Doc Verification: Verify identity using banking or database records without uploading physical documents * Liveness and Biometrics: Prove you are a real human presence to prevent bot attacks and fraud * Behavioral Intelligence: Analyze user patterns to detect suspicious activity without compromising sensitive data Lumia chain integrates Sumsub's verification orchestration to support this functionality, ensuring that sensitive user information is processed securely while meeting strict global compliance requirements. Credential Issuance and On-Chain Attestations Lumia Passport credentials are issued through Sumsub's trusted verification flow. The integration supports: * Global Coverage: Verification capabilities across 220+ countries and territories * Multi-Level Checks: From basic liveness to advanced AML screening These credentials support: * Personal information verification (name, address, date of birth) * Government-issued IDs and proof of address validation * Accreditation status for qualified investors * Continuous monitoring for AML risks Once verified, the status can be anchored on-chain as a verifiable attestation or Soulbound Token (SBT), ensuring immutability and allowing dApps to check status without re-verifying data. Reusable Identity Mechanism The Sumsub-integrated Passport implements a reusable identity protocol that allows users to verify once and share their status across multiple dApps. This is achieved through: * Unified Profile: A single verification flow creates a portable identity * Privacy-Preserving Checks: dApps verify the "Verified" status rather than raw data * Cross-Service Portability: Seamless onboarding to new services within the ecosystem * Fine-grained access control mechanisms Users can choose when to present their verified status to each dApp, maintaining privacy while enabling necessary regulatory verifications. ### Key Features and Benefits #### Simplified User Onboarding Lumia Passport eliminates the complexity of traditional blockchain onboarding: * **No Seed Phrases**: Users don't need to memorize or secure 12-24 word recovery phrases * **Social Recovery**: Authorize trusted friends, family, or devices to help recover accounts * **Web2-Style Login**: Authenticate using familiar methods like email, social accounts, or biometrics * **Instant Account Creation**: Smart accounts are deployed on-demand when first needed #### Gasless Transactions Through Paymaster integration, Lumia Passport enables truly gasless experiences: * **Sponsored Transactions**: Protocol or application pays gas fees on behalf of users * **ERC-20 Gas Payment**: Pay transaction fees using any supported token (USDC, LUMIA, etc.) * **Flexible Fee Models**: Developers can implement custom fee structures * **No Native Token Required**: Users don't need to hold LUMIA tokens to interact with dApps The Paymaster acts as a gas tank, covering transaction costs and enabling seamless onboarding for Web2 users unfamiliar with blockchain economics. #### Enhanced Security Features Lumia Passport provides multiple layers of security: **Session Keys** Create temporary authorization keys with limited permissions and time bounds. For example: * Allow a gaming dApp to execute trades up to 100 LUMIA for 24 hours * Grant a DeFi protocol permission to interact with specific smart contracts * Revoke access instantly if a device is compromised **Multi-Chain Validation** Validate transactions across multiple blockchains before execution, enabling: * Cross-chain transaction coordination * Unified security policies across chains * Protection against replay attacks on different networks **Passkey Support** Leverage device-native biometric authentication: * Face ID or Touch ID on mobile devices * Windows Hello on desktop * Hardware security keys for maximum protection **Transaction Limits** Configure spending limits to prevent account drainage: * Set maximum transferable value per transaction * Define daily or weekly spending caps * Implement time-locked large transactions **Whitelists** Create lists of trusted addresses: * Only allow transfers to pre-approved addresses * Prevent phishing attacks and malicious transactions * Add friction to unusual transaction patterns #### Flexible Authorization Lumia Passport is completely signer-agnostic, supporting: * **Traditional Private Keys**: Standard ECDSA signatures * **Multi-Signature**: Require multiple approvals for transactions * **Social Recovery**: Designated guardians can help restore access * **Hardware Wallets**: Ledger, Trezor integration * **Biometric Authentication**: Fingerprint, facial recognition * **Passkeys**: WebAuthn-based authentication * **Future Quantum-Proof**: Ready for post-quantum cryptography Users can mix and match authentication methods and change them over time without affecting their account address or assets. #### Cross-Chain Compatibility Lumia Passport works seamlessly across multiple blockchains: * Native support for all EVM-compatible chains * Integration with Polygon AggLayer for unified liquidity * Cross-chain account abstraction through Particle Network * Atomic operations spanning multiple chains Users maintain a single Passport identity while interacting with dApps deployed on different chains, with all bridging and interoperability handled automatically in the background. ### Compliance and Regulatory Features #### KYC/AML Integration Lumia Passport ensures regulatory compliance through: **Global Regulatory Alignment** The KYC process is designed to be flexible and adaptable to different jurisdictions: * Country-specific KYC requirements * Regional data protection compliance (GDPR, CCPA) * Industry-specific regulations (MiFID II for financial services) * Ongoing monitoring and reporting capabilities **Institutional Requirements** For institutional participants, Lumia Passport supports: * Enhanced due diligence (EDD) procedures * Accredited investor verification * Corporate KYC for entities * Beneficial ownership identification * Source of funds verification **Compliance Monitoring** Ongoing compliance features include: * **Transaction Monitoring**: Real-time analysis of transaction patterns * **Risk Assessment**: Automated scoring based on behavior and associations * **Reporting Tools**: Generate compliance reports for auditors and regulators * **Alert Systems**: Flag suspicious activities for review * **Audit Trail**: Immutable record of all KYC and compliance actions #### Privacy-Preserving Compliance Despite strict compliance requirements, Lumia Passport maintains user privacy: * Credentials stored off-chain with only hashes on-chain * Zero-knowledge proofs for verification without data exposure * Selective disclosure of only necessary information * Encrypted credential storage * User-controlled data sharing #### Real-World Asset (RWA) Enablement Lumia Passport is essential for RWA applications: **Asset Tokenization** Enable compliant tokenization of real-world assets: * Real estate properties * Commodities (gold, diamonds, aluminum) * Art and collectibles * Intellectual property * Securities and financial instruments **Legal Framework Support** Integration with legal and regulatory frameworks: * Smart contract templates for compliant agreements * Bailee agreements for asset custody * Common law compliance structures * Jurisdictional flexibility **Fractional Ownership** Enable compliant fractional ownership: * Verify investor accreditation * Enforce ownership transfer restrictions * Maintain shareholder registries * Distribute dividends or yields # zkML DeFi Models for Asset Management Lumia L2 is at the forefront of integrating cutting-edge technologies to revolutionize the DeFi space. One of the key innovations we are introducing is the use of Zero-Knowledge Machine Learning (zkML) for asset management. By leveraging the power of off-chain AI models and bringing the data on-chain via zkML, we aim to provide our users with the best yield opportunities across the web3 ecosystem. ### Understanding zkML Zero-Knowledge Machine Learning (zkML) is a groundbreaking approach that combines the principles of machine learning with zero-knowledge proofs (ZKPs). In the context of asset management, zkML allows us to train AI models on sensitive financial data without compromising privacy or security. The core idea behind zkML is to enable the generation of outputs or predictions from an AI model without revealing the sensitive training data itself. This is achieved through the use of ZKPs, specifically zk-SNARKs (Zero-Knowledge Succinct Non-Interactive Argument of Knowledge). zk-SNARKs provide a way to prove the integrity of the output generated by an AI model without disclosing the underlying model parameters or the training data. This ensures that the AI model's predictions are accurate and trustworthy, while maintaining the privacy and confidentiality of the data used to train the model. ### Building Off-Chain AI Models for Yield Optimization At Lumia L2, we are developing sophisticated off-chain AI models that leverage the vast amount of data available across the web3 ecosystem. These models are designed to analyze various yield opportunities, both within Lumia L2 and on other platforms integrated into Lumia Steam. Our AI models employ advanced machine learning techniques, such as deep learning and reinforcement learning, to identify the most promising yield opportunities. By considering factors such as market trends, historical performance, liquidity, and risk profiles, these models can provide data-driven insights and recommendations to optimize users' returns. The off-chain nature of these AI models allows us to process large volumes of data efficiently and continuously update the models based on the latest market conditions. This ensures that the yield recommendations provided to our users are always up-to-date and reflect the current state of the web3 ecosystem. ### Bringing Data On-Chain via zkML While the AI models operate off-chain, we utilize zkML to bring the relevant data and predictions on-chain in a secure and privacy-preserving manner. This is achieved through the use of zkML circuits built with Succint, a powerful zkML framework. Succint enables us to convert the off-chain AI models into arithmetic circuits that can be executed on-chain. These circuits take the input data, perform the necessary computations, and generate zero-knowledge proofs that verify the integrity of the output without revealing the underlying data or model parameters. The zkML circuits are designed to be highly efficient and scalable, allowing us to process large amounts of data and generate proofs quickly. This ensures that the yield recommendations provided to our users are not only accurate but also delivered in a timely manner. ### Custom EigenLayer AVS for Verification To further enhance the security and trust in our zkML asset management system, we leverage a custom EigenLayer AVS (Actively Validated Services) for verification. EigenLayer is a cutting-edge framework that enables the creation of decentralized and trustless verification services. Our custom EigenLayer AVS is specifically designed to verify the zero-knowledge proofs generated by the zkML circuits. It acts as an independent and decentralized verifier, ensuring that the proofs are valid and the output generated by the AI models is accurate. The EigenLayer AVS operates on a decentralized network of nodes, each of which independently verifies the zkML proofs. This distributed verification process provides an additional layer of security and trust, as it eliminates the need for a single centralized verifier. ### Technical Breakdown Here's a high-level technical breakdown of how zkML is integrated into Lumia L2 for asset management: 1. **Off-Chain AI Models**: We develop and train advanced AI models using state-of-the-art machine learning frameworks such as TensorFlow or PyTorch. These models are designed to analyze yield opportunities across the web3 ecosystem and provide data-driven recommendations. 2. **Data Preprocessing**: The input data for the AI models is preprocessed and normalized to ensure compatibility with the zkML circuits. This may involve techniques such as feature scaling, one-hot encoding, and data augmentation. 3. **zkML Circuit Compilation**: Using the Succint framework, we compile the off-chain AI models into zkML circuits. This process involves converting the model's computational graph into an arithmetic circuit representation that can be executed on-chain. 4. **Proof Generation**: The zkML circuits are executed off-chain using the preprocessed input data. During this process, the circuits generate zero-knowledge proofs that attest to the integrity of the output without revealing the underlying data or model parameters. 5. **On-Chain Verification**: The generated zkML proofs, along with the necessary public inputs, are submitted to the custom EigenLayer AVS for verification. The AVS nodes independently verify the proofs and reach a consensus on the validity of the output. 6. **Yield Recommendations**: Once the zkML proofs are verified, the yield recommendations generated by the AI models are made available to users on Lumia L2. These recommendations are presented in a user-friendly interface, allowing users to make informed decisions about their investments. 7. **Continuous Model Updates**: The off-chain AI models are periodically retrained and updated based on the latest market data and user feedback. This ensures that the yield recommendations remain accurate and relevant over time. ### Conclusion By integrating zkML into our asset management system, Lumia L2 is revolutionizing the way users interact with DeFi platforms. Our off-chain AI models, powered by advanced machine learning techniques, provide data-driven yield recommendations that help users maximize their returns. Through the use of zkML circuits built with Succint and verified by our custom EigenLayer AVS, we bring the power of AI on-chain in a secure, privacy-preserving, and trustless manner. This ensures that users can benefit from the insights generated by our AI models without compromising the confidentiality of their data. As we continue to push the boundaries of zkML and AI in the DeFi space, Lumia L2 is well-positioned to become the go-to platform for users seeking the best yield opportunities across the web3 ecosystem. By combining cutting-edge technology with a user-centric approach, we are paving the way for a new era of intelligent and secure asset management in the decentralized world. # Yield Optimiser Model High level overview of Lumia's Off-Chain Model ### 1. Sentiment Analysis with Natural Language Processing (NLP) To capture the social media presence and sentiment around DeFi platforms, particularly on Twitter, we will employ NLP techniques: * Collect tweets related to DeFi platforms using relevant hashtags, token tickers, and keywords. * Preprocess the tweet data by removing noise, handling abbreviations, and normalizing the text. * Apply sentiment analysis models, such as VADER or BERT-based models, to quantify the sentiment associated with each platform. * Incorporate the sentiment scores as features in the yield optimization model to capture the impact of social media sentiment on potential yields. ### 2. Time Series Forecasting with LSTM To predict future APYs and capture the temporal dynamics of yield rates, we can use LSTM (Long Short-Term Memory) networks, a variant of recurrent neural networks (RNNs): * Collect historical data on APYs, TVL growth, and other relevant time-dependent variables for each DeFi platform. * Preprocess the time series data by normalizing, handling missing values, and creating appropriate time lags. * Train an LSTM model to learn the temporal patterns and dependencies in the yield data. * Use the trained LSTM model to forecast future APYs and capture potential APY drops based on TVL acquisition speed. ### 3. Ensemble Modelling To incorporate multiple factors and improve the robustness of the yield optimization model, we will create an ensemble of different models: * Build individual models for each factor, such as: * Regression models for the relationship between social media sentiment and yields. * Decision tree models for the impact of fees on yield optimization. * Gradient boosting models for the relationship between TVL growth and yields. * Combine the predictions from these individual models using ensemble techniques like stacking or weighted averaging. * The ensemble model will take into account the outputs from the sentiment analysis, time series forecasting, and other factor-specific models to provide a comprehensive yield recommendation. ### 4. Reinforcement Learning for Dynamic Optimization To adapt to changing market conditions and optimize yields dynamically, we will employ reinforcement learning (RL) techniques: * Formulate the yield optimization problem as a sequential decision-making task, where the RL agent (model) learns to make optimal decisions based on the current state of the DeFi ecosystem. * Define the state space to include relevant factors such as social media sentiment, TVL growth, APYs, and fees. * Define the action space as the selection of DeFi platforms or investment strategies. * Design a reward function that incentivizes the RL agent to maximize yields while considering factors like APY drops and platform stability. * Train the RL agent using algorithms like Q-learning or policy gradients to learn the optimal yield optimization strategy. ### 5. Continuous Learning and Adaptation To ensure the model remains up-to-date and adapts to new trends and platforms, we will implement a continuous learning framework: * Regularly collect new data on social media sentiment, APYs, TVL growth, and other relevant factors. * Retrain the individual models (sentiment analysis, time series forecasting, factor-specific models) with the updated data. * Fine-tune the ensemble model and the RL agent based on the latest data and user feedback. * Monitor the performance of the yield optimization model and make adjustments as necessary.High Level Overview of Lumia's Off-Chain Yield Optimiser Model
Sample verified contract view
Based off PolygonCDK