Architecture Overview
Last updated
Last updated
A on Ethereum that help connect Ethereum validators to eOracle via . These contracts manage the network's cryptographic identity, stake records, operator set and enable eOracle to slash validators.
Ideally, the best infrastructure for oracle operations would be Ethereum itself, but the high costs and latency of on-chain processes make this infeasible. To address this, the EO-chain is operated with a subset of the Ethereum validator set using the This chain is used to aggregate and produce cryptographically verifiable data. The EO-Chain is at the center of eOracle operations, offloading computation from the base layer, which reduces costs and latency. The EO-Chain creates immutable records of all eOracle activity. These records are used to cryptographically prove operator rewards and slashing.
are responsible for observing real-world data, validating it, and reporting it to the eOracle chain. are responsible for maintaining the consensus of the eOracle chain. Together, these roles operate the eOracle protocol.
Smart contracts on the EO-chain that enable aggregation and verification of data submitted by validators. These smart contracts produce digitally signed, verifiable data by aggregating the signatures of , accounting for their respective voting power.
eOracle provides to use eOracle data as a pull oracle. Coupled with the , dapps can automate their data usage with or
Smart contracts can be on consumer blockchains to integrate eOracle data. These contracts can verify the validity of signatures produced by the eOracle protocol and enable dapps to read and use their desired data.
