Changing the new configuration of the node-> What to do with existing delegations

teonite / casper-node

Reference client for CASPER protocol

https://casper.network

Apache License 2.0

0 stars 0 forks source link

Changing the new configuration of the node-> What to do with existing delegations #5

Open przemyslaw opened 9 months ago

przemyslaw commented 9 months ago

We can foresee the following scenarios:

delegators will auto-accept the new conditions (current behavior) - thus, they can get undelegated if they’re not within the new delegation limits
delegators will be left with their original delegation terms until any delegation/redelegation/undelegation happens

We've decided to implement undelegating those out of limits

wojcik91 commented 7 months ago

This relates to setting validator-level delegation limits. For now we agreed to implement forced undelegation as part of https://github.com/teonite/casper-node/issues/4.

This in effect means that if a validator sets a delegation limit and some delegator stakes are outside the limit, those delegators will be automatically unstaked (following a normal undelegation flow with a delay) before the next auction is run.