Hello, and welcome back to The Bitcoin Brief, a live and interactive show taking place every Monday at 9AM eastern or 2PM UK time across the ungovernable network. Each week, we go through the news, the releases, and the developments that actually matter in Bitcoin.

This, of course, includes self custody, privacy, the tools you can run yourself, and the people trying to make all of that harder. If it affects your ability to hold and spend your own money without asking permission, then we want to talk about it.

This show and the topics that we cover are powered by freedom.tech, a daily news desk that uses AI to monitor hundreds of sources so we can continue to bring you the signal each and every week.

We love to have you help stay the conversation by commenting live, asking questions, boosting the show, or just sharing it with your friends. My name's Q and A. I'm head of customer experience at Foundation. And as always, I am joined by Max, the head honcho of the Ungovernable Network.

Max, how's it going? Good morning, mate. Yeah. It's it's going okay, all things considered. Thank you. How about you? If I could summarize myself in a meme, it would be the the Koreans on the rooftop.

It's it's been an interesting couple of weeks for reasons that I'm sure are not lost on everybody listening to this. We're gonna dive into that shortly. But as the the... I guess the show title suggests, the fun's not stopping, is it?

We we had a boring spell for a while, and I hoped for some excitement. This is not the excitement I hoped for. The the excitement I think I hoped for was, like, some sort of interesting price action or some sort of new developments that made things cooler and better.

And what we've got instead is just, like, I just feel like I'm on high alert every morning with some new disaster. Something that would have had the limelight for, like, two or three months now gets the limelight for, like, half a day before the next problem.

But I guess that's why these shows do exist is to try and help us and others try and navigate the stormy seas. We just weren't expecting the storm to be quite as fucking mental as it is. Yeah. It's

it's a it's a wild time. I I feel like I've said that on every brief that we've done for the past, like Yeah. I don't know, ten to twelve weeks lately. It's just 2026 has been absolutely Has it been... Unbelievable and not in a good way. Hello to... Yeah. Worst? It's been the worst, hasn't it? Because, like, 2020

was, like, horrible for price. I remember, like, March 2020, you remember seeing or watching us go to, like, three k. And I remember being like, oh, like, fuck. This isn't this isn't ideal.

This is not this is not a good situation. This doesn't feel nice, but it's not the same sort of doesn't feel nice. This is a this is a worse doesn't feel nice because friends and people we know have been hacked and attacked, and every project pretty much we know has been hacked and attacked, and nothing feels stable.

It's it's different. Yeah. Absolutely. Quick hello to We Are Satoshi Pods who's in the live chat saying, glad to catch it live. Nice to have you with us. Thank you. Yeah. Thank to start on such a such a downer. But... Yeah.

So we... We've had a a couple of weeks away. Not planned, unfortunately. And it was me that called off the shows again for for obvious reasons. We've we've had a bit of an incident, to put it lightly.

That over at Foundation HQ, The last couple of weeks have been... Well, it's basically in fight or flight mode, scrambling, trying to make things as right as they can, support customers. And I guess, just plug the the gaps and and make sure that our systems are secure once again.

We've now published the the full report, which I will endeavor to link in the show notes. It's on the the the public forum. All of that's in there. I was posting updates as regularly as I could as and when the incident was unfolding to keep people as in loop... In the loop as possible.

So the full report is there, but I've got kind of a a brief summary for those people that aren't in the forum or have no desire to kind of sit there and read through a lot of text. Mhmm. So, yeah, on...

What was the date now? Late on the Sunday October 25, our customers and weirdly some people that weren't our customers began receiving emails claiming that their passport had been recalled.

There were more than 23,000 emails sent out to 21 and a half thousand email addresses carrying our branding. It came from a real foundation email address, And some of those emails included the recipient's own purchase details. They look like very convincing emails.

The emails pointed to websites in a typical phishing fashion asking for recovery phrases, your seed words. Ten minutes after the first report, our team was on a call. This was like late eastern time. I was in bed at the time.

And by about 11:30 eastern time that night, the team had... Or the team that were online, thankfully, had managed to figure out in the early stages what had gone on, revoked how the attackers were able to get into our systems, more on that in a minute, and removed the fake sub domain,

which I believe was something like incident.foundation.xyz, and stopped all remaining emails that were still in the queue just before 1AM. But loads of them were already sent as I as I mentioned.

So the attacker got into our systems through a self hosted cal.com. Some people will know that... Referred to as Calendly. I believe it had a rebrand at some point, but we self hosted our own version because it's open source software. It's basically an appointment booking app that we run on our own servers.

Well, a code execution bug within that software lets the attackers run commands on the server that it was hosted on with the earliest confirmed activity being a couple of days before all of these emails initially went out.

From there, they chained together with a second bug that was in the software that hands out the credentials to our other applications. So they were able to collect keys for email, the store, and our DNS, the domain settings and stuff as well.

All of those internal systems sat behind a VPN and staff accounts use two factor authentication. Neither of which helped because the attacker was working from an application that was already inside the VPN network using those credentials through that secondary bug that were built for software.

So that... Because those credentials were built for other piece of software to access, there is no kind of two f a in that scenario. No employee accounts or devices were compromised. So the data that was accessed includes names, email addresses, order details, and archived support conversations.

For a subset of those customers, it did also include postal addresses, phone numbers, and partial credit card details, which is the the last four digits and the expiry dates.

We never have or hold full card numbers. That's the way that card merchants operate is that, you know, if you're the the vendor, you see the last four digits. So that data just simply wasn't there because that's how Shopify and Stripe work.

Some of this... This is the most annoying part of the whole thing to me is that a lot of this was all the data that was that was under us impression, gone, completely erased. It was from our old WooCommerce store where I had access to and I could see when it was online that the old orders showed redacted.

Because I frequently have to go in there to validate old orders for like, warranty purposes and things like that. And I distinctly remember going in, typing in an order number and it would just be like order number 3000 and 78 and all of the fields literally said the word redacted.

So we were under the impression that that would all gone because we had it set to erase that data. It was a it was a flag in WooCommerce. Well, unfortunately, it turns out that WooCommerce also did some database migrations as part of its kind of natural software life cycle.

And when it did that, old copies of the database with the unredacted customer information remained. But when we went in in the admin panel, it was gone.

So a little bit frustrating to say the least, but again, that's not an excuse to remove our culpability in this. At the end of the day, the data was in our custody and, you know, that ultimately just falls on us.

To be very, very clear here, fund... Any funds held on any passport device are completely safe. The same goes for Envoy. There is no vulnerabilities whatsoever in any of our hardware or our software that is affected by this.

The main risk, which is exactly what's happened since then, is that scammers are using the data to talk to people and try and get them to give up their recovery phrase or to just send funds to directly to the attacker's address.

Customers have reported phone calls posing as our support team, quoting the the leaked data, including names and addresses, order numbers, that sort of stuff. And there's been various different prongs of the attack.

We think probably from multiple different attackers. Some of it's saying there's a recall for their device, or they're saying there's a... There is a vulnerability with the device and that they need to send funds to a quote vault to secure them.

Basically, just trying to shock people and panic them into giving up either their funds directly or their seed phrase as well. As I said, the the full report is on the form if you wanna get in even more into the details.

And I guess... Yeah. It also includes what we're changing going forward, more information on the number of people affected. And if anybody's listening to this and needs some support or has any questions on this, then feel free to reach out to me directly at hello@foundation.xyz, and I'll do my best to,

you know, help out and offer any support or guidance as as I can, basically. Needless to say, this has hit us all pretty hard to say the least. Again, there is kind of no... Not trying to worm away out of culpability here, like, we had the data, we thought it was deleted and it unfortunately wasn't.

The the tooling that was in WooCommerce was insufficient to... We just trusted what the admin panel said. Obviously, that excludes the newer Shopify stuff, which was also accessed. And as a side part to that, which is also equally as annoying is that Shopify has

oh, sorry. Shopify doesn't have an auto redaction tool like WooCommerce offered. So we were building our own, but that had not been rolled out as yet because it was a custom tool that was going through engineering review to make sure that it was, you know,

it was airtight essentially before we rolled that out. So the customer data on Shopify had not yet been redacted. That is in line with our updated privacy policy. But again, the data was still there and it was unfortunately accessed.

I think that covers all my notes on it, Max. But if you have any follow-up questions or anything that you feel like I haven't covered properly, you know, feel free to to ask any questions that you've got. Yeah. I mean, a few.

We asked Satoshi Pod as sort of covering a bit of it, though. They've asked what lessons learned would you share with other Bitcoin companies who will inevitably face similar problems? And thank you for being transparent and honest.

That's one of my questions really is, like, how do we move forward? Like, a, I respect the fact that you and the rest of the team have taken accountability and held your hands up and said, we fucked up, and, you know, we're sorry, and we're gonna try and fix it, which I think is an important step, which you don't always see.

And then beyond that is, you know, how does everyone move forward? Because it seems to me at least anything you put on the Internet, any information, anywhere is vulnerable. And if you... That's the assumption that I would have personally moving forward. No matter how much I trust a company or a team or anything,

I would just put it as, like, if you're putting information out there, it might well be be used and taken. Yeah. From a customer perspective, it... It's the same message we've been saying time and time again, and this is another reminder of it is the the less information you can have out there,

the better. And if that means that you have to jump through additional hoops to protect yourself, then if it's important enough to you, then you should do that.

But with that said, there should still be an expectation that if you do business with a company that they have an obligation to protect your data. So to answer, we ask the Toshipod's question.

I guess, don't be... Like, you have to be attacking your own systems and you have to be... You can't rest on your laurels and think, you know, for example, for us, we check the admin panel and it said redacted, so it... It's redacted. Like, that's not enough. You have to go and do more and you have to

think like an attacker, unfortunately. And for most businesses, especially smaller businesses, that's a difficult thing to do because you wanna build your product, then you wanna go and market your product. And anything that's a distraction from that can seem like a waste of time.

But, unfortunately, we're... We now live in a world where anybody with a couple $100 has access to super intelligence. And if they're motivated enough to go and attack your shit, then they're gonna do that if they think that there is some money to be made.

And what that basically means is that every team has to consistently do more and more to secure anything that they have that is vulnerable. That could be money. That could be data. It could be secrets,

anything. Like, you just... You cannot rest on your laurels anymore and you have to... Just because everything is okay now, doesn't mean it's gonna be okay in two weeks or in two years. For us, weirdly, we have...

Since we started in 2020, we kind of champion self hosting as much software as we could. And that oftentimes...

Whilst it made us feel good that we were keeping as much of our information in house as possible, it creates a big burden. And it also exposes you to more code bases, different servers, and the the the overall maintenance cost and burden of that is very, very cumbersome.

So we're currently exploring self hosting less stuff with... Which might sound weird, but the goal is the same as it always was and that's keeping control of as much software as you can and of our customers' data.

But this incident has shown us that sometimes self hosting everything isn't always the answer. And it's not, you know, it's not a privacy or a security panacea just because you self host something.

Like, we would we would argue... Arguably have been better off hosting loads of our stuff on Cloudflare, and maybe we wouldn't have got hit by this, which is an ironic twist in the tail. So we are, again, going over all of our stuff, retiring old software,

just delving deeper on anything that touches anything that's considered valuable to an outsider, basically, and just getting way under the surface to make sure that everything's operating in the same way that it should.

And to take it a step further as well, like, this required chaining two vulnerabilities together. So it's it's no longer just a case of, okay, we host this piece of software. Is it secure? Can we review it with AI?

It's also, you know, how does that interact with other pieces of software that we host or that we interact with? Because sometimes, and more often not these days, it is more than one thing chained together that reduces...

Sorry, that

is the reason for Increases attack. Yeah. Exactly. Yeah. It's very difficult to... Like, once you have multiple bits of software interacting together, the the way that you can review things, like the different types of attack just...

It gets a bit crazy trying to cover it all and be able to review it all. You said earlier about, like, smaller teams trying to build this infrastructure while building a product and also outside of building a product, like, get people to actually know what they're doing and want to buy from them. Like, it does seem as a small team,

I don't know what I would do. Like, you lean on something like... Was it WooCommerce? You said he was... Who's the one that said things were redacted. And then Yep. You know, you

then have a failure there, and it doesn't act the way that you thought it was gonna act. So then, you know, if you're relying on these other companies to do things, then how can you review their codes if it's not open? I don't know if there's... Is or not.

And it just becomes... It seems like a a full time task just trying to keep the stuff secure. So outside of, like, running a business and doing... You know, running a business and keeping personal data of customers secure, I think we also need to remind ourselves as Bitcoiners and and people who care about our privacy is just no

matter what changes happen from any company, I really think going forward, you know, everyone's gonna do their best. Foundation will do their best. Everyone's gonna try and keep up with these attacks and and make the changes they can to try and do what they can. But

I just think at this point, I wouldn't wanna put my information in anywhere. Like, if it can be avoided, don't trust anyone or anything. Not that they're malicious, but that just... These attacks are fucking mental. And, like, the people who are doing the attacks are relentless,

and it's changing every single day. And so I think, you know, the last maybe 10 episodes or so, I've said, you know, very boring, the same message over and over again. Don't keep all your eggs in one basket.

If you're gonna buy anything off the Internet, have it sent to a PO box or an army barrack. Yeah. Don't don't do an... You know, if you can buy in person, that's a much better situation. And it's it's not... Like I said, it's not like these companies are malicious and they're selling your data or anything like that. It's just...

I mean, fuck. It's not a good situation. And if it can be avoided, that's... That... That's the best thing is, like, just don't give any more information if you can possibly avoid it. Yeah. Absolutely.

So like I said, just to repeat myself, if anybody feels like they may have been or have been affected by this, then feel free to send me an email. I can give the best advice I can to kind of help, you know, bolster up your security.

If you've got any concerns about what data was was kind of exposed for you personally, or if you wanna strategize with your, you know, your security setup, that sort of thing, you know, it's fine me. Hello at foundation dot x y z, and I'll do my best to to assist.

Yeah. I guess there's a lot of people in that situation and not just from what's happened with foundation, but over the years, you know, many of these data breaches from many different companies,

people may just have been like, oh, well, I'll just leave it. You know, I'm getting phone calls every now and then, but so does everyone. I'm getting these phishing emails every now and then, but so does everyone.

But it sounds like there's maybe some strategies that people can implement to

make some, yeah, make some changes and not be attacked as much. I think someone actually messaged... Was it on the last episode? I'm trying to remember who it was. Someone someone... Was it in a tweet? Someone had asked about how can I find out what information might be held on me that's on the dark net and available?

Is there a way for me to find this and and also, like, erase as much as possible that's out there. I can't remember who asked it now, but I said I'd I said I'd ask the question. Maybe it was on Twitter.

Like, how do... Is there a

is there a guide that you suggest on this kind of stuff? Like, it is like... Is it am I pwned or am I... Is this something like that? Searching for that. I'm gonna drop it in the chat now. It's haveibeenpwned.com, but that's only for email addresses, I believe.

Just dropped it in the chat there. You can pop your email address in, and it will basically search against known data breaches and let you know whether or not there's any matches there. Outside of that, I I believe there might be paid services where you can go and kind of search for

more information than that, but I don't have any experience in using those whatsoever or or I'm able to name any. I just... It kind of... The concept rings a bell, I'm pretty sure they're available, but I have no idea how expensive they are or how effective they are.

Before we move on, because we've got a lot of stuff to cover here, for someone who might be in that situation, changing a phone numb... This is, like, varying degrees of how much of a pain in the ass things are.

Yeah. Changing an email, pretty easy. Like, not the hardest thing. Go and get a proton. Go and get something. Whatever. Like Mhmm. Okay.

Annoying because you still sometimes gotta verify things or people might have your old emails. You still gotta run it kind of... That's the annoying part. You've always gotta kind of keep these old numbers and emails and stuff, but email's the easiest.

Phone number, easy, but linked to a lot of things, and people are always like, fuck. I still gotta kind of keep that, you know, like a a phone in the drawer, but keep paying the contract wherever for a while. And then, obviously, the hardest one is address. Like, if if you've sent something to your physical address,

I hope people haven't, but if they have, it's like, okay. If you're if you're renting, maybe not the hardest thing in the world to move. Might be worth thinking about it if if you own it. Like, it's a it's a lot more of a difficult thing to do.

What's the advice for... If we ignore the the living situation, that's a hard one, but mobile number, email. What's your suggestion? Like, what should people do there? What... When they... When it's not an option to to move house, basically?

When it's not... Well, if... I think if it is an option to move house and you've been in one or multiple data breaches, it's probably the best thing is to move. That... That's that's my opinion. But with the with the phone and the email, given that our phone and our email

is a difficult thing to just, like, step away from and just, like, never look at again, would the would the suggestion be keep an old number, but just have it on airplane mode and turn it on every month or so just to see if you got anything important.

Do that for a year and, like, you know, after that, then fuck it off and the same with an email. Get new ones, or is there, like, a strategy where you... Do you see what I mean? Because, like, you can't just... If I just canceled my phone contract

and I just, like, fucked off my email and never signed in again, I guarantee I'll miss important shit. There'll be stuff where it's like, oh, fuck. I missed that. And that was a... That's now a big problem.

Like, what's a good way to manage that? Is there a good way? Yeah. Thankfully, I've never had to go through this, but I'm pretty sure that if you... Certain carriers will allow you to change your number and have a forwarding service for a while.

Might be might be paid, but that would allow you to switch immediately and then not miss anything. But other than that, I mean, on on the phone number side, then outside of that, if your carrier doesn't offer it or it's not available in your jurisdiction, it is just a case of, like,

listing out all of your accounts and then going through and changing them one by one. Mhmm. The... I guess the good thing that you can do these days is, like, you could... If you've got a local AI agent, you can have it go through all of your inbox and just tell it, look,

pull out all of my accounts. And, obviously, it'll it'll be able to do that because, you know, it'll see, like, your bills coming in or something like that, which is why it's local. And then say, like, draft emails to all of these people and just,

you know, have, like, a boilerplate text to say, look, please change my number from this to this, or please give me the instructions, or please just disregard the number and only contact me via email or something like that. You could use something like that. That's... For the emails for the emails

with hindsight, it would... You you would suggest this is why email aliases are crucial when you use any service online because if one gets breached, just turn off the alias and you don't you don't have to have that big start over again.

But otherwise, again, it's the same sort of situation where you just need to list all your... All of your accounts. Oh, no. Actually, well, with with email, you can set up all auto forwards, can't you?

Mhmm. So you... But but, ultimately, you still gotta change to sell supplier x,

Stop emailing this one after this date. So you still need to notify people and companies that you've got a business relationship with. There's no kinda two ways around it. You can get around it easily with forward invoice and fix the underlying problem, does it?

No. Good point. And and and then with email, when you do make the change, I like Proton how you can just... You know, you have your multiple different ones. So, you know, you sign up for this service and you give x, whatever.

I think that's quite good. Apple actually has a service built in where it's like Hide my email. Hide my email, which is pretty... That's pretty good as well. Like Mhmm. If you if you don't wanna step outside of, like, the Apple ecosystem, it's pretty decent.

But, yeah, I think, you know, I don't really have anything else to say on it. I don't I don't have any more questions. Like I say, I I appreciate that you guys have put your hands up, admitted you fucked up, and could have done more, and you're gonna move forward and do what you can. And

outside of that, there's not really much more that can be said other than I apologize to anyone who has listened to the show and is caught up in this. I really hope that you've taken our advice, read the the home addresses, and and that kind of stuff.

And if you haven't and if there are issues, you can reach out, and I'll try and help, and Q will try and help in any way they can. And outside of that, I think it's time probably to get into the rest of the doom

with with the rest of the companies and everyone else in the space who is also being attacked daily. Yeah. Well, before we do that, just two two quick little bits of other business for me was in Amsterdam for BTC Amsterdam. Yeah.

And whilst as you can tell by my... The tone of my voice, I'm feeling pretty black pilled on Bitcoin in general these days. Yeah. Getting in a room with a load of Bitcoin is... Did invigorate me a little bit. It was nice to... It was a bit a bit more of a smaller conference when compared with something like Vegas, which was nice.

An awesome location called the Sugar Factory in in Amsterdam. Got to meet some old friends, make some new ones, and did a a talk on human authority hardware,

which was filmed. So I I would imagine that'll be coming out soon. And as and when it does, I'll make sure to tweet it, and then we can drop it into some show notes or something like that. So that was fun. Did a little panel with with Derek Ross, who we've had on Freedom Debt Friday, and with Seth, who everybody knows all too well.

So that was fun. I would imagine that was on one of the main stages, so that will definitely be filmed, and we can share that when that one comes out as well. And

this... We asked the Hushpod. I'm someone's a killer conference. I'm so bullish. Blackpill can go in the trash can. Yeah. See? That's what we need. It's a bit of positivity in the comments.

Thank you. That's nice and positive. It was a great conference. I think... When did I go? It must have been four years ago now or something like that. I went to the Amsterdam conference, and it was it was great. A great bunch of people and, yeah, really good conference and good bars and, like, drinks and bits afterwards as well. So,

yeah, sometimes it is that just like...

I think if we if we focus on the attacks and the doom too much, it's really easy to get really depressed. And I I have to say that I'm guilty of it. I'm often saying to my missus, I'm like, fuck this. Should I just should I just fucking go back to normal fear at land? I've got enough shit to be getting on with. Should I just...

I've I've I've had enough. And she's like, yeah. But you care and, know, you'd like this stuff and it's and it's true. Like, I do care and I do like this stuff and I do like some of the people. Like, some are absolutely comes. But, like, there... There's a lot of there's a lot of cool stuff that's being built and there's a reason

that it's being built. And if we think, like, if we really think about what we're trying to do, it is create more freedom for ourselves to to sort of step outside of the cage that's being built around us.

And more importantly than that is to stop it being worse for our children. Like, our our lives are much more controlled than our parents. Our parents are much more controlled than their parents. And it's if that continues,

then I don't want to wake up and my kids are like, hold on. You sort of were involved in this thing that could have allowed us to spend money without being controlled if we took the right steps, and we could step outside of the system.

And you just stopped, and you went and did a fucking normal job that contributed nothing to society,

really. You just put money in your pocket, and you did that. And, like, yeah. Like, if I was if I was my kids, I'd look at myself, me and go, like, you're a fucking loser. Like, why'd you do that? You should have stuck around. So that's kind of what keeps me going.

And and then you see, like, when you go to these conferences and you meet other people who are pouring their heart and soul into these projects and building cool stuff. It's... It it does remind you why we're here. It is important.

Yeah. Absolutely cosign that. It's good to get that that little reminder, you know, when you go and have a chat with people and you realize that most people are much different on... In person than they are on the Internet.

That's that's too true. Yeah. Yeah. Right. That's enough positivity. Let's go let's go back to the hacks and the vulnerability, shall we? Yeah. Alright. So LMbits put out a PSA telling every single operator to shut down after recent attack that drained one of their tipping bots.

LMbits, for those of you who don't know, is the software behind a lot of paywalls, tipping bots, as I mentioned, point of sale setups, and community wallets. So plenty of people hold sats in it without maybe even knowing the name because it is, like, prolific back end infrastructure at this point.

Well, yesterday, November 8, at around half twelve UTC, LMbits flagged the possible vulnerability in its paywall extension and told operators to disable it immediately. Around eighty minutes later, it escalated.

Every LN bit service should stop immediately following a new wave of attacks with security patches to follow. The hosted my.lnbits.com service also went offline. Couple of confirmed victims at the moment, one called BitTipBot, whose operator Kevin Ravensburg says that new accounts using the exploit withdrew 2,200,000

sats between 9AM and 2PM yesterday before the warning went out. He has pledged to repay users himself and Ben Arks has of LMbits has said that patches would land within twenty four to forty eight hours.

And a fix for SSRF protection was merged into LMbits' development branch at around midday today, the ninth of the ninth of November. There's still no patch release yet. It's still in our branch. There's no official security advisory.

And the latest available version is still 1.62, which dates back to September. The cause at the moment is not confirmed. Yeah. And BitTipBot is still the only operator that I've seen at least to report actual losses.

So if you do run an LM bit seven, you're listening to this live or or recorded, turn off immediately until further notice and keep your eyes on the LMBit's Twitter and GitHub pages to see when it's safe to install a new update and kind of get everything back online.

Repeat myself again. Don't have funds hot unless you absolutely have to and minimize how much funds you have hot no matter what team, no matter what you're running.

Just try and minimize your risk, please. Yeah. Absolutely. Next one's an update on the the colossal Binance hack, which is a little over a week old now.

The hot wallets backing the customer balances in Binance's own proof of reserve data were drained across several chains in about twenty minutes, including eighteen thousand two hundred and seventy bitcoin, totaling around $1,400,000,000.

And it's been split into 19 separate wallets. The totals range between 5.8 and 6,400,000,000 with Binance itself citing 6,340,000,000, which is the total the total hack amounts, which is obviously the largest exchange hack on record by a long shot. I actually had in my slides in in Amsterdam

the Bybit hack, which was like 1,400,000,000. And I had in my notes that this was the biggest one by a long shot. And, obviously, I did I did that. Like, I put the slides there, a few days before a few days before the Binance hack occurred.

Yeah. It it absolutely eclipses everything. So just to just to carry on quickly the update before you you come in.

The FBI is attributing it to North Korea as always. Withdrawals reopened in phases from the November 1, and users pulled a net 3,600,000,000 off their accounts in the first few hours. So clearly quite a lot of people spooked by this as you would expect.

Binance says that losses are covered from its SAFU. Yes, that's s a f e fund and from company money. And on the November 6, Elliptic, the chain analysis firm reported that the hackers had swapped about $50,000,000 worth of stolen XRP, mostly into Bitcoin through Thorchain with about 3,100,000,000 still in identified wallets.

By the November 7, around 2,300 Bitcoin from those swaps had moved and 88 Bitcoin had gone through a coin join, where the main 18,000 remaining had not moved in bulk.

Wow. It... Like, fucking... You know, it speaks to how crazy things are at the moment because I saw the Binance hack stuff go on. And,

you know, I just do... I do a daily report with my missus in the morning. We have a coffee and show what's happening what's happening with your work, and I go What's broken today? She tells... Yeah. She tells me what's happening with hers, and then I say, yeah. Well, it's been a hack, and there's been this. And I was like, yeah.

Binance just got hacked. It's, 6 point something billion. And the way I delivered it was just like, it's just fucking normal. And then I'd forgotten about it by the next day, really. I mean, obviously, I'm not affected by it. I don't use them. And I was just like, yeah. It's, you know... But what do you do? It's like

self custody is obviously still the right thing, but it's gotta be done right. Otherwise, you know, things can go horribly wrong, and then you can't trust the exchanges. It's it's a crazy...

It's just... And the numbers are so big. Like, $6,000,000,000 worth? That's a fucking outrageous number. Yeah. And and do you know what? Even more outrageous is I found out afterwards that that was something like 6% of their total reserves?

What? Yep. Oh my god. They're massive, aren't they? Yeah. Are they big? I mean, the bottom line is bigger than... They're bigger than Coinbase. Oh, yeah. Yeah. Biggest in the world. Yeah.

I... I'm almost certain I've seen that or heard that stat somewhere that it was like it was like less than 10% of the total, like, assets under management. So they got 100,000,000,000 ish ish, and they're just like, okay. We got hacked.

That feels to me like, you know, if I went into my BTCPay server and, like, funds have been drained, I'd be like, fuck. Okay. It's... But we don't keep, like, everything on there. Okay. It's like, it doesn't kill us. That's kind of the equivalent for them with this. They're like they're like, it's alright. It's only 6,000,000,000.

Yeah. It was a colossal amount. I'm trying to find it now the exact figure, but... Oh, here we go. As of November 2026, finance reports that customer assets total approximately 129,400,000,000.

Oh, okay. So, yeah, like, 5%. That's mental. And so the other thing I I wanted to know on this is, obviously, it was all the different coins going everywhere. It said that a load had been swapped from XRP into Bitcoin.

Yep. I'm pretty sure I heard there was a load frozen that was on, like, the USD Loads. Whatever. Yeah. Yeah. Couple of billion. Okay. And that's that's just because they can't swap it quick enough or it just gets frozen.

Yeah. Like, there's no way for them to... Why even why even bother hack, like, taking that or draining that if you know... Because they must know. Like, North Korea seems to, like... They... We're told they hack fucking everything.

So they must be pretty good at what they do. They must go, oh, yeah. Like, you know, probably best just to leave that shit because it's gonna be frozen. Yeah. It does seem strange. I mean... But, like,

they've they've they've obviously realized the errors of their ways and started swapping as much as they can into Bitcoin because they know it can't be stopped. Yeah. And then my final my final thought on it is I always wonder with this stuff. I saw the Binance hack,

and I was like, oh, good. Because I... Like, most of the little that I have left is just in Monero now because it's usable. And

I was like, oh, good. That would mean the the value is probably gonna go up drastically on Monero because it's what people would swap into if they're smart. Like, so surely, that's gonna mean the price goes up. And they didn't really... I mean, it is going up, but it's not really made that much difference.

And then I've seen that they're not really funneling it through there. And I do wonder, is that like a liquidity thing and they don't wanna move price because it's such a small market cap and Bitcoin's obviously so much bigger? Like, what's their thinking?

Because as an attacker, I would I would use that not swapping in and out of all of these weird and wonderful coins and jumping through all these hoops. Like, I look at what they do. I get very, very sophisticated on the front end and actually hacking and saving the money.

And then to me, at least, I look at it and I go, it looks really unsophisticated what they do with what they take. It seems really basic. Yeah. I'd... I I would imagine it probably is a liquidity thing.

But, again, it's hard to get into the mind of somebody who's just stolen $6,000,000,000 worth of assets.

You briefly mentioned Monero then. I know this is a bit quintial, but this will get a chuckle from everybody watching. I'm just gonna switch my screen share. Did you see this? Yes.

So for the for the audio listeners that don't see what I'm sharing, it's a screenshot by an account or tweet Mars Spits Bars. By Mars Spits Bars. The caption is Pivot King, and it's a screenshot of Bitcoin Mechanic's YouTube channel, and the title is Monero.

And then this is being quote tweeted by our very own Seth for privacy, and his caption is simply Please, no. Oh god. Please, no. Which I just thought was funny. That was, it it got me a little bit of a chuckle,

in and amongst my black pill moments. So Yeah. I found a good You're welcome. Good for that. What's that what's that film where it's like, you know, the girl... Dark haired girl who's like, no. No. No. The, like, small budget film that went massive. No idea what you're talking about.

There's, like, a small budget film where they spent, like, a couple of million and it went fucking huge. Alright. And there's this actress who's... And she, like, plays, like, a a sweet girlfriend that turns into a proper bunny boiler, like, psychopath.

Anyway, if you don't know, it's not gonna it's not gonna mean anything. Fair enough. Before we move on from the Binance stuff, obviously, a bit of time has now passed and there's a bit more of a post mortem that's gone on.

And apparently, this this hack traces back five months and apparently no key was stolen in the the classic sense. The attackers drove Binance's own wallet signing system from the inside. In June, a wallet DevOps engineer searching for a popular AI coding tool installed a tampered copy of the homebrew package manager from a search result.

Binance caught it, replaced the laptop, and rotated the credentials. In September, a second engineer was approached by a fake recruiter on a legitimate job platform. A second interview came with a coding task that carried malware, replaced the py ENV tool with a malicious copy.

And on the October 20, the attackers used that machine and an internal AI tool to take over two more engineers machines which gave them the wallet signing service used in the October 29 drain.

So fake recruiters and poisoned installers target anybody who runs code, not just simple exchange stuff. And basically, they they did it from from the inside out. So they didn't actually get hold of the private keys. They just got hold of, like, their their internal software to to process their own withdrawals, essentially.

Pretty wild. Pretty wild.

I actually skipped one on the list, and it's BTC pay service. Let me scroll back up. So this one dates back. It's actually harking back to the original BTC pay server hack where hot wallets on servers were drained.

Well, apparently, there's a new route to that same attack for servers that haven't been updated. The bug was fixed in version two point four point two, and servers already on two four two or later were not touched, and neither were wallets whose keys lived off the server, such as hardware wallets.

The first wallet was drained on the November 1 and the first theft reports arrived at 9AM. And the community warning went out just an hour later. Attackers took BTC and LTC Litecoin, Bitcoin.

BTCPay is not given a loss figure or describe the new method, but it landed three days after BTCPay two four seven fixed 85 separate security findings. Goes without saying if you're running version two point four point one or older, treat that server as compromising, get your funds off there ASAP.

And if you can't, just take the server offline ASAP. And don't have funds hot. Like, it's not necessary. Yeah. Yeah. I I can't think of... Like, obviously, in some situations, it might be necessary, but for most, it's not. And for the for the hassle of, like, setting that up, which takes five, ten minutes, You know, we we had...

What was it? Like, whatever day it was when that happened, Jordan messaged me,

and I was, like, in bed. I was like, for fuck's that another problem? And he's like, I'll just go and check. And I was like, I only went on there because I had the Flint stuff. You know? So I had some some stuff. Was like, oh, is that attackable? I'll I'll I'll pull that onto one chain. I'll just set that up.

But it was a nice feeling knowing at least, like, okay, like, whatever funds are on there are Saffu because I've got it, you know, I've got it constrained to my hardware. It's not not hot. And don't know where I'm going with that other than if you are in that situation where you're running a store and you don't already have it

set up with your hardware, probably a good time to do it. Yeah. And also the mempool's dead, so you don't really need Lightning at the moment if you don't want to. So the cheese on chain.

Yeah. Except except everyone wants to use Lightning. So... That's true. Yeah. I think the slid thing with auto swap outs is is a good trade off. It is a really good trade off. I've not had any issues with it. It's been fucking smooth.

You know? Yeah. I can't complain. And and, also, I didn't do anything for a couple of hours after Jordan messaged me because I saw it late, and, you know, nothing had been swept. I was... I would have been fine, I think, even with it on there on Flint, but I just did it as a precaution. And you can do the auto...

Whatever it is, know, set set your limits and it will sweep. So I think it's good. Good stuff. Alright. Next on the list, chain analysis breach widens. Chainalysis builds the surveillance datasets that exchanges and police forces use to screen Bitcoin addresses for naughty people.

On thirtieth of thirtieth of October... That was Oh, I got that. The thirtieth, the naughty people. Just just in case people thought I was like singing to analysis his praises. On the thirty fourth of October, disclosed that an outside attacker using what it called an offensive agentic technique had got into its systems and

internal tools accessing user IDs, names, email addresses, and organization roles. On the November 4, it took it to KYT, know your transaction, and address screening products offline after what it called abnormal activity.

And that night said the breach was worse. Names, usernames, password, hashes, and live tokens for every Chainalysis user had been exposed.

The products came back online on the November 7, and every user now has to reset their password and rotate their API keys. No attacker has been named, and chain analysis says it is not... It has found no access to investigation content.

For three days, exchanges that relied on the screening were running without it, and the company holding address clusters and labels on ordinary Bitcoin users could not keep its own customer data secure.

That is a way to use your clankers. If you're an attacker and you're thinking, yeah, I wanna fuck shit up today. I just wanna cause some carnage. Go and do it with those pricks. Go and cause them some drama.

Yeah. Very well deserved. Absolute cunts. Onto some more positive news. Bull Bitcoin now says it's the first exchange to offer pay join on deposits and withdrawals on every on chain buy or sell through its full wallet exchange.

So pay join is on by default. Very nice. In a pay join, for those of you that don't know, both sides of the transaction, so the sender and the receiver will contribute coins to the the transaction.

And this is with an aim to break the chain analysis assumption that all inputs in a transaction belong to one owner, the sender, known as the common input ownership heuristic. So this

hides or, you know, obfuscates from the the payment intent from outside observers, but obviously not from bull Bitcoin itself, which still knows what it sent, you know, because it's it's a party in the transaction.

Obviously, this only works on chain. And the first buy into an empty wallet is a normal transaction because the wallet doesn't have any coins to contribute to to the page on if that makes sense.

Well, this is pretty cool. I have no idea how they're facilitating this or getting around that from a regulatory perspective. But, I mean, the team there seem pretty based and of... I think they've got some legal battles going on with some regulators somewhere. So they seem to be up for a fight, which I tip my hat to.

Yeah. Very cool. I guess maybe they can do it as, like, cluster payments. You know? Maybe they could do something like that and say that it's it's, like, for fees because the fees are unmanageable at the moment. They've gotta do it that way.

Yeah. Maybe. But there... There's a little... Something in my notes there that made me think, give me a clue as to how they're doing it. It says, the first buy into an empty wallet is a normal transaction because,

obviously, you're kind of depositing to an empty account on the exchange sort of thing. Mhmm. So that leads me to believe maybe they're kind of keeping a wallet per customer. And then once you've got some funds in your account,

you've got fund... And and they're kinda classifying it as your pay joining with yourself, if you know what I mean. Right. I don't know. Maybe. I'm just I'm just guessing. I haven't read any Either way, it's good. On it. Yeah. Absolutely.

Next on the list, FinCEN and the Fed withdraw the $250 travel rule proposal. FinCEN and the Federal Reserve have withdrawn their October 2020 proposal to cut the record keeping and travel rule threshold for cross border transfers from 3,000 down to $250.

Okay. A move that would have written crypto explicitly into those rules. The $3,000 threshold stays and the agency say that any similar future proposal would need a fresh comment period. CoinCenter counts this as the latest in a run of withdrawals

after the December 2021 hosted wallet proposal and the October 2023 mixing proposal were both dropped in early October.

Yeah. A shred of good news? I guess. Yeah. You know, take what we can. Yeah. Absolutely. Next on the list. On the September 2, on chain investigator Zach XBT, great follow if you don't already follow him Yes. Flagged the theft of about $133,000,000 from Credit Mutel Arkea, a French bank using flows he spotted on public blockchains.

The bank did not confirm anything until two days later when it said the attackers had compromised the service provider, used the bank's own accounts to wire money to other banks, then converted it to crypto through exchanges.

Some of the converted funds have since been frozen, again, presumably because they've done it into stable coins, you silly, silly boys. Why? Why? Can I just set, like, final point on this? Sometimes I think that some of these hacks may be state sponsored, and that may be why they do this because

I can't imagine that someone is so inept at their job as a hacker to do that sort of stupid stuff. And I feel like by doing that, you you win in two ways. One, you make it look like an unsafe industry and one that must be regulated.

So you're gonna come in, you make it safe for people, which is what they like to do. And then secondly, it shows that stablecoins are much more useful and better than these other dirty cryptocurrencies because, oh, look, we can we can safely

stop the attackers, and we can get the money back. Isn't that better? So that's why maybe I would think, putting my conspiracy hat on that some of this shit is state sponsored Just to scare everyone and cause just unbelievable amounts of drama,

stop people wanting to self custody, stop people wanting to use cryptocurrency in general. And if they are, they use these ones that can be frozen by them, which are even worse than dollars because then they're just completely trackable, completely freezable Mhmm. Completely open book. It's even worse. So just a thought.

Yeah. I... The the thing I found interesting around this one is it's kind of like a reverse hack, so to speak. Like, it it goes in opposite direction than normal where they they they... The actual hack was entirely inside the banking system, and then they use crypto as the exit. Whereas normally,

you get a few million dollars worth of XRP, and you're like, what what am I gonna do with this crap? Let me get it into a stable coin or something so I can, like, actually spend it on stuff. And it seems like they've gone kinda the opposite way, but, obviously Yeah. True. It's just use Bitcoin people for fuck's sake. Yeah. Yeah.

Alright. Last one. Wrenches axe. A 23 year old crypto holder in France was targeted... One is fucked. This one is... This is this is the ultimate black pill. Oh my god. A crypt holder in France was targeted for the second time since 2022.

On the October 31, men tried to kidnap him at his father's home in Vendee, somewhere in France, and he fired a pistol at them. Good on you. On the November 4, he was sentenced to thirty months in prison and a fifteen year weapons ban because prosecutors said the attackers were already fleeing when he fired.

I'm sorry. Absolutely. I am sorry. Fucking. If you break into somebody's home to try and... Well, I don't even need to follow-up. If you break into somebody's home Yeah. All bets are off. Yeah.

It's Yeah. Especially when this person's... It's already... It's the second time. Yep. Yep. Yep. So it's the second time, and this poor cunt is like, right. Police are obviously gonna do fuck all to protect me. My information is out there probably because the tax authorities have sold it to the highest bidder.

And now I'm gonna try and protect myself. And so he's done that. He's done the job of the police because they can't fucking do it or actually just don't care about doing it. And then they've gone,

cheers doing our job there, mate. But what we're gonna have to do is put you in a cage for a few years and take away your ability to defend yourself going forward. What the fuck? Yeah. I I have a couple of follow ups here. Number one, I didn't know general public could own a weapon,

a gun in France. That's news to me. No. I think you can. You just have to have you have to have licenses. You can own guns in The UK as well. You just Well, yeah. Have licenses. Licenses. Yeah. Yeah.

And the the follow-up here says, in Russia, police reported on the November 3 the arrest of five men accused of picking a programmer as a target from photos of luxury cars on his social media.

They held him in a garage for five hours in September and forced him to send 10.4 BTC, which is around $800,000. Yeah. Don't flex online, people, if you're a credit holder. Definitely don't flex online.

But, yeah, I I just feel like that should be taken... I mean, there's no logic to any of this, but that should be taken into account. You've been held. You've had money stolen from you, presumably hasn't got it back. You've gone to protect yourself.

Like, that is just so unbelievably mental. Yep. And, you know, the... We've talked about it before. We need to do a show on, like, physical security in the Bitcoin world because even if you're not flexing and your information's out there, there's ways you can protect yourself

that... And that that put you in a cage, basically. You know, like, it... You're like, I wanna protect my family, so I'll get all the weapons. And like, okay. I don't care if they're legal or illegal because morally, I should be able to protect my family within my own home, obviously.

And then so you then do that and you successfully protect your family, and then you get put in a cage. And then how good are you at protecting your family from a cage? Not very. So there has to be ways to think about, like, simple simple basic stuff to make it very difficult for attackers to get you at home or elsewhere.

And it's just crazy that this has to be something we think about, but it definitely seems that as we go forward, it it has to be thought about. Mhmm. Yeah. Definitely. Right. Let's let's hit some boost. Let's get some positivity going.

We've had two weeks off, so I'm gonna... I've I've included everybody. Normally, we just do the top few, but I wanna wanna give back and get some positivity going. So top of the list, Bonesaw.

10,000 stats. Love and appreciate your work, gentlemen. Thank you very much, Bonesaw. It's a new name, actually. I've not heard of Bonesaw before. Bonesaw McGraw is the full name. Ah, okay. Yeah. Bonesaw McGraw. Yeah. Thank you very much. Appreciate you.

Lonely Pumpkins. Who knew hardware signers can be bought on Facebook marketplace? I'm I'm in the market for a parachute. Maybe I'll check there next. Keep on keeping it real, gents. Thank you, mate.

X patriotic with 0 point 01 x more, $6. Shout out to Seth for helping Fulcrum speed up 10 x on deep wallets. Yeah. We we covered that one on the last show a couple of weeks ago. He's he's putting those many clunkers to to good use, so thank you, sir. Certainly is.

Closed network with 15,000 stats says, because q and a is a Chad on x. Cheers, boys. I assume that's why we we get the stats, because you're just a Chad. Yeah. Promise that's not a sock puppet of mine. He's a Chad, but only on x. He's he's a useless come everywhere else. You're a Chad on x, though.

Next on the list, user 25498104. Presumably, your computer or you... Presumably, your computer you interface with Sparrow and your node should not be separate from... Should be separate from any computer you're running AI agents on, local AI or not.

Perhaps even a separate network sort of soft sandboxing. I mean, ultimately, separation is is the best way to...

Protect yourself? Yeah. Prove... For prevention, especially when you're talking about general purpose hardware like a laptop or something like that. And it's even more important if you're using Spyro as a hot wallet because, obviously, the funds are hot. You know, in that scenario, I would never do that.

Little bit less important if you just got, you know, a watch only for your passport on there or something like that, then maybe, you know, I probably would feel a bit more comfortable running a local AI agent. But, I mean, yeah, ultimately, that that sort of quote soft sandboxing

is is the best way to go about things. And if you're gonna be doing experimental shit with AI, be it local or not, then, yeah, doing so on its own machine is is the best way to do that or at least on a machine away from your Bitcoin.

Yeah. I was gonna say the other way around. I I would always think that just having a separate laptop or phone for anything to do with Bitcoin is not a bad shout. And then if you're using local AI, you want it you want it to have all the other access to all your other information because it's much more useful that way. So sandboxing

it that way around is probably the the best. Agreed.

Nakamoto sixty one zero two. You messed one. Sorry about that. User one two nine three one eight two five. Thanks for BitKey correction. Shows strong character. What was the BitKey correction? Yeah. So this was this was the user, like, two or three shows ago. I I erroneously said around BitKey

not having great privacy because they see all of your coins. And then that user called me out, corrected me, and then we... Corrected myself on the the follow-up show, and they were just thanking us for for the correction.

Good. So thank you for thanking us for our correction. Yeah. Thank you. Nakamoto $610.02, 1,000 sats. Appreciate the work. Appreciate you. Read with 333 sats says hashtag forty hours per week.

Rev Hoddle says essential hashtag forty hours per week with 329 We've got a catch up this week. We've had a couple of weeks off, so we've got a catch up for people with this forty hours per week stuff.

Silis Thornbrook, 210 sats. No message. Thank you, Silis. Nosdagang, a 101. And they said $849. That's like 2.4 passport price. What are we talking about this 849? Oh, is it that Motorola phone?

Must have been... No. I think it's even more than that, you know. I'm sure I'm sure I saw someone tweeting that it was like 12 or $1,400 or something crazy. Not that 849 is a phone.... As well, isn't it? Have you seen... Yeah. Alright. I don't know. I I kind of I kind of like the look. It's a bit different

rather than just everything looking exactly the same. I do like that things are measured, like value is now measured in passport primes, 2.4 passport primes. I think I think, like, if we have a basket of goods, like, rib eye steak, passport primes, and what else? Like,

maybe, like, a clawed subscriptions or something like that, would that give us a pretty good pretty good measure. Yeah. I'm scanning through our... The last show, and I can't see what we're talking about. It was $849.

I think it was that phone. I think it was that phone. I just think it's more than we thought. Yeah. It has come out. It's definitely more than that now, isn't it? Anyway, user 11694472. Pretty sure you can do phone, brackets blue and nunchuck, computer, brackets sparrow, and hardware as a multisig.

Wonder if Kate could add something to a cake wallet or cupcake to make multisig on a budget or if that's a bad idea. Yeah. No. I don't think it's a terrible idea to have... Where you have a mobile signer as one of the the keys in a multisig.

Yeah. I agree. I think it's actually... There's a lot to be said for that. Yeah. Last one, Max. I'll leave it to you. User one one six nine four four seven two said, have you seen Edison Motors?

Where are... They are... Were using more available parts to build diesel electric trucks. No. Diesel electric. What's a diesel electric? Like a Electric talk on the hill, diesel range in the bush.

I

don't know. Interesting. I'm not a big truck guy, to be honest. I don't know whether that makes sense. Generally, I think trucks and electric doesn't make a lot of sense, generally. But Yeah. I don't know.

I don't know. Like, I'm not completely poo pooing electric because we talk... You know, we talked a lot about the... That new Tesla thing. Although, you remember I said, would you go for the the Porsche or would you go for the Tesla? I sent you a little video of the Porsche. What... What's your option now now that you've seen it?

Oh, did you? You sent me a Yeah. I tagged... Oh, I tagged I tagged you in it just so that you could see and and hear. What's what's the model number? Let me pull it up. I didn't. I I don't remember it. What's it? I can't remember what it's called. The new Porsche, whatever it is called. I don't follow things that I can't afford.

Porsche nine six three? It might be that MissionX. Go... No. Go... Just go on... Just put new Porsche or something.

That's that it? I think so.

No. No. That looks electric. No. Go... Just just put, like, Newport. What other ones have they got? Nine six three. No. No.

Wish my brain works. No.

Let me let me see. New Porsche model. Maybe somebody can hit us in the comments quickly with it. No. I'll I'll find it.

Might be mission s.

Is it this one? Mission s. Mission s.

It's really nice. And it's all analog, like manual, proper analog, no screens. Oh, it looks like a nine one eight. Yeah. It's really fucking nice. Oh, do the dials actually do that where they pop out sideways? I think so. And and and manual.

And I think it's gonna be a flat eight. A flat eight? Yeah. They do a flat six, don't they? I think I think it's gonna be a flat... It's fucking cool. I do like that. That is... And it sounds sick as well. So it's like... It it... It's gonna sit above the nine eleven as, like, sort of super car,

you know, hyper car, super car. Visible fan wheel at the rear. Yeah. It's really nice. I like it. I like it. I'll

go with that over the Tesla even though it's gonna be less. Yeah. I mean, let... Let's be honest. Oh, I do like the interior. Yeah. That's nice. Yeah. Although it does look like it's just got an iPhone just propped on the middle of the dash. It's got something there, but they still sell it as a manual.

And it's just, like, very simple and clean and just non techy. I I do like. Yeah. I like. Let's go after Well, thank you to all the boosters for for pushing us towards a shared ownership on the new mission s. We'll we'll be putting our order in in 2048.

Yes. And looking forward to driving that. Right. Very quickly, let's just round out some of the release highlights. As always, there'll be a huge list of release notes for everything in the last week or so.

These are just a quick highlights. Electrum version four point eight point four, this is a security release, and the second one in two weeks

Separate from the malicious server fix in four point eight point three. This one closes the floor where anyone can send a malformed onion message and force Electron to disconnect from its lightning channel peer.

The wallet now drops incoming Onion messages entirely rather than processing them. The update also refuses channel announcements where both node IDs are the same and fixes restoring pre 2.0 seeds, had all been broken for a couple of versions.

Not a very exciting one, but if you are bizarrely still on an Electrum user in 2026, then make sure you're up to date. If not, you can the same Is thing that hit a lot of people... A lot of projects where, like, tour wasn't working because, like, a new Tor update stopped everything from working, like, a lot of the wallets and

bits and pieces weren't. Tor changed something, yeah, in their library, which broke a lot of shit, but I think this is separate. Okay. Because, yeah, that that Ashigaru wasn't running.

What else was I trying? There's a few different wallets and few different things that weren't running and weren't working. And I was like, what the fuck is going on here? And then it was like, oh, yeah. Because everyone has to now update to this thing, otherwise, it doesn't work.

Yeah. We we weren't hit with it with Envoy for some reason. That's why I never really paid it much attention. But I'm I'm I'm pretty sure it was something to do with, like, the tool network deprecating a a really old version. Yeah. And it keeps... Something like that. Yeah.

Cake wallet six point five point three been released. This one adds support for the BitBox o two Nova hardware wallet over Bluetooth on iPhone and iPad with a pairing code check along with built in BTC map and then other non bitcoin related support stuff.

Core lightning version 26 o 6.10 has been released. Third security release for the implementation in three weeks. This one fixes vulnerabilities reported from a number of sources covering dual funding, splicing, and signature checks on peers.

Once again, if you run a call lightning node, please make sure you're up to date and are mitigating by not having too many funds hot because it is a dangerous time to do so. And finally, Liana.

We haven't had a release for quite some time. Version 16 is out. Liana is a really cool self custody wallet that builds in time locked recovery paths using mini script so that you can do cool stuff with inheritance.

Version 16 shipped a couple of days ago alongside the matching Liana business two point o. Taproot is now the installer's recommended default. The encrypted descriptor backup, the file which holds the wallet setup

and needs to sit alongside the keys for any recovery, And it moves to the BIP one thirty eight format with a privacy mode so the files can be stored anywhere without revealing what it describes.

Also, labels now carry over from related addresses, coins, transactions, and the app adds French, Italian, Portuguese translations.

Oh, this is a breaking change, apparently. Opening a wallet in version 16 migrates its database. And once migrated, it cannot be opened in older versions. So make sure that you back up your wallet descriptor before upgrading because this is a one way migration.

Okay. Sorry? Are done. We are done. We are done indeed. Very nice. Before we cut off, just a reminder, we need to do local recordings as well as cloud. I've just worked it out the other day that we can do local. It's like a beta thing, but it is much higher quality.

And, like, with that one with John that we did on the Friday, which was just fucked on the cloud one and everywhere else, I luckily had turned on the local, and with a bit of editing and pissing around, it's now good. So it's just like a...

Which is due to hit the feeds tomorrow in case people are wondering where it is. Yeah? Yes. That's gonna hit. I just... I... There was no point in putting it out like it was because it just... It it was unusable.

It's fine. But with with the editing, it's gonna be good. Happy days. Alright. I am heading to Manchester late this week for Freedom Fest, and we're gonna be doing Freedom Tech Friday live from the the show in Manchester. We've got Derek Ross coming on to talk about Omaki.

Omaki? Omachi? Don't know how to say it. But that that new Linux distro that everybody's raving about. Now he's been building it for mobile. He's an avid vibe coder. I have not had two minutes to play with this. I'm really excited to to see what he's been building and to showcase. Yeah.

So looking forward to that. We'll be going live at the same time as always on Friday. And other than that, I hope you all have a wonderful week free from as many black pills as possible. Stay ungovernable.

Bye.