Attention ⚡ nerds!

Can anyone help explain wtf is going on here with a force close of a channel on my LND node?

I force closed 3 channels 4 weeks ago, but I still have pending sats.

This is the initial force close TX:

https://mempool.space/tx/2803aaa71b088013e2dd5abe0824c981f9ad245e495d7814220a4bfca6b498dc

But I see this has been RBF-ed by this TX:

https://mempool.space/tx/2be81fa9a6ff2fd66ae254c04b83a4a915bb56dde89bc9b97813f26449ef2f44

Did my node do that?!

That last TX looks wild and has an output significantly less than the TX it replaced! 😱

Reply to this note

Please Login to reply.

Discussion

Yeah, I see it's not confirmed yet.

But how come it got RBF-ed and my output has now gone from 0.01663919 to 0.00043251?

Hey that's true what in the fuck ??

WILD

I have no clue what's going on.

1.6M sats (~1k USD) seem to have evaporated ☠️

You should hop onto the LND slack and report this, very weird!

Do you have an invite link? The one on their website is ded.

Why do you have 293 inputs there?

he appreciates receiving feedback

ahahahahah

No idea!

Apparently the anchor got swept and consolidated with a bunch of other swept anchors.

LND won't spend the original output until this mega TX clears.

It must have been HIM again (Elon Musk):

Update:

OK, this is now sorted. For those curious, my LN anchor TX got RBF-ed into an anchor consolidation TX (part of the protocol apparently), but that TX was not in my mempool (300MB) and so LND wouldn't let me spend my output in the parent TX.

So, I increased my mempool memory, waited for it to sync (which took a while) and then boom, it appeared. LND restart and the 'stuck' TX is now spendable.

LN is a beast.

Thx to nostr:npub1l5u0zd00va02ch5n6ke2wwxyzamuy5qcsqcu4uwu7pa3dpapleysf7aap5 for the insight and helping get my sats unfucked!

Your zap address is not working mate. 👀

Fixed, thx for the heads up

ZAPPED ⚡