Full node - Revision history

NotATether: Update sizes

2025-12-14T10:57:13Z

Update sizes

← Older revision		Revision as of 10:57, 14 December 2025
Line 15:		Line 15:
	Nodes that have different ''consensus'' rules are actually using two different networks/currencies. Changing any of the consensus rules requires a [[hard fork]], which can be thought of as creating a new currency and having everyone move to it. Consensus rules are different from ''policy'' rules, which specify how a node or miner prioritizes or discourages certain things. Policy rules can be changed freely, and different nodes can have different policy rules. Because all full nodes must use ''exactly'' the same consensus rules in order to remain compatible with each other, even duplicating bugs and oddities in the original consensus rules, creating a full node from scratch is extremely difficult and dangerous. It is therefore recommended that everyone who wishes to run a full node uses software based on the [[reference client]], which is the only client guaranteed to behave correctly.		Nodes that have different ''consensus'' rules are actually using two different networks/currencies. Changing any of the consensus rules requires a [[hard fork]], which can be thought of as creating a new currency and having everyone move to it. Consensus rules are different from ''policy'' rules, which specify how a node or miner prioritizes or discourages certain things. Policy rules can be changed freely, and different nodes can have different policy rules. Because all full nodes must use ''exactly'' the same consensus rules in order to remain compatible with each other, even duplicating bugs and oddities in the original consensus rules, creating a full node from scratch is extremely difficult and dangerous. It is therefore recommended that everyone who wishes to run a full node uses software based on the [[reference client]], which is the only client guaranteed to behave correctly.

	At minimum, a full node must download every transaction that has ever taken place, all new transactions, and all block headers. Additionally, full nodes must store information about every unspent transaction output until it is spent. By default full nodes are inefficient in that they download each new transaction at least twice, and they store the entire block chain (more than ~~165~~ GB as of ~~20180214~~) forever, even though only the unspent transaction outputs (<2 GB) are required. Performance can improved by enabling <code>[https://bitcointalk.org/index.php?topic=1377345.0 -blocksonly]</code> mode and enabling [https://bitcoin.org/en/release/v0.12.0#wallet-pruning pruning].		At minimum, a full node must download every transaction that has ever taken place, all new transactions, and all block headers. Additionally, full nodes must store information about every unspent transaction output until it is spent. By default full nodes are inefficient in that they download each new transaction at least twice, and they store the entire block chain (more than 600 GB as of 2025) forever, even though only the unspent transaction outputs (<15 GB) are required. Performance can improved by enabling <code>[https://bitcointalk.org/index.php?topic=1377345.0 -blocksonly]</code> mode and enabling [https://bitcoin.org/en/release/v0.12.0#wallet-pruning pruning], and by using faster storage devices such as SSDs.

	===Archival Nodes===		===Archival Nodes===

NotATether: Add image of Bitcoin Core

2025-12-14T10:51:03Z

Add image of Bitcoin Core

← Older revision		Revision as of 10:51, 14 December 2025
Line 1:		Line 1:
	Any computer that connects to the Bitcoin [[network]] is called a '''node'''. Nodes that fully verify all of the rules of Bitcoin are called '''full nodes'''. The most popular software implementation of full nodes is called [[Bitcoin Core]], its latest release can be found [https://github.com/bitcoin/bitcoin/releases on the github page]. Another less popular software implementation of full nodes is called [[Bitcoin Knots]], its latest release can be found [https://github.com/bitcoinknots/bitcoin/releases on the github page].		Any computer that connects to the Bitcoin [[network]] is called a '''node'''. Nodes that fully verify all of the rules of Bitcoin are called '''full nodes'''. The most popular software implementation of full nodes is called [[Bitcoin Core]], its latest release can be found [https://github.com/bitcoin/bitcoin/releases on the github page]. Another less popular software implementation of full nodes is called [[Bitcoin Knots]], its latest release can be found [https://github.com/bitcoinknots/bitcoin/releases on the github page].

			[[File:BitcoinCore-node.jpg\|thumb\|upright=1\|The main window of Bitcoin Core]]

	==What makes a full node?==		==What makes a full node?==

Fiach: Updated to remove a 404 link to a no longer maintained forked full node, replaced this with a link to a list of currently maintained and no longer maintained full nodes. Also added a note/link mentioning Bitcoin Knots as it's now a notable portion of

2025-09-22T17:58:46Z

Updated to remove a 404 link to a no longer maintained forked full node, replaced this with a link to a list of currently maintained and no longer maintained full nodes. Also added a note/link mentioning Bitcoin Knots as it's now a notable portion of

← Older revision		Revision as of 17:58, 22 September 2025
Line 1:		Line 1:
	Any computer that connects to the Bitcoin [[network]] is called a '''node'''. Nodes that fully verify all of the rules of Bitcoin are called '''full nodes'''. The most popular software implementation of full nodes is called [[Bitcoin Core]], its latest release can be found [https://github.com/bitcoin/bitcoin/releases on the github page].		Any computer that connects to the Bitcoin [[network]] is called a '''node'''. Nodes that fully verify all of the rules of Bitcoin are called '''full nodes'''. The most popular software implementation of full nodes is called [[Bitcoin Core]], its latest release can be found [https://github.com/bitcoin/bitcoin/releases on the github page]. Another less popular software implementation of full nodes is called [[Bitcoin Knots]], its latest release can be found [https://github.com/bitcoinknots/bitcoin/releases on the github page].

	==What makes a full node?==		==What makes a full node?==
Line 65:		Line 65:
	If you run the [[Bitcoin Core]]/[[bitcoind]] wallet, you are running a full node. If you open port 8333, you will contribute to the network's capacity. If you actually use the wallet feature, or if you use a lightweight client like [[MultiBit]] but configure it to connect exclusively to your full node, then you will contribute to the network's economic strength and receive protection from some possible attacks against lightweight nodes.		If you run the [[Bitcoin Core]]/[[bitcoind]] wallet, you are running a full node. If you open port 8333, you will contribute to the network's capacity. If you actually use the wallet feature, or if you use a lightweight client like [[MultiBit]] but configure it to connect exclusively to your full node, then you will contribute to the network's economic strength and receive protection from some possible attacks against lightweight nodes.

	There are a few alternate full node implementations, but they are not recommended for serious use because it is currently difficult to determine whether they implement the consensus rules with 100% accuracy. Even very slight inaccuracies could cause serious problems for the users of these alternate clients. Example of implementations [https://~~bitcore~~.io/~~guides~~/full-node~~/ Bitcore], [[libbitcoin]], [[btcd]~~].		There are a few alternate full node implementations, but they are not recommended for serious use because it is currently difficult to determine whether they implement the consensus rules with 100% accuracy. Even very slight inaccuracies could cause serious problems for the users of these alternate clients. Example of implementations [[libbitcoin]], [[btcd]], [https://bitcoinfo.org/bitcoin-information/full-node.html a list of other Full Nodes].

	=== Tips and tricks for running a node ===		=== Tips and tricks for running a node ===

V: Fixed current block subsidy value.

2024-10-18T20:25:56Z

Fixed current block subsidy value.

← Older revision		Revision as of 20:25, 18 October 2024
Line 4:		Line 4:

	Full nodes download every block and transaction and check them against Bitcoin's consensus rules. Here are examples of consensus rules, though there are many more:		Full nodes download every block and transaction and check them against Bitcoin's consensus rules. Here are examples of consensus rules, though there are many more:
	* Blocks may only [[controlled supply\|create]] a certain number of bitcoins. (Currently 6.25 BTC per block.)		* Blocks may only [[controlled supply\|create]] a certain number of bitcoins. (Currently 3.125 BTC per block.)
	* Transactions must have correct signatures for the bitcoins being spent.		* Transactions must have correct signatures for the bitcoins being spent.
	* Transactions/blocks must be in the correct data format.		* Transactions/blocks must be in the correct data format.

Tris T7: /* Privacy */ edit ref

2022-04-08T16:16:09Z

Privacy: edit ref

← Older revision		Revision as of 16:16, 8 April 2022
Line 38:		Line 38:
	=== Privacy ===		=== Privacy ===

	Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ [[BIP37 privacy problems\|do not provide much privacy]] against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.		Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ [[BIP37 privacy problems\|do not provide much privacy]] against nodes who connected directly to the wallet.<ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>

	For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.		For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.

Furunodo: /* What makes a full node? */ 6.25

2020-06-23T10:32:34Z

What makes a full node?: 6.25

← Older revision		Revision as of 10:32, 23 June 2020
Line 4:		Line 4:

	Full nodes download every block and transaction and check them against Bitcoin's consensus rules. Here are examples of consensus rules, though there are many more:		Full nodes download every block and transaction and check them against Bitcoin's consensus rules. Here are examples of consensus rules, though there are many more:
	* Blocks may only [[controlled supply\|create]] a certain number of bitcoins. (Currently 12.5 BTC per block.)		* Blocks may only [[controlled supply\|create]] a certain number of bitcoins. (Currently 6.25 BTC per block.)
	* Transactions must have correct signatures for the bitcoins being spent.		* Transactions must have correct signatures for the bitcoins being spent.
	* Transactions/blocks must be in the correct data format.		* Transactions/blocks must be in the correct data format.

Furunodo: /* Tips and tricks for running a node */ ` =>

2020-06-10T21:33:57Z Tips and tricks for running a node: ` => <tt> ← Older revision Revision as of 21:33, 10 June 2020 Line 79: Line 79: * Improve sync speed by increasing the dbcache value in configuration. This value controls how many megabytes of RAM to use for the database cache, increase it to as much as your hardware allows to reduce the disk operations and increase speed. * Improve sync speed by increasing the dbcache value in configuration. This value controls how many megabytes of RAM to use for the database cache, increase it to as much as your hardware allows to reduce the disk operations and increase speed. * To store the blockchain files on an external hard drive use `-datadir`. e.g. `-datadir=/path/to/your/bitcoin/directory`. * To store the blockchain files on an external hard drive use <tt>-datadir</tt>. e.g. <tt>-datadir=/path/to/your/bitcoin/directory</tt>. * Store the chainstate directory on an SSD drive to improve the speed.<ref>[https://www.reddit.com/r/Bitcoin/comments/7iaa3t/if_you_run_a_full_node_on_a_hdd_put_your/ If you run a full node on a hdd put your chainstate directory on an external ssd].</ref> * Store the chainstate directory on an SSD drive to improve the speed.<ref>[https://www.reddit.com/r/Bitcoin/comments/7iaa3t/if_you_run_a_full_node_on_a_hdd_put_your/ If you run a full node on a hdd put your chainstate directory on an external ssd].</ref>

Belcher: /* Privacy */ Add link to BIP37 privacy problems 2019-02-18T14:37:47Z Privacy: Add link to BIP37 privacy problems ← Older revision Revision as of 14:37, 18 February 2019 Line 38: Line 38: === Privacy === === Privacy === Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>. Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ [[BIP37 privacy problems|do not provide much privacy]] against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>. For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits. For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits. Belcher: /* References */ Add to category privacy 2019-02-15T20:12:59Z References: Add to category privacy ← Older revision Revision as of 20:12, 15 February 2019 Line 98: Line 98: [[Category:Technical]] [[Category:Technical]] [[Category:Privacy]] {{Bitcoin Core documentation}} {{Bitcoin Core documentation}} Belcher: /* Privacy */ Rephrased, the important part is downloading all the blocks, not storing them on your hard disk 2018-11-26T22:18:03Z Privacy: Rephrased, the important part is downloading all the blocks, not storing them on your hard disk ← Older revision Revision as of 22:18, 26 November 2018 Line 38: Line 38: === Privacy === === Privacy === Having the blockchain stored on your hard drive is the most private way to have a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>. Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>. For many use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits. For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits. === Security === === Security ===

← Older revision		Revision as of 21:33, 10 June 2020
Line 79:		Line 79:
	* Improve sync speed by increasing the dbcache value in configuration. This value controls how many megabytes of RAM to use for the database cache, increase it to as much as your hardware allows to reduce the disk operations and increase speed.		* Improve sync speed by increasing the dbcache value in configuration. This value controls how many megabytes of RAM to use for the database cache, increase it to as much as your hardware allows to reduce the disk operations and increase speed.

	* To store the blockchain files on an external hard drive use `-datadir`. e.g. `-datadir=/path/to/your/bitcoin/directory`.		* To store the blockchain files on an external hard drive use <tt>-datadir</tt>. e.g. <tt>-datadir=/path/to/your/bitcoin/directory</tt>.

	* Store the chainstate directory on an SSD drive to improve the speed.<ref>[https://www.reddit.com/r/Bitcoin/comments/7iaa3t/if_you_run_a_full_node_on_a_hdd_put_your/ If you run a full node on a hdd put your chainstate directory on an external ssd].</ref>		* Store the chainstate directory on an SSD drive to improve the speed.<ref>[https://www.reddit.com/r/Bitcoin/comments/7iaa3t/if_you_run_a_full_node_on_a_hdd_put_your/ If you run a full node on a hdd put your chainstate directory on an external ssd].</ref>

← Older revision		Revision as of 14:37, 18 February 2019
Line 38:		Line 38:
	=== Privacy ===		=== Privacy ===

	Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.		Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ [[BIP37 privacy problems\|do not provide much privacy]] against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.

	For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.		For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.

← Older revision		Revision as of 20:12, 15 February 2019
Line 98:		Line 98:

	[[Category:Technical]]		[[Category:Technical]]
			[[Category:Privacy]]

	{{Bitcoin Core documentation}}		{{Bitcoin Core documentation}}

← Older revision		Revision as of 22:18, 26 November 2018
Line 38:		Line 38:
	=== Privacy ===		=== Privacy ===

	~~Having~~ the blockchain ~~stored on your hard drive~~ is the most private way to ~~have~~ a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.		Downloading the entire blockchain is the most private way to operate a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.

	For ~~many~~ use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.		For some use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.

	=== Security ===		=== Security ===