Clive Updates - the first step to an encrypted profile

The two main goals described in the previous post are still valid: making Clive more user-friendly and implementing encrypted profiles. Both goals are in progress - you can read about them below. Additionally, we prepared a script that runs the CLI (command-line interface) more easily.

Changes towards encrypted profiles

To improve security we are working on the encrypted profile functionality. Therefore, before you start working with Clive you must enter a password - log in to your profile. All data stored in your profile, such as working and tracked accounts, and key aliases will be stored in an encrypted profile file. This requires many changes to both the CLI (command line interface) and TUI (text-based user interface):

TUI - new screen allowing profile selection and creation when logging in,
TUI/CLI - changes in locking and unlocking the profile,
TUI/CLI - stored data encryption.

The functionality will be delivered in two main parts: the first part - TUI-related changes, but without encryption, and the second part - CLI-related changes with profile data encryption.

We are changing the way we store data so if you have already created a profile, you will have to recreate it. This inconvenience is related to changes in the next release.

We have finished the first part of the work:

While starting Clive you have to select a profile and enter the password.

When you click on the wallet state indicator presenting: i.e. UNLOCKED status, your profile will be locked and you will have to enter a password to unlock a profile. The dashboard is no longer accessible without entering a password

Additionally, you can now easily switch between multiple profiles in the TUI:

To make Clive more user-friendly

We are still working on making Clive more user-friendly. In this release we changed behavior on views with operations: transfer, transfer to/from savings, power up, power down, set the withdraw routes, and delegate. There are the following changes:

The fast broadcast was removed - it is unnecessary now as the cart and transaction summary were combined into a single page.
We added an Add to cart button, but you can still use bindings if it is more convenient for you.
If you press the Add to cart button or Enter, the operation is:
- added to cart
- the application remains on the same operation screen
- all data like values entered into input fields is set to default values, also the receiver of transfer and power up/down is automatically set to your working account
- the The operation was added to the cart notification is displayed.

A new script to run the CLI Clive easier

We created a custom Bash script to launch the Clive CLI more easily in a dockerized environment. The script for running the TUI is already available and I wrote about it here

Just like the previous script, this script also maps host directories to the Docker container and allows for persistent storage of user profiles. It allows for easy use of the CLI.