joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 09:46:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add node glossary term and full node types in dev guide

Browse source 
Added a node glossary term

Added descriptions of full nodes, archival nodes, and pruned nodes to the dev guide.

Linked the term "peer" to node instead of original location.
This commit is contained in:
Andrew Chow 2017-05-21 22:48:52 -04:00
parent 582be1bf61
commit 2390680b5d
5 changed files with 38 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

9
_includes/devdoc/guide_p2p_network.md
View file

@ -10,10 +10,13 @@ http://opensource.org/licenses/MIT.
{% autocrossref %}
The Bitcoin network protocol allows full nodes
([peers][peer]{:#term-peer}{:.term}) to collaboratively maintain a
(peers) to collaboratively maintain a
[peer-to-peer network][network]{:#term-network}{:.term} for block and
transaction exchange. Many SPV clients also use this protocol to connect
to full nodes.
transaction exchange. Full nodes download and verify every block and transaction
prior to relaying them to other nodes. Archival nodes are full nodes which
store the entire blockchain and can serve historical blocks to other nodes.
Pruned nodes are full nodes which do not store the entire blockchain. Many SPV
clients also use the Bitcoin network protocol to connect to full nodes.
Consensus rules do not cover networking, so Bitcoin programs may use
alternative networks and protocols, such as the [high-speed block relay