4. Oracle Daemon
Last updated
Was this helpful?
Last updated
Was this helpful?
The next step would be to add an oracle member, and start using the Oracle Daemon with the oracle member private key to craft and send reports to the vPool.
By default, the pool expects at least two members before it can start operating, but Kiln runs the global oracle member, so adding one regular member will do the trick.
Remember, you can remove the global oracle member from your vPool only if you have at least 5 members in your oracle quorum, and if you toggle the ejection flag.
The call is pretty simple, and should be performed by the vFactory admin
You can find the oracle daemon inside the operatord
repository. It contains all the daemons that an operator might need to run.
The oracle daemon is configured using a config.yaml
file. Let's start by creating a directory for the oracle daemon:
And then, create ~/oracle_datadir/config.yaml
, here's how it should look for one oracle member
name
is for logging purposes
private-key
is the private key of the member that you wish to run
pool
is the address of the vPool
you wish to report for
nexus
is the address of the Nexus
contract
purchase
is set to true
if the member will also participate in performing the purchaseValidators
call on the vPool
maxTxCostWei
is the maximum allowed cost of a tx in wei
It might take a bit of time to sync, but anything pulled from EL/CL that we'll need to reuse is stored inside the sqlite
database that will be created. This would greatly speedup possible restarts.
You should now ping Kiln to make sure that the global oracle member is running on their end. If that's the case, we should see oracle reports being posted