Replying to Avatar Peter Todd

74.1 sat/vB mempool min fee!

It's possible that someone is setting up for an attack on lightning. The current Lightning protocol is kinda broken with respect to fees, as your commitment transaction (and refund transaction) isn't necessarily high fee enough to get propagated.

It's not quite as much of a problem as you'd expect, as many well connected nodes (rg mempool.space) have much bigger mempools. But anyway, lightning needs to get this fixed.

Not using RBF to begin with was a big mistake.

#m=image%2Fjpeg&dim=1080x455&blurhash=Z46RN2Tc%255I.D%25RjOS-WE0%3Fdtn%25OE1X9s.In%251In%25D%256X2V%7CIURit9oZoOM%5DxcR%23RRRhaxohbWo%24&x=c19d2c798c710dd0cb3babdcf0f0918feb17fa554d4d1c42598f539de6428716
Avatar
Louferlou 2y ago

Very dumb question I guess but why do nodes wait for new htlc to go through their mutual channel to build the next commitment tx and update the feerate ?

Why can’t they build a new commitment tx every x block/time to keep the fees up to date ?

Reply to this note

Please Login to reply.

Discussion

Avatar
Peter Todd 2y ago

No matter how often you try to keep fees up to date, the fact is they can change unexpected by the time that you actually need the transaction. This is especially true in cases where nodes go offline unexpected – one of the more common reasons to need to force close in the first place.