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

When determining active set, rather than weighting the nodes by just the stake, use stake * performance #3234

Closed
jstuczyn opened this issue Mar 28, 2023 · 0 comments · Fixed by #3235
Closed

When determining active set, rather than weighting the nodes by just the stake, use stake * performance #3234

jstuczyn opened this issue Mar 28, 2023 · 0 comments · Fixed by #3235
Assignees
@jstuczyn
Milestone
2023.16 (v1.1.15)

Comments

@jstuczyn
Copy link
Contributor

No description provided.

@jstuczyn jstuczyn self-assigned this Mar 28, 2023
@jstuczyn jstuczyn added this to the week-14 (v1.1.15) milestone Mar 28, 2023
@jstuczyn jstuczyn mentioned this issue Mar 28, 2023
Merged
1 task
@jstuczyn jstuczyn changed the title When determining active set, rather then weighting the nodes by just the stake, use stake * performance When determining active set, rather than weighting the nodes by just the stake, use stake * performance Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jstuczyn jstuczyn

Labels
None yet
Projects
Core systems
Archived in project
Milestone
2023.16 (v1.1.15)
Development

Successfully merging a pull request may close this issue.

Feature/performance active set selection nymtech/nym
1 participant
@jstuczyn