Data directory - Bitcoin Wiki Bitcoin core datadir

Содержание статьи

From Bitcoin Wiki

The data directory is the location where Bitcoin's data files are stored, including the wallet data file.

Default Location


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


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

C:\Documents and Settings\YourUserName\Application data\Bitcoin (XP) C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Vista and 7)

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

You can also store Bitcoin 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:\BitcoinData then click on "Properties" of a shortcut to bitcoin-qt.exe and add -datadir=D:\BitcoinData at the end as an example:

"C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\BitcoinData

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


By default Bitcoin will put its data here:


You need to do a "ls -a" to see directories that start with a dot.

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

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


By default Bitcoin will put its data here:

~/Library/Application Support/Bitcoin/

Directory Contents


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

  • .lock
    • Bitcoin data directory lock file
  • bitcoin.conf [optional]
    • Contains configuration options.
  • 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
  • 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 (150 GB as of Nov 2017) for every output being spent.

locks subdirectory

[v0.8 and above] Contains "undo" data.

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 all of 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.

See Also


  1. Ultraprune merged in mainline
Это интересно:

Bitcoin Core 0.10 Build Matrix Script · GitHub

From Bitcoin Wiki

There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

Linux Quickstart

The simplest way to start from scratch with the command line client, automatically syncing blockchain and creating a wallet, is to just run this command (without arguments) from the directory containing your bitcoind binary:


To run with the standard GUI interface:


Command-line arguments

These commands are accurate as of Bitcoin Core version v0.14.0.

Command Description
-? Print this help message and exit
-version Print version and exit
-alertnotify= Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
-blocknotify= Execute command when the best block changes (%s in cmd is replaced by block hash)
-assumevalid= If this block is in the chain assume that it and its ancestors are valid and potentially skip their script verification (0 to verify all, default: 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90, testnet: 00000000000128796ee387cf110ccb9d2f36cffaf7f73079c995377c65ac0dcc)
-conf= Specify configuration file (default: bitcoin.conf)
-datadir= Specify data directory
-dbcache= Set database cache size in megabytes (4 to 16384, default: 300)
-loadblock= Imports blocks from external blk000??.dat file on startup
-maxorphantx= Keep at most unconnectable transactions in memory (default: 100)
-maxmempool= Keep the transaction memory pool below megabytes (default: 300)
-mempoolexpiry= Do not keep transactions in the mempool longer than hours (default: 336)
-blockreconstructionextratxn= Extra transactions to keep in memory for compact block reconstructions (default: 100)
-par= Set the number of script verification threads (-2 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
-pid= Specify pid file (default:
-prune= Reduce storage requirements by enabling pruning (deleting) of old blocks. This allows the pruneblockchain RPC to be called to delete specific blocks, and enables automatic pruning of old blocks if a target size in MiB is provided. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, >550 = automatically prune block files to stay under the specified target size in MiB)
-reindex-chainstate Rebuild chain state from the currently indexed blocks
-reindex Rebuild chain state and block index from the blk*.dat files on disk
-sysperms Create new files with system default permissions, instead of umask 077 (only effective with disabled wallet functionality)
-txindex Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)

Connection options:
-addnode= Add a node to connect to and attempt to keep the connection open
-banscore= Threshold for disconnecting misbehaving peers (default: 100)
-bantime= Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
-bind= Bind to given address and always listen on it. Use [host]:port notation for IPv6
-connect= Connect only to the specified node(s); -noconnect or -connect=0 alone to disable automatic connections
-discover Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)
-dns Allow DNS lookups for -addnode, -seednode and -connect (default: 1)
-dnsseed Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect/-noconnect)
-externalip= Specify your own public address
-forcednsseed Always query for peer addresses via DNS lookup (default: 0)
-listen Accept connections from outside (default: 1 if no -proxy or -connect/-noconnect)
-listenonion Automatically create Tor hidden service (default: 1)
-maxconnections= Maintain at most connections to peers (default: 125)
-maxreceivebuffer= Maximum per-connection receive buffer, *1000 bytes (default: 5000)
-maxsendbuffer= Maximum per-connection send buffer, *1000 bytes (default: 1000)
-maxtimeadjustment Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: 4200 seconds)
-onion= Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
-onlynet= Only connect to nodes in network (ipv4, ipv6 or onion)
-permitbaremultisig Relay non-P2SH multisig (default: 1)
-peerbloomfilters Support filtering of blocks and transaction with bloom filters (default: 1)
-port= Listen for connections on (default: 8333 or testnet: 18333)
-proxy= Connect through SOCKS5 proxy
-proxyrandomize Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1)
-rpcserialversion Sets the serialization of raw transaction or block hex returned in non-verbose mode, non-segwit(0) or segwit(1) (default: 1)
-seednode= Connect to a node to retrieve peer addresses, and disconnect
-timeout= Specify connection timeout in milliseconds (minimum: 1, default: 5000)
-torcontrol=: Tor control port to use if onion listening enabled (default:
-torpassword= Tor control port password (default: empty)
-upnp= Use UPnP to map the listening port (default: 0)
-whitebind= Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
-whitelist= Whitelist peers connecting from the given IP address (e.g. or CIDR notated network (e.g. Can be specified multiple times. Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway
-whitelistrelay Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: 1)
-whitelistforcerelay Force relay of transactions from whitelisted peers even if they violate local relay policy (default: 1)
-maxuploadtarget= Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)

Wallet options:
-disablewallet Do not load the wallet and disable wallet RPC calls
-keypool= Set key pool size to (default: 100)
-fallbackfee= A fee rate (in BTC/kB) that will be used when fee estimation has insufficient data (default: 0.0002)
-mintxfee= Fees (in BTC/kB) smaller than this are considered zero fee for transaction creation (default: 0.00001)
-paytxfee= Fee (in BTC/kB) to add to transactions you send (default: 0.00)
-rescan Rescan the block chain for missing wallet transactions on startup
-salvagewallet Attempt to recover private keys from a corrupt wallet on startup
-spendzeroconfchange Spend unconfirmed change when sending transactions (default: 1)
-txconfirmtarget= If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 6)
-usehd Use hierarchical deterministic key generation (HD) after BIP32. Only has effect during wallet creation/first start (default: 1)
-walletrbf Send transactions with full-RBF opt-in enabled (default: 0)
-upgradewallet Upgrade wallet to latest format on startup
-wallet= Specify wallet file (within data directory) (default: wallet.dat)
-walletbroadcast Make the wallet broadcast transactions (default: 1)
-walletnotify= Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
-zapwallettxes= Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup (1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)

ZeroMQ notification options:
-zmqpubhashblock= Enable publish hash block in
-zmqpubhashtx= Enable publish hash transaction in
-zmqpubrawblock= Enable publish raw block in
-zmqpubrawtx= Enable publish raw transaction in

Debugging/Testing options:
-uacomment= Append comment to the user agent string
-debug= Output debugging information (default: 0, supplying is optional). If is not supplied or if = 1, output all debugging information. can be: addrman, alert, bench, cmpctblock, coindb, db, http, libevent, lock, mempool, mempoolrej, net, proxy, prune, rand, reindex, rpc, selectcoins, tor, zmq, qt.
-help-debug Show all debugging options (usage: --help -help-debug)
-logips Include IP addresses in debug output (default: 0)
-logtimestamps Prepend debug output with timestamp (default: 1)
-minrelaytxfee= Fees (in BTC/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.00001)
-maxtxfee= Maximum total fees (in BTC) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: 0.10)
-printtoconsole Send trace/debug info to console instead of debug.log file
-shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)

Chain selection options:
-testnet Use the test chain

Node relay options:
-bytespersigop Equivalent bytes per sigop in transactions for relay and mining (default: 20)
-datacarrier Relay and mine data carrier transactions (default: 1)
-datacarriersize Maximum size of data in data carrier transactions we relay and mine (default: 83)
-mempoolreplacement Enable transaction replacement in the memory pool (default: 1)

Block creation options:
-blockmaxweight= Set maximum BIP141 block weight (default: 3000000)
-blockmaxsize= Set maximum block size in bytes (default: 750000)
-blockprioritysize= Set maximum size of high-priority/low-fee transactions in bytes (default: 0)
-blockmintxfee= Set lowest fee rate (in BTC/kB) for transactions to be included in block creation. (default: 0.00001)

RPC server options:
-server Accept command line and JSON-RPC commands
-rest Accept public REST requests (default: 0)
-rpcbind= Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces)
-rpccookiefile= Location of the auth cookie (default: data dir)
-rpcuser= Username for JSON-RPC connections
-rpcpassword= Password for JSON-RPC connections
-rpcauth= Username and hashed password for JSON-RPC connections. The field comes in the format: :$. A canonical python script is included in share/rpcuser. The client then connects normally using the rpcuser=/rpcpassword= pair of arguments. This option can be specified multiple times
-rpcport= Listen for JSON-RPC connections on (default: 8332 or testnet: 18332)
-rpcallowip= Allow JSON-RPC connections from specified source. Valid for are a single IP (e.g., a network/netmask (e.g. or a network/CIDR (e.g. This option can be specified multiple times
-rpcthreads= Set the number of threads to service RPC calls (default: 4)

UI Options:
-choosedatadir Choose data directory on startup (default: 0)
-lang= Set language, for example "de_DE" (default: system locale)
-min Start minimized
-rootcertificates= Set SSL root certificates for payment request (default: -system-)
-splash Show splash screen on startup (default: 1)
-resetguisettings Reset all settings changed in the GUI

Many of the boolean options can also be set to off by specifying them with a "no" prefix: e.g. -nodnseed.

Bitcoin.conf Configuration File

All command-line options (except for -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. A user-friendly configuration file generator is available here. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin data directory, but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.

Operating System Default bitcoin datadir Typical path to configuration file
Windows  %APPDATA%\Bitcoin\ C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
Linux $HOME/.bitcoin/ /home/username/.bitcoin/bitcoin.conf
Mac OSX $HOME/Library/Application Support/Bitcoin/ /Users/username/Library/Application Support/Bitcoin/bitcoin.conf

Note: if running Bitcoin in testnet mode, the sub-folder "testnet" will be appended to the data directory automatically.

Sample Bitcoin.conf

Copied from

## bitcoin.conf configuration file. Lines beginning with # are comments.
## # Network-related settings: # Run on the test network instead of the real bitcoin network.
#testnet=0 # Run a regression test network
#regtest=0 # Connect via a SOCKS5 proxy
#proxy= # Bind to given address and always listen on it. Use [host]:port notation for IPv6
#bind= # Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
#whitebind= ##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode= ##
## addnode will connect you to and tell you about the ##
## nodes connected to In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
############################################################## # Use as many addnode= settings as you like to connect to specific peers
#addnode= # Alternatively use as many connect= settings as you like to connect ONLY to specific peers
#connect= # Listening mode, enabled by default except when 'connect' is being used
#listen=1 # Maximum number of inbound+outbound connections.
#maxconnections= #
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
# # server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
#server=0 # Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.
# This option can be specified multiple times (default: bind to all interfaces)
#rpcbind= # If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
# is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used
# when the server and client are run as the same user.
# If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
# method(DEPRECATED) is to set this pair for the server and client:
# The second method `rpcauth` can be added to server startup argument. It is set at intialization time
# using the output from the script in share/rpcuser/ after providing a username:
# ./share/rpcuser/ alice
# String to be appended to bitcoin.conf:
# rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
# Your password:
# On client-side, you add the normal user/password pair to send commands:
# You can even add multiple entries of these to the server conf file, and client can use any of them:
# rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99 # How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established. #rpcclienttimeout=30 # By default, only RPC connections from localhost are allowed.
# Specify as many rpcallowip= settings as you like to allow connections from other hosts,
# either as a single IPv4/IPv6 or with a subnet specification. # NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
# because the rpcpassword is transmitted over the network unencrypted. # server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
# it is also read by bitcoind to determine if RPC should be enabled #rpcallowip=
#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96 # Listen for RPC connections on this TCP port:
#rpcport=8332 # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect= # Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).
# This setting is over-ridden by the -paytxfee option.
#txconfirmtarget=n # Miscellaneous options # Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100 # Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00 # Enable pruning to reduce storage requirements by deleting old blocks. # This mode is incompatible with -txindex and -rescan.
# 0 = default (no pruning).
# 1 = allows manual pruning via RPC.
# >=550 = target to stay under in MiB. #prune=550 # User interface options # Start Bitcoin minimized
#min=1 # Minimize to the system tray



Start automatically

To configure the Bitcoin client to start automatically:

You might use the configuration-file, or the GUI-Settings:

Settings -> Options

then mark the checkbox titled:

[X] Start Bitcoin on system startup

Batch automation

To work with batch, you have to start the daemon (bitcoind.exe). The bitcoin.exe run with option "-server" will respond with GUI-messages you are not able to process its answers.



See Also

оплата hashflare сбербанк онлайн.

Multibit or bitcoin-qt datadir -

It is not connected to the internet or Bitcoin, so core should not be any balance information available. This overview includes changes that affect behavior, not code moves, minor refactors and string updates. Bitcoin Windows, do not forget to uninstall all earlier versions of datadir Bitcoin datadir first, especially if you are switching bitcoin the bit version. All command-line options except for -conf may core specified in a configuration file, and all configuration file options may also be specified on the command line. Core arbitrary data in the blockchain is datadir a bad idea; it is less costly and far more efficient to store non-currency data elsewhere.

haasbot bitcointalk slrrt »

who owns bitcoin

Due to some quirks in the path resolution, if you want to use a custom directory for Armory and Bitcoin, the —datadir and —satoshi-datadir arguments are inconsistent. Use of getrawtransaction for retrieving confirmed transactions with unspent outputs has been deprecated. Sign up using Facebook. Possible duplicate of Bitcoin-Qt setup: However, this is not yet implemented for many RPC calls, this is expected to land in a later release.

faucetbox dogecoin faucets »

cara kerja bitcoin

This data independence improves wallet privacy and security. This can be the same core drive, an external bitcoin drive, or a removable medium such core USB drive or SD card. Sign up using Facebook. The following lines are example options in bitcoin. Both commas and spaces can be used to separate parameters in both the bracket syntax and datadir RPC command syntax. No spam, just great content like this. The following table shows where each field has been datadir to:.

powercolor 6950 mining bitcoins »

Bitcoin Core: как пользоваться, как установить и настроить bitcoin кошелёк

<< Go back to the previous page

Похожие статьи