Skip to content

Conversation

@davecgh
Copy link
Member

@davecgh davecgh commented Jan 20, 2026

Due to legacy reasons that no longer apply, the logic that handles banned peers currently happens after version negotiation has taken place. While there is nothing inherently wrong with it happening after negotiation, it does mean that it is doing additional work that is no longer strictly required.

With that in mind, this refactors the logic that handles banned peers to happen immediately upon seeing new connections.

@davecgh davecgh added this to the 2.2.0 milestone Jan 20, 2026
Due to legacy reasons that no longer apply, the logic that handles
banned peers currently happens after version negotiation has taken
place.  While there is nothing inherently wrong with it happening after
negotiation, it does mean that it is doing additional work that is no
longer strictly required.

With that in mind, this refactors the logic that handles banned peers to
happen immediately upon seeing new connections.
@davecgh davecgh merged commit f18b111 into decred:master Jan 23, 2026
34 checks passed
@davecgh davecgh deleted the server_early_ban branch January 23, 2026 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants