The most interesting feature delivered in this release is the alarm management in TUI (text-based user interface). It informs a user about important and potentially dangerous events related to a user’s account or to the user’s watched accounts.
We updated the TUI (text-based user interface) framework and corrected some issues (check the issue list at the bottom of the article).
In CLI (command line interface) we extended the recurrent transfer of possibility to define them in HBD - a missing feature from a previous release.
The alarm management
The following events trigger alarms:
a. related to user recovery account:
- recovery account is on the warning list,
- changing recovery account process in progress (a user changes a recovery account),
- pending account recovery request exists(a recovery account creates a request) - coming soon.
b. related to owner key:
- owner key change in progress - coming soon.
c. related to governance:
- governance voting expiration,
- governance votes never created,
- declining voting rights in progress.
d. related to recurrent transfer:
- recurrent transfer exists - coming soon,
- lack of funds for the next transfers - coming soon,
- error occurs while attempting to send a transfer - coming soon.
Where are the alarms?
You can find alarms by clicking Details next to the account name. You can check the list of alarms related to a working account or watched accounts.
Account details view
The account details view is divided into three tabs. The first tab contains information about alarms. The second and third ones are not implemented yet.
The alarm view
The alarm info view contains information on why the alarm was triggered and how to fix it. If available, there is also information about the expiration date and a link to the view for resolving it. Note that when the account is watched, you can't fix the alarm, even if the solution in clive is possible.
A user may also mark an alarm as harmless - the alarm marked as harmless will not be displayed anymore.
The recurrent transfer - extension
In this release, it is possible to define a recurrent transfer in HBD. It works the same as for HIVE - see our previous post
Example:
clive process transfer-schedule create --amount "3 HBD" --repeat 2 --frequency 2d --to bob --password alice --sign alice_key
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.12
TL;DR
docker run -ti hiveio/clive:v1.27.5.12
Congratulations @thebeedevs! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 100 replies.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts: