lnd: "the passed output does not belong to the wallet" when attempting to bump fee
Background
I recently tried to close a channel but the closing transaction has too low a fee. However, when I try to bump the fee, the wallet claims that the output does not belong to the wallet. The transaction ID appears in lncli listchaintxns:
nate@nates-server:~$ lncli listchaintxns | grep "c36ffcdd245425a1c0bbbdaf65693f4dbe1e050d5a29e1aa9d2079d4ba7cc925"
"tx_hash": "c36ffcdd245425a1c0bbbdaf65693f4dbe1e050d5a29e1aa9d2079d4ba7cc925",
Your environment
lnd version 0.12.1-beta commit=v0.12.1-beta- Ubuntu 20.04 LTS, AMD64, kernel 5.4.0-70-generic
- Bitcoin Core version v0.21.0
Expected behaviour
Closing transaction is bumped, using CPFP or RBF
Actual behaviour
nate@nates-server:~$ lncli wallet bumpfee c36ffcdd245425a1c0bbbdaf65693f4dbe1e050d5a29e1aa9d2079d4ba7cc925:1 --sat_per_byte 20
[lncli] rpc error: code = Unknown desc = the passed output does not belong to the wallet
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 46 (29 by maintainers)
@djkazic if fees don’t go down within that period, yes. That’s why we have channels with anchor outputs now (still not enabled by default, has some implications on wallet balance). As for why it’s 1 sat/vbyte, it depends. It could be that the last fee negotiation happened at a time fees were low enough and the peers haven’t reconnected since. At least one fee update per hour of channel uptime is attempted by lnd.
Is there a reason it chose such a low fee bucket at 1 sat/vB? At current mempool rates that’s unlikely to ever confirm. Does this mean potentially waiting months if not years for the force close to go through?