From 0e62742ef5d42b4d1f4ecc2eb3ea655aa9193a67 Mon Sep 17 00:00:00 2001 From: bengtlofgren Date: Wed, 10 Jan 2024 16:28:45 +0000 Subject: [PATCH] changed most namadaw functions --- .../docs/pages/introduction/quick-start.mdx | 4 ++-- packages/docs/pages/operators/ibc.mdx | 2 +- .../networks/genesis-flow/participants.mdx | 2 +- .../operators/validators/validator-setup.mdx | 2 +- .../docs/pages/users/transparent-accounts.mdx | 22 ++++++++----------- .../transparent-accounts/multisignature.mdx | 10 ++------- 6 files changed, 16 insertions(+), 26 deletions(-) diff --git a/packages/docs/pages/introduction/quick-start.mdx b/packages/docs/pages/introduction/quick-start.mdx index c52b2ab8..8108c2f7 100644 --- a/packages/docs/pages/introduction/quick-start.mdx +++ b/packages/docs/pages/introduction/quick-start.mdx @@ -47,7 +47,7 @@ This should sync your node to the ledger and will take a while (depending on you First you will need an implicit account in order to receive tokens. You can generate one with: ```shell copy -namadaw address gen --alias +namadaw gen --alias ``` For the remainder of this introduction, let's assume your go-to alias is `stanley`. @@ -55,7 +55,7 @@ For the remainder of this introduction, let's assume your go-to alias is `stanle This will generate a new account and store it in the default keychain. You can see the account with: ```shell copy -namadaw address list +namadaw list --addr ``` {/* #TODO: ADD some output */} diff --git a/packages/docs/pages/operators/ibc.mdx b/packages/docs/pages/operators/ibc.mdx index 4282ff05..06eaf58f 100644 --- a/packages/docs/pages/operators/ibc.mdx +++ b/packages/docs/pages/operators/ibc.mdx @@ -166,7 +166,7 @@ cp ./target/release/hermes /usr/local/bin/ ### Create the relayer account On each chain, there must be a `relayer` account. The alias should be the same as `chains.key_name` in the config. On a namada chain, this can be done by running ```bash copy -namadaw key gen --alias relayer +namadaw gen key --alias relayer ``` This will generate a key for the relayer account. The key will be stored in the `wallet.toml` that is found in the [base directory](./ledger/base-directory.mdx) of the node, inside the `chain-id` folder. For example, if the `chain-id` is `namada-test.0a4c6786dbda39f786`, the `wallet.toml` will be found in `$HOME/.local/share/namada/namada-test.0a4c6786dbda39f786/wallet.toml` (on a ubuntu machine where `base-dir` has not been set up properly). diff --git a/packages/docs/pages/operators/networks/genesis-flow/participants.mdx b/packages/docs/pages/operators/networks/genesis-flow/participants.mdx index 2682b839..0836d166 100644 --- a/packages/docs/pages/operators/networks/genesis-flow/participants.mdx +++ b/packages/docs/pages/operators/networks/genesis-flow/participants.mdx @@ -21,7 +21,7 @@ This can be done through the namada cli: ```bash ALIAS="" -namadaw --pre-genesis key gen --alias $ALIAS +namadaw --pre-genesis gen --alias $ALIAS ``` After the user has entered their passwords and written down their mnemonic phrase, the namada cli will save the keys to the `pre-genesis` folder inside the [base directory](../../ledger/base-directory.mdx). diff --git a/packages/docs/pages/operators/validators/validator-setup.mdx b/packages/docs/pages/operators/validators/validator-setup.mdx index 82e3f494..908fa632 100644 --- a/packages/docs/pages/operators/validators/validator-setup.mdx +++ b/packages/docs/pages/operators/validators/validator-setup.mdx @@ -30,7 +30,7 @@ The user must first generate a key pair for their validator account. ```bash copy KEY_ALIAS="aliace" -namada wallet key gen --alias $KEY_ALIAS +namada wallet gen --alias $KEY_ALIAS ``` Now choose a name for your validator: diff --git a/packages/docs/pages/users/transparent-accounts.mdx b/packages/docs/pages/users/transparent-accounts.mdx index 6021b831..f4eec0a3 100644 --- a/packages/docs/pages/users/transparent-accounts.mdx +++ b/packages/docs/pages/users/transparent-accounts.mdx @@ -29,11 +29,11 @@ Note the use of the placeholder `keysha` for the key parameter. This is a compl ```shell copy KEY_ALIAS="keysha" -namada wallet key gen --alias $KEY_ALIAS +namada wallet gen --alias $KEY_ALIAS ``` -The derived implicit address shares the same `keysha` alias. The previous command has the same effect as `namada wallet address gen --alias keysha`. +The derived implicit address shares the same `keysha` alias. The previous command has the same effect as `namada wallet gen --alias keysha`. By default, the keys are stored encrypted. @@ -43,7 +43,7 @@ Namada wallet supports keypair generation using a [mnemonic code](https://github To generate a keypair for a default path use ```shell copy KEY_ALIAS="keysha" -namada wallet key gen --alias $KEY_ALIAS --hd-path default +namada wallet gen --alias $KEY_ALIAS --hd-path default ``` @@ -67,7 +67,7 @@ namada wallet key restore --alias keysha --hd-path default ### List all known keys ```shell copy -namada wallet key list +namada wallet list --keys ``` ## Manage addresses @@ -76,32 +76,28 @@ namada wallet key list To manage addresses, similar to keys, various sub-commands are available: ```shell copy -namada wallet address +namada wallet --help ``` ### Generate an implicit address Let's call the implicit address `accountant`: ```shell copy -namada wallet address gen --alias accountant +namada wallet gen --alias accountant ``` - -Note that this will also generate and save a key from which the address was derived and save it under the same `accountant` alias. Thus, this command has the same effect as `namada wallet key gen --alias accountant`. - - ```shell copy -namada wallet address gen --alias keysha --hd-path default +namada wallet gen --alias keysha --hd-path default ``` generates an address using a [mnemonic code](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) and [HD derivation path](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki). ### Restore the address ```shell copy -namada wallet address restore --alias keysha --hd-path default +namada wallet derive --alias keysha --hd-path default ``` ### List all known addresses ```shell copy -namada wallet address list +namada wallet list --addr ``` \ No newline at end of file diff --git a/packages/docs/pages/users/transparent-accounts/multisignature.mdx b/packages/docs/pages/users/transparent-accounts/multisignature.mdx index d363f3be..43496e87 100644 --- a/packages/docs/pages/users/transparent-accounts/multisignature.mdx +++ b/packages/docs/pages/users/transparent-accounts/multisignature.mdx @@ -16,21 +16,15 @@ Before creating an account, a user must generate at least one cryptographic `key The following method will generate such a key: ```shell -namadaw key gen \ +namadaw gen \ --alias my-key1 ``` A second key can be generated as well (which will be useful for multisigs): ```shell -namadaw key gen \ +namadaw gen \ --alias my-key2 ``` -An implicit address can also be generated: -```shell -namadaw address gen \ ---alias my-address -``` - Accounts on Namada are initialised through the following method: **Non-multisig account (single signer)**