What Actually Happens Inside a DIA Oracle?
Most people see an oracle's final price feed. Fewer look at the contracts responsible for producing it.
DIA Lumina separates this process into three key components on Lasernet.
1. Pods: Where Feeder submissions are stored
Independent Feeder nodes submit market data to their dedicated Pod smart contracts. This separates submissions into distinct onchain records instead of putting every Feeder's data into one shared storage contract.
2. Aggregators: Where data becomes a price
Aggregator smart contracts read data from Pods and apply configurable rules to validate and combine submissions into oracle outputs.
Different configurations can support different asset requirements and application-specific needs.
3. Spectra: Delivering data across chains
After computation, Spectra enables oracle data to reach supported destination networks, making the output usable by smart contracts across ecosystems.
Why this design matters
Separating storage, computation and delivery creates a more modular oracle architecture. Developers can inspect onchain activity and configure aggregation logic rather than treating the final price as an unexplained number.
Of course, transparent computation doesn't automatically guarantee accurate source data or eliminate manipulation. Source quality, configuration and security still matter.
But in DeFi, being able to examine how a price was produced is an important part of building trust.
Don't just look at the oracle output. Look at the architecture behind it.
$DIA
Most people see an oracle's final price feed. Fewer look at the contracts responsible for producing it.
DIA Lumina separates this process into three key components on Lasernet.
1. Pods: Where Feeder submissions are stored
Independent Feeder nodes submit market data to their dedicated Pod smart contracts. This separates submissions into distinct onchain records instead of putting every Feeder's data into one shared storage contract.
2. Aggregators: Where data becomes a price
Aggregator smart contracts read data from Pods and apply configurable rules to validate and combine submissions into oracle outputs.
Different configurations can support different asset requirements and application-specific needs.
3. Spectra: Delivering data across chains
After computation, Spectra enables oracle data to reach supported destination networks, making the output usable by smart contracts across ecosystems.
Why this design matters
Separating storage, computation and delivery creates a more modular oracle architecture. Developers can inspect onchain activity and configure aggregation logic rather than treating the final price as an unexplained number.
Of course, transparent computation doesn't automatically guarantee accurate source data or eliminate manipulation. Source quality, configuration and security still matter.
But in DeFi, being able to examine how a price was produced is an important part of building trust.
Don't just look at the oracle output. Look at the architecture behind it.
$DIA