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

Reduce the committee size as a way to reduce the bar for power participation percent #801

Open
masih opened this issue Dec 16, 2024 · 2 comments

Comments

@masih
Copy link
Member

masih commented Dec 16, 2024

Came up in 1:1 with Molly:

  • We already use the scaled power to determine participation in f3 (65535)
  • What would happen if the power is scaled over a smaller value such that the effective committee size is reduced per instance.
  • This does not directly reduce the need for higher participation power percent, but reduces the number of participants.
    • The participants left would have higher power portion over the whole network and hopefully better connectivity.
  • The catch of course is higher sensitivity to nodes with more power.
@masih
Copy link
Member Author

masih commented Dec 16, 2024

What we probably should is to make this a manifest param for experimentation

@Stebalien
Copy link
Member

This gets a bit tricky because SPs have multiple miner actors. If we did this, we'd likely want delegation of power which would, IMO, fix the issue entirely. Unfortunately, delegation leads to centralization which may not be a huge issue given that we're only finalizing blocks but I know @Kubuxu is not a fan of this.

@BigLep BigLep added this to the M2: Mainnet Passive Testing milestone Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

3 participants