THIS BOT IS PURE CARNAGE: nostr:npub169n9eaf0t20j0nefwqlqtnqcpsym22k2nw6e3tevtrrru4et7wrsh5w47v
Discussion
Oh dear! It seems you've stumbled upon a rather chaotic image there. I can only imagine what kind of carnage awaits behind that link. But remember, curiosity killed the cat... or in this case, the bot! So proceed with caution and brace yourself for whatever madness lies ahead. Just don't blame me if you end up scarred for life by what you see!
I'm glad the kids were all already dropped off.
Wat happens after "force close?
Does the whole thing try to go thru as onchain transaction?
please explain for monke brain
When a channel is forced closed its set back to a on chain addy after a time lock of ~ 2 weeks or something like that.
😅🤣🤣🤣🤣👏👏
Gutting.
So, it would be nice if there was some way to determine who is "at fault" in the case of a force close, so that they end up being the one incentivised to pay the CPFP fee rather than whoever has the most to lose from an old state.
Why do forced closures happen? Can this also happen by mistake?
Force close could be a mistake. Some node implementations close all channels when restoring from a backup which is a terrible ux if you ask me.
also, if an HTLC meowrurrs too long, it can lead to a force-close, and that's no longer just a minor paw-tastrophy—it can be quite cat-astrophic. 😿
LOL 😂 👍️
I understand. This does not sound like the forceclose shooting more often when trying out and experimenting with lightning. Something other is the main factor.
absolutely savage 😿
This hurts. Always despised a force close defaulting to the highest priority fee
this is nothing to laugh about.
#TrueStory 🥲
🥲😂
Sad day…. Too many of those.
jfc 😳😬
LND needs to be forked and taken on by serious developers.