[bug]: unable to bump a channel open transaction

[rkfg]

Background

Bumping the UTXO with lncli wallet bumpfee --conf_target 3 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, no error reported. After exactly 30 seconds the CPFP tx is created and instantly removed as "invalid", it's never broadcasted. Tried the same with --sat_per_vbyte with any number up to 20, same outcome.

Mar 11 11:09:28 fullnode lnd[1252982]: 2023-03-11 11:09:28.529 [INF] SWPR: Candidate sweep set of size=1 (+0 wallet inputs), has yield=0.00519214 BTC, weight=397
Mar 11 11:09:28 fullnode lnd[1252982]: 2023-03-11 11:09:28.531 [INF] SWPR: Sweep candidates at height=780267 with fee_rate=1886 sat/kw, yield 1 distinct txns
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.534 [INF] SWPR: Candidate sweep set of size=1 (+0 wallet inputs), has yield=0.00519214 BTC, weight=397
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.539 [INF] SWPR: Creating sweep transaction 199a1f155bbc523e8a9328177211f7deaf1145a756dfbebf38d4c4ec7e7b48d1 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1886 sat/kw, tx_weight=445, tx_fee=0.00000839 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.545 [INF] LNWL: Inserting unconfirmed transaction 199a1f155bbc523e8a9328177211f7deaf1145a756dfbebf38d4c4ec7e7b48d1
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.637 [INF] LNWL: Removed invalid transaction: (*wire.MsgTx)(0x405e051580)({
Mar 11 11:09:58 fullnode lnd[1252982]:  Version: (int32) 2,
Mar 11 11:09:58 fullnode lnd[1252982]:  TxIn: ([]*wire.TxIn) (len=1 cap=15) {
Mar 11 11:09:58 fullnode lnd[1252982]:   (*wire.TxIn)(0x4053df5aa0)({
Mar 11 11:09:58 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 11 11:09:58 fullnode lnd[1252982]:    SignatureScript: ([]uint8) <nil>,
Mar 11 11:09:58 fullnode lnd[1252982]:    Witness: (wire.TxWitness) (len=1 cap=1) {
Mar 11 11:09:58 fullnode lnd[1252982]:     ([]uint8) (len=64 cap=64) {
Mar 11 11:09:58 fullnode lnd[1252982]:      00000000  1f b9 b7 0b 8f 8c 52 45  23 1b e9 db 23 23 bd 8f  |......RE#...##..|
Mar 11 11:09:58 fullnode lnd[1252982]:      00000010  64 9f 65 cd a8 b0 72 4d  44 f2 87 cc ce 90 d3 13  |d.e...rMD.......|
Mar 11 11:09:58 fullnode lnd[1252982]:      00000020  c5 2b fb 12 ec d8 43 eb  bb 95 83 a3 04 57 3e 92  |.+....C......W>.|
Mar 11 11:09:58 fullnode lnd[1252982]:      00000030  de 53 55 7e 61 d1 9d 5e  60 17 b9 73 d1 21 f2 aa  |.SU~a..^`..s.!..|
Mar 11 11:09:58 fullnode lnd[1252982]:     }
Mar 11 11:09:58 fullnode lnd[1252982]:    },
Mar 11 11:09:58 fullnode lnd[1252982]:    Sequence: (uint32) 0
Mar 11 11:09:58 fullnode lnd[1252982]:   })
Mar 11 11:09:58 fullnode lnd[1252982]:  },
Mar 11 11:09:58 fullnode lnd[1252982]:  TxOut: ([]*wire.TxOut) (len=1 cap=15) {
Mar 11 11:09:58 fullnode lnd[1252982]:   (*wire.TxOut)(0x4038a97620)({
Mar 11 11:09:58 fullnode lnd[1252982]:    Value: (int64) 519123,
Mar 11 11:09:58 fullnode lnd[1252982]:    PkScript: ([]uint8) (len=34 cap=500) {
Mar 11 11:09:58 fullnode lnd[1252982]:     00000000  51 20 90 2d 57 a5 43 f7  cd 75 f1 55 58 03 89 fd  |Q .-W.C..u.UX...|
Mar 11 11:09:58 fullnode lnd[1252982]:     00000010  1c 7e 82 b3 4d f7 d7 96  23 73 fc a2 6c eb e5 7f  |.~..M...#s..l...|
Mar 11 11:09:58 fullnode lnd[1252982]:     00000020  58 b0                                             |X.|
Mar 11 11:09:58 fullnode lnd[1252982]:    }
Mar 11 11:09:58 fullnode lnd[1252982]:   })
Mar 11 11:09:58 fullnode lnd[1252982]:  },
Mar 11 11:09:58 fullnode lnd[1252982]:  LockTime: (uint32) 780267
Mar 11 11:09:58 fullnode lnd[1252982]: })
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.640 [INF] NTFN: Canceling spend notification: spend_id=89, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000

Your environment

• version of lnd 0.15.5
• which operating system (uname -a on *Nix) Raspbian testing amd64
• version of btcd, bitcoind, or other backend bitcoind v24.0.0
• any other relevant environment details

[guggero]

Could you take a look at the bitcoind logs to see why the transaction is rejected?

[rkfg]

No error messages there. Should I enable some verbose logging for that? If yes, which subsystems exactly?

[rkfg]

I enabled mempool, mempoolrej and validation, the tx doesn't appear in the log at all. It looks like it's removed on the lnd side, no?

[guggero]

Hmm, weird. Can you try the following please:

lncli newaddress p2tr
# gives you a new addr
lncli wallet psbt fund --inputs='["0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0"]' --outputs='{"<addr_from_prev_command>":519123}' --sat_per_vbyte 5

And then send me the output of that in Slack?

Also, you can try increasing the lnd log level to LNWL=debug if the TX doesn't even get to bitcoind.

[rkfg]

I don't have Slack, sorry. The command result is this:

[lncli] rpc error: code = Unknown desc = input 0 not found in list of non-locked UTXO

I tried LNWL=debug before and there was nothing useful about the reasons of that tx being invalid.

[rkfg]

All there is with debug on:

Mar 13 12:51:50 fullnode lnd[1252982]: 2023-03-13 12:51:50.629 [DBG] LNWL: Returning 3427 sat/kw for conf target of 3
Mar 13 12:51:50 fullnode lnd[1252982]: 2023-03-13 12:51:50.633 [DBG] LNWL: Returning 3427 sat/kw for conf target of 3
Mar 13 12:51:50 fullnode lnd[1252982]: 2023-03-13 12:51:50.634 [INF] SWPR: Candidate sweep set of size=1 (+0 wallet inputs), has yield=0.00518602 BTC, weight=397
Mar 13 12:51:50 fullnode lnd[1252982]: 2023-03-13 12:51:50.634 [INF] SWPR: Sweep candidates at height=780604 with fee_rate=3427 sat/kw, yield 1 distinct txns
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.638 [DBG] LNWL: Returning 3427 sat/kw for conf target of 3
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.639 [INF] SWPR: Candidate sweep set of size=1 (+0 wallet inputs), has yield=0.00518602 BTC, weight=397
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.643 [INF] SWPR: Creating sweep transaction f03b22d3395cbb6f65cb98bf5601d25ffaa9c0fc2507241699f16f6446a439fe for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 3427 sat/kw, tx_weight=445, tx_fee=0.00001525 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.649 [INF] LNWL: Inserting unconfirmed transaction f03b22d3395cbb6f65cb98bf5601d25ffaa9c0fc2507241699f16f6446a439fe
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.650 [DBG] LNWL: Marked address bc1pjqk40f2r7lxhtu24tqpcnlgu06ptxn0h67tzxulu5fkwhetltzcqw67zun used
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.698 [INF] LNWL: Removed invalid transaction: (*wire.MsgTx)(0x4067f40740)({

[guggero]

Ah, you might need to run lncli wallet releaseoutput 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 first. And if you get an error about "insufficient funds", just decrease the satoshi value in the --outputs flag by a hundred sats or so.

[rkfg]

Did releaseoutput, still getting the same error about input 0 not found in list of non-locked UTXO.

[guggero]

Hmm, weird. So the wallet probably sees it as already spent. So then 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 also doesn't appear in lncli listunspent? You might need to restart lnd and then don't issue any bump commands but instead try the PSBT one again.

[rkfg]

No, it does appear in listunspent:

> lncli listunspent
{
        "utxos": [
                {
                        "address_type": 4,
                        "address": "bc1pxl0eyghuec44w8rkkvaneefzevzwpnm2gdkx5nnlzf8xjez33gps54newe",
                        "amount_sat": 519962, 
                        "pk_script": "512037df9222fcce2b571c76b33b3ce522cb04e0cf6a436c6a4e7f124e6964518a03",
                        "outpoint": "0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0",
                        "confirmations": 0
                },

[guggero]

Does it currently appear in lncli wallet listleases? If not, can you try the PSBT command again please?

[rkfg]

I restarted lnd and the wallet psbt fund command fails just as before. That UTXO doesn't appear in listleases.

[guggero]

Did releaseoutput, still getting the same error about input 0 not found in list of non-locked UTXO.

Ah, right, because it's still unconfirmed and we never added the --min_confs and --spend_unconfirmed flags to the lncli wallet psbt fund command. Dang, let me think of another way to debug this.

[guggero]

You could try lncli sendcoins --sweepall --min_confs 0 --addr <your_addr> as that would probably log the error more verbosely (if there is one). But that will consolidate all your UTXOs, which you might not want to do.

[rkfg]

I'd prefer not to if possible. Also, that UTXO doesn't show in lncli listunspent, including with --unconfirmed_only which shows no UTXO at all. So I'm not sure it'd even be considered for consolidation (but I might be wrong).

[guggero]

Didn't it show in lncli listunspent just a few moments ago? Could be that the sweeper is trying to sweep something and is using up that UTXO, that's why you can't use it for bumping the channel. How many UTXOs do you have in total on that node?

[guggero]

Can you grep your whole log for 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38 please?

[rkfg]

Yeah, it was there before I restarted lnd, now it's gone. I don't have anything else to sweep (checked lncli wallet pendingsweeps, it's empty), all the FCs were swept a while ago.

> lncli listunspent | jq '.utxos|length'
11

The log grepped by txid:

Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.031 [INF] FNDG: Generated ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) for pending_id(71d45d09aa308a34de0e5364b4246f8ea75a239c6fa061a319392c270f387e6a)
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.056 [INF] FNDG: Generated ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) for pending_id(404e31a6310267e3d14e7253f057664692576001c5025a216a25bfcc1294d270)
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.815 [INF] CNCT: Creating new ChannelArbitrator for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.821 [INF] CNCT: ChannelArbitrator(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1): starting state=StateDefault, trigger=chainTrigger, triggerHeight=779356
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.822 [INF] NTFN: New spend subscription: spend_id=86, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, script=0 eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec, height_hint=779356
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.823 [INF] NTFN: Dispatching historical spend rescan for outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, script=0 eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec, start=779356, end=779356
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.975 [INF] FNDG: Finalizing pending_id(404e31a6310267e3d14e7253f057664692576001c5025a216a25bfcc1294d270) over ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1), waiting for channel open on-chain
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.976 [INF] CNCT: Close observer for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) active
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.978 [INF] NTFN: New confirmation subscription: conf_id=16, txid=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38, num_confs=2 height_hint=779356
Mar 05 03:12:57 fullnode lnd[1252982]: 2023-03-05 03:12:57.978 [INF] FNDG: Waiting for funding tx (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38) to reach 2 confirmations
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.009 [INF] CNCT: Creating new ChannelArbitrator for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.015 [INF] NTFN: Historical spend dispatch finished for request outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, script=0 eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec (start=779356 end=779356) with details: <nil>
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.027 [INF] CNCT: ChannelArbitrator(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2): starting state=StateDefault, trigger=chainTrigger, triggerHeight=779356
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.041 [INF] NTFN: New spend subscription: spend_id=87, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, script=0 5320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c, height_hint=779356
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.041 [INF] NTFN: Dispatching historical spend rescan for outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, script=0 5320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c, start=779356, end=779356
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.047 [INF] FNDG: Finalizing pending_id(71d45d09aa308a34de0e5364b4246f8ea75a239c6fa061a319392c270f387e6a) over ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2), waiting for channel open on-chain
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.048 [INF] NTFN: New confirmation subscription: conf_id=17, txid=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38, num_confs=3 height_hint=779356
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.048 [INF] CNCT: Close observer for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) active
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.049 [INF] FNDG: Waiting for funding tx (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38) to reach 3 confirmations
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.067 [INF] NTFN: Historical spend dispatch finished for request outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, script=0 5320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c (start=779356 end=779356) with details: <nil>
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.089 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) w/ newer version
Mar 05 03:12:58 fullnode lnd[1252982]: 2023-03-05 03:12:58.829 [INF] LNWL: Inserting unconfirmed transaction 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38
Mar 05 03:14:46 fullnode lnd[1252982]: 2023-03-05 03:14:46.017 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 05 03:14:46 fullnode lnd[1252982]: 2023-03-05 03:14:46.020 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 05 03:54:06 fullnode lnd[1252982]: 2023-03-05 03:54:06.518 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 05 03:54:06 fullnode lnd[1252982]: 2023-03-05 03:54:06.519 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values
Mar 05 22:34:23 fullnode lnd[1252982]: 2023-03-05 22:34:23.915 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 05 22:34:23 fullnode lnd[1252982]: 2023-03-05 22:34:23.916 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values
Mar 05 22:34:27 fullnode lnd[1252982]: 2023-03-05 22:34:27.240 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 05 22:34:27 fullnode lnd[1252982]: 2023-03-05 22:34:27.240 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values
Mar 08 04:02:49 fullnode lnd[1252982]: 2023-03-08 04:02:49.839 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) w/ newer version
Mar 08 04:02:49 fullnode lnd[1252982]: 2023-03-08 04:02:49.840 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) w/ newer version
Mar 08 04:02:49 fullnode lnd[1252982]: 2023-03-08 04:02:49.958 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) w/ newer version
Mar 08 04:02:49 fullnode lnd[1252982]: 2023-03-08 04:02:49.959 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) w/ newer version
Mar 08 11:33:29 fullnode lnd[1252982]: 2023-03-08 11:33:29.709 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 08 11:33:29 fullnode lnd[1252982]: 2023-03-08 11:33:29.711 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 08 15:02:26 fullnode lnd[1252982]: 2023-03-08 15:02:26.555 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 08 15:02:26 fullnode lnd[1252982]: 2023-03-08 15:02:26.556 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 08 16:54:58 fullnode lnd[1252982]: 2023-03-08 16:54:58.682 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) w/ newer version
Mar 08 16:54:58 fullnode lnd[1252982]: 2023-03-08 16:54:58.682 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) w/ newer version
Mar 08 16:54:58 fullnode lnd[1252982]: 2023-03-08 16:54:58.728 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) w/ newer version
Mar 08 16:54:58 fullnode lnd[1252982]: 2023-03-08 16:54:58.728 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) w/ newer version
Mar 09 14:45:43 fullnode lnd[1252982]: 2023-03-09 14:45:43.428 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 09 14:45:43 fullnode lnd[1252982]: 2023-03-09 14:45:43.430 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values
Mar 09 15:13:37 fullnode lnd[1252982]: 2023-03-09 15:13:37.880 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 09 15:13:37 fullnode lnd[1252982]: 2023-03-09 15:13:37.884 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 10 13:20:05 fullnode lnd[1252982]: 2023-03-10 13:20:05.410 [INF] SWPR: Sweep request received: out_point=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, witness_type=TaprootPubKeySpend, relative_time_lock=0, absolute_time_lock=0, amount=0.00519962 BTC, params=(fee=1000 sat/kw, force=false, exclusive_group=<nil>)
Mar 10 13:20:05 fullnode lnd[1252982]: 2023-03-10 13:20:05.411 [INF] NTFN: New spend subscription: spend_id=88, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000, height_hint=780131
Mar 10 13:20:05 fullnode lnd[1252982]: 2023-03-10 13:20:05.411 [INF] NTFN: Dispatching historical spend rescan for outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000, start=780131, end=780131
Mar 10 13:20:05 fullnode lnd[1252982]: 2023-03-10 13:20:05.505 [INF] NTFN: Historical spend dispatch finished for request outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000 (start=780131 end=780131) with details: <nil>
Mar 10 13:20:35 fullnode lnd[1252982]: 2023-03-10 13:20:35.522 [INF] SWPR: Creating sweep transaction 1c7d5ce63b16514020d347f20b5280c57d52551480d25058b63daae07a05a88a for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1000 sat/kw, tx_weight=445, tx_fee=0.00000445 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:20:35 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:21:44 fullnode lnd[1252982]: 2023-03-10 13:21:44.304 [WRN] WLKT: Unhandled witness type TaprootPubKeySpend for input 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0
Mar 10 13:22:45 fullnode lnd[1252982]: 2023-03-10 13:22:45.184 [INF] SWPR: Creating sweep transaction 1c7d5ce63b16514020d347f20b5280c57d52551480d25058b63daae07a05a88a for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1000 sat/kw, tx_weight=445, tx_fee=0.00000445 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:22:45 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:23:22 fullnode lnd[1252982]: 2023-03-10 13:23:22.190 [INF] SWPR: Creating sweep transaction 1c7d5ce63b16514020d347f20b5280c57d52551480d25058b63daae07a05a88a for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1000 sat/kw, tx_weight=445, tx_fee=0.00000445 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:23:22 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:24:23 fullnode lnd[1252982]: 2023-03-10 13:24:23.166 [INF] SWPR: Creating sweep transaction 1c7d5ce63b16514020d347f20b5280c57d52551480d25058b63daae07a05a88a for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1000 sat/kw, tx_weight=445, tx_fee=0.00000445 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:24:23 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:26:08 fullnode lnd[1252982]: 2023-03-10 13:26:08.898 [INF] SWPR: Creating sweep transaction af542547035bee0bb91912237933332d922ec6a893fa9f58a2e977c721dc0591 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1250 sat/kw, tx_weight=445, tx_fee=0.00000556 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:26:08 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:27:50 fullnode lnd[1252982]: 2023-03-10 13:27:50.586 [INF] SWPR: Creating sweep transaction f9fdc5207160bf6ae15597f7d23b5aba3b8636c857669c568c42609a52e2d1b4 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 2500 sat/kw, tx_weight=445, tx_fee=0.00001112 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:27:50 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:28:58 fullnode lnd[1252982]: 2023-03-10 13:28:58.111 [INF] SWPR: Creating sweep transaction 81476c3b70d9e981f9e2768d1589951ea5b2981292e7c52ecfa10fe02020d972 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 12147 sat/kw, tx_weight=445, tx_fee=0.00005405 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:28:58 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:34:16 fullnode lnd[1252982]: 2023-03-10 13:34:16.185 [INF] SWPR: Creating sweep transaction 81476c3b70d9e981f9e2768d1589951ea5b2981292e7c52ecfa10fe02020d972 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 12147 sat/kw, tx_weight=445, tx_fee=0.00005405 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:34:16 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:36:32 fullnode lnd[1252982]: 2023-03-10 13:36:32.918 [INF] SWPR: Creating sweep transaction 15619c35c28909718d8127be2879116a5bb0b0abc0ecf653f536ae5d4f8f1c69 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1750 sat/kw, tx_weight=445, tx_fee=0.00000778 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:36:32 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:41:27 fullnode lnd[1252982]: 2023-03-10 13:41:27.936 [INF] SWPR: Creating sweep transaction 15619c35c28909718d8127be2879116a5bb0b0abc0ecf653f536ae5d4f8f1c69 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1750 sat/kw, tx_weight=445, tx_fee=0.00000778 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:41:28 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:41:28 fullnode lnd[1252982]: 2023-03-10 13:41:28.001 [INF] NTFN: Canceling spend notification: spend_id=88, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000
Mar 10 13:44:13 fullnode lnd[1252982]: 2023-03-10 13:44:13.472 [INF] SWPR: Sweep request received: out_point=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, witness_type=TaprootPubKeySpend, relative_time_lock=0, absolute_time_lock=0, amount=0.00519962 BTC, params=(fee=5000 sat/kw, force=false, exclusive_group=<nil>)
Mar 10 13:44:13 fullnode lnd[1252982]: 2023-03-10 13:44:13.485 [INF] NTFN: New spend subscription: spend_id=89, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000, height_hint=780131
Mar 10 13:44:43 fullnode lnd[1252982]: 2023-03-10 13:44:43.497 [INF] SWPR: Creating sweep transaction c877c9c8062adcc000f958611b07882b656a17f07bc10daf4002b1374869aa05 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 5000 sat/kw, tx_weight=445, tx_fee=0.00002225 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:44:43 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:45:22 fullnode lnd[1252982]: 2023-03-10 13:45:22.643 [INF] SWPR: Creating sweep transaction c877c9c8062adcc000f958611b07882b656a17f07bc10daf4002b1374869aa05 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 5000 sat/kw, tx_weight=445, tx_fee=0.00002225 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:45:22 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:46:38 fullnode lnd[1252982]: 2023-03-10 13:46:38.420 [INF] SWPR: Creating sweep transaction c877c9c8062adcc000f958611b07882b656a17f07bc10daf4002b1374869aa05 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 5000 sat/kw, tx_weight=445, tx_fee=0.00002225 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:46:38 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 13:47:40 fullnode lnd[1252982]: 2023-03-10 13:47:40.671 [INF] SWPR: Creating sweep transaction 81476c3b70d9e981f9e2768d1589951ea5b2981292e7c52ecfa10fe02020d972 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 12147 sat/kw, tx_weight=445, tx_fee=0.00005405 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 13:47:40 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 15:06:08 fullnode lnd[1252982]: 2023-03-10 15:06:08.989 [INF] SWPR: Creating sweep transaction cb0fc3bc41dafe02700186e5a2abaf06b280ab7991a3b42fd9fbac38981bacf1 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 12182 sat/kw, tx_weight=445, tx_fee=0.0000542 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 15:06:09 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 17:47:01 fullnode lnd[1252982]: 2023-03-10 17:47:01.507 [INF] SWPR: Creating sweep transaction 5ab2926efde8976d1848b02ad2643b033ce646e72ad64b59c451f47d5cd42676 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 12208 sat/kw, tx_weight=445, tx_fee=0.00005432 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 17:47:01 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 18:17:49 fullnode lnd[1252982]: 2023-03-10 18:17:49.632 [INF] SWPR: Creating sweep transaction 19eb4bd7acfb38fce2fda5505c691fc79f7a96e09ebecf8715f98a9ce73c33b8 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 9022 sat/kw, tx_weight=445, tx_fee=0.00004014 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 18:17:49 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 10 23:54:42 fullnode lnd[1252982]: 2023-03-10 23:54:42.902 [INF] SWPR: Creating sweep transaction f5213bc601da18ab27f21e71e5188aad6e53eb79b524c1a82298ff1c3751b0b3 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 12227 sat/kw, tx_weight=445, tx_fee=0.00005441 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 10 23:54:43 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 11 10:51:08 fullnode lnd[1252982]: 2023-03-11 10:51:08.386 [INF] SWPR: Creating sweep transaction 882fd81ee6a91fa069a7a8e1f6e77727d1360f2a6f98211aedb6c91b7729b6af for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 2273 sat/kw, tx_weight=445, tx_fee=0.00001011 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 11 10:51:08 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.539 [INF] SWPR: Creating sweep transaction 199a1f155bbc523e8a9328177211f7deaf1145a756dfbebf38d4c4ec7e7b48d1 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 1886 sat/kw, tx_weight=445, tx_fee=0.00000839 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 11 11:09:58 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 11 11:09:58 fullnode lnd[1252982]: 2023-03-11 11:09:58.640 [INF] NTFN: Canceling spend notification: spend_id=89, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000
Mar 11 19:27:27 fullnode lnd[1252982]: 2023-03-11 19:27:27.916 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 11 19:27:27 fullnode lnd[1252982]: 2023-03-11 19:27:27.917 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 12 03:40:44 fullnode lnd[1252982]: 2023-03-12 03:40:44.831 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 12 03:40:44 fullnode lnd[1252982]: 2023-03-12 03:40:44.832 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 13 12:39:43 fullnode lnd[1252982]: 2023-03-13 12:39:43.498 [INF] SWPR: Sweep request received: out_point=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, witness_type=TaprootPubKeySpend, relative_time_lock=0, absolute_time_lock=0, amount=0.00519962 BTC, params=(fee=3 blocks, force=false, exclusive_group=<nil>)
Mar 13 12:39:43 fullnode lnd[1252982]: 2023-03-13 12:39:43.502 [INF] NTFN: New spend subscription: spend_id=90, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0, script=1 0000000000000000000000000000000000000000000000000000000000000000, height_hint=780601
Mar 13 12:40:13 fullnode lnd[1252982]: 2023-03-13 12:40:13.514 [INF] SWPR: Creating sweep transaction 84d9bed510f3df8ca873230738d392f317cb7987a6f425b40c637651a46dcff8 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 3427 sat/kw, tx_weight=445, tx_fee=0.00001525 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 13 12:40:13 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 13 12:41:53 fullnode lnd[1252982]: 2023-03-13 12:41:53.762 [INF] SWPR: Creating sweep transaction 8c1c275459efdb9d313471b0485323746942b95f16e561511c682afb10a3beaa for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 3427 sat/kw, tx_weight=445, tx_fee=0.00001525 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 13 12:41:53 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 13 12:45:52 fullnode lnd[1252982]: 2023-03-13 12:45:52.336 [INF] SWPR: Creating sweep transaction 7149a946c1936d86cbf9a410a39d478e7211c2595114e1ef189fce1c1bf105a1 for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 3427 sat/kw, tx_weight=445, tx_fee=0.00001525 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 13 12:45:52 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 13 12:46:51 fullnode lnd[1252982]: 2023-03-13 12:46:51.317 [INF] SWPR: Creating sweep transaction f03b22d3395cbb6f65cb98bf5601d25ffaa9c0fc2507241699f16f6446a439fe for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 3427 sat/kw, tx_weight=445, tx_fee=0.00001525 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 13 12:46:51 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 13 12:52:20 fullnode lnd[1252982]: 2023-03-13 12:52:20.643 [INF] SWPR: Creating sweep transaction f03b22d3395cbb6f65cb98bf5601d25ffaa9c0fc2507241699f16f6446a439fe for 1 inputs (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0 (TaprootPubKeySpend)) using 3427 sat/kw, tx_weight=445, tx_fee=0.00001525 BTC, parents_count=0, parents_fee=0 BTC, parents_weight=0
Mar 13 12:52:20 fullnode lnd[1252982]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 13 13:19:46 fullnode lnd[1252982]: 2023-03-13 13:19:46.233 [WRN] FNDG: fundingManager shutting down, stopping funding flow for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 13 13:19:46 fullnode lnd[1252982]: 2023-03-13 13:19:46.233 [ERR] FNDG: Unable to advance pending state of ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2): error waiting for funding confirmation for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2): funding manager shutting down
Mar 13 13:19:46 fullnode lnd[1252982]: 2023-03-13 13:19:46.233 [ERR] FNDG: Unable to advance pending state of ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1): error waiting for funding confirmation for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1): funding manager shutting down
Mar 13 13:19:46 fullnode lnd[1252982]: 2023-03-13 13:19:46.233 [WRN] FNDG: fundingManager shutting down, stopping funding flow for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 13 13:26:25 fullnode lnd[3114824]:    PreviousOutPoint: (wire.OutPoint) 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0,
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.331 [INF] NTFN: New confirmation subscription: conf_id=1, txid=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38, num_confs=2 height_hint=780607
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.388 [INF] NTFN: New confirmation subscription: conf_id=2, txid=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38, num_confs=3 height_hint=780607
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.516 [INF] FNDG: Waiting for funding tx (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38) to reach 2 confirmations
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.517 [INF] FNDG: Waiting for funding tx (0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38) to reach 3 confirmations
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.806 [INF] NTFN: New spend subscription: spend_id=39, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, script=0 eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec, height_hint=780607
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.806 [INF] NTFN: Dispatching historical spend rescan for outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, script=0 eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec, start=780607, end=780608
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.809 [INF] NTFN: New spend subscription: spend_id=56, outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, script=0 5320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c, height_hint=780607
Mar 13 13:26:26 fullnode lnd[3114824]: 2023-03-13 13:26:26.809 [INF] NTFN: Dispatching historical spend rescan for outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, script=0 5320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c, start=780607, end=780608
Mar 13 13:26:27 fullnode lnd[3114824]: 2023-03-13 13:26:27.594 [INF] CNCT: Close observer for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) active
Mar 13 13:26:27 fullnode lnd[3114824]: 2023-03-13 13:26:27.600 [INF] CNCT: Close observer for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) active
Mar 13 13:26:27 fullnode lnd[3114824]: 2023-03-13 13:26:27.820 [INF] CNCT: ChannelArbitrator(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1): starting state=StateDefault, trigger=chainTrigger, triggerHeight=780608
Mar 13 13:26:28 fullnode lnd[3114824]: 2023-03-13 13:26:28.209 [INF] CNCT: ChannelArbitrator(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2): starting state=StateDefault, trigger=chainTrigger, triggerHeight=780608
Mar 13 13:26:28 fullnode lnd[3114824]: 2023-03-13 13:26:28.225 [INF] NTFN: Historical spend dispatch finished for request outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, script=0 5320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c (start=780607 end=780608) with details: <nil>
Mar 13 13:26:28 fullnode lnd[3114824]: 2023-03-13 13:26:28.225 [INF] NTFN: Historical spend dispatch finished for request outpoint=0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, script=0 eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec (start=780607 end=780608) with details: <nil>
Mar 13 13:27:31 fullnode lnd[3114824]: 2023-03-13 13:27:31.834 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1) w/ newer version
Mar 13 13:27:31 fullnode lnd[3114824]: 2023-03-13 13:27:31.836 [WRN] CHBU: Replacing disk backup for ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2) w/ newer version
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.033 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.034 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.154 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.159 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.594 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.608 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.685 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 13 13:27:32 fullnode lnd[3114824]: 2023-03-13 13:27:32.686 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 13 13:27:33 fullnode lnd[3114824]: 2023-03-13 13:27:33.289 [INF] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1)
Mar 13 13:27:33 fullnode lnd[3114824]: 2023-03-13 13:27:33.289 [WRN] PEER: Peer(033fc44ec70c1c5a269a7d7c1cfdaf6f9ec7a92bbe7a8e1473e3663ce7ce8d399b): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:1, using default values
Mar 13 13:27:46 fullnode lnd[3114824]: 2023-03-13 13:27:46.864 [INF] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): loading ChannelPoint(0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2)
Mar 13 13:27:46 fullnode lnd[3114824]: 2023-03-13 13:27:46.865 [WRN] PEER: Peer(02f7467f4de732f3b3cffc8d5e007aecdf6e58878edb6e46a8e80164421c1b90aa): Unable to find our forwarding policy for channel 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:2, using default values

[rkfg]

Now I tried to bump that UTXO and it results in an error:

[lncli] rpc error: code = Unknown desc = the passed output does not belong to the wallet

Is it because I released the lease?

[guggero]

I think it might be because the UTXO is locked by the sweeper.

Would you be willing to run a patched lncli so we can get the PSBT funded (which would greatly help to debug this)?

You'd basically compile and run lncli from this PR: https://github.com/lightningnetwork/lnd/pull/7510

Steps:

• cd /tmp && git clone git@github.com:lightningnetwork/lnd.git && cd lnd
• git fetch origin pull/7510/head:custom-lncli && git checkout custom-lncli
• make build tags="walletrpc"
• /tmp/lnd/lncli-debug wallet releaseoutput 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0
• /tmp/lnd/lncli-debug wallet psbt fund --inputs='["0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0"]' --outputs='{"<addr_from_your_wallet>":519000}' --min_confs=0 --sat_per_vbyte 5

That will not spend anything, just give a PSBT that should contain some info to help debug the problem.

NOTE: Just use the custom lncli for those commands, don't update your running lnd node to that version (as that will upgrade to latest master).

[rkfg]

I built lncli, however it doesn't work:

> ./lncli-debug wallet releaseoutput 0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0
[lncli] rpc error: code = Unknown desc = unknown output
> ./lncli-debug wallet psbt fund --inputs='["0891630eac3c56a538b28947ebbf356530d550e68081ff2cdf4d10f2a210cb38:0"]' --outputs='{"my_addr_here":519000}' --min_confs=0 --sat_per_vbyte 5
[lncli] rpc error: code = Unknown desc = input 0 not found in list of non-locked UTXO

The two channels from that UTXO are still pending though.

[guggero]

It sounds like you're fighting a timing battle against the sweeper... Can you try again directly after a restart of lnd?

[yyforyongyu]

There's the --sweeper.batchwindowduration=30s might be helpful here, which configs the sweep interval.

[rkfg]

The problem now is that the command doesn't even succeed now while it did before. And I'd just restarted lnd before trying these commands.

[guggero]

Hmm, okay, let's try something else. Can you send me the output of lncli wallet accounts list --address_type p2tr, preferably in a more private chat (I can offer Telegram, Twitter, Nostr, all with the same username) as the output is privacy sensitive.

[rkfg]

Sent you a message on Nostr

[Roasbeef]

@rkfg are you running a node w/ default settings? If so, then your node might have dropped the tx out of the mempool. You can increase the mempool size, then confirm that lnd does a rebroadcast on start up. After that, you should be able to do the fee bump.

[Roasbeef]

The TX is likely being removed (as in the first log), as the input is an unknown, since the transaction that created the input (funding tx) isn't in the mempool of your node.

[Roasbeef]

@rkfg do you have logs beyond that last line? It should show the actual broadcast error.

[rkfg]

@rkfg are you running a node w/ default settings? If so, then your node might have dropped the tx out of the mempool. You can increase the mempool size, then confirm that lnd does a rebroadcast on start up. After that, you should be able to do the fee bump.

Hmm, yes, and this makes a lot of sense! Unfortunately, I can't test right now as I'm rescanning the chain after resetting my wallet and it will take about 5 more hours...

@rkfg do you have logs beyond that last line? It should show the actual broadcast error.

No other errors, after the message about invalid tx it's just the usual gossip log.

[rkfg]

After rescanning the blocks for wallet transactions, there are few issues:

• the pending channels are still pending but I see the funding UTXO inputs as unspent (they show in lncli listunspent), my on chain balance also reflects that (
• bumping the fee still results in [lncli] rpc error: code = Unknown desc = the passed output does not belong to the wallet
• creating PSBT results in [lncli] rpc error: code = Unknown desc = input 0 not found in list of non-locked UTXO

What do I do next?

[guggero]

I'd suggest you run your bitcoind node with a slightly bigger mempool (-maxmempool=512) and broadcast the channel funding TX again:

lncli wallet publishtx 020000000001031f6a7d82c9fd0b1e32e912932a7a3497d04165cf3b6e04f95fe455a7b658381d0000000000ffffffff96b5e28e36b89906d34cfc110cd033c7f799a11ccd0702275edc67990e577d9b0100000000ffffffffc1d1f2eeb9ce1792a38dc49cbde043741ea3d548602fc2c3f36038246317bdcf0000000000ffffffff031aef07000000000022512037df9222fcce2b571c76b33b3ce522cb04e0cf6a436c6a4e7f124e6964518a03c0c62d0000000000220020eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec404b4c00000000002200205320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c0140c39e7e3f2785ec8692912798e1b6af27447f9c23d06c5c59b751f0bb9307353ffab249ea1ac12c7b393781de16ab96f4835d460ad497f9862c8560f363d42e690140aaeb5b3d8b9a271471338b076d326f5ccf93818cea7d5945b1f03ef10cb659a9c375425c42707ee76a161144eb87ad4f50640fbc10bd3c84ddd2fe4a75aff1160140c4e049d7446bd22343ca122d1ef0c1b6dfe72f3824af7d984db408f2b93c7e44092bd1a614fe53d9f751ffd43caa3e0357ccd78aaea602e16b41ab2f6c94b67500000000

Then attempt the bumpfee command again.

[rkfg]

Oooooffff, it finally worked: https://mempool.space/tx/ebfc6b2247142c8490a20c4c9ff95fdccd4b9018f136496b32363935989c793a

Thanks, this rebroadcast and bump helped. I increased the mempool but I think it's not really needed as I disabled persisting it on disk long ago, it takes enormous load on RPi when I restart bitcoind so just dropping it is much better. After restart it should have plenty of space before repopulating with new txs but anyway, I guess it wouldn't eat all the remaining RAM with 512 Mb limit.

Okay, now we have a bunch of issues to fix when working in a congested environment. Unfortunately, it's gonna be like that in the foreseeable future. One of the big problems is that I didn't have this tx among my wallet txs until I rebroadcasted it. Kinda makes sense after resetting the wallet txs because channel open tx can't be derived directly from the seed if I understand it right, it includes two node pubkeys, and in my case there are 2 channels and one change output. So if mempool.space didn't save this tx I'm not sure how I'd have recovered it.

The enhancements I'd suggest:

• provide a better error message if we're unable to send a bump tx, tell the user to check if mempool is full because currently it totally looks like a bug, a valid tx is considered invalid for no apparent reason. Thanks @Roasbeef for finding the real reason for that!
• broadcast the channel open tx before bumping (if it's not currently done), idk if it's easy to detect purging of such tx

Guess that's it. Feel free to close this issue as it's technically solved, or maybe it's good to keep it around until a better mempool congestion mitigation is implemented.

[guggero]

Oooooffff, it finally worked

Okay, nice!

Yeah, kudos to Roasbeef for figuring that out, I guess I got side tracked fearing it might be something worse. I think we can do the following on the lnd side:

• Improve the logging (so we can actually see why a transaction is deemed invalid and is removed) --> I'm going to create a PR for that.
• Make sure we re-publish all pending transactions regularly --> This is actually addressed by https://github.com/lightningnetwork/lnd/pull/7448 which is in the current RC of v0.16.0-beta.
• Look at the mempoolminfee field of the getmempoolinfo RPC that was added with bitcoind v0.21.0 and reject creating any transactions below that fee. That won't solve the issue for Neutrino though, as we don't have access to that fee rate info. --> Going to create a new issue for this.

[guggero]

Documented a possible fix for this in https://github.com/lightningnetwork/lnd/issues/7512, going to close the issue (logging PR will be coming soon as well).

[ayrthpr]

Hi everyone,

First of all, thank you all for the great effort in make LND running in our own home nodes. The help you provide is highly appreciated.

I've been facing a similar problem to this since yesterday, in particular with transaction: e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309. I erroneously tip 1 sat/vB instead of 10, and even if I can see the transaction in the meempool, my node is not able to bump the fee.

What I am doing is the following:

1. I increased the mempool (-maxmempool=512) and broadcast the channel funding TX again:

lncli wallet publishtx 0200000000010102e5d8c103d3f87c48567d0d20ad0cac7416b7046944530448a94eb784bca2320000000000000000000240420f0000000000220020ab5285033019fa81163922c9f7741c8b743507678648fb457772415a18ebaebe1ac62d00000000002251207c2c105f7b88b72377cab2fc6a21a1a4bb3a007e48e77db106a0bd867c22db2302483045022100c24aa8ff883fc6d943d5756ba6e0076a300b79d0ab4d8836fe329a36aa9a60be02205d8bfc69eb36e8adce582613b1a2b1f075a994d783b5580a3be08c894bb81a81012103ded649cbcd2b884983d572405e4f051274b896e6145280cc9c386937bd503ba200000000

Result: { "txid": "e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309" }

2. Then I try to bump the fee and this is what happens:

lncli wallet bumpfee --sat_per_byte 20 e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309:0 Result: [lncli] rpc error: code = Unknown desc = the passed output does not belong to the wallet

3. I've also tried with command lncli wallet releaseoutput e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309:0

And the result is: [lncli] rpc error: code = Unknown desc = unknown output

Do you have any idea of to proceed to unlock this transaction?

[guggero]

You need to bump the change output, so try lncli wallet bumpfee --sat_per_byte 20 e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309:1 instead.

[ayrthpr]

I've done what you said, no error now but no change in transactions in other nodes (i.e. mempool.space).

I've checked with command lncli wallet pendingsweeps that transaction increase has been registered by own node:

    "pending_sweeps": [
            {
                    "outpoint": "e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309:1",
                    "witness_type": "TAPROOT_PUB_KEY_SPEND",
                    "amount_sat": 2999834,
                    "sat_per_vbyte": 20,
                    "broadcast_attempts": 8,
                    "next_broadcast_height": 796071,
                    "requested_sat_per_vbyte": 20,
                    "requested_conf_target": 0,
                    "force": false
            }
    ]

That means that the command worked, however I suspect that transaction has been forgotten from my own node (because it does not appear in my bitcoin explorer) and cannot be released to the network.

When I use the command: lncli wallet publishtx, now it says: [lncli] rpc error: code = Unknown desc = unmatched backend error: -26: mempool min fee not met, 166 < 1335.

EDIT: Find below my logs

Jun 26 19:42:01 AYRServer lnd[1070]: 2023-06-26 19:42:01.350 [INF] CRTR: Processed channels=0 updates=11 nodes=3 in last 59.999965452s
Jun 26 19:42:47 AYRServer lnd[1070]: 2023-06-26 19:42:47.993 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
Jun 26 19:42:48 AYRServer lnd[1070]: 2023-06-26 19:42:48.007 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
Jun 26 19:42:50 AYRServer lnd[1070]: 2023-06-26 19:42:50.479 [ERR] BTCN: Unable to rebroadcast transaction e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309: -26: mempool min fee not met, 166 < 1272
Jun 26 19:43:01 AYRServer lnd[1070]: 2023-06-26 19:43:01.349 [INF] CRTR: Processed channels=0 updates=18 nodes=2 in last 59.998417865s
Jun 26 19:43:43 AYRServer lnd[1070]: 2023-06-26 19:43:43.784 [INF] SRVR: New inbound connection from 127.0.0.1:34144
Jun 26 19:43:43 AYRServer lnd[1070]: 2023-06-26 19:43:43.784 [INF] SRVR: Finalizing connection to 021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3@127.0.0.1:34144, inbound=true
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] PEER: Peer(021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3): Loading ChannelPoint(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0), isPending=false
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): starting
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] HSWC: Trimming open circuits for chan_id=794921:1273:0, start_htlc_id=19
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] HSWC: Adding live link chan_id=9dc6c7a39b706f7dbadf8b89b4efe91bdc433fa7913aaeaad551a9e97e65850f, short_chan_id=794921:1273:0
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0)
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] NTFN: New block epoch subscription
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] PEER: Peer(021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3): Negotiated chan series queries
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.087 [INF] DISC: Creating new GossipSyncer for peer=021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.086 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): HTLC manager started, bandwidth=7099565 mSAT
Jun 26 19:43:44 AYRServer lnd[1070]: 2023-06-26 19:43:44.087 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): attempting to re-synchronize
Jun 26 19:43:45 AYRServer lnd[1070]: 2023-06-26 19:43:45.387 [WRN] DISC: ignoring remote ChannelAnnouncement for own channel
Jun 26 19:43:45 AYRServer lnd[1070]: 2023-06-26 19:43:45.534 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): received re-establishment message from remote side
Jun 26 19:43:45 AYRServer lnd[1070]: 2023-06-26 19:43:45.534 [INF] DISC: Received new remote announcement signature for 794921:1273:0
Jun 26 19:43:45 AYRServer lnd[1070]: 2023-06-26 19:43:45.536 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): sending 2 updates to synchronize the state
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.045 [INF] PEER: Peer(021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3): unable to read message from peer: EOF
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.045 [INF] PEER: Peer(021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3): disconnecting 021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3@127.0.0.1:34144, reason: read handler closed
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.045 [WRN] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): received warning message from peer: chan_id=9dc6c7a39b706f7dbadf8b89b4efe91bdc433fa7913aaeaad551a9e97e65850f, err=update_fee 253 outside range 1925-67420 (currently 4432)
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.046 [INF] NTFN: Cancelling epoch notification, epoch_id=325
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.246 [INF] DISC: Removing GossipSyncer for peer=021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.246 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): stopping
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.246 [INF] HSWC: ChannelLink(0f85657ee9a951d5aaae3a91a73f43dc1be9efb4898bdfba7d6f709ba3c7c69d:0): exited
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.247 [INF] HSWC: Removing channel link with ChannelID(9dc6c7a39b706f7dbadf8b89b4efe91bdc433fa7913aaeaad551a9e97e65850f)
Jun 26 19:43:47 AYRServer lnd[1070]: 2023-06-26 19:43:47.993 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
Jun 26 19:43:48 AYRServer lnd[1070]: 2023-06-26 19:43:48.007 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
Jun 26 19:43:50 AYRServer lnd[1070]: 2023-06-26 19:43:50.478 [ERR] BTCN: Unable to rebroadcast transaction e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309: -26: mempool min fee not met, 166 < 1271
Jun 26 19:44:01 AYRServer lnd[1070]: 2023-06-26 19:44:01.350 [INF] CRTR: Processed channels=0 updates=11 nodes=5 in last 59.99991581s
Jun 26 19:44:47 AYRServer lnd[1070]: 2023-06-26 19:44:47.994 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
Jun 26 19:44:48 AYRServer lnd[1070]: 2023-06-26 19:44:48.008 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
Jun 26 19:44:50 AYRServer lnd[1070]: 2023-06-26 19:44:50.480 [ERR] BTCN: Unable to rebroadcast transaction e230f9f104421b9386354c7708ca9e0f9994e10f98f51ce76f1e32a320f71309: -26: mempool min fee not met, 166 < 1269

[guggero]

Yes, so in order to get the original funding TX in the mempool, you need to increase the mempool size of your bitcoind node.

[ayrthpr]

Finally worked... Thanks for your support guggero!

[bitcoin-2504]

Hi, I have similar issue with transaction having been sent on low fee prior to ordinals taken off. Transaction was purged from mempool and is just sitting as a pending channel, with no trace of transaction within lightning node. I have increased my mempool to 1gb to prevent in future.

Any help would be much appreciated.

[guggero]

Did you restart lnd to re-broadcast the transaction?

[bitcoin-2504]

Have reboot pc number of times since increasing the mempool memory and also restarted lnd

[marcelofukuoka]

I'd suggest you run your bitcoind node with a slightly bigger mempool (-maxmempool=512) and broadcast the channel funding TX again:

lncli wallet publishtx 020000000001031f6a7d82c9fd0b1e32e912932a7a3497d04165cf3b6e04f95fe455a7b658381d0000000000ffffffff96b5e28e36b89906d34cfc110cd033c7f799a11ccd0702275edc67990e577d9b0100000000ffffffffc1d1f2eeb9ce1792a38dc49cbde043741ea3d548602fc2c3f36038246317bdcf0000000000ffffffff031aef07000000000022512037df9222fcce2b571c76b33b3ce522cb04e0cf6a436c6a4e7f124e6964518a03c0c62d0000000000220020eba94ed8d1ffb7dcd7293bd5bddce65595e985fb1fd7aa536d4618e8d2b15cec404b4c00000000002200205320596e8e1be9ec246aee3bd5b647ffddff8181628debaa78ac52883bbca60c0140c39e7e3f2785ec8692912798e1b6af27447f9c23d06c5c59b751f0bb9307353ffab249ea1ac12c7b393781de16ab96f4835d460ad497f9862c8560f363d42e690140aaeb5b3d8b9a271471338b076d326f5ccf93818cea7d5945b1f03ef10cb659a9c375425c42707ee76a161144eb87ad4f50640fbc10bd3c84ddd2fe4a75aff1160140c4e049d7446bd22343ca122d1ef0c1b6dfe72f3824af7d984db408f2b93c7e44092bd1a614fe53d9f751ffd43caa3e0357ccd78aaea602e16b41ab2f6c94b67500000000

Then attempt the bumpfee command again.

Hi guggero,

I am having the same problem. I have read this topic and I think the first thing I have to do is to increase the mempool size of my bitcoind node. In order to do that, I have to edit the lnd.conf file, is it? If that´s the way, the edited file should be like this: [Bitcoind] bitcoind.maxmempool=512

Is it rigth? Thank you!

[guggero]

No, you need to edit your bitcoind's config file and add maxmempool=512.

[marcelofukuoka]

bitcoind's config file

Hi guggero, Just to make sure I am doing right, the file to edit is: bitcoin.conf? I use umbrel, the pathway for me is showing: ./app-data/bitcoin/data/bitcoin/bitcoin.conf

Thank you!