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

Finalize open group operator selection method #396

Open
shanejearley opened this issue Aug 7, 2023 · 0 comments
Open

Finalize open group operator selection method #396

shanejearley opened this issue Aug 7, 2023 · 0 comments

Comments

@shanejearley
Copy link
Contributor

shanejearley commented Aug 7, 2023

The open group operators need to be selected automatically in a way that ensures both consistent high performance and decentralization (not relying on a few operators, but many).

Operator Fees

Since operators can otherwise arbitrarily set their own fees outside of the registry, they are required to keep their fees below the registry's proposed maximum amount, or else they will be ineligible for selection. If their fees are changed to more than the maximum amount while they are actively operating, they will be automatically reshared.

Eligibility Requirements

  • Registered and active with the open group (confirmed on-chain)
  • Not currently resharing out of the open group (confirmed on-chain)
  • 1 ETH available from collateral not yet bound to a pool (confirmed on-chain)
  • DKG enabled/available (confirmed by participation)
  • Equal or above SSV performance threshold (24h, 30d, etc.)

Sorting Dimensions

  • Active validator count (could be confirmed on-chain, but might be expensive)
  • Last collateral deposit (could be confirmed on-chain, but might be expensive)

Questions

  • How should operators be selected based on their fees (within the eligible range)? Should the operators be split into a max four groups of calculated fee tiers and selected from each group?
  • How can the selection allow new operators (without any SSV performance history)? Should these new operators require 2 ETH (or some other amount larger than the current) collateral per validator until enough SSV performance history is recorded?
  • Should the (initial) open group make SSV DAO verification an eligibility requirement?
  • Can SSV performance threshold or a useful proxy metric be brought or confirmed on-chain? (Maybe the Rated UMA oracle?)
@shanejearley shanejearley added this to the Deploy testnet v1 (beta) milestone Aug 7, 2023
@shanejearley shanejearley modified the milestones: Deploy testnet v1 (beta), Deploy mainnet v1 Aug 7, 2023
@shanejearley shanejearley changed the title Finalize scalable operator selection method Finalize operator selection method Aug 7, 2023
@shanejearley shanejearley changed the title Finalize operator selection method Finalize open group operator selection method Nov 29, 2023
@shanejearley shanejearley modified the milestones: Deploy staking app, Deploy staking contracts Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants