Category:Nodes: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
Luke-jr (talk | contribs)
Created page with "A Bitcoin node maintains connections with the Bitcoin network, and relays traffic based on policies."
 
Evoskuil (talk | contribs)
Provide more clarity and info on consensus warning.
 
(3 intermediate revisions by one other user not shown)
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.
 
==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==
 
* [[:Category:Clients|Clients]]
* [[:Category:Frontends|Frontends]]
* [[:Category:Developer|Developer]]
* [[:Category:Software|Software]]
 
==References==
 
[[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