Data directory

From Peercoin Wiki
Jump to: navigation, search

The location where Peercoin's data files are stored, including the wallet data file.

Default Location

The Peercoin core and Peerunity data directories currently use the name "PPCoin" instead of "Peercoin", though this will likely be changed in v0.5. Windows builds from Fuzzybear use "Peercoin".


Note: If you are using a Windows build from Fuzzybear, substitute "PPCoin" with "Peercoin" in the following.

Go to Start -> Run (or press WinKey+R) and run this:


Peercoin's data folder will open. For most users, this is the following locations:

C:\Documents and Settings\YourUserName\Application data\PPCoin (XP)

C:\Users\YourUserName\Appdata\Roaming\PPCoin (Vista and 7)

"AppData" and "Application data" are hidden by default.

You can also store Peercoin data files in any other drive or folder.

If you have already downloaded the data then you will have to move the data to the new folder. If you want to store them in D:\PeercoinData then click on "Properties" of a shortcut to Peercoin-qt.exe and add -datadir=D:\PeerCoinData at the end as an example:

"C:\Program Files (x86)\Peercoin\peercoin-qt.exe" -datadir=d:\PeerCoinData

Start Peercoin, now you will see all the files are created in the new data directory.


By default Peercoin will put its data here:


You need to do a "ls -a" to see directories that start with a dot. Alternatively, press Ctrl-h while viewing your home folder.

If that's not it, you can do a search like this:

find / -name wallet.dat -print 2>/dev/null


By default Peercoin will put its data here:

~/Library/Application Support/PPCoin/

To find this:

  1. Open a new Finder window.
  2. Go to your "Library" folder and click on it.
  3. Now click on the folder "Application Support"
  4. Now hit Shift + Command + G
  5. This brings up a small window near the top that says "Go to the folder...". In its text field, in that small window, enter the following: ~/Library/Application Support/PPCoin
  6. You now see the hidden PPCoin folder inside the Application Support folder.

Directory Contents


  • .lock
    • BDB lock file
  • ppcoin.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
    • Peercoin'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 peercoins.
  • 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 peercoin-specific file format, unrelated to any database system<ref>Ultraprune merged in mainline</ref>.

The data, index and log files are used by Oracle Berkeley DB, the embedded key/value data store that Peercoin 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 Peercoin 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 peercoins. You should not transfer this file to any third party or they may be able to access your peercoins.
  • 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 peercoin-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.

See Also


<references />