mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2025-02-16 17:42:06 +00:00
Edited ch10_network.adoc with Atlas code editor
This commit is contained in:
parent
5ae29e5db4
commit
bb86b3766b
@ -282,7 +282,7 @@ acknowledge the +version+ message and establish a connection by sending
|
|||||||
a +verack+.
|
a +verack+.
|
||||||
|
|
||||||
How does a new node find peers? The first method is to query DNS using a
|
How does a new node find peers? The first method is to query DNS using a
|
||||||
number of _DNS seeds_, which are DNS servers that provide a list of IP
|
number of _DNS seeds_, which are((("DNS seeds"))) DNS servers that provide a list of IP
|
||||||
addresses of Bitcoin nodes. Some of those DNS seeds provide a static
|
addresses of Bitcoin nodes. Some of those DNS seeds provide a static
|
||||||
list of IP addresses of stable Bitcoin listening nodes. Some of the DNS
|
list of IP addresses of stable Bitcoin listening nodes. Some of the DNS
|
||||||
seeds are custom implementations of BIND (Berkeley Internet Name Daemon)
|
seeds are custom implementations of BIND (Berkeley Internet Name Daemon)
|
||||||
@ -411,7 +411,7 @@ shrink as needed without any ((("Bitcoin network", "nodes", "network discovery",
|
|||||||
|
|
||||||
=== Full Nodes
|
=== Full Nodes
|
||||||
|
|
||||||
Full nodes are nodes that verify every transaction in every block on the
|
Full nodes ((("Bitcoin network", "nodes", "full nodes, purpose of")))((("nodes", "full nodes", "purpose of")))((("full nodes", "purpose of")))are nodes that verify every transaction in every block on the
|
||||||
valid blockchain with the most proof of work.
|
valid blockchain with the most proof of work.
|
||||||
|
|
||||||
Full nodes
|
Full nodes
|
||||||
|
Loading…
Reference in New Issue
Block a user