What happens between an exchange price and an onchain oracle feed?
That’s one of the most interesting questions in oracle infrastructure.
With some oracle designs, users have limited visibility into the internal processing behind the final price.
DIA approaches this differently through Lasernet, its Layer-2 rollup built for oracle computation.
Here’s how the Lumina architecture works:
1. Feeders collect data
Independent operators gather granular data from CEXs, DEXs and other sources, then submit it to Lasernet.
2. Pods store submissions
Smart contracts hold feeder data onchain, making submissions available for further processing.
3. Aggregators calculate the feed
Onchain contracts apply validation rules and configurable methodologies to produce the final oracle output.
One methodology $DIA uses is MAIR — Moving Average with Interquartile Range — which combines moving-average pricing with outlier filtering.
Why does this matter?
Because transparency isn't only about knowing the final price. It's also about being able to inspect how submitted data was processed.
And there’s a token connection: DIA pays for gas on Lasernet, giving the token a functional role in oracle transactions.
That doesn't guarantee token appreciation. It connects utility to actual network usage.
For me, the architectural distinction worth watching is simple:
Data sourcing → Onchain processing → Verifiable oracle output.
The more complex DeFi becomes, the more important it is to understand how oracle data is produced—not just where it ends up.
That’s one of the most interesting questions in oracle infrastructure.
With some oracle designs, users have limited visibility into the internal processing behind the final price.
DIA approaches this differently through Lasernet, its Layer-2 rollup built for oracle computation.
Here’s how the Lumina architecture works:
1. Feeders collect data
Independent operators gather granular data from CEXs, DEXs and other sources, then submit it to Lasernet.
2. Pods store submissions
Smart contracts hold feeder data onchain, making submissions available for further processing.
3. Aggregators calculate the feed
Onchain contracts apply validation rules and configurable methodologies to produce the final oracle output.
One methodology $DIA uses is MAIR — Moving Average with Interquartile Range — which combines moving-average pricing with outlier filtering.
Why does this matter?
Because transparency isn't only about knowing the final price. It's also about being able to inspect how submitted data was processed.
And there’s a token connection: DIA pays for gas on Lasernet, giving the token a functional role in oracle transactions.
That doesn't guarantee token appreciation. It connects utility to actual network usage.
For me, the architectural distinction worth watching is simple:
Data sourcing → Onchain processing → Verifiable oracle output.
The more complex DeFi becomes, the more important it is to understand how oracle data is produced—not just where it ends up.