Author: Mike Hearn 2013-06-19 10:43:29
Published on: 2013-06-19T10:43:29+00:00
The discussion in this context is related to the Bitcoin version message field and its variable length. The issue being discussed is whether or not the fRelayTxes flag should be optional, with one person suggesting that it should be fixed for each protocol version. The standard BIP 37 does not require the flag to appear, but rather states that if it is false then broadcast transactions will not be announced until a filter{load,add,clear} command is received. Bitcoin-Qt on master sends it now although it doesn't affect anything. The code in main.cpp indicates the number of fields per protocol version has always been variable length. The argument against this is that a deterministic number of fields per protocol version is more sensible and easier for parsing messages. However, making it optional is necessary because old clients don't send it.
Updated on: 2023-06-06T19:06:24.702557+00:00