./zwallet vp-addcommand which require specific parameters. To view parameters use the
--ddestination flag by which certain amount of tokens gets transferred to receiver's wallet requires values in the form of wallet client_id: amount of tokens. The destination
--dparameter has to be repeated for transferring to more than one destination whereas lock duration and minimum locked tokens for the vesting pool is required and has to match specified vesting pool config limit. Also, the number of tokens locked should match or more than the sum of destination amounts specified to create a read pool.
./zwallet vp-listcommand is used to display the vesting pool list for a given wallet. Parameters can be viewed using
catcommand. If not specified it will use the wallet at
vp-infocommand. Check the troubleshooting section for solution.
./zwallet vp-infocan be used to view information for a particular vesting pool. Parameters can be viewed using the
./zwallet vp-info --help
vp-infocommand. Check the troubleshooting section for resolution.
./zwallet vp-triggercommand is used to instantly transfer vesting tokens to destination wallets before expiration time. Parameters can be viewed using the
./zwallet vp-trigger --helpcommand.
vp-listcommand. To demonstrate the
vp-triggerfunctionality we will consider a vesting pool which has some vested tokens to transfer to destination wallets. Here is
vp-infoof a vesting pool before triggering.
vp-triggeron this pool and transfer the tokens right away.
vp-infocommand the Vesting pool info should not show tokens in
.zwallet vp-unlockcommand can be used to unlock tokens from a vesting pool by both the owner and destination wallets. Note that owner can only unlock tokens which are not yet vested while receiver can only unlock vested tokens.
./zwallet vp-unlock --help.
vp-unlockfunctionality we will do unlocking of tokens from owner wallet side then the destination side.
can unlockvariable above. Use
vp-unlockto unlock that.
./zwallet vp-stopcommand is used to stop transferring of tokens to a destination wallets. The owner can stop vesting for a destination and unlock the rest of tokens not yet vested.
./zwallet vp-stop --helpcommand.
--d(client _id of the destination wallet) is required. Both can be fetched using the
vp-stopfunctionality we are considering the vesting pool which has some tokens vested for destinations. Here is a
vp-infofor that pool.
--dflag would be the client_id mentioned in the
vp-info. Here is a output of vesting pool after
./zwallet vp-deletecommand is used to delete a created vesting pool and unlock the tokens not yet vested. Parameters for
vp-deletecan be viewed using
./zwallet vp-delete --help.
vp-deletefunctionality lets consider a vesting pool with some vested tokens. Here is a
vp-infofor that pool:
vp-infocommand and you will see this response