build/packaging: prep kcnd/kbnd configs for permissionless (KIP-311)#980
Open
hyunsooda wants to merge 2 commits into
Open
build/packaging: prep kcnd/kbnd configs for permissionless (KIP-311)#980hyunsooda wants to merge 2 commits into
hyunsooda wants to merge 2 commits into
Conversation
Permissionless CNs must form a full mesh sized at MaxNodeCount(100) plus reserved CN<->EN slots(3); the packaged kcnd default of 100 leaves no headroom for the mesh once the validator count nears the ceiling and the own-type connection cap gets clamped below MaxNodeCount. Constraint: CN maxconnections must be >= MaxNodeCount + reserved cross-type slots (see networks/p2p/server_util.go MaxPhysicalConnectionsLowerBound) Confidence: high Scope-risk: narrow
kbn's --authorized-nodes flag and its backing table allowlist were removed in 4879302 (discover: remove authorized nodes filtering) so that bootnodes satisfy KIP-311: a BN must accept discovery pings from any node type with no allowlist filtering. kbnd.conf still declared AUTHORIZED_NODES="" and passed it through to kbn; if an operator ever filled it in, kbn would fail to start on the now-unrecognized flag. Constraint: KIP-311 requires BN to accept UDP pings from any node type with no allowlist filtering Directive: do not reintroduce a static bootnode-level node allowlist — validator admission is handled by the dynamic on-chain CNPeers mechanism instead Confidence: high Scope-risk: narrow
hyunsooda
marked this pull request as draft
July 14, 2026 03:34
hyunsooda
changed the title
hyunsooda
marked this pull request as ready for review
July 14, 2026 03:40
2dvorak
approved these changes
Jul 14, 2026
ian0371
approved these changes
Jul 16, 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
3 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
MAXCONNECTIONS100→103 in kcnd/kcn-conf packaging (linux, rpm, windows) so the permissionless CN full mesh (MaxNodeCount 100 + reserved CN<->EN slots 3) fits without clamping.AUTHORIZED_NODES/--authorized-nodesbootnode config from kbnd packaging (linux, rpm). The flag was already deleted fromkbnin 4879302 to satisfy KIP-311 (BN must accept discovery pings from any node type, no allowlist), so a filled-in value would just fail kbn startup on an unrecognized flag.Types of changes
Checklist
I have read the CLA Document and I hereby sign the CLAin first time contribute after having read CLA$ make test)Related issues
Further comments