aptos-core icon indicating copy to clipboard operation
aptos-core copied to clipboard

[Feature Request] Being Able to Move StakePool.pending_active -> StakePool.inactive?

Open PaulFidika opened this issue 2 years ago • 1 comments

I noticed that in the stake.move module, there is a way to move StakePool.pending_inactive -> StakePool.active; the function is called reactivate_stake.

However, there is no function that can move StakePool.pending_active -> StakePool.inactive. So basically, once you put AptosCoin into the pending_active balance, there's no way to take it back out again, other than to wait for the next epoch to occur, have the stake be moved into active, and then manually move it to pending_inactive, wait for pending_inactive_secs to expire, and then wait for the next epoch-boundary to sweep the money back into inactive. This could be a 14 - 28 day process (dependent upon the pending_inactive_secs value).

I could create a function that does this easily, however looking at the stake module makes me feel like this was an intentional omission. In the sense that allowing people to put lots of pending-stake in the current epoch, and then remove it right before the next epoch, might present some security risk. There seems to be a lot of logic around trying to predict voting power in the next epoch and making sure it doesn't increase too rapidly.

Thoughts?

PaulFidika avatar Sep 10 '22 17:09 PaulFidika

This issue is stale because it has been open 45 days with no activity. Remove the stale label or comment - otherwise this will be closed in 15 days.

github-actions[bot] avatar Nov 07 '22 03:11 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove the stale label or comment - otherwise this will be closed in 15 days.

github-actions[bot] avatar Dec 24 '22 01:12 github-actions[bot]

This is something we have on our list for implementation in Q1'23

movekevin avatar Jan 04 '23 08:01 movekevin

This issue is stale because it has been open 45 days with no activity. Remove the stale label or comment - otherwise this will be closed in 15 days.

github-actions[bot] avatar Mar 14 '23 01:03 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove the stale label or comment - otherwise this will be closed in 15 days.

github-actions[bot] avatar Apr 29 '23 01:04 github-actions[bot]

This is intended. pending_active also has voting power(check here). So it should freeze until the next lockup period.

xindingw avatar Apr 29 '23 03:04 xindingw