Nah force closes during high fees.
Seeing multiple people opened 1m sat channels get forced closed for 500k fee over the last few days.
Having a hard time recommending people setup their own nodes given this
Discussion
Ahh. That’s really rough. So is there a situation where if fees get high enough a channel can force-close as a result of something contractual?
Or is it more that the unfortunately-timed force close just hurts extra bad when fees are high?
I'm not sure about that. Clearly I have a lot to learn!
I made a critical mistake last night while hardening my home network and inadvertently blocked necessary routing through my node with a dumb firewall rule. I didn't catch it and htlc's were stuck while I slept. My node broadcasted a force close commitment. 🤦♂️🤦♂️🤦♂️
Learning a lot today! Certain lengths - or degrees - of downtime (but not others?) will cause a force close?
Sorry for your loss of sats 🫂
What I learned/surmised yesterday happened in a whirlwind, so the details aren't quite clear to me yet.
> Node fine, no issues
> apply newly learned firewall rules, go to sleep
> wake up, see force close
> panic
> firewall logs show blocked IP's to node while sleep
> nuke firewall rules
The particular network firewall rule was 'Drop invalid state', which I don't fully understand and blindly applied as part of an overall hardening guide.
So, to attempt answering your question given my limited knowledge:
An offline node doesn't seem to cause anything to get stuck, but an online node with broken LAN routing appears to be a real issue.
Perhaps my node appeared as viable in the graph, accepted an htlc, but threw it in the fuckin trash? 🤷♂️
What I just said doesn't quite add up to me, because I'm wondering why my own node would broadcast a force close if it was in fact the 'bad actor'. I was under the impression that other nodes in the route would force close as a result of my node not 'playing fairly'.
All I know is the only variable out of place here is that LAN firewall rule.