From c743491c5a2bbecebb46c16f35209d399bbbd67a Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Sun, 27 Mar 2022 18:19:40 +0000 Subject: [PATCH] Allow `txn-mempool-conflict` errors when broadcasting transactions This can be seen, among other times, when a channel is cooperatively- (or counterparty-)closed and we restart, causing us to attempt to broadcast our local commitment tx, which conflicts with the original closing transaction. --- src/bitcoind_client.rs | 1 + 1 file changed, 1 insertion(+) diff --git a/src/bitcoind_client.rs b/src/bitcoind_client.rs index 0b37ac3..15ee8cf 100644 --- a/src/bitcoind_client.rs +++ b/src/bitcoind_client.rs @@ -265,6 +265,7 @@ impl BroadcasterInterface for BitcoindClient { if !err_str.contains("Transaction already in block chain") && !err_str.contains("Inputs missing or spent") && !err_str.contains("bad-txns-inputs-missingorspent") + && !err_str.contains("txn-mempool-conflict") && !err_str.contains("non-BIP68-final") && !err_str.contains("insufficient fee, rejecting replacement ") { -- 2.39.5