aboutsummaryrefslogtreecommitdiff
path: root/test/functional/mempool_unbroadcast.py
diff options
context:
space:
mode:
authorJohn Newbery <john@johnnewbery.com>2021-06-16 10:47:56 +0100
committerJohn Newbery <john@johnnewbery.com>2021-07-09 17:24:08 +0100
commit2837a9f1eaa2c6bf402d1d9891d9aa84c4a56033 (patch)
tree5e9afdc056a180a8c83377b2d6be52cb5b847e25 /test/functional/mempool_unbroadcast.py
parent8ab0c77299a5b184a8d0edf38f26a97bf9bbed6e (diff)
downloadbitcoin-2837a9f1eaa2c6bf402d1d9891d9aa84c4a56033.tar.xz
[mempool] Only add a transaction to the unbroadcast set when it's added to the mempool
Currently, if BroadcastTransaction() is called to rebroadcast a transaction (e.g. by ResendWalletTransactions()), then we add the transaction to the unbroadcast set. That transaction has already been broadcast in the past, so peers are unlikely to request it again, meaning RemoveUnbroadcastTx() won't be called and it won't be removed from m_unbroadcast_txids. Net processing will therefore continue to attempt rebroadcast for the transaction every 10-15 minutes. This will most likely continue until the node connects to a new peer which hasn't yet seen the transaction (or perhaps indefinitely). Fix by only adding the transaction to the broadcast set when it's added to the mempool.
Diffstat (limited to 'test/functional/mempool_unbroadcast.py')
0 files changed, 0 insertions, 0 deletions