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

Extend desirability function to consider oversaturated pools #1828

Closed
ilap opened this issue Sep 2, 2020 · 2 comments
Closed

Extend desirability function to consider oversaturated pools #1828

ilap opened this issue Sep 2, 2020 · 2 comments

Comments

@ilap
Copy link

ilap commented Sep 2, 2020

Desirability function is based on the assumption of the Nash equilibrium, and therefore does not consider the possibility of the over-saturation of the pools.
As a consequence, an over-saturated pool will have the same desirability, and therefore ranking, than any non- or fully saturated pool.

Though, I understand the logic of the decision, but I think the desirability and therefore the ranking should consider the over-saturated pools to indirectly incentivase the users to delegate to the non-saturated pools.

This new addition could be considered as some max threshold i.e. max 100% of the desirability, which depends only on the level of the oversaturation of the relevant pool.

Monetary epansion

This can be very easily implemented in the haskell code by slightly modifying these three function belows:

@ilap
Copy link
Author

ilap commented Sep 3, 2020

I do not think it is necessary as the non-myopic reward would consider the oversaturated stake later anyway.
But, it would be a nice to have feature for checking the oversaturation at the ranking/desirability part too and not just in the non-myopic reward, to allow some others to be fit in the k number of pools instead of an over-saturated one.

@nc6
Copy link
Contributor

nc6 commented Sep 8, 2020

I think the sensible thing here is to follow the CIP: https://github.com/cardano-foundation/CIPs/blob/master/CIP1/CIP1.md

The current ranking scheme is operating as designed; a change to the design needs to be proposed and considered more widely. Issues here are more for things we know we want to change!

@nc6 nc6 closed this as completed Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants