pull down to refresh

LN isn't trustless because when you open a channel, you are trusting your channel peer not to close it during an unreasonably high fee environment.
You think you own X% of the sats in your channel, but really, a miner owns some of those sats.
What are your practical recommendations to manage the fees? From the UX point of view it's a nightmare. If I specify 23 sats/vByte to close a channel the final result often varies from 12 to 80 and it seams totally unrelated from the current mempool activity.
reply