Lum0x
lum0x
  • Overview
    • πŸ”¦About the Lum0x
    • πŸ”¦Quick Start
    • πŸ”¦Roadmap
    • πŸ”¦Glossary
  • Architecture
    • πŸ”¦Consensus
    • πŸ”¦Code Verification Layer
    • πŸ”¦Data Aggregation
    • πŸ”¦Deterministic Programming
  • Lum0x INDEXER
    • πŸ”¦Operator Guides
      • βšͺHow to become an operator
      • βšͺOperator dashboard
      • βšͺChoosing a feed to validate
    • πŸ”¦Publisher Guides
      • βšͺHow to become a publisher
      • βšͺPublishing a feed
        • πŸ’‘Submitting via Console
        • πŸ’‘Submitting via GitHub Code
    • πŸ”¦Feeder Guides
      • βšͺHow to become a feeder
      • βšͺQuerying a feed
  • Lum0x DeSoc Services
    • πŸ”¦DAGG - Data Source Aggregator
    • πŸ”¦0xFunction - DeComputation
    • πŸ”¦TrustStore - Decentralized DB
    • πŸ”¦MetaFrame - DataWrap Frame
  • Other
    • πŸ”¦Use Cases
    • πŸ”¦Lite Paper
    • πŸ”¦FAQ
    • Twitter
    • Explorer
Powered by GitBook
On this page
  • How Is It Made Public?
  • Why Is It Necessary?
  • Example 1: DeSoc User Point Allocation System
  • Example 2: DeSoc User Credit Scoring System
  1. Architecture

Code Verification Layer

PreviousConsensusNextData Aggregation

Last updated 10 months ago

The JavaScript-based computational instructions written in 0xFunction are publicly available on the Lum0x code verification layer. This is similar to how contracts are deployed on a blockchain, verified, and made visible on explorers.

These instructions are executed and agreed upon by a decentralized processing system, not by a single central entity. Once verified, 0xFunction scripts are immutable and will execute exactly as coded, without any external interference or manipulation. This is akin to traditional smart contracts on the EVM (Ethereum Virtual Machine).

How Is It Made Public?

The code undergoes the following process to be stored in the trust layer, allowing users to verify its contents on the explorer:

  1. Submission: The code is submitted either through the console or via a GitHub permalink.

  2. Verification: The submitted code is reviewed and verified by the decentralized network operators.

  3. Storage: Once verified, the code is stored in the Lum0x trust layer(code verficiation layer).

  4. Access: Users can access and inspect the verified code on the Lum0x explorer, ensuring transparency and trust in the feed’s operation.

Why Is It Necessary?

Currently, most computations within the DeSoc ecosystem are opaque. It’s unclear how they operate, for what purpose, and who is behind the calculations. By publicizing and fixing these computational instructions, and allowing decentralized entities to compute and reach consensus according to these codes, a truly decentralized serverless function emerges, free from intermediaries.

Example 1: DeSoc User Point Allocation System

As-Is:

Users must trust the entity managing the point system without knowing the rules, methods, or personnel involved in the calculations.

To-Be:

The rules governing the point system are publicly available as code. This code is immutable and is processed and agreed upon by decentralized nodes (Lum0x operators). The transparency of the process and the reliability of the results are guaranteed.

Example 2: DeSoc User Credit Scoring System

As-Is:

Users rely on the credit scoring system without insight into the hidden rules, irregular update cycles, or lack of real-time data.

To-Be:

The system’s rules are codified and made public. The computation and results are handled and validated in a decentralized manner by Lum0x operators. This ensures transparency in the operation of the credit scoring system and guarantees the accuracy and reliability of the results.


For detailed instructions on performing code verification and submitting 0xFunction, please refer to the following document.

πŸ”¦
βšͺPublishing a feed