This allows us to over-ride the built in OCLIF JSON flag group which
exists at https://github.com/oclif/core/blob/213e9203fd7f0f5aaffdcc9eb28d2828f7679373/src/util/aggregate-flags.ts#L4C1-L7C3

This should make all the RPC flags show up in their own section in
--help now.

Because it defaulted to true instead of undefined.

It will show an example to see the native currency information

This creates a standard in laying our command code.

I don't think anyone used this, and it's confusing showing up in the
list.

In an attempt to make them follow the style guide

* feat(rust): Add xchacha20poly1305 functions

* chore(rust): Add license header

* chore(rust): Add audit for cpufeatures

* chore(rust): Add audit for password-hash

* chore(rust): Move crates to exemptions

* refactor(rust): Use NONCE_LENGTH const

…1305 (#5217)

* feat(rust,rust-nodejs): Add napi `encrypt` function for
xchacha20poly1305

* chore(rust): lint rust

* feat(rust,rust-nodejs): Add napi `encrypt` function for
xchacha20poly1305

* chore(rust): lint rust

* feat(rust-nodejs): Add napi `decrypt` xchacha20poly1305 function

* feat(ironfish,rust-nodejs): Add EncryptedAccount class

* chore(rust-nodejs): lint rust

* chore(rust-nodejs): cargo clippy fix

* feat(ironfish): Add test for invalid passphrase

* feat(ironfish): Add error type for failed decryption

* feat(ironfish): Save encrypted accounts in the wallet

* feat(ironfish): Revert storing id

* test(ironfish): Fix account value test

* feat(ironfish): Add `encrypt` method for account

* fix(ironfish): Remove extra KEY_LENGTH constant

* test(ironfish): Fix serialization test

* test(ironfish): Update fixture

* feat(ironfish): Fix encrypt test for account

* update migrations descriptions, migrations list supports json

* use waitForOpen instead of a try/catch for DB

Making these commands consistent with our style guide

…5261)

This adds optional new table output to the wallet command

You can now use `wallet:use --unset` to unset the default account

Previously, the RPC wasn't receiving this parameter properly due to it being
left out of the yup schema. Add it to the schema so that the flag is properly
passed through.

This makes it more clear that it expects a name of an account

* feat(ironfish): Add lock to wallet

* test(ironfish): Add test for no accounts

…on (#5274)

* Add `wallet:transactions:delete` command

* remove remoteflags

* feat(ironfish): Add unlock to wallet

* feat(ironfish): Relock if unlock throws an error

This moves various UI components I've seen into the CLI's UI folder. It
moves select prompts and other things from utils into the UI if they are
related to a UI component.

Also convert the output to a card

adds a workflow input for `AWS:{BRANCH}` and adds a deploy step for deploying
the branch-named image to our AWS ECR repository

)

…5300)

* feat(ironfish): Remove cached accounts when encrypting/decrypting

* feat(ironfish): Check if wallet is encrypted when calling setAccount

Also remove things that are not visible in `wallet:status`

* Add new helper to select a user account

* Upgrade commands to use useAccount

* Add the ability to delete a transaction to the wallet and RPC

* add unit tests for wallet and rpc

And rename or delete command specific competing flags. These command
flags had chars that were not consistent across commands like
"confirmations". It's best not to have command specific single letter
char shortcuts.

This does nothing as all flags are by default required: false.

This makes the user type in the account name they are trying to delete

…one test (#5324)

* feat(cli): Add `wallet:encrypt`

* Update ironfish-cli/src/commands/wallet/encrypt.ts

Co-authored-by: mat-if <[email protected]>

---------

Co-authored-by: mat-if <[email protected]>

* feat(cli): Add `wallet:decrypt`

* Update ironfish-cli/src/commands/wallet/decrypt.ts

Co-authored-by: mat-if <[email protected]>

---------

Co-authored-by: mat-if <[email protected]>

* feat(cli): Add `wallet:unlock`

* Update ironfish-cli/src/commands/wallet/unlock.ts

Co-authored-by: mat-if <[email protected]>

---------

Co-authored-by: mat-if <[email protected]>

…ounts (#5333)

…5344)

…5352)

* feat(ironfish): Add passphrase to import account for encrypted dbs

* feat(ironfish): Move valid passphrase check to db

…dress (#5356)

Also logs if the transaction is not accepted or broadcast when calling the CLI chain:broadcast command.

* feat(ironfish): Add passphrase to reset account methods

* feat(ironfish): Fix validation for passphrase

* feat(ironfish): Update return type

…5357)

…5355)

)

a multisig account generated using a Ledger device will have a access to the
participant identity, but not the secret or keyPackage

uses a separate interface for MultisigHardwareSigner to cover this case and
expands the MultisigKeys type to cover this interface

the distinct interface allows us to store multisig keys for the Ledger case
without a database migration for existing multisig keys