> For the complete documentation index, see [llms.txt](https://docs.eniac.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eniac.network/getting-started/oracles/chainlink-relayer.md).

# Chainlink Relayer

The Chainlink Relayer presents an innovative solution, seamlessly and instantaneously bridging Chainlink price feeds from Ethereum to the ENI Chain. This crucial functionality empowers decentralized applications (dApps) on ENI that require robust and up-to-date pricing information.

Crucially, these price updates are precisely relayed to a dedicated smart contract on the ENI Chain, which we refer to as the 'Shadow Aggregator.' This Shadow Aggregator is meticulously engineered to possess an identical interface to Chainlink's native aggregators. This design significantly streamlines the development process: once dApps complete their initial integration with the ENI ecosystem, they can effortlessly pivot their existing Chainlink integrations to leverage the relayed data, minimizing development overhead.

To ensure transaction finality and data integrity, clients typically await approximately 20 block confirmations – roughly a 5-minute window – after submitting a transaction. This synchronization mechanism guarantees the reliable delivery of critical information.

**Currently, during this introductory (or 'XPlan') phase, data submissions by Relayers are restricted to authorized addresses to ensure stability and control. However, a key aspect of our future vision is to evolve into a fully permissionless system. Upon the mainnet's launch, we plan to upgrade this mechanism, enabling anyone to run a Relayer and contribute price data, thereby embracing a truly decentralized model.**

### Shadow Aggregators

For each aggregator on Ethereum, ENI provides a *shadow aggregator* on ENI Chain.

### Service Status

{% embed url="<https://status.eniac.network/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eniac.network/getting-started/oracles/chainlink-relayer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.