Bitcoin Notes 2

Directory Contents


An overview of these is in in the Bitcoin Core documentation.

  • .lock
    • Bitcoin data directory lock file
  • bitcoin.conf [optional]
  • blkxxxx.dat [Versions prior to v0.8.0]
    • Contains concatenated raw blocks. Stored are actual Bitcoin blocks, in network format, dumped to disk raw.
  • blkindex.dat [Versions prior to v0.8.0]
    • Indexing information used with blkxxxx.dat
    • Used by BDB
  • db.log
  • debug.log
    • Bitcoin’s verbose log file. Automatically trimmed from time to time.
  • wallet.dat
    • Storage for keys, transactions, metadata, and options. Please be sure to make backups of this file. It contains the keys necessary for spending your bitcoins.
  • addr.dat [Versions prior to v0.7.0]
    • Storage for ip addresses to make a reconnect easier
  • peers.dat [Versions v0.7.0 and later]
    • Storage for peer information to make a reconnect easier. This file uses a bitcoin-specific file format, unrelated to any database system[1].
  • fee_estimates.dat [Versions v0.10.0 and later]
    • Statistics used to estimate fees and priorities. Saved just before program shutdown, and read in at startup.

The data, index and log files are used by Oracle Berkeley DB, the embedded key/value data store that Bitcoin uses.

database subdirectory

Contains BDB journaling files

testnet3 subdirectory

Contains testnet versions of these files (if running with -testnet)

blocks subdirectory

[v0.8 and above] Contains blockchain data.

  • blk*.dat
    • Stored are actual Bitcoin blocks, in network format, dumped to disk raw. They are only needed for re-scanning missing transactions in a wallet, reorganizing to a different part of the chain, and serving the block data to other nodes that are synchronizing.
  • blocks/index subdirectory
    • [v0.8 and above] A LevelDB database that contains metadata about all known blocks, and where to find them on disk. Without this, finding a block would be very slow.

chainstate subdirectory

[v0.8 and above] A LevelDB database with a compact representation of all currently unspent transaction outputs and some metadata about the transactions they are from. The data here is necessary for validating new incoming blocks and transactions. It can theoretically be rebuilt from the block data (see the -reindex command line option), but this takes a rather long time. Without it, you could still theoretically do validation indeed, but it would mean a full scan through the blocks (7 GB as of may 2013) for every output being spent.

locks subdirectory

[v0.8 and above] Contains “undo” data.

  • rev*.dat

You can see blocks as ‘patches’ to the chain state (they consume some unspent outputs, and produce new ones), and see the undo data as reverse patches. They are necessary for rolling back the chainstate, which is necessary in case of reorganizations.

Personally identifiable data [v0.8 and above]

This section may be of use to you if you wish to send a friend the blockchain, avoiding them a hefty download.

  • wallet.dat
    • Contains addresses and transactions linked to them. Please be sure to make backups of this file. It contains the keys necessary for spending your bitcoins. You should not transfer this file to any third party or they may be able to access your bitcoins.
  • db.log
    • May contain information pertaining to your wallet. It may be safely deleted.
  • debug.log
    • May contain IP addresses and transaction ID’s. It may be safely deleted.
  • database/ folder
    • This should only exist when bitcoin-qt is currently running. It contains information (BDB state) relating to your wallet.
  • peers.dat
    • Unknown whether this contains personally identifiable data. It may be safely deleted.

Other files and folders (blocks, blocks/index, chainstate) may be safely transferred/archived as they contain information pertaining only to the public blockchain.


The database files in the “blocks” and “chainstate” directories are cross-platform, and can be copied between different installations. These files, known collectively as a node’s “block database”, represent all of the information downloaded by a node during the syncing process. In other words, if you copy installation A’s block database into installation B, installation B will then have the same syncing percentage as installation A. This is usually far faster than doing the normal initial sync over again. However, when you copy someone’s database in this way, you are trusting them absolutely. Bitcoin Core treats its block database files as 100% accurate and trustworthy, whereas during the normal initial sync it treats each block offered by a peer as invalid until proven otherwise. If an attacker is able to modify your block database files, then they can do all sorts of evil things which could cause you to lose bitcoins. Therefore, you should only copy block databases from Bitcoin installations under your personal control, and only over a secure connection.

Each node has a unique block database, and all of the files are highly connected. So if you copy just a few files from one installation’s “blocks” or “chainstate” directories into another installation, this will almost certainly cause the second node to crash or get stuck at some random point in the future. If you want to copy a block database from one installation to another, you have to delete the old database and copy allof the files at once. Both nodes have to be shut down while copying.

Only the file with the highest number in the “blocks” directory is ever written to. The earlier files will never change. Also, when these blk*.dat files are accessed, they are usually accessed in a highly sequential manner. Therefore, it’s possible to symlink the “blocks” directory or some subset of the blk*.dat files individually onto a magnetic storage drive without much loss in performance (see Splitting the data directory), and if two installations start out with identical block databases (due to the copying described previously), subsequent runs of rsync will be very efficient.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s