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

Split VNs into exact size committees #821

Open
Cifko opened this issue Dec 6, 2023 · 1 comment
Open

Split VNs into exact size committees #821

Cifko opened this issue Dec 6, 2023 · 1 comment
Assignees

Comments

@Cifko
Copy link
Contributor

Cifko commented Dec 6, 2023

No description provided.

@Cifko Cifko self-assigned this Dec 6, 2023
@Cifko
Copy link
Contributor Author

Cifko commented Dec 6, 2023

The solution for this is not decided yet. We have a outstanding PR #803 that makes the committee size +-1 committee_size. But the committee range is not uniform now.
Another discussed ideas

  • the shard key will be just order in which the VNs are assigned to the buckets. Bad think is that a lot of VNs will move from one committee to another on epoch change.
  • changing the shardid of each VNs to fall into a desired bucket. This is probably not doable because during the VN registration we don't know the final number of buckets when the epoch change (many VNs can still be registered). Even if you find a way to construct the shardid somehow. And noone register in the next epoch, some VNs can be invalid in the next epoch (VN registration validity passes for them). You would have to move the existing VNs from their current committees to somewhere else to achieve balance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Selected for development
Development

No branches or pull requests

1 participant