The oracle core is the off-chain component that oracles who are part of an oracle pool run. This oracle core provides a HTTP API interface for reading the current protocol state & another for submitting datapoints. Once a datapoint is submited, the oracle core will automatically generate the required tx and post it as well as any other actions required for the protocol to run. This thereby allows the oracle to participate in the oracle pool protocol without any extra effort for the oracle operator.
The oracle core requires that the user has access to a full node wallet in order to create txs & perform UTXO-set scanning. Furthermore each oracle core is designed to work with only a single oracle pool. If an operator runs several oracles in several oracle pools then a single full node can be used, but several instances of oracle cores must be run (and set with different api ports).
Connector must also be used with the oracle core in order to acquire data to submit to the pool. Each connector sources data from the expected sources, potentially applies functions to said data, and then submits the data to the oracle core via HTTP API during the
Live Epoch stage in the oracle pool protocol. All oracles for a given pool are expected to use the exact same connector, thereby making it simple to onboard and get started.
The current oracle core is built to run the protocol specified in the Deviation Checking Oracle Pool Spec.
Other documents can also be found explaining how various parts of the oracle core work in the docs folder.
Building & Running An Oracle
The majority of oracle operators will only need to focus on setting up their own oracle core to work with an already bootstrapped oracle pool. This section will explain how to do so for oracles using the ERG-USD connector. The steps are exactly the same for other connectors, but simply require using that connector's prepare script.
It is assumed that you are running this oracle on Linux, and have the following prerequisites:
- Access to an Ergo Node v3.3.0+ with an unlocked wallet.
- A recent stable version of the Rust Compiler installed.
- The Linux CLI tool
libssl-devpackage on Ubuntu (aka
openssl-develon Fedora, and potentially slightly different on other distros) installed.
- Clone this repository via:
git clone email@example.com:ergoplatform/oracle-core.git
- Enter into the connector's script folder:
- Run the prepare script which will automatically compile the oracle core and the connector for you:
- Enter into the newly created
cd ../../erg-usd-oracle-deployed & ls
- Edit your
oracle-config.yamlwith your Ergo Node information, your oracle address (address that was used for bootstrapping the pool & is inside of your Ergo Node wallet), and other relevant pool information. (Optionally acquire a pre-configured
oracle-config.yamlfrom the user who bootstrapped the oracle pool and simply fill in your node info/oracle address)
- Ensure your Ergo Node is running (and matches the info you input in the config) and has it's wallet unlocked (with some Ergs in the wallet to pay for tx fees).
- Launch your oracle by running
screeninstance will be created which launches both the oracle core and the connector. (Press
Ctrl+a - nto go between the core & the connector screens).
- If your node is running and properly configured, the oracle core will inform you that it has successfully registered the required UTXO-set scans:
UTXO-Set Scans Have Been Successfully Registered With The Ergo Node
- Press enter to confirm that the scans have been registered. Your oracle core is now properly set up and waiting for the UTXO-set scans to be triggered in order to read the state of the oracle pool on-chain to then perform actions/txs.
- Rescan the blockchain history by either using the
/wallet/rescanGET endpoint of your node, or by deleting
.ergo/wallet/registryin your Ergo Node folder. Either option triggers a rescan after the blockchain progresses into the next block.
- Once the node has finished rescanning (which can be checked via the
/wallet/statusendpoint and comparing the
walletHeightvalue to the current blockheight), the oracle core & connector will automatically issue transactions and move the protocol forward.
- Congrats, you can now detach from the screen instance if you wish via
Ctrl+a d. (And reattach via
screen -r) Your oracle core/connector will run automatically going forward.
Bootstrapping An Oracle Pool
In order for an oracle pool to run, it must be first created/bootstrapped on-chain. This is the bootstrap process that is required before oracle operators can run their oracle core and have the pool function on-chain.
Check out the Oracle Pool Bootstrap folder for detailed instructions about how to bootstrap an oracle pool using the CLI tool or manually.
Writing A New Connector
If you are looking to create a new Oracle Pool for a new datapoint, you need to write a new Connector. This process has been greatly simplified thanks to
Now within 15-20 lines of Rust code, you can easily create your own Connector that plugs right in to the Oracle Core.
If you would like to integrate your pool with the Ergo Explorer we have also created
Frontend Connector Lib. This library builds off of
Connector Lib and automatically provides + runs an API server which produces all of the data required for the frontend.
Building a Frontend Connector provides a single endpoint which summarizes the majority of relevant data about your Oracle Pool, and as such can also be useful if you intend to create your own custom website/frontend for showing off what is going on in your pool.