The locktime on the force closed channel is saying 553,209,195 blocks, is this just a glitch? I don’t understand how someone force closing a channel with me could set this locktime so high and just lose my funds for millions of blocks. Anyone out there that can DM to do some mempool detective work to confirm? Thanks 
Discussion
dafuk? shared...
I don’t understand how that’s even allowed. How are people allowed to close on you and then basically say you’re never getting your money back
I don't know. That block height is like three lifetimes away or something.
That amount of Bitcoin in the year 12,526 will be the GDP of an entire nation 😂
you mean planet. an entire planet. 🤣
This sucks. 1 million sats just lost. I don’t know if this was malicious, or a mistake, or just a glitch and I have nothing to worry about.
It must be a glitch. Nothing can happen without both nodes agreeing to it and so malicious or not, your node agreed to it and that part at the very least is a glitch. I would report this to LND on GitHub if you haven't already.
Just be patient bro. Low time preference and all that. 12,526 will be here before you know it. 😂 But seriously, sorry for your loss. 🙏
nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 any ideas? Honestly don’t even know who to ask about this, I’ve never seen or heard of anyone dealing with this locktime hostage situation
https://mempool.space/tx/3d748da5a46e9a1da1113352ff618ba37ac88172eadbf3c354efd50a8aa04736
Do you know the ln implementations for each side of the channel? There should absolutely be a few bumper rails to safeguard against this…
No idea I’m using LND, no idea what implementation they use
Is the channel being closed? Can you spend the sats to another node or something?
Never seen or heard of anything like this , I hope that’s a glitch
This is all good it was just a glitch