kip-311: clarify a peer counts once regardless of transport channels#123
Open
hyunsooda wants to merge 1 commit into
Open
kip-311: clarify a peer counts once regardless of transport channels#123hyunsooda wants to merge 1 commit into
hyunsooda wants to merge 1 commit into
Conversation
The MaxPhysicalConnections / inbound-capacity limits are defined in terms of "physical peer connections", which could be misread as sockets. State explicitly that a multi-channel peer counts once, so the budgets stay per-peer regardless of how many channels a peer opens. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ian0371
approved these changes
Jun 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
KIP-311 defines
MaxPhysicalConnections/ inbound capacity as "physical peerconnections", which can be misread as sockets. This adds one sentence clarifying that a
multi-channel peer counts once toward the limit, keeping the budgets per-peer.
Wording-only / non-normative — no spec or behavior change.
Pairs with kaiachain/kaia#965, which aligns inbound admission to this peer-based counting.
Types of changes
Checklist
I have read the CLA Document and I hereby sign the CLAin first time contributionRelated issues
Further comments