* Adapted vault display to have a space before address value (for derivations); which fixes the incorrect selection when double-clicking an address in the terminal

* Added a CHANGELOG.md file
* Adapted config.md example of vault usage
* Adapted some of the command descriptions to be more consistent

   * Now checking if GcliError Input message was for doing "ctrl+c" or "Esc" key in a prompt; in wich case we terminate the execution with the message.
   * Small correction in vault_account::compute_suri_account_tree_node where it's better to return GcliError instead of panic using unwrap if the password was incorrect.
* Renamed `clap` arguments "value_name" in different places where it wasn't clear what kind of value was expected.
   * Using "ADDRESS" everytime we expect an AccountId
   * Using "USERNAME" everytime we expect a Username (most were requesting "TARGET")
* Small corrections in `clap` help messages for `vault derive`
* Added print of selected Vault item when using vault::try_fetch_key_pair method; just before requesting it's associated password (whenever we will try to sign for an action mostly)

* Added support to show g1v1 base58 public key from (ed25519) ss58 address, AccountId, ed25519::Public with tests for those
* Renamed SecretFormat.Cesium to SecretFormat.G1v1
   * Adapted `clap` display help to reflect the change
   * Still supporting using "cesium" as "-S" secret format argument and mapping it to SecretFormat.G1v1
* Adapted display of vault
   * Changed column "Format" into "Crypto", showing either "ed25519" or "sr25519" instead of "cesium" or "substrate"
   * Adapted 1st row header to "SS58 Address/G1v1 public key"
   * For "ed25519" account, showing a 2nd row just below containing "└ G1v1: <base58 public key value>"
   * Adapted test cases and added a G1v1 account example
* Adapted (String) Display of vault_account to include "g1v1_pub_key" value when crypto_scheme is Ed25519

Co-authored-by: Hugo Trentesaux <hugo.trentesaux@lilo.org>

Co-authored-by: Hugo Trentesaux <hugo.trentesaux@lilo.org>

Co-authored-by: Hugo Trentesaux <hugo.trentesaux@lilo.org>

   * Put back simple `address` and `name` arguments in main.rs (with conflicts_with statement to prevent their usage at the same time)
   * Declared conflicts between indexer <=> no-indexer, indexer <=> network, url <=> network
   * Kept AddressOrVaultNameGroup args for vault usage since it's the only way to define one required arg within a group cleanly

* Relaxed "update" restrictions in vault_account.rs before_save checks

* Started to investigate being able to make subkey command and trying to use sp_core::crypto::CryptoType instead of custom KeyPair
* Big refactoring to have all in one vault_account db table; using recursion through `parent` property
* Added AccountTreeNode object and related methods to be able to more easily handle whole tree of accounts
* Removed now unused vault_derivation
* Replaced remaining usages of `rpassword` and removed the dependency
* Added `indoc` dependency to support cleaner display of multi-line strings in tests

Small cleanup for data's db connection; adding method connect_db that returns a &DatabaseConnection (or panics with explanation message)

Also changed some methods visibility so only connect_db is visible for usage.

Made an extra check of derivation path to make sure it's not linking to the same SS58 Address as "root" suri when doing `vault import|migrate`

* Cleaned-up code in several places
* Now retrieving secret value in "substrate uri" format from the different prompt_xxx_and_compute_keypair methods

* Simply using "name" for the name given to an SS58 Address in the vault

* Adapted to have more coherent commands descriptions and added `long_about` more detailed description for `import` and `derivation`
* Added the `vault list for` command
* Added display of "format" of <Root> derivations in all `vault list` commands
* Only allowing derivations for format "substrate" and "seed"

* Added "/.idea" exclusion in .gitignore (for when using JetBrains IDEs)
* Added dialoguer dependency for easier user input handling (see in inputs.rs)
* Added sea-orm dependency to allow having DB entity mappings and use a local sqlite file database
* Added rstest test dependency for parameterized tests support
* Added derivation tests for each SecretFormat (including cesium v1 key derivation, using sp_core::ed25519::Pair)
* Made a lot of changes to add vault_account and vault_derivation db tables to persist vault keys & derivations
* Added support for KeyPair::Ed25519 linking to sp_core::ed25519::Pair which can be created from secret seed retrieved from nacl::sign::Keypair (which is created from cesium id + secret)
** This was necessary to allow deriving keys from "cesium v1" keys (to be reviewed - it might be a bad idea to permit that from a security point of view)
* Only kept original (substrate) keyfiles support for migration (use "vault list-files" and "vault migrate")
* Added possibility to give either "-a" Address or "-v" Vault Name as general option
* Added extra commands in Vault
** list-files: (deprecated)List available key files (needs to be migrated with command "vault migrate" in order to use them)
** migrate: (deprecated)Migrate old key files into db (will have to provide password for each key)
** 'list' now has sub-commands 'all' or 'root' to show all keys or only root keys (without derivation path)
** use: "Use specific vault key (changes the config address)", which will have the same behaviour as `gcli <-a <Address>|-v <VaultName>> config save` (left a FIXME in there to review)
** derivation: Add a derivation to an existing (root) vault key
** rename: Give a meaningful vault name to a vault key or derivation
** remove: Remove a vault key (and potential derivations if it's a root key)
* Had to bubble up "await" and "async" in a lot of places
* ...

on runtime 802
changed crypto types

closes #35

* working dockerfile

* wip dockerfile

TODO make duniter-polkadot-sdk repo lighter to avoid long download time in docker build

(cherry picked from commit 5f4b716f)

* update subxt and polkadot sdk

Moul authored 11 months ago and poka committed 11 months ago

* identity show: switch received and issued certs position

Make more sense to me, you receive from the left and issue to the right

That’s how they are presented in Cesium and Silkaj

* also for smith cert

* get cert count from cert meta

poka authored 1 year ago and Hugo Trentesaux committed 1 year ago

* update schema for enums

* update to hasura endpoint

* more macro

* Ignore non_camel_case_types in vscode stage

Are we carring about conventions ?

* 2 macros to rule them all

* example on how to deserialize

* adapt graphql request to Hasura engine

* improve online smith command

* start indexer refac

* v0.2.8

* improve current block display

* clippy fmt

* display names of migrated identities in tech members

* minor indexer improvements

* add finalized / latest info

* improve readability of indexer check

* move into function

* remove unnecessary complexity

* wip add phrase generation

* prepare 0.2.7 release

* remove dep

* add predefined keys and update doc

* wip add save from cmd line

* improve error management

* allow to store password-protected secret

* wip use rage for password-encrypted keys

* wip poc for keystore