pending force close

[jquiros2]

I'm using 0.17.4-beta, in btcpayserver.

I realized a channel had been disconnected for months, even though it had been open for a few years. I tried to do a force close on it about three weeks ago, and waited thinking two weeks was more or less the norm for these to clear.

Then a little past the two weeks I decided to look into it. This is the transaction.

From what I could gather, the fee was way too low, so I tried to bump the close txn fee via:
./bitcoin-lncli.sh wallet bumpfee --conf_target 6 --force 52ee43c1c7976556e5803a7018fd4a8e9e1b53383436c72fb5493f9b6d0b5690:1
but i get
[lncli] rpc error: code = Unknown desc = the passed output does not belong to the wallet

I also tried bumping up the old channel's close fee:
./bitcoin-lncli.sh wallet bumpclosefee --sat_per_vbyte 80 d662b0faf02393110ebbf897d40b5816ddc5c38156c891c04c2247c7a2bc316c:1
And this gives me no error, but I do not see any change in the close transaction details.

Several days ago I raised mempool size to 800 via
maxmempool=800 and restarted.

I am also wondering if maybe something is awry because I am not running a full node. I'm using btcpayserver's 'opt-save-storage' option which only saves about a year of block info, and the original channel creation was several years ago.

Some of the info I found involves using chantools, but I don't grasp enough to see why my fee bumps haven't gone through.

A) Does every time I "bump" a fee, increase it by that amount, or set the new fee to that new amount?

B) Could it be related to having maxmempool set to 800 because not enough "history" is available? I currently have 4G on our server but could temp change the server config to have more, and increase maxmempool=4000 but prefer to do that only if it might help. But I beligve maxmempool is just how large it will allow it to grow "from this point forward."
This is the current mempoolinfo:

 ./bitcoin-cli.sh getmempoolinfo
{
  "loaded": true,
  "size": 111926,
  "bytes": 163160286,
  "usage": 604767760,
  "total_fee": 21.96407912,
  "maxmempool": 800000000,
  "mempoolminfee": 0.00001000,
  "minrelaytxfee": 0.00001000,
  "incrementalrelayfee": 0.00001000,
  "unbroadcastcount": 0,
  "fullrbf": true
}

C) What suggestions do you have? I have been trying to grasp everything but still can't find a clear and relatively safe path forward for this case.

Please advise!

./bitcoin-lncli.sh pendingchannels
{
    "total_limbo_balance": "9897306",
    "pending_open_channels": [],
    "pending_closing_channels": [],
    "pending_force_closing_channels": [],
    "waiting_close_channels": [
        {
            "channel": {
                "remote_node_pub": "021abdd2431bd4205b760e13e76b080ecb812804c33b399372d974d50b384d92d7",
                "channel_point": "d662b0faf02393110ebbf897d40b5816ddc5c38156c891c04c2247c7a2bc316c:1",
                "capacity": "10000000",
                "local_balance": "9897306",
                "remote_balance": "102312",
                "local_chan_reserve_sat": "100000",
                "remote_chan_reserve_sat": "100000",
                "initiator": "INITIATOR_REMOTE",
                "commitment_type": "STATIC_REMOTE_KEY",
                "num_forwarding_packages": "2",
                "chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
                "private": false,
                "memo": ""
            },
            "limbo_balance": "9897306",
            "commitments": {
                "local_txid": "52ee43c1c7976556e5803a7018fd4a8e9e1b53383436c72fb5493f9b6d0b5690",
                "remote_txid": "a83bcc7b3c8ff257145785cb121002e1a3b9617e335fa0140bb22524decd02d2",
                "remote_pending_txid": "",
                "local_commit_fee_sat": "381",
                "remote_commit_fee_sat": "381",
                "remote_pending_commit_fee_sat": "0"
            },
            "closing_txid": "52ee43c1c7976556e5803a7018fd4a8e9e1b53383436c72fb5493f9b6d0b5690"
        }
    ]
}

[tlindi]

I did test similar situation to find if it's safe to run pruned node (ie BTCPay space saver).

I stopped lnd, set prune to 10GB and let Bitcoin Core run more than month for it to purge last block when lnd had sync.

Result lnd can not start. To recover full blockchain needed to be downloaded onto Bitcoin Core. The lnd was able to resync and start.

This mine is not exactly your case. But I'd quess there will be issues if you channed force closure time blocks was purged. At least it likely cause issues for you to study what happend.

My (maybe wrond and time consuming) proposal for solution - study a lot and carefully restore LND from aezeed and SCB-file with connection to Bitcoin Core full node which has a full blockchain data.

And you will need some more knowledged Guy to help ypu too. Your commitments on limbo channel are just too small (some 300sats) for closure ever be mined. Meaning somekind of bump should be done, but it might be bit hard...

Good luck!

[tlindi]

But it seems you have gotten your sats to safe:
https://mempool.space/tx/52ee43c1c7976556e5803a7018fd4a8e9e1b53383436c72fb5493f9b6d0b5690
Congraz!

[jquiros2]

yes, thanks. used antpool accelerator to mine it. but had to pay them twice ($50x2).
that'll teach me to check channels more frequently!