# What we do

Chainlink offers its own services for selected blockchains. At the same time, the speed at which new chains are deployed is constantly increasing. Be it as L2s or even L3s or as another competitive L1s.

Relink Protocol has developed a proxy service solution that forwards the random data request to an officially from Chainlink supported chain and processes the result accordingly.

A Relink oracle network signs the data generated by Chainlink and passes the original data along with the signatures to the callback method. The signature checks in the consumer base contract mean that no data can be changed on the way from the relaying backend.

## Process diagram 

The following is an example of the process flow for a Relink data request for Chainlink data on Polygon. For more information and details on the individual steps, please have a look at the [**Architecture Overview**](/architecture/overview.md).

<div data-full-width="true"><figure><img src="/files/AphhPHVfCpyVRzWxcjwR" alt=""><figcaption><p>Relink request generic example architecture</p></figcaption></figure></div>

## Real world example

As an example, a randomness request (VRF) on the EVM chain "Horizen EON" is used here.

* `InitiateRandomnessRequest`  in this [transaction](https://eon-explorer.horizenlabs.io/tx/0xca36b05a3e13347b2f9e3fe36ddba35d0ee269ad10ced83bcbe36425d6ace1ca) on Horizen EON (September-06-2023 10:40:43 PM +2 UTC)
  * it's an Example Consumer contract
* `RequestRandomWords` in this [transaction](https://polygonscan.com/tx/0xf75edde27564edc86d8aabebcef1362ad75b0f202ca66f652fdde89bbca4ff2c) on Polygon (Sep-06-2023 10:41:03 PM +2 UTC)
* `RandomnessReceived` in this [transaction](https://polygonscan.com/tx/0xd0a9ca2300674b80384cbe61d722c42c40e1f207dab2abd85c35572863648b37) on Polygon (Sep-06-2023 10:41:17 PM +2 UTC)
* `CallbackWithRandomness` in this [transaction](https://eon-explorer.horizenlabs.io/tx/0x38b4f66c675999d56975de2e8a5c6380d529c8e51f45d7aca83e93a0641f5766) on Horizen EON (September-06-2023 10:41:55 PM +2 UTC)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.relink.services/overview/what-we-do.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.