Determine whether key records are stored in plaintext or encrypted form and when the wallet database is rewritten.
Trace passphrase-derived key material, salt, derivation settings and encrypted master-key records.
The exact VTA release implementation should be pinned before claiming a specific cipher/KDF parameter set.
| Area | Finding | Status |
|---|---|---|
| Wallet key concept | Wallet private keys are security-sensitive material; this audit does not expose or inspect user key data. | Security boundary |
| Encrypted key records | Legacy Bitcoin-derived wallet architectures support encrypted-key records and a master-key layer; exact VTA implementation must be pinned to its release. | Release-specific |
| Passphrase → KDF | Legacy wallet encryption uses a passphrase-derived encryption key with salt/derivation parameters; exact VTA values require source verification. | Release-specific |
| Master-key storage | Master-key metadata is a separate storage concern from the private key itself. Do not equate a stored master-key record with a plaintext private key. | Needs VTA source pin |
| Wallet DB rewrite | Encryption transitions in legacy wallet implementations can require rewriting/removing unencrypted key material from the database. | Release-specific |
| Backup security | A wallet backup can contain security-critical key material; backup access must be treated as sensitive even when the wallet is encrypted. | Operational security |
| RPC exposure | Wallet RPC should remain local-only where possible. Do not expose the VTA RPC port publicly. | Operational rule |
| Exact VTA cipher/KDF | No exact cipher/KDF parameters are asserted on this page without a pinned VTA wallet source file. | Not verified |
| Cryptographic test vectors | No VTA-specific wallet encryption/decryption vector was executed by this package. | Not measured |
1. Pin exact VTA Core release / commit. 2. Locate CWallet / CCryptoKeyStore / CCrypter equivalents. 3. Locate EncryptWallet / Unlock / ChangeWalletPassphrase. 4. Record KDF algorithm, salt length and iteration handling. 5. Record cipher/mode and IV/key derivation. 6. Trace AddKey / AddCryptedKey / WriteCryptedKey. 7. Trace WriteMasterKey and wallet DB records. 8. Verify database rewrite after encryption. 9. Build known-answer encryption/decryption tests. 10. Verify backup + restore behavior on a disposable test wallet.
wallet.dat, private keys, seed phrases or RPC passwords to the benchmark site. This audit can be completed using source code and disposable test vectors without exposing real funds.