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
Introduce the unvest ACTION to enable the revocation of unallocated vested staked tokens from a designated account that meets specific vesting preconditions set by the system contract. This action requires the return of these tokens to the eosio system account.
/** * Facilitates the removal of vested staked tokens from an account, ensuring that these tokens are reallocated to the system's pool. * * @param account - the target account from which tokens are to be unvested. * @param stake_net_quantity - the amount of NET tokens to unvest. * @param stake_cpu_quantity - the amount of CPU tokens to unvest.*/
[[eosio::action]]
voidunvest(const name account, const asset stake_net_quantity, const asset stake_cpu_quantity);
Preconditions
System authentication through require_auth(eosio) is mandatory.
The stake_net_quantity must not surpass the net_weight attributed to the account in userres.
The stake_cpu_quantity must not exceed the cpu_weight linked to the account in userres.
The unvested tokens will be transferred directly to the eosio system account.
Normal unstaking periods will be disregarded during this process.
The voting weight associated with the account will be recalibrated subsequent to the token unvesting.
Purpose
Introduce the
unvest
ACTION to enable the revocation of unallocated vested staked tokens from a designated account that meets specific vesting preconditions set by the system contract. This action requires the return of these tokens to theeosio
system account.Feedback provided by
unvest
ACTION SpecificationPreconditions
require_auth(eosio)
is mandatory.stake_net_quantity
must not surpass thenet_weight
attributed to theaccount
inuserres
.stake_cpu_quantity
must not exceed thecpu_weight
linked to theaccount
inuserres
.eosio
system account.References
changebw
The text was updated successfully, but these errors were encountered: