diff options
author | MarcoFalke <falke.marco@gmail.com> | 2021-03-24 19:28:21 +0100 |
---|---|---|
committer | MarcoFalke <falke.marco@gmail.com> | 2021-03-24 19:28:24 +0100 |
commit | ed49203daabb6550d44518792c30faad64bf9a9f (patch) | |
tree | 88d7c94dd8fc6001de0bb6577635d9c7165dfe04 /src/consensus/tx_verify.h | |
parent | 23b15601dfeb0f4e61343acce3bf3111f54ea6e7 (diff) | |
parent | 39a9ec579f023ab262a1abd1f0c869be5b1f3f4d (diff) |
Merge #21357: test: Unconditionally check for fRelay field in test framework
39a9ec579f023ab262a1abd1f0c869be5b1f3f4d Unconditionally check for fRelay field in test framework (Troy Giorshev)
Pull request description:
picking up #20411 (rebased onto master)
There is a discrepancy in the implementation of our p2p protocol between
bitcoind and the testing framework. The fRelay field is an optional
field at the end of a version message as of protocol version 70001.
However, when deserializing a message in bitcoind, we don't check the
version to see if it should have an fRelay field or not. Instead, we
unconditionally attempt to deserialize into the field.
This commit brings the testing framework in line with the implementation
in core.
This matters for a version message with the following fields:
Version = 60000
fRelay = 1
Bitcoind would deserialize this into a version message with
Version=60000 and fRelay=1, whereas (before this commit) our testing
framework would deserialize this into a version message with
Version=60000 and fRelay=0.
ACKs for top commit:
jnewbery:
utACK 39a9ec579f023ab262a1abd1f0c869be5b1f3f4d
Tree-SHA512: 13a23f1180b7121ba41cb85baa38094b41f4607a7c88b3384775177cb116e76faf5514760624f98a4e8a830767407c46753a7e0285158c33e0c6ce395de8f15c
Diffstat (limited to 'src/consensus/tx_verify.h')
0 files changed, 0 insertions, 0 deletions