diff options
| author | WeebDataHoarder <weebdatahoarder@noreply.gammaspectra.live> | 2025-09-24 09:07:20 +0200 |
|---|---|---|
| committer | WeebDataHoarder <weebdatahoarder@noreply.gammaspectra.live> | 2025-09-24 09:22:28 +0200 |
| commit | 39c7a228563a7120469369554fbd4dce92cb7eba (patch) | |
| tree | 8940c95778d85b966cd2b55bcc0515acc87d12d7 /src/rpc | |
| parent | 0eaac4445efc9f25ff17e79cf3166671d2289d77 (diff) | |
| download | monzero-core-39c7a228563a7120469369554fbd4dce92cb7eba.tar.gz monzero-core-39c7a228563a7120469369554fbd4dce92cb7eba.tar.xz monzero-core-39c7a228563a7120469369554fbd4dce92cb7eba.zip | |
Send ZMQ miner notifications after txpool additions
Bug was introduced in c069c04ede338929c50297558fee15192aa0f67c, before this txpool additions were not notified on block addition
When receiving blocks with previously unknown conditions, miner data was sent first, but txpool add events for already-added transactions in previous block were sent afterward. Miners would then include already-mined transactions in their new templates due to receiving the mistimed txpool add event.
The fix is to send miner notifications AFTER txpool events are sent, and before normal block notifications are sent (for mining switch speed purposes)
Fixes c069c04ede338929c50297558fee15192aa0f67c / #9135
Fixes dfee15eee18a97be5a8fb9822527f98ebd1b33e9 / #7891
Diffstat (limited to 'src/rpc')
0 files changed, 0 insertions, 0 deletions