The new release is ready. The Hive Power management is now available in the TUI (text-based user interface). We also added a small, but useful functionality - Known account
. The framework on which our application is based - Textual, has also been updated.
TUI Hive Power management
In the previous release, we delivered:
- make a power up - operation
transfer_to_vesting_operation
The more information you can find in the previous post
In this release the following operations are available:
- make or cancel a power down (
withdraw_vesting_operation
), - set or unset withdrawal routes (
set_withdraw_vesting_route_operation
), - delegate or remove delegation of hive power (
delegate_vesting_shares_operation
).
All the operations listed above work the same as any other operation in Clive, so you may:
- Fast broadcast,
- Add to cart,
- Finalize the transaction.
TUI Hive Power management - power down (withdraw_vesting_operation
)
The Power down operation converts HP/VESTS into HIVE. The withdrawal is done in 13 parts during 13 weeks starting one week after this operation is included in the blockchain.
On the Power down tab, you may create a new or cancel pending power down (withdraw_vesting_operation
). While creating you might choose between HP or VESTS. If you select HP, it will be converted to VESTS with the displayed rate.
If you enter the amount, Clive shows information about the calculated amount of each of the 13th weekly withdrawals. The already set withdrawal vesting routes are also shown on this view.
In order to cancel the existing power down, the withdraw_vesting_operation
with an amount of zero is created.
There can be only one active power down process. If a user creates a new power down when the old one is still in progress, the old power down will be canceled and will be replaced by a new one.
TUI Hive Power management - set withdrawal routes ( set_withdraw_vesting_route_operation)
On the Withdraw routes tab, you may set or remove existing withdrawal routes, so you may decide where and how much percent of Hive should be transferred during each next power down withdrawal. You may also decide that the Hive may be immediately converted to Hive Power by selecting the “Auto vest” box.
This operation may be created at any moment, independent of any pending power down operation, even if no power down operation is currently in progress. You may set up to 10 accounts.
TUI Hive Power management - delegate hive power ( delegate_vesting_shares_operation)
The operation delegate_vesting_shares_operation allows delegating an amount of vesting_shares to a delegatee account. The vesting_shares are still owned by the delegator, but the voting power and resource credit are transferred.
When a delegation is removed, the delegated vesting shares are frozen for five days to prevent voting twice.
The minimal amount of vesting shares is 1/3 of the fee for creating a new account.
On the Delegate tab, you may add a new or remove an existing Hive Power delegation. If you have created a delegation to the delegatee and create a new delegation for him, the old one will be replaced by the new one.
If you have any Hive Power delegations already, they will be listed on this view and you will be able to remove them.
Known account
We added a simple but useful feature to protect users from a very basic misspelling.
Next to all fields where you provide the account, there is a checkbox labeled Known?
.
If you enter an account name and mark the account as known, the information will be saved and the next time you fill in an account name, Known account
will be displayed, otherwise you’ll be warned about an unknown account.
So if you enter an incorrect account name, text unknown account
will be displayed.
Complete list of corrected issues
More info about running Clive can be found here: Clive - alpha release. Please make sure you are using the most recent version: v1.27.5.8
TL;DR
docker run -ti hiveio/clive:v1.27.5.8