The Anatomy of `wallet.dat`: Records, Keys, and Metadata

12. The Anatomy of wallet.dat: Records, Keys, and Metadata

To truly understand your "Internal Bank," you must look at the Anatomy of the wallet.dat file. This file is not just a "Key Store"; it is a "Financial Time Capsule." It contains the history of every payment you have received, the labels you have written, the settings of your wallet, and the encrypted secrets of your wealth. In an SQLite wallet, this data is organized into a single "Main Table" with three columns: Type, Key, and Value. It is the "Anatomy of the Sovereignty."

Every piece of information in your bank has its own "Record Type." For example, a transaction is stored as a tx record, a label as a purpose record, and an encrypted key as a mkey record. By understanding these types, the Sovereign Architect can perform a "Digital Autopsy" on their own wallet to verify its integrity.

Analyzing the Record Types: WalletBatch::ReadBestBlock

In the source code (src/wallet/walletdb.cpp), the wallet reads the "Current State" of the blockchain from the database to know where it left off.

/**
 * This is an example of how the wallet reads a "Metadata" record from the vault.
 */
bool WalletBatch::ReadBestBlock(CBlockLocator& locator)
{
    // 1. We look for the "bestblock" key in the database.
    // 2. This record tells us the "Hash" of the last block we successfully audited.
    return Read("bestblock", locator);
}

Explaining the Anatomy: The Ledger Rows

• tx Records: These are the "History Entries." Every time you send or receive money, the wallet saves the full transaction data here. It includes the "Confirmations," the "Fee Paid," and the "Time Received." Even if the blockchain itself were to disappear, your wallet.dat would still remember your personal history. It is the "Memory of the Bank."

• mkey Records (Master Keys): These are the "Encrypted Guards." As we saw in Chapter 7, the Master Key is the AES-scrambled secret that unlocks your vault. In the database, this record contains the "Salt," the "Iteration Count," and the "Encrypted Payload." It is the "Heart of the Defense."

• purpose and label Records: These are the "Human Layers." They map addresses to names like "Rent" or "Alice." This metadata is never shared with the network, but it is vital for your own "Management of the Identity." Without these records, your wallet would be a sea of anonymous numbers. It is the "Clarity of the Sovereign."

• minversion: This is the "Age of the Vault." It tells the software which version of Bitcoin Core was used to create the wallet. This prevents old software from accidentally opening a new wallet and corrupting its data. It is the "Compatibility of the Core."

The "Total Audit" of the Vault

As a Sovereign Architect, you should know that your wallet.dat is a "Living Document." Every time you perform an action, the computer is writing new rows into this ledger. By keeping this file safe and making regular backups, you are preserving the "Entirety of your Financial Being." You are the "Master of the Anatomy," the one who understands every cell and every bone of the internal bank. You are the "Guardian of the Capsule."