ODIN Protocol
Search…
ODIN Protocol
Introduction
ODIN NODE
Before Getting Started
Getting Started
Creating an ODIN Wallet
Becoming ODIN Validator
Editing a validator
Oracle Validators
Google Cloud Run executor
AWS Lambda executor setup
Baldur to Heimdall
Restarting ODIN node
CLI delegation
Using ODIN Web
Unjailing a Validator
FAQ
ODIN token
Testnet Reward Program
Testnet Staking
RESOURCES
Website
Whitepaper
Github
Whitepaper
Abstract
Powered By GitBook
Oracle Validators
configuring yoda and your Lambda function executor instance
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;
1
yoda config chain-id $CHAIN
2
yoda config node http://localhost:26657
3
yoda config validator $VALIDATOR
4
yoda config broadcast-timeout "5m"
5
yoda config rpc-poll-interval "1s"
6
yoda config max-try 5
Copied!
Add several keys with the following;
1
yoda keys add REPORTER_01
2
yoda keys add REPORTER_02
3
yoda keys add REPORTER_03
4
yoda keys add REPORTER_04
5
yoda keys add REPORTER_05
Copied!
This is because yoda works with multiple reporter addresses to allow it to submit multiple transactions concurrently.
Previous
Editing a validator
Next
Google Cloud Run executor
Last modified 4d ago
Copy link