> For the complete documentation index, see [llms.txt](https://geodb.gitbook.io/odin-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://geodb.gitbook.io/odin-protocol/oracle-validators.md).

# Oracle Validators

While validators do not need to become oracles, each oracle validator will need to have it's own AWS lambda or GCP run function instance.  Yoda is the oracle daemon.  It is already included in the container, but will need to be configured.  Before following the yoda configuration instructions below, visit the appropriate subpage for instructions on setting up your executor on the function platform of preference.

First, yoda will need to be configured;

```bash
yoda config chain-id odin-mainnet-freya
yoda config node http://localhost:26657
yoda config validator $VALIDATOR
yoda config broadcast-timeout "5m"
yoda config rpc-poll-interval "1s"
yoda config max-try 5
```

Add several keys with the following;

```bash
yoda keys add REPORTER_01
yoda keys add REPORTER_02
yoda keys add REPORTER_03
yoda keys add REPORTER_04
yoda keys add REPORTER_05
```

This is because Yoda works with multiple reporter addresses to submit multiple transactions concurrently.

The next step in Yoda configuration is to set your function executor configuration parameter;

```
yoda config executor "rest:<your_aws_lambda_endpoint>?timeout=7s"
```

Your reporter addresses, along with some loki, must be supplied to the blockchain to trigger account creation.

```
odin tx multi-send 1loki $(yoda keys list -a) \
  --from $ADDRESS \
  --chain-id $CHAIN
```

Next, you will add the reporter addresses to your validator;

```bash
odin tx oracle add-reporters $(yoda keys list -a) \
  --from $ADDRESS \
    --chain-id odin-mainnet-freya
```

Now, we will activate our validator as an oracle on the blockchain;

```bash
odin tx oracle activate \
  --from $ADDRESS \
    --chain-id odin-mainnet-freya
```

We will want to verify our oracle is functioning;

```bash
odin query oracle validator $VALIDATOR
```

If everything is working as it should be, the output should include the parameter "is\_active", and the value should be "true".


---

# 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 dynamically by asking a question.

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

```
GET https://geodb.gitbook.io/odin-protocol/oracle-validators.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.