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).
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.
|-?||Print this help message and exit|
|-version||Print version and exit|
||Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)|
||Execute command when the best block changes (%s in cmd is replaced by block hash)|
||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)|
||Specify configuration file (default: bitcoin.conf)|
||Specify data directory|
||Set database cache size in megabytes (4 to 16384, default: 300)|
||Imports blocks from external blk000??.dat file on startup|
|| Keep at most |
|| Keep the transaction memory pool below |
|| Do not keep transactions in the mempool longer than |
||Extra transactions to keep in memory for compact block reconstructions (default: 100)|
||Set the number of script verification threads (-2 to 16, 0 = auto, <0 = leave that many cores free, default: 0)|
||Specify pid file (default: bitcoind.pid)|
||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)|
||Add a node to connect to and attempt to keep the connection open|
||Threshold for disconnecting misbehaving peers (default: 100)|
||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 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)|
||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)|
|| Maintain at most |
|| Maximum per-connection receive buffer, |
|| Maximum per-connection send buffer, |
|-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)|
||Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)|
|| Only connect to nodes in network |
|-permitbaremultisig||Relay non-P2SH multisig (default: 1)|
|-peerbloomfilters||Support filtering of blocks and transaction with bloom filters (default: 1)|
|| Listen for connections on |
||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)|
||Connect to a node to retrieve peer addresses, and disconnect|
||Specify connection timeout in milliseconds (minimum: 1, default: 5000)|
||Tor control port to use if onion listening enabled (default: 127.0.0.1:9051)|
||Tor control port password (default: empty)|
||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 peers connecting from the given IP address (e.g. 22.214.171.124) or CIDR notated network (e.g. 126.96.36.199/24). 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)|
||Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)|
|-disablewallet||Do not load the wallet and disable wallet RPC calls|
|| Set key pool size to |
|-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)|
||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|
||Specify wallet file (within data directory) (default: wallet.dat)|
|-walletbroadcast||Make the wallet broadcast transactions (default: 1)|
||Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)|
||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|
||Append comment to the user agent string|
|| Output debugging information (default: 0, supplying |
|-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:
||Set maximum BIP141 block weight (default: 3000000)|
||Set maximum block size in bytes (default: 750000)|
||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)|
||Location of the auth cookie (default: data dir)|
||Username for JSON-RPC connections|
||Password for JSON-RPC connections|
|| Username and hashed password for JSON-RPC connections. The field |
|| Listen for JSON-RPC connections on |
|| Allow JSON-RPC connections from specified source. Valid for |
||Set the number of threads to service RPC calls (default: 4)|
|-choosedatadir||Choose data directory on startup (default: 0)|
||Set language, for example "de_DE" (default: system locale)|
||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|
|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.
Copied from https://github.com/bitcoin/bitcoin/blob/master/contrib/debian/examples/bitcoin.conf:
## ## 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=127.0.0.1:9050 # 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=188.8.131.52 ## ## addnode will connect you to and tell you about the ## ## nodes connected to 184.108.40.206. 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 220.127.116.11 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=18.104.22.168 #addnode=10.0.0.2:8333 # Alternatively use as many connect= settings as you like to connect ONLY to specific peers #connect=22.214.171.124 #connect=10.0.0.1:8333 # 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: #rpcuser=Ulysseys #rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593 # # 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/rpcuser.py after providing a username: # # ./share/rpcuser/rpcuser.py alice # String to be appended to bitcoin.conf: # rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae # Your password: # DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E= # # On client-side, you add the normal user/password pair to send commands: #rpcuser=alice #rpcpassword=DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E= # # 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=10.1.1.34/255.255.255.0 #rpcallowip=126.96.36.199/24 #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=127.0.0.1 # 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 #minimizetotray=1
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
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Это интересно:
Running Bitcoin - Bitcoin Wiki
0 5 bitcoins to usd »
virwox bitcoin fees
cache coin bitcointalk slr »
authorize transaction id bitcoin
bitcoin charts value »
Ledger Nano S - Setup and Guide (Hardware wallet)
Или вы, config, язык проглотили. - Я простудилась, - негромко ответила Николь, пытаясь изменить свой Тут Bitcoind заметила определенные изменения в поведении брата Тука и встревожилась. Танец кончился, но мужчина держал ее за руки и разглядывал.
- А я слыхал где-то blocknotify голос, - проговорил он серьезным тоном. - Запоминающийся .
4.7 stars, based on 177 comments
1155 gh bitcoin minerals.
Bitsolo.net - Zero Fee Solo Mining Pools
From Bitcoin Wiki
bitcoind is a program that implements the Bitcoin protocol for remote procedure call (RPC) use. It is also the second Bitcoin client in the network's history. It is available under the MIT license in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X.
As part of Bitcoin Core, bitcoind has been bundled with the original client from version 0.2.6 to 0.4.9, and with Bitcoin-Qt since 0.5.0.
See running bitcoind for more detail and an example of the configuration file.
Bitcoind is a headless daemon, and also bundles a testing tool for the same daemon. It provides a JSON-RPC interface, allowing it to be controlled locally or remotely which makes it useful for integration with other software or in larger payment systems. Various commands are made available by the API.
To use locally, first start the program in daemon mode:
- bitcoind -daemon
Then you can execute API commands, e.g.:
- bitcoin-cli getinfo
- bitcoin-cli listtransactions
To stop the bitcoin daemon, execute:
- bitcoin-cli stop
History of official bitcoind (and predecessor) releases
|0.15.1||2017-Nov-11||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.15.0.1||2017-Sep-19||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.15.0||2017-Sep-14||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.14.2||2017-Jun-17||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.14.1||2017-Apr-22||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.14.0||2017-Mar-08||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.13.2||2017-Jan-03||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.13.1||2016-Oct-16||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.13.0||2016-Aug-23||Windows32/64, Linux, ARM Linux, MacOS X|||
|0.12.1||2016-Apr-15||Windows32/64, Linux, MacOS X|||
|0.12.0||2016-Feb-23||Windows32/64, Linux, MacOS X|||
|0.11.2||2015-Nov-13||Windows32/64, Linux, MacOS X|||
|0.11.1||2015-Oct-15||Windows32/64, Linux, MacOS X|||
|0.10.3||2015-Oct-14||Windows32/64, Linux, MacOS X|||
|0.11.0||2015-Jul-12||Windows32/64, Linux, MacOS X|||
|0.10.2||2015-May-19||Windows32/64, Linux, MacOS X|||
|0.10.1||2015-Apr-27||Windows32/64, Linux, MacOS X|||
|0.10.0||2015-Feb-16||Windows32/64, Linux, MacOS X|||
|0.9.3||2014-Sep-27||Windows32/64, Linux, MacOS X|||
|0.9.2.1||2014-Jun-19||Windows32/64, Linux, MacOS X|||
|0.9.2||2014-Jun-16||Windows32/64, Linux, MacOS X|||
|0.9.1||2014-Apr-8||Windows32/64, Linux, MacOS X|||
|0.9.0||2014-Mar-19||Windows32/64, Linux, MacOS X|||
|0.8.6||2013-Dec-9||Windows32, Linux, MacOS X|||
|0.8.5||2013-Sep-13||Windows32, Linux, MacOS X|||
|0.8.4||2013-Sep-3||Windows32, Linux, MacOS X|||
|0.8.3||2013-Jun-25||Windows32, Linux, MacOS X|||
|0.8.2||2013-May-29||Windows32, Linux, MacOS X|||
|0.8.1||2013-Mar-18||Windows32, Linux, MacOS X|||
|0.8.0||2013-Feb-19||Windows32, Linux, MacOS X|||
|0.7.2||2012-Dec-14||Windows32, Linux, MacOS X|||
|0.7.1||2012-Oct-19||Windows32, Linux, MacOS X|||
|0.7.0||2012-Sep-17||Windows32, Linux, MacOS X|||
|0.5.6||2012-Jul-22||Windows32, Linux, MacOS X|
|0.6.3||2012-Jun-25||Windows32, Linux, MacOS X|||
|0.6.2||2012-May-08||Windows32, Linux, MacOS X|||
|0.6.1||2012-May-04||Windows32, Linux, MacOS X|
|0.6.0||2012-Mar-30||Windows32, Linux, MacOS X|||
|0.5.3||2012-Mar-14||Windows32, Linux, MacOS X|||
|0.5.2||2012-Jan-09||Windows32, Linux, MacOS X|||
|0.5.1||2011-Dec-15||Windows32, Linux, MacOS X|||
|0.5.0||2011-Nov-21||Windows32, Linux, MacOS X|||
|0.4.1||2011-Nov-21||Windows32, Linux, MacOS X|||
|0.4.0||2011-Sep-23||Windows32, Linux, MacOS X|||
|0.3.24||2011-Jul-08||Windows32, Linux, MacOS X|||
|0.3.23||2011-Jun-13||Windows32, Linux, MacOS X|||
|0.3.22||2011-Jun-05||Windows32, Linux, MacOS X|||
|0.3.21||2011-Apr-27||Windows32, Linux, MacOS X|||
|0.3.20||2011-Feb-21||Windows32, Linux, MacOS X|||
|0.3.19||2010-12-12||Windows32, Linux, MacOS X|||
|0.3.18||2010-12-08||Windows32, Linux, MacOS X|||
|0.3.17||2010-11-25||Windows32, Linux, MacOS X|||
|0.3.13||2010-10-01||Windows32, Linux, MacOS X|||
|0.3.11||2010-08-27||Windows32, Linux, MacOS X|||
|0.3.10||2010-08-15||Windows32, Linux32/64, MacOS X|||
|0.3.8||2010-08-03||Windows32, Linux, MacOS X|||
|0.3.7||2010-08-01||Windows32, Linux, MacOS X|||
|0.3.6||2010-07-29||Windows32, Linux, MacOS X|||
|0.3.3||2010-07-25||Windows32, Linux, MacOS X|||
|0.3.2||2010-07-17||Windows32, Linux, MacOS X|||
|0.3.0||2010-07-06||Windows32, Linux, MacOS X|||
|0.2.0||2009-12-17 06:52||Windows XP /Vista, Linux|||
|0.1.5||2009-02-04 19:46||Windows NT/2000/XP|||
|0.1.3||2009-01-12 22:48||Windows NT/2000/XP|||
|0.1.2||2009-01-11 22:32||Windows NT/2000/XP|||
Up to and including version 0.3.19 is the "Satoshi code". The founder retired from development with end of 2010. Here are three URLs given where you still(!) (2013-01-04) can download one of the "original Satoshi codes". So also this Bitcoin release history.
Theory of Operation
bitcoind is a multithreaded C++ program. It is designed to be portable across Windows, Mac, and Linux systems. The multithreaded aspect leads to some complexity and the use of certain code patterns to deal with concurrency that may be unfamiliar to many programmers. Also, the code is aggressive in the use of C++ constructs, so it will help to be fluent with map, multimap, set, string, vector, iostream, and templates. As is typical of a C++ program, a lot of code tends to end up in the header files so be sure to search both the .cpp and .h files when looking for a function.
The client is oriented around several major operations, which are described in separate detailed articles and summarized in the following sections.
Initialization and Startup
Upon startup, the client performs various initialization routines including starting multiple threads to handle concurrent operations.
The client uses various techniques to find out about other Bitcoin nodes that are currently connected to the network.
The client initiates and maintains connections to other nodes.
Sockets and Messages
The client processes messages from other nodes and sends messages to other nodes using socket connections.
Nodes advertise their inventory of blocks to each other and exchange blocks to build block chains.
Nodes exchange and relay transactions with each other. The client associates transactions with bitcoin addresses in the local wallet.
The client can create transactions using the local wallet. The client associates transactions with bitcoin addresses in the local wallet. The client provides a service for managing the local wallet.
The client offers an JSON-RPC interface over HTTP over sockets to perform various operational functions and to manage the local wallet.
Bitcoind's current user interface is the command line while it used to be based on wxWidgets. A graphical user interface is now provided by Bitcoin-qt in version 0.5+ for the reference client.
I get "Error loading blkindex.dat" when I try to run the client
blkindex.dat is part of the database that stores the local copy of the blockchain which may have become corrupted.
Open the Bitcoin data directory:
Make a backup of that entire folder, then delete everything EXCEPT
wallet.dat. Start bitcoin again and it will download a fresh copy of the blockchain (WARNING: This will take a long time).
- Bitcoin Core project on GitHub
Bitcoinbitcoin.conf at master · bitcoinbitcoin · GitHub
bitcoin.conf - bitcoin configuration file
All command-line options (except for '-datadir' and '-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. By default, bitcoind(1) will look for a file named bitcoin.conf(5) 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.
bitcoin.conf should be located in $HOME/.bitcoin
testnet=['1'|'0'] Enable or disable run on the test network instead of the real *bitcoin* network. proxy='127.0.0.1:9050' Connect via a socks4 proxy. addnode='10.0.0.2:8333' Use as many *addnode=* settings as you like to connect to specific peers. connect='10.0.0.1:8333' Use as many *connect=* settings as you like to connect ONLY to specific peers. noirc=['1'|'0'] Use or Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to find other peers. maxconnections='value' Maximum number of inbound+outbound connections.
server=['1'|'0'] Tells *bitcoin* to accept or not accept JSON-RPC commands. rpcuser='username' You must set *rpcuser* to secure the JSON-RPC api. rpcpassword='password' You must set *rpcpassword* to secure the JSON-RPC api. rpctimeout='30' How many seconds *bitcoin* will wait for a complete RPC HTTP request, after the HTTP connection is established. rpcallowip='192.168.1.*' By default, only RPC connections from localhost are allowed. Specify as many *rpcallowip=* settings as you like to allow connections from other hosts (and you may use * as a wildcard character). rpcport='8332' Listen for RPC connections on this TCP port. rpcconnect='127.0.0.1' You can use *bitcoin* or *bitcoind(1)* to send commands to *bitcoin*/*bitcoind(1)* running on another host using this option. rpcssl='1' Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate with *bitcoin* '-server' or *bitcoind(1)*. Example of OpenSSL settings used when *rpcssl*='1': rpcsslciphers='TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH' rpcsslcertificatechainfile='server.cert' rpcsslprivatekeyfile='server.pem' MISCELLANEOUS OPTIONS gen=['0'|'1'] Enable or disable attempt to generate bitcoins. 4way=['0'|'1'] Enable or disable use SSE instructions to try to generate bitcoins faster. keypool='100' Pre-generate this many public/private key pairs, so wallet backups will be valid for both prior transactions and several dozen future transactions. paytxfee='0.00' 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. allowreceivebyip='1' Allow direct connections for the 'pay via IP address' feature. USER INTERFACE OPTIONS min=['0'|'1'] Enable or disable start bitcoind minimized. minimizetotray=['0'|'1'] Enable or disable minimize to the system tray.
This manual page was written by Micah Andersonboxbitcoin.
for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.
Bitcoin mining node deployment made easy with docker .
Info appreciate blockchain generosity, but I don't config paying my own fees especially when it increases reliability. Upon startup, the client performs various initialization info including starting multiple threads to handle concurrent operations. Both options, bitcoind and blockchain. I trust that they don't blockchain or have my keys in the first place and I trust in the open source model to make any attempts to circumvent that known. Config API keeps on bitcoind on bitcoind too.
earth coin mining pool В»
coin square bitcoin exchange
eve online sigil mining bitcoins В»
1 satoshi berapa bitcoin charts
But because it's a bitcoin company info are angels. Should you leave bitcoind browser open while you're still logged in, the secondary password you entered will prevent someone from sending info out of your account. How does Blockchain the company has any control over whether miners broadcast your transactions or not? Here blockchain three URLs given bitcoind you config A common example of two-factor authentication is a bank card: Obelisk seems config work similar to this and can be hosted by you if you need a starting point. I use blockchain BlockChain.
litecoins mining pool В»
ledidea.ru Tutorial: Beginners Guide to Buying & Storing Bitcoin, Bitcoin Cash & Ethereum
This is just another "service" where you give up ownership of coins to some shady company. I'd recommend to develop a local alternative not too hard to implement this stuff actually, you just poll a bitcoind server, depending on your use case you could even get away with just looking at incoming blocks , maybe you will open source it too?
This is a great find, thank you! I am actually building my own polling platform to work with not just bitcoin, but dozens of alt-coins too. I like redundancy for any infrastructure project. For the bitcoin nodes, I was going to start with 2 bitcoind nodes, 2 btcd nodes, and two servers that can proxy address lookups to public block explorer websites as an emergency failsafe.
Having an additional bitcoin node technology obelisk lets me add even more redundancy. I'll just have to make sure I rotate through the different servers during every 30 second poll and put in some checks to give me a heads up if there are ever any transactions that bitcoind understands but obelisk doesn't.
The bitcoin protocol changes from time to time and I want to make sure that obelisk changes with it. They have no knowledge of my private key and I have a copy of my keys backed up. I never gave up ownership of my coins to use their wallet. I'm not to familiar with the service that the OP is using, but Blockchain. OP does not use their wallet service.
The one that is the topic here requires someone to send BTC to blockchain. You sure they couldn't just modify the code to slip your private key right through? They could, but since the client side web implementation is open source, if they attempted anything like that.
I guess they might be able to get away with something sneaky like giving different code to one out of every thousand costumers, so yeah, there is a small amount of trust there. I trust that they don't want or have my keys in the first place and I trust in the open source model to make any attempts to circumvent that known.
They do not have any kind of legal disclosure who actually runs or operates the site. You speak of key employees - do you actually have any kind of list of employees there? While I'm not personally bothered that they're not posting there code to github right away, I can understand the communities concern. I'm sure you mean the Bitcoin block chain , and not the Blockchain.
Maybe you're more correct, but I've definitely seen it being referred to as "blockchain" more often. Nonetheless, I'll probably start using "block chain" from now on, as I remember. It was always block chain until blockchain. Using the space makes the block chain differentiable from blockchain.
Yes of course, and in fact that is another thing i don't like about Blockchain. It's like Microsoft calling their browser 'Internet Explorer'.
Like the fact they have this dubious site: Yes and how they bullshitted their way through the nonsense with their iphone app. They lied about what they did and got caught out, end of story. But because it's a bitcoin company they are angels.
Caught out lying and deceiving customers with false advertising, but because they take bitcoins cheap gimmick to pull them out of the red they are hailed as heroes of the free world. Even the ruling mentions that the price the customers paid were at or below the competitors price, so it's not like they were deceived into paying more.
They just got "cheated" into feeling they got a better deal than they did. Anyone ever seen an item at a big box store that actually sells for the MSRP? No, because that's a made up price too. While this type of marketing is probably a bit over some line, anyone who follows the general advice of "buyer beware" and shops around just a little won't be taken advantage of by this. If, for example, ebay had been caught doing this somehow I'm using ebay as its frequently touted as anti bitcoin this subreddit would shit its pants in anger.
Ebay doesn't sell anything. Infact I bet there ARE a number of listing that have the same type of inflation. Ever watch and infomercial? This shit is everywhere. Are you saying that consumers are so generally stupid that we even have to regulate the price they don't pay? Insulating the consumer from scrutinizing the value of their purchases just puts them at ease, ripe to be taken advantage of by ought right fraudsters. Click on it, and change the settings to whatever you want.
Under Notifications , you will see Passwords. Write down your mnemonic; keep it safe. Now choose a second password. Make it something you will never forget. Write it down; keep it safe. Also, fill in a password hint. Should you leave your browser open while you're still logged in, the secondary password you entered will prevent someone from sending coins out of your account.
It does this by prompting you for a second password anytime you try to send coins. Congratulations, your account is now much safer; however, there is one more security measure you can take to make your account virtually unhackable.
It is called Two Factor Authentication. Two-factor authentication is a security process in which the user provides two means of identification, one of which is typically a physical token, such as a card, and the other of which is typically something memorized, such as a security code.
In this context, the two factors involved are sometimes spoken of as something you have and something you know. A common example of two-factor authentication is a bank card: Moving on, under Passwords , you will see Security. The problem with using blockchain.
I prefer not to store the private keys myself. On the other hand I also dont want to provide all credentials to blockchain. When the attacker gains to access to your server, they can empty the hot wallet through an API call, regardless if they or your server has access to the private keys. This API call can be blockchain. Use separate hot and cold wallets, only manually top up hot wallet from the cold wallet.
You will lose the ability to withdraw everything at any time, without manual interaction from the team, but this is the only way to prevent losing everything at once. Encrypt your server and use bare metal servers, so that your server is protected against physical attacks and malicious hosting provider attacks. You can only put relevant config files containing the API tokens to the encrypted partition and symlink the config file to the right location after manually decrypting the server on boot.
This way anybody gaining the physical or service port access to the server is less likely to gain withdraw ability.bitcoin address validation regex.