Skip to content
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

One option of election model 'Oracle Group' #1291

Closed
doubiliu opened this issue Nov 27, 2019 · 0 comments
Closed

One option of election model 'Oracle Group' #1291

doubiliu opened this issue Nov 27, 2019 · 0 comments
Labels
Discussion Initial issue state - proposed but not yet accepted

Comments

@doubiliu
Copy link
Contributor

Summary or problem description
This topic is closely linked to Oracle Nodes Election #1278
Since there are many problems with the election model that need to be avoided and resolved,
I want to introduce a new model 'Oracle Group'

In @vang1ong7ang comment,we can find both problems with CN elections and strong bindings.
Elections :The preference of the 49% voters......
Strong bindings:view attack.(But this maybe can be solved by change IP)

#1278 (comment)

Do you have any solution you want to propose?
Maybe it is difficult to solve these problem.Maybe we can try a new way.
So I introduce 'Oracle Group'.And I want to use this way to return operation right to users.

Group
Any node that enables Oracle functionality can become a potential Oracle service provider in Neo network. These nodes can be aggregated into one group according to certain rules and wishes, and the group provides Oracle services to users. A group can be created by a sponsor and set the corresponding election and registration rules.
The most authoritative group is a general-purpose group voted by the Neo consensus node, which can provide a more reliable Oracle service.
User can decide which group to use. It is recommended to use generic groups, but in some special cases, such as special authorization, restricted access, etc., other groups can be used.

Group generation process
The overall can be divided into 3 steps:

  1. Create a group: Create a new group, the user needs to set the group ID, registration rule contract address, voting rule contract address.
  2. Register to be a candidate: only a candidate node has the right to be elected
  3. Vote: The official node list is dynamically modified after each time of voting.
    image

general-purpose group
register rule,voting rule : We can use the rules for electing consensus nodes

Neo Version

  • Neo 3

Where in the software does this update applies to?

  • Other:Oracle
@doubiliu doubiliu added the Discussion Initial issue state - proposed but not yet accepted label Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

No branches or pull requests

1 participant