deploy: make peer limits customizable #3132
Merged
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.
We've been raising the peering limits on our PL nodes, as the testnet grows, maxing out concurrent connections.
We also update the CometBFT default value for
p2p.allow_duplicate_ip
false -> true. The purpose of this option is raise the cost for attackers to spam a network with node/validator identities run on the same host. That's relevant for mainnet, but during testnet, we want to maximize the ability to peer, so newcomers can join in.Refs #3056.