Forwarded from Down Fall
I have this annoying issue in my node: it does not forget some channels due to: "ONCHAIN:1 outputs unresolved: waiting confirmation that we spent DELAYED_OUTPUT_TO_US (cbxx....cf1:0) using OUR_DELAYED_RETURN_TO_WALLET". ( this one is like a year old , and it's still there ). I have like 20 of them
However, cbxx....cf1:0 has already returned to my wallet . The tx shows up in mempool.space . Does it mean cln couldn't find it on my btc node (it's a full node, not pruned) ? Should I try to use the dev rescan wallet to resolve the issue ? How did it happen in the first place. I think it's been like this since a few release ago. (I'm still on 24.05, not sure if it's fixed on 24.08 and nobody seems to complain about it, maybe it only happens on my node)
However, cbxx....cf1:0 has already returned to my wallet . The tx shows up in mempool.space . Does it mean cln couldn't find it on my btc node (it's a full node, not pruned) ? Should I try to use the dev rescan wallet to resolve the issue ? How did it happen in the first place. I think it's been like this since a few release ago. (I'm still on 24.05, not sure if it's fixed on 24.08 and nobody seems to complain about it, maybe it only happens on my node)
Forwarded from no bullshit bitcoin
LifPay Temporarily Suspends Operations, Winds Down Wallet Services
https://www.nobsbitcoin.com/lifpay-temp-suspends-operations/
https://www.nobsbitcoin.com/lifpay-temp-suspends-operations/
Lightning's Best Moments
njump.me/nevent1qvzqqqqqqypzqhvnjd5jmfjxtw0z522zyd3852t7v6xmzjnz0g2ewqnk2kuk9fljqyt8wumn8ghj7am0wshxummnw3ezuurpwf68jtcqypz53kd3mdmevtzhcya8yu29rgnz7zuk8vmwe6s30un2nv85ev50wu07nlk
smallworlnd (npub1tk…pwnl5)
smallworlnd on Nostr:
A post mortem on this exploit if you're curious. The attacker paid a hold invoice as expected, but force-closed the channel immediately on first confirmation of the funding transaction, which is very much not expected. That basically broke
🔥1