DjedAlliance / Oracle-Ergo-OffChainComponent

Core off-chain component of Oracle Pools

Oracle Core v2.0

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).

The current oracle core is built to run the protocol specified in the EIP-0023 PR.

Roadmap

In progress

• v2.0-beta. Run a public oracle pool on testnet. See planned tasks

Next

• v2.0-RC. Launch on the mainnet. See planned tasks

Getting started

Download

Get the latest release binary from Releases Or install it from the source code with:

cargo install --path core

If you want to run it as systemd daemon check out this section. Run it with oracle-core --help or oracle-core <SUBCOMMAND> --help to see the available commands and their options.

Setup

Generate an oracle config file from the default template with:

oracle-core generate-oracle-config

and set the required parameters:

• oracle_address - a node's address that will be used by this oracle-core instance(pay tx fees, keep tokens, etc.). Make sure it has coins;
• node_url, node_api_key - node connection parameters;

Bootstrapping a new oracle pool

To bootstrap a new oracle pool:

• Run

oracle-core bootstrap --generate-config-template bootstrap.yaml

to generate an example of the bootstrap config file.

• Edit bootstrap.yaml (see the parameters list below);
• Make sure node's wallet is unlocked;
• Run

oracle-core bootstrap bootstrap.yaml

to mint tokens and create pool, refresh, update boxes. The pool_config.yaml file will be generated. It contains the configuration needed to run this pool;

• Run an oracle with

oracle-core run

Bootstrap parameters available to edit:

• [token]:name, description - token names and descriptions that will be used to mint tokens;
• [token]:quantity - number of tokens to mint;
• data_point_source - can be one of the following: NanoErgUsd, NanoErgXau, NanoErgAda;
• min_data_points - minimal number of posted datapoint boxes needed to update the pool box (consensus);
• max_deviation_percent - a cut off for the lowest and highest posted datapoints(i.e. datapoints deviated more than this will be filtered out and not take part in the refresh of the pool box);
• epoch_length - minimal number of blocks between refresh(pool box) actions;
• min_votes - minimal number of posted ballot boxes voting for a change to the pool box contracts;
• min_storage_rent - box value in nanoERG used in oracle and ballot boxes;

Check out How I bootstrapped an ERG/XAU pool on testnet report for an example.

Invite new oracle to the running pool

To invite a new oracle the person that bootstrapped the pool need to send one oracle token and one reward token. On bootstrap X oracle and reward tokens are sent to the oracle_address, where X is the total oracle token quantity minted on bootstrap. Use scripts/send_new_oracle.sh to send one oracle, reward and ballot token. Besides the tokens the pool config file that you are running now should be sent as well. Send pool_config.yaml to the new oracle.

Joining a running pool

To join the existing pool one oracle and one reward token must be received to the address which will be used as oracle_address in the config file of the oracle. The received pool_config.yaml config file must placed accordingly.

To run the oracle:

• Make sure node's wallet is unlocked;
• Run an oracle with

oracle-core run

Extract reward tokens

Since the earned reward tokens are accumulating in the oracle box there is a command to send all accumulated reward tokensminus 1 (needed for the contract) to the specified address:

oracle-core extract-reward-tokens <ADDRESS>

To show the amount of accumulated reward tokens in the oracle box run

oracle-core print-reward-tokens

Transfer the oracle token to a new operator

Be aware that reward tokens currently accumulated in the oracle box should be extracted with extract-reward-tokens command firstbefore transferring the oracle token to the new address. Run

oracle-core transfer-oracle-token <ADDRESS>

Ensure the new address has enough coins for tx fees to run in a pool. As with inviting a new oracle, the pool config file that you are running now should be sent as well. Send pool_config.yaml to the new operator.

Updating the contracts/tokens

Changes to the contract(parameters)/tokens can be done in three steps:

• prepare-update command submits a new refresh box with the updated refresh contract;
• vote-update-pool command submits oracle's ballot box voting for the changes;
• update-pool command submits the update transaction, which produces a new pool box; Each of the step is described below. See also a detailed instruction on Updating the epoch length

Create a new refresh box with prepare-update command

Create a YAML file describing what contract parameters should be updated. See also an example of such YAML file at Updating the epoch length Run:

oracle-core prepare-update <YAML file>

This will generate pool_config_updated.yaml config file which should be used in update-pool command. The output shows the new pool box contract hash and reward tokens amounts for the subsequent dozen epochs. To be used in the vote-update-pool command run by the oracles on the next step.

Vote for contract update with vote-update-pool command

Run

oracle-core vote-update-pool <NEW_POOL_BOX_ADDRESS_HASH_STR> <UPDATE_BOX_CREATION_HEIGHT>

Where:

• <NEW_POOL_BOX_ADDRESS_HASH_STR> - base16-encoded blake2b hash of the serialized pool box contract for the new pool box
• <UPDATE_BOX_CREATION_HEIGHT> - The creation height of the existing update box.

are required parameters, with optinal (in case of minting a new reward token):

• <REWARD_TOKEN_ID_STR> - base16-encoded reward token id in the new pool box (use existing if unchanged)
• <REWARD_TOKEN_AMOUNT> - reward token amount in the pool box at the time of update transaction is committed

They are printed in the output of the prepare-update command.

Update the pool box contract with update-pool command

Make sure the pool_config_updated.yaml config file generated during the prepare-update command is in the same folder as the oracle-core binary. Run

oracle-core update-pool

With optional(only if minted) parameters: <REWARD_TOKEN_ID_STR> - base16-encoded reward token id in the new pool box (only if minted) <REWARD_TOKEN_AMOUNT> - reward token amount in the pool box at the time of update transaction is committed (only if minted)

This will submit an update tx. After the update tx is confirmed, remove scanIds.json and use pool_config_updated.yaml to run the oracle (i.e., rename it to pool_config.yaml and restart the oracle). Distribute the pool_config.yaml file to all the oracles. Be sure they delete scanIds.json before restart.

Import update pool config with import-pool-update command

Make sure the pool_config_updated.yaml config file generated during the prepare-update command is at hand. Run

oracle-core update-pool pool_config_updated.yaml

This will update the pool_config.yaml, removes scanIds.json. Restart the oracle afterwards.

How to run as systemd daemon

To run oracle-core as a systemd unit, the unit file in systemd/oracle-core.service should be installed. The default configuration file path is ~/.config/oracle-core/oracle_config.yaml. This can be changed inside the .service file

cp systemd/oracle-core.service ~/.config/systemd/user/oracle-core.service
systemctl --user enable oracle-core.service

Verifying contracts against EIP-23

It is recommended to check that the contracts used are indeed coming from EIP-23. Run the following command to get encoded hashes of each contract:

./oracle-core print-contract-hashes

or if running from source files:

cargo test check_contract_hashes -- --nocapture

Check these values against those described in EIP-23.