@@ -441,17 +441,17 @@ frequently have to re-establish sessions to its peers.
441
441
442
442
### Limiting resource consumption of peers behind symmetric NATs, useful for light-clients
443
443
444
- Peers with non-contactable ENRs do not get inserted into kbuckets. Nodes that are behind
444
+ Peers with uncontactable ENRs do not get inserted into kbuckets. Nodes that are behind
445
445
symmetric NATs will naturally never succeed in pinpointing one external socket for peers
446
- to reach them on by [runtime address discovery] and therefore their non-contactable ENRs
446
+ to reach them on by [runtime address discovery] and therefore their uncontactable ENRs
447
447
will never update to contactable ENRs. This means, these peers will never respond to
448
448
requests, as only peers in kbucktes are sent requests. This does not cohere with the
449
- p2p-model, rather the server-client model where the peer with a non-contactable ENR acts
449
+ p2p-model, rather the server-client model where the peer with a uncontactable ENR acts
450
450
as the client. This misalignment is especially bothersome for well behaving (externally
451
451
reachable) light-clients operating on limited resources. Discv5.2 corrects this
452
452
side-effect of [runtime address discovery] by setting introducing a configurable limit to
453
- the number of sessions at a time with peers with non-contactable ENRs, the lower limit
454
- being 1. Nodes must accept sessions with at least one peer with a non-contactable ENR to
453
+ the number of sessions at a time with peers with uncontactable ENRs, the lower limit
454
+ being 1. Nodes must accept sessions with at least one peer with a uncontactable ENR to
455
455
for [runtime address discovery] to be enabled on the discv5.2 network.
456
456
457
457
### Fault tolerance
0 commit comments