Skip to content
Available on private testnetTestnet: yesMainnet: Not availableSoftware: Core bad4a06ea · protocol pqwerai-v8-testnet/1Updated

Accounts and backup

Your account is an Ethereum-style key pair. The private key is kept in an encrypted keystore file on your PC and is only ever decrypted for a single signing call. This page covers every account and backup task.

Create or import an account

The setup wizard (first start) and Settings → Accounts both let you:

Action What happens
Create a new account A fresh key is generated and encrypted under your password.
Import a private key Paste a raw 0x… private key; it is encrypted into a keystore.
Import a V3 keystore Load a Web3 Secret Storage V3 file (for example one made by pqwerai-cli).
Import from a backup Restore accounts from a wallet backup file (see below).

You can hold multiple accounts, give each one a label, and switch between them. Keystores created by pqwerai-cli are byte-compatible and can be imported and used to sign here, and vice-versa.

Keystore format

Keys are stored as Web3 Secret Storage V3 (scrypt N=2¹⁸, AES-128-CTR, keccak MAC) via Nethereum — the same format as go-ethereum and pqwerai-cli. This is why a keystore moves between the GUI, the CLI and Core without conversion.

Change your password

Settings → Accounts → Change password re-encrypts the keystore under a new password. The private key is never written out in the clear during the change.

Remove an account

Removing an account moves its keystore file aside — it is never deleted outright. If you remove an account by mistake, the file is still on disk and can be restored.

Keep a backup

The wallet cannot recover a key you never backed up. If you lose the keystore and its password, the account and its test funds are gone. Make a backup (below) as soon as you create an account.

Back up your wallet

The wallet supports two backup formats:

Format What it protects Encryption
pqwerai-cli backup v1 Encrypted keystores plus a SHA-256 digest Each keystore keeps its own V3 encryption
Encrypted backup v2 The whole bundle sealed as one file AES-256-GCM under scrypt (N=2¹⁷, r=8, p=1) of a separate backup passphrase of at least 12 characters; every header field is authenticated

To make one, choose Create backup, pick the format, and for v2 enter a backup passphrase that is different from your keystore password. The wallet writes the backup to the location you choose and never overwrites an existing file.

The v2 format has been cross-checked both ways against pqwerai-cli and an independent Python implementation, so a backup made in the GUI restores in the CLI and the reverse.

Verify and restore

  • Verify backup checks the file's integrity (and, for v2, that the passphrase and every authenticated header field are correct) without importing anything.
  • Restore backup imports the accounts from a verified backup. Restore never overwrites your current keystores; resolve any name clash first.

Tips

  • Store the backup file and its passphrase separately from the PC that runs the wallet.
  • A backup passphrase is only as strong as you make it — use at least 12 characters, and prefer a long phrase.
  • After restoring on a new PC, re-approve your node on the Network page before signing.

Sources at 7a33c77104: apps/pqwerai-wallet-windows/README.md

Found a problem? Report a documentation issue · Build testnet-rc1+7a33c77104