BIP155: mention IPv4-in-IPv6 range MUST NOT be sent within IPV6 #2234

pull brunoerg wants to merge 1 commits into bitcoin:master from brunoerg:2026-08-bip155 changing 1 files +5 −1
  1. brunoerg commented at 2:26 PM on August 3, 2026: contributor

    There was a discrepancy between Bitcoin Core and btcd - that I noticed with bitcoinfuzz - about the rejection of IPv4-in-IPv6 when parsing an addrv2 message. btcd ended up implemented the same behavior while it raised a discussion about this not being mentioned in the BIP.

    Rejecting this kind of addresses is important for canonical encoding. The whole point of this BIP is having exactly one representation for each network. Besided that, there are other reasons such as reachability accounting, defense against evasion/bypassing address‑type policy, etc.

    That said, this PR changes BIP155 to document the behavior where IPv4 addresses embedded in IPv6 should be rejected.

  2. BIP155: mention IPv4-in-IPv6 range MUST NOT be sent within IPV6 8a4ed72e28
  3. brunoerg commented at 2:33 PM on August 3, 2026: contributor
  4. jonatack added the label Proposed BIP modification on Aug 3, 2026
  5. jonatack added the label Pending acceptance on Aug 3, 2026
  6. jonatack approved
  7. jonatack commented at 2:06 AM on August 4, 2026: member

    ACK, good and correct clarification here, consistent with the behavior of BIP155's implementation in Bitcoin Core.

    cc BIP author @laanwj for feedback or sign-off


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bips. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-08-05 15:10 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me