Are you having trouble withdrawing Lightning from @binance ? I am but I know the reason and its not your fault. For the last few weeks any attempt to withdraw Lightning from Binance to my LND based Lightning node would tell me "no route"

This has been a long time coming!

https://github.com/lightning/bolts/pull/1228 by @realtbast

🚨 If you are running LND older than 0.18.5 and/or Lightning Terminal older than 0.14.1, stop what you are doing and upgrade immediately. Thieves are draining funds using exploits that were fixed in these releases. 🚨

Dear LifPay Users, After thorough evaluation and in aligned with regulatory requirements, we have made the difficult decision to temporarily suspend LifPay’s operations. As part of the wind-down process for the wallets, we kindly ask a

Good question. First of all, you should know that...

Alby Hub forced one of my channels to close. The photo below is how I found out about it. I did not initiate the action. It appears that it can happen if the channel isn't used very often. That's the only explanation I can find. https

> **BROKEN** ... call Rusty Russell ! uh oh https://m.primal.net/PiUN.png Never underestimate your users 😂 https://m.primal.net/PiUo.png

Discussion of a bug in LND's on-chain handling that can be exploited to steal funds

Custodial Bitcoin Lightning Network wallet Alby has started confiscating user funds, labeled as an "inactivity fee"! 😵‍💫

Allegedly, terms of service were recently updated to allow the company to seize customer funds on custodial accounts that haven't had…

all day every day https://image.nostr.build/18281434224fcf325d1dfe746050143cdc158831788e2ee94fe841ba09519a8d.jpg nostr:nevent1qqs8q0qnj5lyps23ngrnj64ywk7h77gn95rh8v7cv06ym8up57u3m6spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdxpfv50

Regretfully, just several hours ago an attacker took advantage of some still unknown exploit in the LSP liquidity leasing flow in publsp and liquiditystr. The tldr is that the attacker managed to get some LSPs, including myself, to lease li

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

I have $1,454.96 locked up since Friday (rugged?) by Megalith LSP. These are payments people made through Shakespeare (about 90% of which is AI expenses) https://media.ditto.pub/739fe4dcb3d7d2af851b4340cabed0f05a1f57c6d7e84f70dad4dbe2b8beb

💢LIGHTNING CLOSED ALL OUR CHANNELS. I have no idea why. What a fucking mess this retarded tech is

We'll reopen the channels when our BTC is released from the force-close-limbo

Wen Lightning? ⚡️

Bitcoiners asked for it.

We built it.

Only very few used it.

The consequence?

We sunset it! ❌

No regrets.

It was a great learning.

Now let's build something people actually use! 🚀

Discussion of a bug in Eclair's preimage handling that can be exploited to steal funds