@@ -991,23 +991,23 @@ impl<E: EthSpec> PeerManager<E> {
991991 /// - Do not prune outbound peers to exceed our outbound target.
992992 /// - Do not prune more peers than our target peer count.
993993 /// - If we have an option to remove a number of peers, remove ones that have the least
994- /// long-lived subnets.
994+ /// long-lived subnets.
995995 /// - When pruning peers based on subnet count. If multiple peers can be chosen, choose a peer
996- /// that is not subscribed to a long-lived sync committee subnet.
996+ /// that is not subscribed to a long-lived sync committee subnet.
997997 /// - When pruning peers based on subnet count, do not prune a peer that would lower us below the
998- /// MIN_SYNC_COMMITTEE_PEERS peer count. To keep it simple, we favour a minimum number of sync-committee-peers over
999- /// uniformity subnet peers. NOTE: We could apply more sophisticated logic, but the code is
1000- /// simpler and easier to maintain if we take this approach. If we are pruning subnet peers
1001- /// below the MIN_SYNC_COMMITTEE_PEERS and maintaining the sync committee peers, this should be
1002- /// fine as subnet peers are more likely to be found than sync-committee-peers. Also, we're
1003- /// in a bit of trouble anyway if we have so few peers on subnets. The
1004- /// MIN_SYNC_COMMITTEE_PEERS
1005- /// number should be set low as an absolute lower bound to maintain peers on the sync
1006- /// committees.
998+ /// MIN_SYNC_COMMITTEE_PEERS peer count. To keep it simple, we favour a minimum number of sync-committee-peers over
999+ /// uniformity subnet peers. NOTE: We could apply more sophisticated logic, but the code is
1000+ /// simpler and easier to maintain if we take this approach. If we are pruning subnet peers
1001+ /// below the MIN_SYNC_COMMITTEE_PEERS and maintaining the sync committee peers, this should be
1002+ /// fine as subnet peers are more likely to be found than sync-committee-peers. Also, we're
1003+ /// in a bit of trouble anyway if we have so few peers on subnets. The
1004+ /// MIN_SYNC_COMMITTEE_PEERS
1005+ /// number should be set low as an absolute lower bound to maintain peers on the sync
1006+ /// committees.
10071007 /// - Do not prune trusted peers. NOTE: This means if a user has more trusted peers than the
1008- /// excess peer limit, all of the following logic is subverted as we will not prune any peers.
1009- /// Also, the more trusted peers a user has, the less room Lighthouse has to efficiently manage
1010- /// its peers across the subnets.
1008+ /// excess peer limit, all of the following logic is subverted as we will not prune any peers.
1009+ /// Also, the more trusted peers a user has, the less room Lighthouse has to efficiently manage
1010+ /// its peers across the subnets.
10111011 ///
10121012 /// Prune peers in the following order:
10131013 /// 1. Remove worst scoring peers
0 commit comments