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. 126.96.36.199) or CIDR notated network (e.g. 188.8.131.52/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=184.108.40.206 ## ## addnode will connect you to and tell you about the ## ## nodes connected to 220.127.116.11. 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 18.104.22.168 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=22.214.171.124 #addnode=10.0.0.2:8333 # Alternatively use as many connect= settings as you like to connect ONLY to specific peers #connect=126.96.36.199 #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=188.8.131.52/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Это интересно:
Wallet no sync? - CRYPTOCURRENCYTALK.COM
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 Andersonbitcoin generator v5.1.0 download free.
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 creator dead - P Forex
From Bitcoin Wiki
This is a list of nodes which are considered reliable.
How to use this list
Connect to nodes
You can connect to these nodes with the -addnode=ip switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using -addnode=ip more than once. It is usually a good idea to connect to more than one of these nodes.
Nodes without a fixed ip
If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.
In order to enable hostname lookups for the -addnode and -connect parameters, you must additionally provide the -dns parameter. Example:
bitcoind -dns -addnode=bitcoin.es
Versions prior to 0.3.22 do not support hostnames to the -addnode parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)
Bitcoin Core versions prior to 0.8.0 also could send IP Transactions to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.
To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor
To use Bitcoin with one specific Tor node, run
bitcoin-qt -proxy=127.0.0.1:9050 -connect=abcde.onion
, where abcde.onion needs to be substituted with one of the Tor nodes below. These parameters can be added to bitcoin.conf to make them permanent.
You can find detailed information on running clients and hidden services within Tor in the documentation.
This entire list was last checked on 2017-11-15.
|Hostname||Owner||IP||Fixed||Status||Last Seen (GMT)||Accepts IP transactions|
|btcnode.novit.ro||ovidiusoft - novit.ro||184.108.40.206||No||Down||Yes|
|btcnode.xiro.co||Xiro Labs||220.127.116.11||Yes||Up ()||2017-11-15||No|
|Hostname||Owner||IP||Fixed||Status||Last Seen (GMT)||Accepts IP transactions|
|InductiveSoul.US||Inductive Soul||2601:7:6680:2ac:4d29:40ff:7513:fcc7||Yes||Up ()||11-13-2013 (MDY)||Yes|
|messier.bzfx.net||BZFX/A Meteorite||2001:41d0:1:d632::1||Yes||Up ()|
|stuff.liam-w.io||Liam W||2a06:8ec0:3::1:2e47||Yes||Up ()||No|
This entire list was last checked on 2017-11-15.
|Hostname||Owner||Status||Last Seen (GMT)||Accepts IP transactions|
Adding a node
Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.
To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the END NODELIST line:
|- | ip || your name
See Alsoблок биткоин кэша.
Bitcoin Core Counterparty
In this chapter we will install what is called a
full node. A full node is a program that fully validates transactions and blocks. Almost
all full nodes also help the network by accepting transactions and blocks from
other full nodes, validating those transactions and blocks, and then relaying
them to further full nodes. Most full nodes also serve lightweight clients by allowing them to transmit
their transactions to the network and by notifying them when a transaction
affects their wallet. If not enough nodes perform this function, clients won’t
be able to connect through the peer-to-peer network — they’ll have to use
centralized services instead. Many people and organizations volunteer to run full nodes using spare computing
and bandwidth resources — but more volunteers are needed to allow Bitcoin to
continue to grow. This document describes how you can help and what helping will
cost you. The full node will be reachable over IPv4, IPv6 and as Hidden Service over the Tor network. The Bitcoin blockchain is very large and grows constantly. This is because every
Bitcoin mined and every transaction ever made is recorded in the blockchain. As of April 2015 it is 32 Gigabytes. Along with indexes and other data a full
node occupies around 42 GB (Gigabytes) of disk storage space on the server. You can see the growth of the blockchain over time on the
Bitcoin Blockchain Size
website. To check the available free space of the disk who will hold the Bitcoin database: You can check the diskspace used by a running your full node as follows: This guide assumes we allocate the following IP addresses for our Bitcoin daemon: To add the IP addresses on the server: Also add them to the file Check the “Add also reverse record” when adding the IPv6 entry. Bitcoin daemons listen on TCP ports 8333 and 18333 for incoming connections. IPv4 NAT port forwarding: Allowed IPv6 connections:
$ df -h /var/lib
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/server--vg-root 456G 102G 331G 24% /
$ sudo du -hs /var/lib/bitcoind/*|sort -h
$ sudo ip addr add 192.0.2.39/24 dev eth0
$ sudo ip addr add 2001:db8::39/64 dev eth0
/etc/network/interfaces to make them
persistent across system restarts:
iface eth0 inet static address 192.0.2.39/24
iface eth0 inet6 static address 2001:db8::39/64
Bitcoin test network
Bitcoin test network
In this chapter we will install what is called a full node.
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network — they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources — but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
The full node will be reachable over IPv4, IPv6 and as Hidden Service over the Tor network.
The Bitcoin blockchain is very large and grows constantly. This is because every Bitcoin mined and every transaction ever made is recorded in the blockchain.
As of April 2015 it is 32 Gigabytes. Along with indexes and other data a full node occupies around 42 GB (Gigabytes) of disk storage space on the server.
You can see the growth of the blockchain over time on the Bitcoin Blockchain Size website.
To check the available free space of the disk who will hold the Bitcoin database:
You can check the diskspace used by a running your full node as follows:
This guide assumes we allocate the following IP addresses for our Bitcoin daemon:
To add the IP addresses on the server:
Also add them to the file
Check the “Add also reverse record” when adding the IPv6 entry.
Bitcoin daemons listen on TCP ports 8333 and 18333 for incoming connections.
IPv4 NAT port forwarding:
Allowed IPv6 connections: