"I've been running my LND node with Knots for months without issue."

A response after I warned about fee estimation. Not an issue if you know the game well bur hope fees don't spike.

Reply to this note

Please Login to reply.

Discussion

I tested a filtered Bitcoin node with mempool against the public mempool.space instance

Both fee estimates were within tolerances and either both confirmed or both didn’t on the next block

So non-issue for force closures?

Yes. It must also be understood that mempool consistency is not guaranteed and nodes must be able to tolerate drifts in fee estimates

There’s also the fact that LND has its own proprietary fee estimator, and therefore had a lot of force closures during fee volatility periods with CLN/Eclair nodes

So this would have to be fixed even with uniform mempools

Good nuance. What fee estimation is it using? It’s not from the node associated to it?

I am not sure. Some people also connect it to custom fee estimators too that are neither LND’s own or bitcoind

Knots is more configurable out of the box than Core... I set my mempool to allow fees as low as 0.2 sats/vbyte... Might set OP_RETURN limit to 4MB just as a statement 😁