-
Notifications
You must be signed in to change notification settings - Fork 214
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
Smesher with many small proposals/rewards #5137
Labels
Comments
we have minimal active weight parameter in the config to prevent such issue, we should raise it to known weight in current epoch. additionally there is pending issue of not rewarding atxs in hare that were received too late #4942 , it will disincentivize smesher from keeping his node offline before the start of the epoch |
bors bot
pushed a commit
that referenced
this issue
Oct 20, 2023
closes: #5137 - added a tool that can be used to read db and compute total weight of atxs in the latest epoch - activeset weight configured as a sorted array of tuples (epoch, weight). components select latest tuple that match epoch based on timing of usage
bors bot
pushed a commit
that referenced
this issue
Oct 20, 2023
closes: #5137 - added a tool that can be used to read db and compute total weight of atxs in the latest epoch - activeset weight configured as a sorted array of tuples (epoch, weight). components select latest tuple that match epoch based on timing of usage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we let smeshers choose their own active sets and correspondingly their eligibility slots for proposals each epoch, which can result in a smesher submitting many proposals that each receive only a tiny reward. This appears to be happening with one smesher: 0x318cceb3df7174d42b582ffb4ccfd6ef6fbce4def8aee342c33e264ff78909f8
Example reward: https://explorer.spacemesh.io/rewards/6524347792abdc943072d99c
Coinbase: sm1qqqqqq8q9hxmhdqnktagjx7r65cf3vjfk79knvqnzy7yg
CC @dshulyak
The text was updated successfully, but these errors were encountered: