You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2023. It is now read-only.
Once stakers start the unbonding, their unbonded funds will remain locked during the unbonding period. During this period, these funds don’t generate any rewards neither can they be used for payment, transfer, etc.
This is normal and expected behavior.
However, we want to provide users an option to re-bond their unbonding chunks.
This allows them to continue earning rewards in dapps-staking and returns their unbonding chunks to locked state.
Details
this is only applicable for users who have unbonding chunks
it doesn't matter whether chunks have completed the unbonding period or not
when used, all chunks should be consumed and re-bonded
user can only select one target contract on which they want to re-bond
Required Tasks
implement a new extrinsic call rebond_chunks (or something similar)
unit tests
runtime benchmarks code
Estimated done.
<>
Dependencies
This task has no dependencies but will require UI support to be utilized from the portal side.
The text was updated successfully, but these errors were encountered:
Description
Once stakers start the unbonding, their unbonded funds will remain locked during the
unbonding period
. During this period, these funds don’t generate any rewards neither can they be used for payment, transfer, etc.This is normal and expected behavior.
However, we want to provide users an option to re-bond their unbonding chunks.
This allows them to continue earning rewards in dapps-staking and returns their unbonding chunks to locked state.
Details
Required Tasks
rebond_chunks
(or something similar)Estimated done.
<>
Dependencies
This task has no dependencies but will require UI support to be utilized from the portal side.
The text was updated successfully, but these errors were encountered: