Oli

~Can we keep just one of the three issues that track the same problem?~ - https://github.com/lightningnetwork/lnd/issues/6660 - https://github.com/lightningnetwork/lnd/issues/5983 - https://github.com/lightningnetwork/lnd/issues/6886 EDIT: Issues are very likely related but not the same...

Right, my mistake. It looked to me like at least #6886 and #6660 were caused by the acked updates being kept in memory, but according to your comment above that...

Needs a rebase. And this might have already (partially) been addressed by https://github.com/lightningnetwork/lnd/pull/6710.

> @yyforyongyu Should i submit review changes with fixup commits, or always keep everything squashed into one commit? (docs suggest the former) Since GitHub tracks the diffs of force-pushes, it's...

Duplicate of https://github.com/btcsuite/btcd/issues/1891.

I don't see how a relative `valid_for` would work. When would that start counting? At the moment you add that caveat? Then you could just as well create an absolute...

Should be rebased on the compressed/combined ZC PR.

I took a quick look at how we store/publish the transactions in Pool. Unfortunately I think we can only solve this in a very hacky way without first starting to...

No, the execution fees are what the market participant pays to the auctioneer (service fees). So only the chain fees should be counted IMO.

I took a quick look and it looks like the public key in the witness doesn't match the address on chain. This is really really weird and I can't think...