mirror of
https://github.com/dashpay/dash.git
synced 2024-12-24 19:42:46 +01:00
Ignore recent rejects filter for locked txes (#3124)
* Ignore recent rejects filter for locked txes If we had a conflicting tx in the mempool before the locked tx arrived and the locked one arrived before the corresponding islock (i.e. we don't really know it's the one that should be included yet), the locked one is going to be rejected due to a mempool conflict. The old tx is going to be removed from the mempool by an incoming islock a bit later, however, we won't be able to re-request the locked tx until the tip changes because of the recentRejects filter. This patch fixes it. * Add some explanation
This commit is contained in:
parent
f2d401aa85
commit
c4be5ac4df
@ -976,7 +976,12 @@ bool static AlreadyHave(const CInv& inv) EXCLUSIVE_LOCKS_REQUIRED(cs_main)
|
||||
if (mapOrphanTransactions.count(inv.hash)) return true;
|
||||
}
|
||||
|
||||
return recentRejects->contains(inv.hash) ||
|
||||
// When we receive an islock for a previously rejected transaction, we have to
|
||||
// drop the first-seen tx (which such a locked transaction was conflicting with)
|
||||
// and re-request the locked transaction (which did not make it into the mempool
|
||||
// previously due to txn-mempool-conflict rule). This means that we must ignore
|
||||
// recentRejects filter for such locked txes here.
|
||||
return (recentRejects->contains(inv.hash) && !llmq::quorumInstantSendManager->IsLocked(inv.hash)) ||
|
||||
mempool.exists(inv.hash) ||
|
||||
pcoinsTip->HaveCoinInCache(COutPoint(inv.hash, 0)) || // Best effort: only try output 0 and 1
|
||||
pcoinsTip->HaveCoinInCache(COutPoint(inv.hash, 1));
|
||||
|
Loading…
Reference in New Issue
Block a user