🇬🇧 BITCOIN | Is even more Bitcoin at risk? (Ep 844) 🚀

So you know, I will always do my best to bring you what is going on out there in the Bitcoin world, anything that you might need to be aware of.

And today is no different.

We've got a packed show.

The thumbnail is was talking about more Bitcoin at risk question mark.

That doesn't mean Bitcoin's at risk.

It simply means, could it be? And that's what we're going to talk about right now.

So I saw this tweet, and I don't usually start with tweets, but it was from Bitcoin News, Rob over at Bitcoin News.

And it said, core lightning warns users to upgrade or take their nodes offline.

So core Lightning developers are preparing an emergency release after receiving a wave of AI-generated CVE reports over the past 10 days and validating vulnerabilities requiring fixes.

The team has escalated its response and will release signed binaries while keeping details of the vulnerabilities under embargo for two weeks.

CLN strongly urges everyone to upgrade during that window.

If you don't upgrade, developers recommend taking your node offline due to the known risks.

Previous releases, including 26.04, will no longer be supported.

There was this one.

Old Lightning nodes may be exposed to a full channel wipeout after LND fix lands later than disclosed.

So LND, a lightning network node implementation, has disclosed a channel close floor that can put an entire channel balance at risk in the reproduced maximum loss scenario.

Operators using standard releases below 0.221.0 should treat their nodes as lacking the official fix unless they were independently patched.

The disclosure describes how a malicious channel peer could combine a one block Bitcoin reorg with an old revoked commitment transaction after a cooperative close.

Bastien's Tien Thurie, who published the disclosure, said no affected users were currently known at this point.

So.

Do I understand what I've just covered with you? No.

Seems like a load of old gobbledygook.

But what I can take from that is if you're running a node and you're also running a lightning node and you've got lightning channels opened with someone else, you could be at risk, I guess is what that is saying.

So if that's you...

Get on, dig deep, and do your own research and find out what the hell is going on.

So you know, I will always do my best to bring you what is going on out there in the Bitcoin world, anything that you might need to be aware of.

And today is no different.

We've got a packed show.

The thumbnail is was talking about more Bitcoin at risk question mark.

That doesn't mean Bitcoin's at risk.

It simply means, could it be? And that's what we're going to talk about right now.

So I saw this tweet, and I don't usually start with tweets, but it was from Bitcoin News, Rob over at Bitcoin News.

And it said, core lightning warns users to upgrade or take their nodes offline.

So core Lightning developers are preparing an emergency release after receiving a wave of AI-generated CVE reports over the past 10 days and validating vulnerabilities requiring fixes.

The team has escalated its response and will release signed binaries while keeping details of the vulnerabilities under embargo for two weeks.

CLN strongly urges everyone to upgrade during that window.

If you don't upgrade, developers recommend taking your node offline due to the known risks.

Previous releases, including 26.04, will no longer be supported.

There was this one.

Old Lightning nodes may be exposed to a full channel wipeout after LND fix lands later than disclosed.

So LND, a lightning network node implementation, has disclosed a channel close floor that can put an entire channel balance at risk in the reproduced maximum loss scenario.

Operators using standard releases below 0.221.0 should treat their nodes as lacking the official fix unless they were independently patched.

The disclosure describes how a malicious channel peer could combine a one block Bitcoin reorg with an old revoked commitment transaction after a cooperative close.

Bastien's Tien Thurie, who published the disclosure, said no affected users were currently known at this point.

So.

Do I understand what I've just covered with you? No.

Seems like a load of old gobbledygook.

But what I can take from that is if you're running a node and you're also running a lightning node and you've got lightning channels opened with someone else, you could be at risk, I guess is what that is saying.

So if that's you...

Get on, dig deep, and do your own research and find out what the hell is going on.