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.

Sign up for GitHub

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

Jump to bottom

Runtime node admission policies #2513

Closed
kostko opened this issue Jan 3, 2020 · 0 comments · Fixed by #2533
Closed

Runtime node admission policies #2513

kostko opened this issue Jan 3, 2020 · 0 comments · Fixed by #2533
Labels
c:registry Category: entity/node/runtime registry service

Comments

@kostko
Copy link
Member

kostko commented Jan 3, 2020

Each runtime should be able to define its node admission policy.

Currently only two policies should be supported:

  • Entity whitelist (only nodes belonging to whitelisted entities can register to host a runtime).
  • Anyone with enough stake (currently the only supported policy).

The second one (anyone with enough stake) can introduce liveness issues as long as there is no slashing for compute node liveness (see #2078).
@kostko kostko added the c:registry Category: entity/node/runtime registry service label Jan 3, 2020
@kostko kostko mentioned this issue Jan 3, 2020
Closed
15 tasks
@pro-wh pro-wh mentioned this issue Jan 10, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c:registry Category: entity/node/runtime registry service
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

go registry: for runtimes to whitelist node operators oasisprotocol/oasis-core
2 participants
@kostko @pro-wh