Managing vaults

With the exception of migrating to multi-vault mode, the operations here are only applicable to a multi-vault wallet.

Migrating from v0.4 and earlier

The wallet will automatically convert the default ≤v0.4 database to a single-vault wallet. If you were using multiple, separate databases (with the deprecated --database flag), the recommended migration path is to adopt them into a multi-vault wallet. If you have a database at the default path (~/.accumulate/wallet.db or ~/.accumulate/wallet_encrypted.db), migrate that to multi-vault mode after it is automatically converted into a single-vault wallet. Once that is done, adopt your other databases into the wallet.

It is possible to maintain multiple, separate wallets but this is highly discouraged for the majority of users. The only scenario for which this is recommended is maintaining a separate wallet for use with testnets.

Migrate to multi-vault mode

The following steps will convert a single-vault wallet into a multi-vault wallet with a single vault.

Run accumulate vault migrate.
Confirm you wish to convert your wallet to multi-vault mode.
Choose what your current vault will be named.
Choose whether to encrypt the index database. Encryption is highly recommended.
- This will encrypt the vault list, making it harder to determine which files should be attacked in case a malicious actor gains access to your files.
- Future versions of the wallet may support indexing of keys, accounts, etc. Encrypting these would prevent information leakage.
If you are encrypting your wallet, enter a passphrase.
Done!

GUI

This feature is not yet supported in the GUI

CLI

Create a new vault

Run accumulate vault create [name]
Choose whether to encrypt the vault. Encryption is highly recommended.
If you are encrypting your wallet, enter a passphrase.
Choose to create a new mnemonic or import an existing one. Skipping this step is not recommended, as most functions of the wallet require a mnemonic.
Done!