-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Oracles] Native Oracle Policy #1277
Comments
Can you list what needs to be included in the policy? |
I believe
|
It's a good idea to use the same native contract, it would be a way to have all the network operating parameters in the same contract. But it is not strictly necessary. Currently, we will need to save the authorized Oracle Nodes (current validators), Allowed Protocols/Filters and base cost of oracles use. |
We can start with the implementation of the policy contract, this must include at least:
The only question we have left before implementation is to decide if we prefer a new contract or include it in the current policy contract. 👍 Current policy contract. |
I begin to implement the code of OraclePolicy.
What else need to be added? |
Great @doubiliu, that would be enough for now. |
Maybe we need add a DistributeFee function.We cannot guarantee that the costs will be divisible.Number of nodes is not fixed. |
Also, we may need to consider the timeliness of Oracle nodes. We cannot guarantee that Oracle nodes will still be authorized when CN make consensus. |
For the use of the Oracles we must contemplate a new native contract (or use the current one) that stores the oracle policy and the agreed values, such as authorized nodes, fee, protocols and active filters, blocked endpoints, ...
The idea is that all Oracle nodes share the same policy to obtain homogeneous behavior, but leaving the door open for Oracle node owners to specify a specific policy (for example of supported protocols).
It must be able to add and remove authorized nodes and other values.
This topic is closely linked to Oracle nodes election #1278
The text was updated successfully, but these errors were encountered: