-
Notifications
You must be signed in to change notification settings - Fork 51
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
delegators those overdelegate #69
Comments
Enforcing proper behaviour according to overdelegation is important. Over-delegation hurts the baker as it ruins his statistics for the important rankings. Partial rewards from the overdelegation should be payed to the baker. We have to check which was the last address that did the delegation and caused the over-delegation. A problem: This can not only happen with a new delegation but also with stocking up on an already delegating address by increasing the funds. The behaviour needs to be clearly documented. |
Baking config (yml) file can be used to select payment matrix. Do you think this is essentials for bakers? |
It is not easy to keep track of delegations. Tzscan creates a list of delegations. This can be used for tzscan backend. What about rpc backends? |
I wonder how can I find this by hand, like if I go to an explorer will I be able to see this? As I see it, for now, if it's a new delegation, the easiest would be to give the new delegation 0% from its rewards. |
of course you can see. |
This issue will resolve itself with Tenderbake I think. Check new specification |
Currently, rewards are shared among all delegators. If the delegate is over-delegated this is not desirable for delegators.
It is necessary to implement a mechanism to avoid paying to delegators those over-delegate.
The text was updated successfully, but these errors were encountered: