bitcoin-dev

BIP151 protocol incompatibility

BIP151 protocol incompatibility

Original Postby Eric Voskuil

Posted on: February 13, 2017 05:18 UTC

The BIP151 proposal claims to be backward compatible, but this statement is incorrect.

According to the proposal, non-supporting peers will ignore the encinit messages. However, sending content that existing nodes do not expect is clearly an incompatibility. This can leave an implementation open to DOS attacks if it ignores invalid content. The version handshake must be complete before the protocol level can be determined. Although it may be desirable for this change to come before the version handshake, it cannot be described as backward compatible.