From 0c1d1ae175b2b891d3baa227f2b38208713d8157 Mon Sep 17 00:00:00 2001 From: Kuziwa Sachikonye Date: Mon, 27 May 2019 11:01:25 +0200 Subject: [PATCH] changed the word from reliable to persistant for clarity --- ch08.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch08.asciidoc b/ch08.asciidoc index d2a22c15..074e0e7f 100644 --- a/ch08.asciidoc +++ b/ch08.asciidoc @@ -93,7 +93,7 @@ Once one or more connections are established, the new node will send an +addr+ m .Address propagation and discovery image::images/mbc2_0805.png["AddressPropagation"] -A node must connect to a few different peers in order to establish diverse paths into the bitcoin network. Paths are not reliable—nodes come and go—and so the node must continue to discover new nodes as it loses old connections as well as assist other nodes when they bootstrap. Only one connection is needed to bootstrap, because the first node can offer introductions to its peer nodes and those peers can offer further introductions. It's also unnecessary and wasteful of network resources to connect to more than a handful of nodes. After bootstrapping, a node will remember its most recent successful peer connections, so that if it is rebooted it can quickly reestablish connections with its former peer network. If none of the former peers respond to its connection request, the node can use the seed nodes to bootstrap again. +A node must connect to a few different peers in order to establish diverse paths into the bitcoin network. Paths are not persistent —nodes come and go—and so the node must continue to discover new nodes as it loses old connections as well as assist other nodes when they bootstrap. Only one connection is needed to bootstrap, because the first node can offer introductions to its peer nodes and those peers can offer further introductions. It's also unnecessary and wasteful of network resources to connect to more than a handful of nodes. After bootstrapping, a node will remember its most recent successful peer connections, so that if it is rebooted it can quickly reestablish connections with its former peer network. If none of the former peers respond to its connection request, the node can use the seed nodes to bootstrap again. On a node running the Bitcoin Core client, you can list the peer connections with the command +getpeerinfo+: