Architecture Overview

If you are unfamiliar with the concept of a blockchain oracle, reference the Ethereum Foundation's documentation on blockchain oracles.

The following is a brief overview of the core components that define the EO protocol, to contextualize the data aggregation process.

Ethereum Eigenlayer Integration

A set of smart contracts on Ethereum that help connect Ethereum validators to EO via EigenLayer. These contracts manage the network's cryptographic identity, stake records, operator set and enable EO to slash validators.

EO-Chain

Ideally, the best infrastructure for blockchain 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 eBFT consensus mechanism. This chain is used to aggregate and produce cryptographically verifiable data. The EO-Chain is at the center of EO operations, offloading computation from the base layer, which reduces costs and latency. The EO-Chain creates immutable records of all EO activity. These records are used to cryptographically prove operator rewards and slashing.

Read more here:

EO Chain

Validator Clients

Data validators are responsible for observing real-world data, validating it, and reporting it to the EO chain. Chain validators are responsible for maintaining the consensus of the EO chain. Together, these roles operate the EO protocol.

Aggregator Modules

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 Data Validators, accounting for their respective voting power.

EO Endpoints

EO provides Websocket and REST API to use EO data as a pull blockchain oracle. Coupled with the EO Solidity SDK , dapps can automate their data usage with Python\Typescript or other automation solutions.

Target Network Contracts

Smart contracts can be permissionlessly deployed on consumer blockchains to integrate EO data. These contracts can verify the validity of signatures produced by the EO protocol and enable dapps to read and use their desired data.