Jump to: , Bitcoin Core (formerly Bitcoin-Qt) is the third Bitcoin client, developed by Wladimir J. van der Laan based on the original reference code by Satoshi Nakamoto.[1][2][3]It has been bundled with bitcoind since version 0.5.[4]Bitcoin-Qt has been rebranded to Bitcoin Core since version 0.9.0 [5].Contents 1 2 3 4 5 Bitcoin Core can be used as a desktop client for regular payments or as a server utility for merchants and other payment services.Source code (and build instructions for supported platforms) can be found at the Bitcoin GitHub page.Bitcoin Core is often criticized for being slow in downloading and verifying the Bitcoin transaction database (the blockchain).The download may be quicker using the bootstrap method.NOTE: As of version 0.10.0 it is now slower to download the blockchain via the torrent than it is to download the full blockchain through the P2P client.It has also been criticized for "hogging" upload bandwidth when peers connect to download the blockchain (possible only when run with port 8333 accessible to outside connections).

This perceived "issue" has been discussed extensively on GitHub.Most modern routers support quality-of-service that can be configured to properly share the internet connection across all services, and even deprioritise Bitcoin traffic.Bitcoin Core includes a script for Linux to configure QoS on an individual host.[6]Windows users can also use third-party software such as Netbalancer to throttle the application's upload bandwidth and ensure that one has enough upload bandwidth available for regular computer and internet use to be unaffected.Wallet management is also cumbersome.Unlike clients such as Armory, MultiBit, Electrum and others only one wallet at a time is supported, and its location is required to be the same as the blockchain storage, making it difficult to place the wallet on an encrypted drive.It is recommended to backup the wallet.dat file every 50 transactions, due to the way Bitcoin Core handles change.English Bahasa Indonesia Dansk Deutsch English Español Français Italiano Magyar Nederlands Polski Português Brasil Română Slovenščina Svenska Türkçe Ελληνικά български Русский Українська العربية فارسی हिन्दी 한국의 日本語 简体中文 繁體中文 Bahasa Indonesia Dansk Deutsch English Español Français Italiano Magyar Nederlands Polski Português Brasil Română Slovenščina Svenska Türkçe Ελληνικά български Русский Українська العربية فارسی हिन्दी 한국의 日本語 简体中文 繁體中文 Bitcoin is an innovative payment network and a new kind of money.

Bitcoin uses peer-to-peer technology to operate with no central authority or banks; managing transactions and the issuing of bitcoins is carried out collectively by the network.10 000 bitcoin pizzaBitcoin is open-source; its design is public, nobody owns or controls Bitcoin and everyone can take part.bitcoin visual studio 2012Through many of its unique properties, Bitcoin allows exciting uses that could not be covered by any previous payment system.litecoin local exchangeJump to: navigation, search 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).aml for bitcoin

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).bitcoin aml risksContents 1 2 3 4 5 6 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: These commands are accurate as of Bitcoin Core version v0.14.0.litecoin daily transactionsPrint 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: bitcoind.pid) -prune= Reduce storage requirements by enabling pruning (deleting) of old blocks.ethereum next difficulty

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.ethereum gpu speedWarning: Reverting this setting requires re-downloading the entire blockchain.may tao bitcoin(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: 127.0.0.1:9051) -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.1.2.3.4) 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.1.2.3.4), a network/netmask (e.g.1.2.3.4/255.255.255.0) 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.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.