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

Partial Set Security: Introduce new filters for validators #1781

Closed
Tracked by #853
insumity opened this issue Apr 10, 2024 · 0 comments · Fixed by #1830
Closed
Tracked by #853

Partial Set Security: Introduce new filters for validators #1781

insumity opened this issue Apr 10, 2024 · 0 comments · Fixed by #1830
Assignees

Comments

@insumity
Copy link
Contributor

insumity commented Apr 10, 2024

Introduce new filters for validators so we can have the following:

  1. Cap validator power. For example, we can cap validators' power to 1% which means that if a validator has 3.7% power on the Hub, only 1% of this power would validate the consumer chain.
  2. Cap validator set. A consumer chain might desire that at most m validators can validate it at any point in time.
  3. Allowlisting/Denylisting. A consumer chain can decide on which validators are allowed to validate it and which are not.

The first filter can work irrespectively of whether the chain is Top N or Opt In. With the other two filters this is not the case. For instance, can we cap the validator set with Top N, etc.

@insumity insumity changed the title Introduce active-set capping Introduce new features Apr 10, 2024
@insumity insumity changed the title Introduce new features Introduce new filters on the opted-in validators Apr 10, 2024
@insumity insumity self-assigned this Apr 10, 2024
@insumity insumity changed the title Introduce new filters on the opted-in validators Introduce new filters for validators Apr 10, 2024
@insumity insumity changed the title Introduce new filters for validators Partial Set Security: Introduce new filters for validators Apr 10, 2024
@insumity insumity linked a pull request May 1, 2024 that will close this issue
21 tasks
@insumity insumity closed this as completed May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant