Oli

@hieblmi sorry for the late answer. Here's my input to your three questions: 1. Ah yes, good catch. I agree that we should choose `MinChanDefaultSize` instead of the configurable one...

I was able to reproduce quite easily with go 1.19.1 in an itest. Looks like `*e = alias` triggers this in [`ReadElement`](https://github.com/lightningnetwork/lnd/blob/master/lnwire/lnwire.go#L477). EDIT: Thanks @akovalenko for opening https://github.com/golang/go/issues/55122, looks like...

GitHub shows a conflict, but doesn't say in which file... Can you try rebasing please?

Needs another rebase, will merge this as soon as possible to avoid further conflicts.

Looks like the linter and tests are failing because of a recent change in `master`.

You should use the `lnd` internal compaction (`db.bolt.auto-compact=true`) for compaction. If you don't get any errors on compacting the `channel.db`, you are lucky and can continue using it. BTW, the...

See the comment above. This happens when lnd shuts down after not having been fully started. Which might have happened during the compaction.

@rkfg the history of this is: - With legacy channels (pre `lnd 0.6`) you needed the `per_commit_point` from the remote peer to sweep the to_remote balance (your balance if the...

> @guggero tagged you because it looked like you had touched the code most in the past. Interested to know whether you want external contributors try to come up with...

Update: Talked to @halseth who was involved in the original fix of the stuck HTLC PR (#5214). Though we agree that the payments don't look exactly like those caused by...