|
|
|
|
@ -310,7 +310,7 @@ list of IP addresses of stable Bitcoin listening nodes. Some of the DNS
|
|
|
|
|
seeds are custom implementations of BIND (Berkeley Internet Name Daemon)
|
|
|
|
|
that return a random subset from a list of Bitcoin node addresses
|
|
|
|
|
collected by a crawler or a long-running Bitcoin node. The Bitcoin Core
|
|
|
|
|
client contains the names of five different DNS seeds. The diversity of
|
|
|
|
|
client contains the names of several different DNS seeds. The diversity of
|
|
|
|
|
ownership and diversity of implementation of the different DNS seeds
|
|
|
|
|
offers a high level of reliability for the initial bootstrapping
|
|
|
|
|
process. In the Bitcoin Core client, the option to use the DNS seeds is
|
|
|
|
|
@ -368,38 +368,54 @@ $ bitcoin-cli getpeerinfo
|
|
|
|
|
[source,json]
|
|
|
|
|
----
|
|
|
|
|
[
|
|
|
|
|
{
|
|
|
|
|
"addr" : "85.213.199.39:8333",
|
|
|
|
|
"services" : "00000001",
|
|
|
|
|
"lastsend" : 1405634126,
|
|
|
|
|
"lastrecv" : 1405634127,
|
|
|
|
|
"bytessent" : 23487651,
|
|
|
|
|
"bytesrecv" : 138679099,
|
|
|
|
|
"conntime" : 1405021768,
|
|
|
|
|
"pingtime" : 0.00000000,
|
|
|
|
|
"version" : 70002,
|
|
|
|
|
"subver" : "/Satoshi:0.9.2.1/",
|
|
|
|
|
"inbound" : false,
|
|
|
|
|
"startingheight" : 310131,
|
|
|
|
|
"banscore" : 0,
|
|
|
|
|
"syncnode" : true
|
|
|
|
|
{
|
|
|
|
|
"id": 0,
|
|
|
|
|
"addr": "82.64.116.5:8333",
|
|
|
|
|
"addrbind": "192.168.0.133:50564",
|
|
|
|
|
"addrlocal": "72.253.6.11:50564",
|
|
|
|
|
"network": "ipv4",
|
|
|
|
|
"services": "0000000000000409",
|
|
|
|
|
"servicesnames": [
|
|
|
|
|
"NETWORK",
|
|
|
|
|
"WITNESS",
|
|
|
|
|
"NETWORK_LIMITED"
|
|
|
|
|
],
|
|
|
|
|
"lastsend": 1683829947,
|
|
|
|
|
"lastrecv": 1683829989,
|
|
|
|
|
"last_transaction": 0,
|
|
|
|
|
"last_block": 1683829989,
|
|
|
|
|
"bytessent": 3558504,
|
|
|
|
|
"bytesrecv": 6016081,
|
|
|
|
|
"conntime": 1683647841,
|
|
|
|
|
"timeoffset": 0,
|
|
|
|
|
"pingtime": 0.204744,
|
|
|
|
|
"minping": 0.20337,
|
|
|
|
|
"version": 70016,
|
|
|
|
|
"subver": "/Satoshi:24.0.1/",
|
|
|
|
|
"inbound": false,
|
|
|
|
|
"bip152_hb_to": true,
|
|
|
|
|
"bip152_hb_from": false,
|
|
|
|
|
"startingheight": 788954,
|
|
|
|
|
"presynced_headers": -1,
|
|
|
|
|
"synced_headers": 789281,
|
|
|
|
|
"synced_blocks": 789281,
|
|
|
|
|
"inflight": [
|
|
|
|
|
],
|
|
|
|
|
"relaytxes": false,
|
|
|
|
|
"minfeefilter": 0.00000000,
|
|
|
|
|
"addr_relay_enabled": false,
|
|
|
|
|
"addr_processed": 0,
|
|
|
|
|
"addr_rate_limited": 0,
|
|
|
|
|
"permissions": [
|
|
|
|
|
],
|
|
|
|
|
"bytessent_per_msg": {
|
|
|
|
|
...
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"addr" : "58.23.244.20:8333",
|
|
|
|
|
"services" : "00000001",
|
|
|
|
|
"lastsend" : 1405634127,
|
|
|
|
|
"lastrecv" : 1405634124,
|
|
|
|
|
"bytessent" : 4460918,
|
|
|
|
|
"bytesrecv" : 8903575,
|
|
|
|
|
"conntime" : 1405559628,
|
|
|
|
|
"pingtime" : 0.00000000,
|
|
|
|
|
"version" : 70001,
|
|
|
|
|
"subver" : "/Satoshi:0.8.6/",
|
|
|
|
|
"inbound" : false,
|
|
|
|
|
"startingheight" : 311074,
|
|
|
|
|
"banscore" : 0,
|
|
|
|
|
"syncnode" : false
|
|
|
|
|
}
|
|
|
|
|
"bytesrecv_per_msg": {
|
|
|
|
|
...
|
|
|
|
|
},
|
|
|
|
|
"connection_type": "block-relay-only"
|
|
|
|
|
},
|
|
|
|
|
]
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
@ -411,7 +427,7 @@ maintaining the peer connections automatically.
|
|
|
|
|
|
|
|
|
|
If there is no traffic on a connection, nodes will periodically send a
|
|
|
|
|
message to maintain the connection. If a node has not communicated on a
|
|
|
|
|
connection for more than 90 minutes, it is assumed to be disconnected
|
|
|
|
|
connection for too long, it is assumed to be disconnected
|
|
|
|
|
and a new peer will be sought. Thus, the network dynamically adjusts to
|
|
|
|
|
transient nodes and network problems, and can organically grow and
|
|
|
|
|
shrink as needed without any central control.((("",
|
|
|
|
|
|
David A. Harding
1 year ago