github.com/number571/tendermint@v0.34.11-gost/internal/p2p/pex/doc.go (about) 1 /* 2 Package PEX (Peer exchange) handles all the logic necessary for nodes to share 3 information about their peers to other nodes. Specifically, this is the exchange 4 of addresses that a peer can use to discover more peers within the network. 5 6 The PEX reactor is a continuous service which periodically requests addresses 7 and serves addresses to other peers. There are two versions of this service 8 aligning with the two p2p frameworks that Tendermint currently supports. 9 10 V1 is coupled with the Switch (which handles peer connections and routing of 11 messages) and, alongside exchanging peer information in the form of port/IP 12 pairs, also has the responsibility of dialing peers and ensuring that a 13 node has a sufficient amount of peers connected. 14 15 V2 is embedded with the new p2p stack and uses the peer manager to advertise 16 peers as well as add new peers to the peer store. The V2 reactor passes a 17 different set of proto messages which include a list of 18 [urls](https://golang.org/pkg/net/url/#URL).These can be used to save a set of 19 endpoints that each peer uses. The V2 reactor has backwards compatibility with 20 V1. It can also handle V1 messages. 21 22 The V2 reactor is able to tweak the intensity of it's search by decreasing or 23 increasing the interval between each request. It tracks connected peers via a 24 linked list, sending a request to the node at the front of the list and adding 25 it to the back of the list once a response is received. Using this method, a 26 node is able to spread out the load of requesting peers across all the peers it 27 is currently connected with. 28 29 With each inbound set of addresses, the reactor monitors the amount of new 30 addresses to already seen addresses and uses the information to dynamically 31 build a picture of the size of the network in order to ascertain how often the 32 node needs to search for new peers. 33 */ 34 package pex