Why do we create Clive?

Do you use cli_wallet? It is an old tool to manage operations; you can send a simple transaction using it or create an application based on it. It is secure, but it is old and really hard to use.
We wanted to create an application as powerful and secure as cli_wallet but written in a modern way and with a more user-friendly interface.
Clive doesn’t store your private keys; they are saved in a separate application - Beekeeper, which is asked by Clive to sign the transaction without a need to extract your private key from the storage.
Clive is written as a console-based application. Thanks to that, the hardware requirements are very low; the application can be used via local terminal or SSH and it is very easy to containerize.
Clive can be used in three ways:

• as TUI (text-based user interface) - you can use it by mouse clicking, as with many other desktop or web applications.
• as an internal command line - it allows for controlling any phase of the transaction creation process: starting from its definition, through signing (in both online and offline mode), and finally, broadcasting.
• as a batch tool - designed for shell scripting and provides good integration with Python.

Why is Clive for you?

• It is easy to use - Clive TUI displays a lot of useful information and provides functions accessible both by using a keyboard or a mouse.
• It warns you of specific events occurred on your account (or friends' accounts which you might only want to observe).
• It is secure - after initial keys import, it does not have access to your private keys
• It is cross-platform - due to Python-based implementation (plus prepared Docker environment), we can easily run it on any system (i.e. Windows or Linux).
• It is suitable for advanced tasks since it has a batch mode.

What are our plans?

We plan to deliver the following functionalities step by step and ultimately allow you to use the complete first version of Clive.
The first version will contain the following functionalities:

1. Support for the operations requiring active authority:

• Transfer (already delivered)
• Savings management (transfer to savings, transfer from savings, canceling a transfer from savings) (coming soon)
• Governance (vote for proposals, vote for witnesses, set a proxy)
• Hive Power management (Power Up and Power Down)
• Recurrent transfer

2. Watched account management:

• Allow you to stay up-to-date on the important changes (balances, savings, account updates) of defined watched accounts
• Allow you to add, remove, and customize the order of watched accounts

3. Batch mode - all operations that are available in TUI.

4. Internal command line - all operations that are available in TUI.

Your feedback is invaluable and always welcome.