Data sourcing

At the heart of Lumina is a decentralized data collection system composed of an independent network of Feeders, in charge of sourcing data and feeding it into the Lasernet chain.

Key components

# Feeders

Feeders are nodes that fetch granular market data directly from decentralized exchanges (DEXs), centralized exchanges (CEXs) and 3rd party data sources. These Feeders are responsible for sourcing trade ticks and pushing them to Pods—smart contracts running on DIA’s Lasernet—at configurable intervals i.e 30 seconds. If during those time intervals more than one trade takes place, each Feeder will generate a median (price) value for each asset per exchange, using all trade data.

Feeders consist of three amin elements:

1. Scrapers

2. Collector

3. Processor

4. Feeder

Scrapers

The expected input for a scraper is a set of pair tickers such as BTC-USDT. Tickers are always capitalized and symbols separated by a hyphen. It's the role of the scraper to format the pair ticker such that it can subscribe to the corresponding (websocket) stream.

Collector

The collector gathers trades from all running scrapers. As soon as it receives a signal through a trigger channel it bundles trades in atomic tradesblocks. An atomic tradesblock is a set of trades restricted to one market on one exchange, for instance BTC-USDT trades on Binance exchange. These tradesblocks are sent to the Processor.

Processor

The processor is a 2-step aggregation procedure:

1. Step: Aggregate trades from an atomic tradesblock. The type of aggregation can be selected through an environment variable (see Feeder/main). The only assumption on the aggregation implementation is that it returns a float64.

2. Step: Aggregate filter values obtained in step 1. The selection of aggregation method and assumptions are identical to Step 1. The obtained scalar value is sent to the Oracle feeder.

Feeder

The feeder is feeding a simple key value oracle. It publishes the value obtained from the Processor. It is worth mentioning that the feeder can contain the trigger mechanism that initiates an iteration of the data flow diagram.

---

Find out more about the feeder structure and how to run your own feeder here:

How to run a data feeder

---

Architecture

Data flow in oracle feeders

---

Key benefits

• Crypto-Economic Security: DIA Lumina relies on a decentralized network of nodes (Feeders) backed by staked assets, ensuring the integrity and reliability of data sourcing. Both operators and delegators contribute to the system’s security and are rewarded for their participation. Malfunctioning nodes get slashed, losing their staked assets and reputation.

• Cryptographic Security: Lumina incorporates advanced cryptographic techniques such as zero-knowledge proofs to ensure data verifiability. The system is designed to accommodate future cryptographic advancements, ensuring long-term security and flexibility.

• Any Asset from Any Chain: Lumina’s data sourcing framework is built on first-party scrapers. This allows DIA Lumina to provide feeds for any asset on any chain, with data sourced directly from where it is generated while maintaining transparency and bypassing reliance on third-party data providers.

---

Staking Incentives

To encourage honest behavior, oracle feeders will be rewarded for successful operations and penalized for harmful actions. These incentives ensure that dishonest behavior is punished and becomes economically unviable.

Rewards and penalties will primarily be based on uptime and accuracy, measured by the timeliness of updates and the accuracy of prices compared to other feeders. Initially, feeders will gather the last traded price for assets from centralized exchanges (CEXs). For decentralized exchanges (DEXs), we will use trade simulation-based price estimation, which simulates trades to obtain current exchange rates. This approach ensures more accurate pricing, particularly for assets that are infrequently traded.