Skip to content

Conversation

@ajtowns
Copy link
Contributor

@ajtowns ajtowns commented Jan 7, 2026

Abstract:

This BIP defines a peer-to-peer message that can be used for announcements and negotiation related to support of new peer-to-peer features.

Mailing list post: https://gnusha.org/pi/bitcoindev/aUUXLgEUCgGb122o@erisian.com.au/T/#u

@murchandamus murchandamus changed the title BIP???: Peer feature negotiation BIP Draft: Peer Feature Negotiation Jan 8, 2026
Copy link
Contributor

@murchandamus murchandamus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your submission. This proposal appears already complete from an editorial perspective, and I have hardly any other comments. It would be great to see some P2P experts weigh in, but otherwise, this seems fairly mature.

## Abstract

This BIP defines a peer-to-peer message that can be used for announcements
and negotiation related to support of new peer-to-peer features.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
and negotiation related to support of new peer-to-peer features.
and negotiation related to support of new or optional peer-to-peer features.

basis, or when there is disagreement amongst implementations or users
as to which approach is most desirable.

## Considerations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I’m interpreting this as the stand-in for the Rationale section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants