Difference between revisions of "Category:Nodes"

From Bitcoin Wiki
Jump to: navigation, search
m (Add to Category:Software)
(Provide more clarity and info on consensus warning.)
 
Line 1: Line 1:
A Bitcoin node maintains connections with the Bitcoin network, and relays traffic based on policies.
+
A full node connects to the Bitcoin network, maintains the blockchain, and relays memory pool transactions traffic based on policies.
  
Any alternate implementation that hasn't been '''extremely''' thoroughly tested over several months should carry the warning "under construction, alpha quality, do not trust with money" because they risk splitting the network if they do not follow the reference client 100% (bug-for-bug) yet.
+
==Consensus==
 +
 
 +
Nodes other than the [[Original_Bitcoin_client|original client]] risk creating a hard fork if widely deployed and not following the consensus code as implemented in the original client 100% (bug-for-bug). There is no documented standard for Bitcoin consensus, so presently the implementation is considered the de facto standard.
 +
 
 +
The original client consensus code is maintained as a sub-library called libbitcoinconsensus within the client's source code.<ref>[https://github.com/bitcoin/bitcoin/blob/master/libbitcoinconsensus.pc.in libbitcoinconsensus]</ref> A clone of the original client consensus code is maintained as a standalone library called [[Libbitcoin_Consensus|libbitcoin-consensus]] as part of the [[Libbitcoin]] development toolkit.
  
 
==See Also==
 
==See Also==
Line 9: Line 13:
 
* [[:Category:Developer|Developer]]
 
* [[:Category:Developer|Developer]]
 
* [[:Category:Software|Software]]
 
* [[:Category:Software|Software]]
 +
 +
==References==
  
 
[[Category:Software|Software]]
 
[[Category:Software|Software]]

Latest revision as of 22:41, 12 July 2015

A full node connects to the Bitcoin network, maintains the blockchain, and relays memory pool transactions traffic based on policies.

Consensus

Nodes other than the original client risk creating a hard fork if widely deployed and not following the consensus code as implemented in the original client 100% (bug-for-bug). There is no documented standard for Bitcoin consensus, so presently the implementation is considered the de facto standard.

The original client consensus code is maintained as a sub-library called libbitcoinconsensus within the client's source code.[1] A clone of the original client consensus code is maintained as a standalone library called libbitcoin-consensus as part of the Libbitcoin development toolkit.

See Also

References