Oli

Feel free to look into this. I started and then ran into some fee estimation issues. See my WIP commit here: https://github.com/guggero/lnd/tree/default-change-taproot

Do you have any more information about those ghost UTXOs? Do the outpoints exist on chain (block explorer)? Do they exist in your `lncli listchaintxns` output? If they do, are...

Can you send us some more information please? For example DM me on [our public Slack](https://lightning.engineering/slack.html), same username. It's really hard to say anything without any transaction IDs or on-chain...

@xjmzx Take a look at [`--reset-wallet-transactions`](https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md#forced-in-place-rescan). Closing the issue as I believe the original problem was resolved. @rbpaul feel free to re-open if that isn't the case.

I think the wallet will issue rescans for each found transaction output to find out if it was spent (which AFAIK is a background task independent of the initial wallet...

Okay, thanks for the update. We'll need to take a look at the full logs to dig deeper. Could you please set `--debuglevel=debug` and `--reset-wallet-transactions` on your node (again) and...

Thank you very much @xjmzx for providing the full logs with the correct debuglevel. I think I was able to figure out what's going on: If one or more UTXOs...

Thanks for the info. I can confirm they look the same as those from @xjmzx (two inputs, fully spent into a channel output with no change output). Now that we...

I think the idea of starting to return more useful information with errors is a really good one! There are a few things I personally don't like about the current...

> If error details are a string, is that structured error details? I would argue yes. You get key/value pairs with known and stable keys and you don't have to...