mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-24 23:48:32 +00:00
Edited ch10_network.adoc with Atlas code editor
This commit is contained in:
parent
fc106710db
commit
d157d541fc
@ -39,17 +39,17 @@ protocols in this chapter in addition to the base Bitcoin P2P protocol.
|
||||
|
||||
=== Node Types and Roles
|
||||
|
||||
Although full nodes (peers) in the Bitcoin P2P network are equal to each other,
|
||||
Although((("Bitcoin network", "nodes", "types of")))((("nodes", "types of")))((("full nodes", "purpose of")))((("peers"))) full nodes (peers) in the Bitcoin P2P network are equal to each other,
|
||||
they may take on different roles depending on the functionality they are
|
||||
supporting. A Bitcoin full node validates blocks and may contain other
|
||||
functions, such as routing, mining, and wallet services.
|
||||
|
||||
Some nodes, called _archival full nodes_, also maintain a
|
||||
Some nodes, called _archival full nodes_, also ((("archival full nodes")))maintain a
|
||||
complete and up-to-date copy of the blockchain.
|
||||
Those nodes can
|
||||
serve data to clients that store
|
||||
only a subset of the blockchain and partly verify transactions using a method
|
||||
called _simplified payment verification_, or SPV. These clients are known as lightweight clients.
|
||||
((("SPV (simplified-payment-verification) clients")))((("lightweight clients")))called _simplified payment verification_, or SPV. These clients are known as lightweight clients.
|
||||
|
||||
Miners compete to create new blocks by
|
||||
running specialized hardware to solve the proof-of-work algorithm. Some
|
||||
|
Loading…
Reference in New Issue
Block a user