Are You on Radar?

Hello, and welcome back to Freedom Tech Friday, a weekly live and interactive show hosted on the ungovernable Misfits feeds. We go live for one hour every Friday at 9AM eastern and 2PM UK time, but you can of course catch up later on the podcast feed.

On Freedom Tech Friday, we like to cover the latest news and trends for anything relating to Freedom Technologies. That could be anything from Bitcoin or Monero, encrypted messengers, privacy tools, and everything in between.

Essentially, if there's a news item, tool, or topic that can help you take back some control in today's digital Panopticon, then we wanna talk about it. Name's Q and A, and I'm head of customer experience at Foundation. And as always, I am joined by my good friends Max, the head honcho of the ungovernable empire,

and Seth, who is COO over at Cakewallet. Freedom Tech Friday is a live and interactive show, and you can help steer the conversation by commenting live, pre submitting your questions, boosting the show, sending tips, or just sharing the show with your friends and family.

Top support for the last show with Derek Cross comes from it wasn't with Derek Cross at all. I've done it again. I've scuppered myself with my own notes. It was with Shadrach talking about Archipelago, was a great show. Please go back and listen to it if you haven't done so already.

Top support for that show comes from user two five four nine eight one zero four at fountain dot f m. You should probably get yourself a proper username. They sent 2,100 taps, and they said that they cannot wait to try it. Yeah, me too. Gonna be keeping a close eye on that project

to look for when that alpha release is ready and available for everybody else. So thank you for your support, you are. Without further ado, I'm gonna bring on my lovely co hosts and say hello to Max and Seth. How are you both doing, guys?

Did we get Max back? I think we did. I'll get back. Back in again. Yeah. There we go. He heard you mess up what the last show was, and he just he alt that forward. He was like, fuck this. I'm out. Yeah. Last time. Last time. Yeah. That's it. Yeah. I'm good, mate. I'm excited to have our amazing guest on today.

Excited to hear what he has to say. Wait. We have a guest this week? Yeah. A very, very special guest. Oh. Surprise.

Oh, it's good to be here. Good to be here, guys. Thank you all for handling this. I also just wanna, like before we get anything else, I just wanna give a shout out to to Q, to Max, and to Jordan.

I'm the lazy asshole who doesn't do a lot of the work during the week for this show. We did say that. So Oh, well, okay. As long as y'all have already told people, but I just the the work they put in throughout the week, gathering questions, working on show notes, dropping up guests, all of that, just,

yeah. They're doing absolutely amazing stuff. So I wanted to give them a shout out before we went went any further. All that went behind the scenes. And I wanted to pre apologize because I know you're getting a really high quality feed of a really stuffy, sick sounding voice.

So, yeah, I apologize for that. I'm doing everything I can, but, unfortunately, it was one of those weeks. One of those weeks. We we've got a max. So we're we're used to people being ill on the show. A max.

I haven't been ill for ages, mate. I've I've only had minor little sniffles and snuffles. I've been I've been pretty good. Mentally ill, physically strong. Glad to hear it. Well,

yeah, I I'm guessing, Seth, your your illness is partially driven by the kids, I'd imagine, and partially driven by the the very, very, very quiet week I'm sure you've had, which is why we're here today. For those of you that are living under a rock or don't have social media and have no idea what we're talking about today,

This week, we are gonna be digging into something that landed just a couple of days ago. It seems to have got the whole space talking. Everybody's very, excited about it, myself included.

It's a new app and it is quite literally feed and tech right down to its bones. It takes two of the things that the three of us bang on about constantly on the show and brings them together in a way that people have been asking for quite literally for years.

I could sit here and try and explain it to you, but I'm I'm only gonna do it half justice. And importantly, I'd be stepping on the toes of the man who actually or who is actually the perfect person to break this one down. That's the sickly one in the corner. Because this app that we're gonna be talking about called Radar is

from a team that Seth knows very, very well. We're gonna get into all that. So this is less a case of us reviewing something from the outside and more getting the the the alpha from the man himself, the man who who's the head honcho, driving the force to to actually build the application itself.

So here's what I'm gonna tease. And no more than that because I don't wanna steal Seth's thunder. But if you've ever felt the friction of doing one simple thing on the internet and had to bounce and see multiple apps, jump through multiple hoops, and give up a little bit of your privacy or sovereignty or sanity along the way,

then this is gonna be a show for you to pay attention to. I'm gonna zip it there, hand over to Seth. Floor is yours, sir. You've got this new thing called Radar Chat. What the hell is it?

We do. Yeah. Thank you for the intro, man. Long story short well, I'll I'll start with the the long story. So for a very long time, I mean, we've been playing around with the idea of a messenger in general.

Vic, obviously, he's a he's a serial entrepreneur. He's always coming up with ideas, and he had some stuff he wanted to do with Signal anyways. So we had we had forged Signal. We had started to build in some other features around it, work on a quality of life stuff.

And then in the process of us actually deploying lightning to cake using Spark as we talked about, which we deployed five months ago now, we just started to realize there was an easy combination here that we just had not seen anyone else think of. Like, the idea behind RADAR is not that complex.

I think, like, part of the the focus in the the video that we used at launch was that it's just not it's it's an idea you would have expected someone else to think of and have done sooner, and yet

no one had. So the idea in radar is really we've always had these two separate things where we have our private chat apps. We have really good apps like Signal. We have really good apps like Simplex, Session.

We have lots of choices when it comes to private messaging, and we have really good choices when it comes to self custodial Bitcoin. We have Envoy. We have Cake Wallet. We have Phoenix.

But those things never lived in the same place. And while it doesn't seem like too big of a headache, the the process of always having to go back and forth to pay the people that you're already chatting with, the people you're most likely to be paying anyways, the friends, family,

that person at the the farmer's market you're always buying from every week. We wanted to just combine those two, but without having without having to make you restart your network over. Because that was another big pain point that comes with messengers normally is,

like, let's say you pick up a new messenger, you love the feature set, but are you able to actually convince all of your friends and family to move to it, to to add another messenger app, to jump on it and actually start using it. That's always the hardest part.

So in that process of both getting really familiar with how to do Lightning in a a user friendly way and how successful that was, like, smoothly that launch went and how how well the adoption and the uptake went on Lightning and Cake, it just became clear that we could

we could combine the best of Signal and the best of Bitcoin Lightning into something that would let you actually be able to

to send value where you're already sending messages, to to not have to have a an entirely new network, to not have to deal with a separate wallet app that adds complications, but to build something that was just absolutely

stupid simple from the ground up. We don't want it to be complex. Even when we demo it, you'll see there's not that much I can demo for you, which is very intentional because we don't want it to be this, like, fully featured, complex,

advanced wallet. We want it to be something where it just feels like I have a home for sending and receiving value in my chats, and that's the the basics there. But, yeah, it's been it's been a long time coming. Probably the last

eight months or so, maybe a little bit more than that now at this point that we've been figuring out exactly what this looks like, figuring out what the UX should look like, finding out how to make it ride along the the rails that already exist within signals protocol and network, all of that fun stuff.

Awesome. Yeah. It was a a pleasant sight to see when you you sent me the the tester app and was very, very excited by it. It did make me think actually. Probably around about a year ago, there was an effort that started called Bitcoin for Signal.

Is there any tie in here? Was that the impetus for for you guys to to, like, get started and and and start turning, you know, the the software engine, so to speak, or are the two completely, you know, not related?

It's definitely connected a bit. I mean, like, it was a good it was a good proof that there was interest in the idea, which is always really important when you're building a new company to to be sure that there is actually demand for this thing.

So as as is, as is normal, I'm always a little bit of a slow adopter. Like, I'm a little bit more cautious when it comes to new things. So Vic and I chatted about this a lot. And at first, was like, I don't know about the idea. I don't know if it'll be worth it. Like, why use signals network? What's the

what's the pros and cons here? And, initially, I wasn't quite sure on the idea. And then it really was when I was going back and kinda doing more product research to see, like, what the fit would be like, what the adoption could be like,

what the addressable market is, like, all the stuff you're you're doing when you're starting a company from scratch. And I I was reminded of that campaign. I definitely had remembered it. It had been a long time, though. I think it was maybe even a little more than a year ago now that that campaign happened.

But it was really fascinating one because it was essentially Bitcoiners trying to ask Signal themselves to add Bitcoin into the primary Signal clients. I think the main problem was, and, I may or may not have gotten blocked by Cali because of a meme that I posted, during that campaign, but

the the impetus was we want Signal to add specifically Cashew, eCash into Signal for Bitcoin. So if you go look at at the actual reference apps that they built or at the the website that they made, it was all about eCash, which is understandable from the privacy perspective. Like, obviously, Signal has

absolutely fantastic privacy for the messaging side, so I can understand wanting to match that with the privacy on the financial side. But, obviously, the custody is the issue there. And the the core ask of Signal for of Bitcoin for Signal was we want Signal to become a custodian or find someone else who will be a custodian

for their users' money. And with the regulatory headwinds that Signal already faces, there was just no way that was ever gonna happen. And I think that's why you saw literally nothing, like, no response or anything like that from Signal themselves.

But the idea was sound, and it was crazy the amount of reach and engagement and interest that there was from the Bitcoin community and and broader to get this sort of thing out there. So it wasn't necessarily the start of the idea, but it was, one of those, like, the clearest confirmations of there is huge demand for this.

But it needs to be done in a way that would be self custodial. Because, obviously, we also, like, starting from Cake Wallet Radar itself is a new company,

but starting from CakeWallet and having a lot of the CakeWallet team being the ones actually building this out and specking it out, obviously, we weren't going to become custodians to do this either, and we didn't wanna trust some other custodian with our users' money at the same time.

So wanted to do it in a way that was self custodial or noncustodial, depending on how you wanna, how you want to semantically name, Spark. And that's kinda where we we settled on that.

But, yeah, it was it was such a fascinating campaign, and we really, like, we enjoyed the fact that there was already clarity on demand for this, even from people as high profile as as Jack and others.

Awesome. And before we go into, like, the the mechanics of kind of, you know, how you've achieved the the self custody side of it, which is, you know, obviously something that's important to to us and and to the listeners.

You mentioned around, you know, it's it's essentially, you know, a a built on top of the the groundwork that Signal have done. It's a fork of their project. Obviously, that brings with it what did you say? Like, a 100,000,000

users or something like that? Or Yeah. Over a 100,000,000 monthly active users. Maybe a 150,000,000 now. I'm I'm not sure the the latest number, but it was north of a 100,000,000 when I was last digging into it. Yeah. I mean, arguably, of the the most successful projects or or companies under the the Freedom Tech umbrella. Right?

Where I'm going with this is, you know, obviously, that's probably the the the the main draw was being able to tap into that kind of user base. But was there was there anything else that made you guys want to build on top of what Signal had already done versus

doing something from scratch, which, yes, probably would have been a lot more work, but you would have been able to do things your own way. Like, what was the the decisions along that way? What did they look like?

Yeah. So we definitely thought about both. I think the obviously, like you mentioned, the draw of jumping into it on Cygnus Protocol, part of it is just you don't have to start from scratch as a company either. Like, you're not you're not needing users to

create new accounts, at least in the tier one audience that you're gonna be focused on, and they can continue to message people who they maybe can't send Bitcoin to in radar. So, like, if you switch to radar right now,

maybe your friends and family aren't switching right away, but you can still message them, and you don't have to do anything different to be able to do that. So you don't have to convince them to switch apps just to be able to chat, and then you can slowly get them to move over when you want to start sending

sending sets to them through the Bitcoin side of radar. I mean, the other really nice thing too is, like, I know Signal gets a lot of hate for some of the choices they've made, specifically, like, the phone number requirement.

And it's I know it's not ideal from an anonymity perspective, but they they they make the choices they make for a reason. I think there's a there's a there's a real reason why they are by far the largest messenger out there because they focused on that blend of

essentially perfect messaging and metadata level privacy or at least as as close to it as you can get with a simple and approachable UX. And part of that comes with the phone number requirement, which is something that everyone is used to. Everyone has a phone number.

When you're talking to normies, that's just totally above board, and it is a a huge limiter in terms of spam. So it helps them to keep their network relatively spam free at the same time.

Yeah. Go ahead. Just while we're on that, Seth, I was thinking about this, and I was wondering if you had any advice for people who you know, a lot of people who listen to the show are more on the hardcore side of how they care about their privacy than most people.

So if someone wanted to have a play around with this and maybe they already have, like, a a family chat and a signal that they use on their personal phone, but they're thinking, well, actually, this could be quite useful to use, like, with my Bitcoin friends. Is there a good way

or a suggested way to get the phone number, like, maybe something like silent link? Is there any other, like, clever ways to not get around, but do the best with the system that you have because you have to put a phone number. You have to have something.

How do you best protect your privacy while using it? Yeah. It it used to be a silent link that used to be my suggestion, but they actually don't do the the simple keep SMS only verification plan anymore.

Right. They shut that down a long time ago. So normally, my go to now is cloaked wireless, who you can Okay. You can pay for with Bitcoin, Lightning, Monero, a bunch of other things. Mhmm. You don't have to give over ID or anything like that. You fill out whatever you want in the address field, the ZIP code, the area code, etcetera,

and you get a a permanent line with limited data, but a phone number that you control. It's not the cheapest is the main downside. I believe the lowest plan is 20 or $25 a month. Okay. So it's I I would hope to see that come down. Like, there's just so much need for a persistent verification

number, which is really how I view Secure SMS. Like, no one's using that for texting their friends. Like, it's the the whole point of that really is you want an an a relatively anonymous private line that you can use for your verification of all your public stuff.

Because, like, even when I'm like, this is also super useful. Like, use it for your Telegram. Use it for your Twitter. Like, anywhere that you're using your NIM, you can use a phone number like this. And there are a lot of services that require a phone number to be able to use fully.

And you can do that without actually linking your ID or your home address or your real name or anything like that if you do use Cloaked. That's brilliant. Just one question on that then Yeah. Before we go too off topic is does that then work globally, or is that just like a US based system?

Like, if you need to sometimes you have to, respond back to a message. Sometimes they just send you a code. Can you use that in any country if you're traveling around, or is it, like, US only?

I believe it is US based. I think you could get the SMSs anywhere. I mean, it is gonna be a it's a US number and everything, but, yeah, I think you could get you could actually receive the SMS anywhere. Okay.

Alright. I won't get any more off I won't get us any more off topic. Just a thought, and I might have a play around with that then. Yeah. I can vouch for the Cloak wireless. We've worked with them before at Foundation. Good team behind them and, yeah, very well aligned as well.

Seth, wanna take us back to the self custody aspect of this? That kind of been easy to do that, and that was one of the main sticking points of why somebody hasn't thrown, you know, lightning into a a a chat app until now.

What have you built upon? How have you achieved it? What does that look like from a user perspective? Because it seems like a a huge win. Yeah. I mean, here, we just we leaned on what we already know. So like I mentioned, we we've already deployed Lightning to our almost 2,000,000 downloads.

We've had over 500,000 people create custom Lightning usernames and cake. Like, we've we're already familiar with this, and we saw how how useful and, like, easy it was from just the dev experience perspective and the user experience.

So we we didn't wanna reinvent the wheel here. Obviously, we've thought a lot about ARC as well, and I've been closely following the work by Second, especially, and what they've been doing recently on the ARC side of things, but

we just wanted to stick with what we know. So that was the easiest way to also get up to speed in terms of a a proof of concept, something that we could all start running internally and start playing around with.

So we we shipped it using the the Breeze SDK for Spark for the Lightning perspective, which, as we talked about many times on the show, has a, I think, a a good trust model, not trustless.

I would say trust minimized, and brings with it the the fantastic user experience of not having to deal with channel liquidity. So I don't have to open a channel or have inbound liquidity or anything like that to receive my first stats. I can top up my wallet

the moment I log in to RADAR from Lightning and immediately be able to spend and not have any other problems like that. And user to user within RADAR, you're actually doing Spark to Spark payments.

And then when you wanna ever receive or send, externally, that's when you're actually leveraging the Lightning Network as well. So, honestly, quite straightforward. Like, it's it's something that's already a known quantity, and it fit very well within this

within this use case because it needed to feel the same as on chain Bitcoin but faster. Like, that's that's really what the the vibe needed to be. That's what Signal retargeting when they launched MobileCoin.

Maybe we can talk a little bit about that as well. But the the idea is you need something that feels instant, that lets people send and receive it right away. But the huge, huge, huge benefit, obviously, of using Bitcoin over something like MobileCoin is there's already a massive part of the world that has Bitcoin.

And if you already have Bitcoin, you can just send it straight into Radar, and you're off to the races. You don't need to do anything else. Obviously, if you don't have Bitcoin, you can you can buy it not yet in app. That's gonna be a next next phase where you'll able to buy it directly within the app,

or send in other cryptocurrencies and have them convert it into Bitcoin. But that was a a huge piece of this to make it something that's very, very accessible. The other thing that we like about Spark and that will lean on more in the future is the ability to support stablecoins.

We see this being something like radar being something that's our our end goal is not just Bitcoiners who already use signal as the target audience. Our end goal is people who want a private messenger and want to be able to send value, people who want to be able to handle remittances, people who want to be able to

to fund journalists and dissidents, People who are, like, fighting back the HRF is a perfect example of an org where I think the the people who they work with are an excellent fit for something like Radar.

And we understand that most of those people right now are relying and prefer stablecoins. So we do want the ability to provide a stable balance, to users, and so that's something that Spark also enables us to do already. We don't have that live in radar yet intentionally,

but that is something that we we do like about the system is we could easily deploy that at the same time down the line. Awesome. So presumably from a user perspective here, to go with all that simplicity, there is still some responsibility because it is self custody.

Like, I'm guessing they have a c phrase to to back up. Are they presented with that? What does that piece look like? Yeah. So there is still obviously a seed phrase under the hood. For most users,

technically, they don't have to back up the seed phrase. So something really cool is that we can actually back up the private keys with your signal account in an encrypted way so that only someone who can actually log in to your signal account on a new device could access that those private keys,

which is I know it's a very it's a different trust model than a normal hot wallet. Like, obviously, pushing your keys into to, quote, unquote, the cloud is something that some people are a little bit scared of, but is becoming more and more common. I know Envoy with magic backups

leans into that some way, and that's something we're gonna be doing with K qual as well soon where it's an option for entry level users. And especially for people who, again, are not hardcore Bitcoiners, I think it's a really good fit where if your signal account is pwned, that also means someone has your phone number

and the PIN code to your signal account, and now they have access to all of your chats, and they can message anybody pretending to be you. Like, you have bigger problems than your 50,000 sats or whatever. We're in your radar wallet.

And it gives you that experience where when you log into a new device,

all of your sats are just immediately there. You don't have to do anything. You don't have to think about it or, like, oh, oh, I need to log in, and then, oh, I need to find that seed phrase that I wrote down. You don't have to worry about any of that. So for the the normal user, you don't really have to think about that.

Obviously, though, we want to expose that to users for a secondary backup method. So when you do receive funds for the first time, you'll see on the payment screen a prompt that, tells you to back up your seed phrase, normal 12 word seed phrase, back it up, verify it. Nothing too crazy there.

And that seed phrase, because we're a Spark compatible wallet, it'll work in any other Spark compatible wallet. So Wallace Futoshi, Blink, Cake Wallet,

more and more every day are supporting that, and you could import it there and have all of your sets with you at the same time. The other benefit of that is, like, if you already have a a Lightning wallet and, like, Cake Wallet that you want to also use in RADAR,

so you don't have to manage two different wallets and two different seeds and all of that, is you can import an existing, seed phrase from another Spark compatible wallet

and use that. So you could just have one wallet that you use for all of your hot wallet stuff, and it has the same balance in radar somewhere else. It's it's up to you, of course, but that's the the core way that we've approached it. Try to make it really easy for the the users who are not super Bitcoin native.

But then as you use it more, you do get that prompt to back it up and have the seed phrase just in case so you could recover if something were to happen with your Signal account as well. That's very cool. Something just popped into my head when you're talking about that around how, like, that

cake wallet and I've got radar, and they both got two independent wallets currently. And you mentioned around having them both the same the same wallet, essentially. Would that then mean that I would have my cake. Cash handle and my radar. Chat handle both working and both pointing to the same wallet and both be fully functional?

That is a great question. I believe so.

Maybe we can pull back on next week. Yeah. I haven't actually tried that yet, but it should be possible. I know that we can't just a restriction of the Braze SDK, we can't do multiple in one wallet.

So, like, we can't show you or, like, reveal to you the at kick the cache and the other one at the same time.

But they should both work at the same time if you have them in GAKE and in RADAR at the same time with the same seed phrase, theoretically. There's there's not a limitation on, like, the LNURL side or anything like that to limit it.

That is a good question. And for somebody like me that's already set up and got a few stats in in the new radar chat wallet, can I erase that wallet and then import my my cake wallet wallet without having to, like, re like, touch anything to do with, like, the signal side of it, the messaging side of things?

Yeah. You definitely can. So if you go to the the payments tab and maybe this is a chance for me to just start demoing a little bit. Oh, I can see it now. Yeah. Delete payment wallet. Yeah. Here. Let me see if I can pull this up. Cool.

And then before you dive fully into the the demo, which I'm bringing up right now, I do have one more question that will set us up quite nicely. Yeah. Yeah. I'll just really quickly show you.

Obviously, we'll kinda block this out here and there. But, yeah, if you go into your payments tab, you get all of the the normal settings, things that you can change, lightning logs where if you run into an issue, can reach out to us, and we'll help you out.

You can see your recovery phrase there and back it up if you want to. All the normal stuff you're used to in a Bitcoin wallet, obviously, we keep this really limited. Like, there's not a lot of configuration here because, again, this the target is not where another Bitcoin wallet.

The target is how simply can we enable someone to use Bitcoin to send a received value.

So not getting into complex things here. But yeah. So I can delete the payment wallet if I want to, like, import a new one or I've maybe if I just don't even wanna use payments or something like that, or I can deactivate payments, the the tool entirely.

Normally, it would be delete payment wallet and then start fresh. The one thing that I will call out, and I know one person who's already run into this, if you are going to delete this wallet, but if you've already set a username, like, I think I have actually lost mine by doing this so far.

Oh, no. Nice. Okay. It's available. So, like, if you have already claimed a username here,

make sure that you change it before you delete payment wallet because usernames are tied not to your Signal account but to the actual seed phrase there. So if you if you have like, if you had q and a at radar. Cache and then you delete payment wallet and you put another seed, you're not gonna be able to do q and a radar.

Cache because you you have it on another wallet at that time. So just an important thing to call out. If you don't wanna use the default wallet that's gets created for you when you get into Radar, you'll wanna make sure that you don't have a custom username set there that you want to reuse.

Awesome. That's great. I mean, I was, as you know, I I was one of the few users that managed to to find a little bug in the early

release. And I was pretty pretty sad because I wanted to rush on there and and lock down qrradar.cache.

And when I did get in, thank you for for helping me with that, by the way, I was very happy to see that nobody had stole it. So happy to get one of those one letter ones. I I thought you were gonna, like, block those or maybe charge some sats for them or something like that. But when I tried it, was like, oh, nice. It works.

Just for you. Just for you. Everyone else pays a million sats for the the one letter handles. Privilege. Privilege. Yeah. Before we we dive into the the the demo, access. Where can people get it? There's been a couple of questions pop through around, like, F Droid and Zap Store desktop.

Walk us through that. Yeah. So right now, technically, it's live on the App Store Apple App Store. Google Play is coming, but holy shit. Google are being a pain in the ass with this. We it's been two weeks since we submitted the production version.

And normally, Google are the really fast ones, and they have just been absolute nightmare here. Yeah. I was gonna say, on the Google Play Store. Around. Right? I know. I know. We we were shocked. Like,

I I did not expect Google to be the problem. We submitted super early anyways just to make sure. Like, we we made sure that we would have plenty of time and still wasn't enough time. So we're still in the process of getting through the Google Play Store review. So it's not live on the Play Store yet, which means it won't be live on

man, I'm blanking. What's the Aurora, yet either? It is live on GitHub. Obviously, we'll keep pushing releases there so you can get it via Obtainium or any other tool that pulls from GitHub or download it manually there at the same time, for those on Android.

I would expect we would launch it on our just a custom f droid repo just like we do with k wallet as well.

And a crescent on Zap Store, I think it's there just automatically pulling from GitHub, but I need to double check on that. Our focus more was getting it in the main app stores for the launch rather than the the side smaller ones outside of just GitHub to enable Obtanium.

But, obviously, we will roll out to those those alternate stores. They're just all a little bit different and tricky and add a lot of time to the deployment process. So they're they're something we are definitely working on.

So you can download it with an APK anyway, like, what from Cake website or not, if you if you're Android? From from yeah. Just from the GitHub. It's linked. If you go to radar.chat/install,

you'll see the the APK download link. It'll just take you to the latest GitHub release, and you download it from there. There's also in the Android repo, there's a one tap button to add it to Obtainium with all the right info as well. Okay.

So Obtainium is normally the best way. Like, honestly, those wanting F Droid or a Crest Hunter's App Store or whatever, like, just just use Optaneum. Just pull it from GitHub. It's gonna be way easier and more foolproof and have less problems.

But we will look to add it to those other alternate app stores as we can along the way. But, yeah, Android Avocade is available right now. Just before we move on to the demo, Rips on Twitter has has asked about the the username saying, couldn't somebody theoretically,

like, create a load of wallets and burn a ton of usernames? I I guess the short answer is yes. Yeah. I mean, the only the only way to limit that would be if we made people pay for usernames.

But the then there's obviously the friction and downside of somebody who's new and doesn't have Bitcoin right out of the gate. They won't be able to set that username until they do, and they can pay for it. So, obviously, there's pros and cons of each. I know that's why, like, Wallace Satoshi and others often

gate the custom usernames behind behind a payment. But I think just even like you've seen with Signal usernames,

I don't think it really matters. Like, if you if you can customize it slightly to make it work for you, it's gonna work. And I haven't seen anybody really having problems getting the ones that they want so far with cake wallet, even though we've had, like, more than half a million of those set so far.

But, yeah, it is the downside of making them just freely available and you letting you change every time. But, I mean, if you wanted to spam it, you'd you'd have to create a new seed, import that new seed into radar every time, pick a username, and then you have to save the seed with the username and do that programmatically,

which is possible, but it's not easy. It's not like you can just do that from command line or something like that. So, I'm not too worried about it. Cool. Alright. I'll, show us how it looks, mate.

Yeah. Let's trim it to it. Let me screen share that quick. Is this the part where I get free money? It is. Oh, lucky me.

There we go. Okay. So yeah. I mean, very straightforward. Like I said, like, the goal here is not to be stupid complex. So when you go into the payment screen, you you have very simple controls. You can send. Normally, this is sending to other signal contacts, but you can paste in invoices or, LNURL,

Lightning addresses, that sort of thing. Right here, when you wanna send external, beauty of Spark and Arc and all of those is they're fully Lightning compatible, so you can send out to any Lightning wallet.

No restrictions, low fees. It's it's quite beautiful.

Also, obviously, you can add funds. So for people initially topping this up, I know we will long term let you, like, buy Bitcoin with a with debit card, Apple Pay, Google Pay, all that fun stuff. But right now, the best way is just go ahead and send in Bitcoin from a wallet you already have. So, again, super simple.

Copy that. You get an invoice here. If you if you need an invoice, you can scan that. If you can use the Lightning domain, you can just use your at radar. Cash handle. Go and send in funds.

Super simple. You can see an example here of I topped up my radar wallet to have some more for demos and sending to people. This is just sent from Cakewallet. Took two seconds. Super straightforward.

When it comes to actual payments in chat, again, intentionally very, very simple. So when I'm when I'm chatting with Q and I want to go ahead and pay him back for coffee, I just chatting with him normally, and then I tap the Bitcoin button, put in how many stats I want to do or dollars. Let's just say I'm gonna do do $5.

And then send. Confirm it if I want. There is a slight fee. It's two to three sets for every payment on Spark, but it's very, very minimal and doesn't grow with the amount of the payment itself.

Unlike Lightning, when you are paying outside to a Lightning invoice, obviously, you have to pay routing fees. But that's that's pretty much it. Obviously, you can pay me back if you want to, really. Yeah. I see that on my side already, like, instantly. As soon as press hit send, like, it was, like, one to two seconds.

Do you mind sending me back just a simple payment just so I can see what that looks like as well? Yes. Absolutely. So I hit the Bitcoin icon. I am gonna send you 7,786. That's the exact same amount. And I'm gonna say, you're welcome.

I am gonna hit send. I'm going to check the details and then hit pay processing, and it has gone. Oh.

It's Oh. Always like when you do demo. Come on, mate. Never seen that in my life. It shows a set on my side. What the hell? K. I did I did get it. There you go. Life Interesting. Is that because they're dirty sats, unavailable? He must be blacklisted. Yeah. I forgot that we blacklisted. You go. Well, that's what I can see on my side.

Yep. That is what it normally looks like. I not gonna lie in sending thousands of payments. I have literally never seen this. So that's that's demo live demos for you. Okay. But you got them. Yeah. It's so private, though, that I don't even know how much I've got.

I I just tried the smaller amount. Got it. Can't make this up. Okay. So there you go. Well, the the important part is that the money is in your your account. I do have some amount of money. Yes.

Yeah. So you can see it's it's showing up here. I'm I'm wondering. I'm on the test flight, and we have a internal testing build that just got pushed this morning. So I'm wondering if there's something broken with that. But, obviously, push that to life. Think I'm on the test flight build as well. Yeah. So that might be it.

Okay. Let's blame it on that. Yeah. We'll pretend this is what it looks like. Okay, guys? Just like this. Just like this. But, yeah, I mean, like I said, the the goal here is not complexity, is not super feature rich, is not overwhelming things. It's how straightforward and how simple can we make this.

And that's that's pretty much what it is. That's that's what I I really like about this is for onboarding people and getting them using Bitcoin. It's like, especially for people who have never used it, the fact that it's built on signal,

that it's as simple as it is. I can kind of imagine, like, speaking to one of my family members and being like, change them on there and just say, send them some money for a coffee or send send them something across, and they can see how simple and seamless it is as long as Q's not sending them money. And it gets them

into that ecosystem of like, oh, this is actually a lot simpler than a bank. And once they start to use it and feel that, it's much more powerful than, like, sitting down and doing a PowerPoint presentation

about what is money and, like, why they should care about this Bitcoin thing because no one gives a fuck. But actually seeing it and using it like this is is like the lowest lift possible way.

And then for people all around the world to be able to do it, it's it's clever. It's like it's like the best marketing for Bitcoin I've seen. Yeah. And that's that's definitely the view that we have is I think this is a a perfect orange pilling tool where we can show people how useful it is and how good it is to use,

and then we can explain why it should be something that changes the way that they think about money. Like but not starting with the philosophical. Start with the,

hey. It's literally this easy for me to send this to you. And did you have to create an account? No. Did you have to give up your ID? No. Did you have to link your bank account? No. It's all right there. You get the money instantly, and it is 100% yours.

And that's a a huge a huge way to show people this is something that actually works today. It's not like a pipe dream or something that just may happen someday. It's actually it's actually doable.

Just just one thought on that. Again, I don't wanna derail it too much, but let's say I sent some stats to a family member. Almost certainly, the first thing they're gonna be be asking is, well, what do I do with this now then? Like, how do I spend this then?

Would it be an idea to have a way to be, like like, a spend button or something like that where they could get gift cards through cake or get redirected so they can start to see that

because when I've sent sats to people and set them up with wallets, and they just go, oh, what do I do with this now? I can't spend it anywhere. I can't spend it at Tesco. And I'm like, yeah. I fucking know that. And to do the extra jumps is too much for them. So I just wonder if there's, like, a simple,

yeah, way that they can spend and buy gift cards and do that kind of stuff. Yeah. It's a good idea. I'll definitely have to think about how that could fit in there. I mean, I think part of it is within a system like this. Like, sometimes the money can just move around within radar. Like, you you need to send you send me money for coffee.

I go have lunch with Q. I need to split a bill with him. So a lot of it, it it gains value and use from a social payments perspective without having to actually leave the system. It's just like for it it just it does for someone like you or me or q.

It doesn't for, like, my sister who doesn't give a fuck about Bitcoin, who's only the only person she speaks to about Bitcoin is her annoying brother, and then, like, none of her mates care.

So it it, like, it brings someone who isn't involved in Bitcoin and makes them understand that it has value, and therefore, we're more likely to have more people understand the value, if you see what I mean. Because we're in a weird echo chamber of, like, people who actually use it.

Yeah. It's true. I mean, again, part of the vision is that the people using this are not just Bitcoiners. So they just see that there's Yeah. There's money that they can then send to their other friend who's also on this platform. Yeah. But, yeah, especially early on when it is mostly Us Us hardcore Bitcoiners who are jumping on here.

It'll be a little bit limited. That's where, like, being able to withdraw to a debit card or something using all frames, I think, will be a good addition. Mhmm. Cake Pay is an interesting idea. I'll have to see how we could do that, because, obviously, I wouldn't want it to be as complicated probably as Cake Pay. But

simplifying it down and letting people choose some things for off off ramping through gift cards and debit cards would be interesting. Yeah. Okay. Bon in the chat is asking, do payments have iOS or Android native notifications?

They do not right now. I mean, you'll see them, obviously, when you open the app. And let me see. Yeah. You'll have them at the top of your screen when they when you open the app, but we don't we don't do the notifications when they actually happen right now.

That's something we we can do and have thought about. I mean, I guess there's not a downside to it, but it doesn't like, normally, again, this is something that would be social and not a wallet where you're just, like, randomly receiving payments with no no message comment or anything.

So if there's a a message associated, you're going to get that message. If they're if they type and say, hey. Here's that money from last night, you're gonna get all that. So but, yeah, should we should figure out getting payment info in there in a clean a clean way.

Awesome. BTC pleb in the chat is looks like he might have had the same issue as me. Where should we send him for for support, or is it just wait for the next release? Yeah. I'm not sure what the problem would be there. Obviously, it depends on where they are. I've I have heard that some

signal is a little picky about some places where it sends the SMS verification. So if you are using SMS verification and not the not the other, like, registration lock PIN code part of things, maybe that would be it.

As far as I know, there's no issue with logging in, though. But one thing I do wanna call out that I think has not been super clear to people is, like, this would replace Signal for you if you're using the same account.

You can't be logged into your Signal account in both the Signal app and the Radar app. You need to choose one or the other. Or like we talked about earlier, create a second account with a second, phone number for verification

to be able to use it. So just a, yeah, call out there. That's a good call out. And and just quickly, I do wanna leave time for the pre submit question because we've had quite a lot. But what why is that? What drives that that that we can't have signal and radar running concurrently on the the same phone?

So, I mean, it's it's a signal requirement where they only let you have basically, like, one master device, for lack of a better term, where

your account is primarily logged into, and then you can link other devices. So you actually you can use RADAR as a linked device. There's been a little bit of a problem with that we're we're working through right now.

So you could use it as a linked device, but it won't work quite as well as if you use it as your primary.

Yeah. That's pretty much all there is to it is you can only be, like, properly logged in to your Signal account on one device, and then you can have other linked devices. Linked devices are normally what you'd use for, like, the desktop apps to be able to get notifications and send messages on your desktop or an iPad, something like that.

But just like with your main Signal account, you're not actually logged in to Signal on multiple devices. You could only be logged in on one device at a time, and then you can link other devices as you see fit. You can also link devices with RADAR. I know, Keith, you already did that with desktop apps. Mhmm.

They were testing that the other day. I've been been using the desktop the main signal desktop app as a linked device to RADAR for months now as well. But, yeah, it's just a a limitation of of signal.

I apologies if you have already covered this, but briefly, have you guys got plans of desktop app of your own?

So we're looking into it for sure. I mean, the the nice thing right now is just for the messages side, you don't need a separate, like, custom radar app. For payments, Signal, as far as I can tell in initial digging,

they haven't they they intended the desktop apps, basically, linked devices to not be able to handle payments. They only want the master device to be able to handle payments. So we'll have to see about working around that. I mean, the, like, the the app that we already have technically does work on macOS.

We intentionally don't deploy it there because not not really made for that. But desktop apps is definitely something we're exploring so that you could also do payments there. But like I said, in the meantime, you can just link it to the single desktop app and,

use that for messaging and all that side of things, just not payment specifically. Awesome. Alright. Let's rattle through these pre submitted questions. Guys, if you are listening live, feel free to add yours in. We'll jump across to those because the live always takes precedence. But for now, let's crack on.

First one comes from Noster Gang and said they said, will we be able to use RADAR via Cake? I pressed a little bit further because the question wasn't clear to me, and I said, you know, what do you mean? In what sense? Do you mean, like, sending messages from Cake? And they said, yes. So any plans for that?

No. I mean, we we thought about that of, like, should we just add the messaging part into cake and make it a a feature there? But I think

both the, like, chats in a wallet and a full wallet within a chat app, both are the wrong approach because they're kind of they both get way too complex too quickly. There's just so much difference between a chat app and a fully featured wallet.

And putting the two together in one way or another, it just always ends up being really problematic with the actual user experience and explaining everything to people. So, no, you won't be able to actually, like, do the chatting within Cake Wallet.

Obviously, like I said, your seed phrase will be compatible between the two, between RADAR and Cake Wallet. So you can always use the same wallet between the two or or restore your wallet from radar into cake, whatever you prefer there.

But, no, we won't merge those two. Because I think there needs to be a clear distinction of, like, cake wallet is what you use for the fully fledged, full featured, more privacy functionality, like all of the other stuff that comes with all of the great things we're doing at Cakewallet and keep that separate from RADAR and vice versa.

I'm really glad you said that. Alright. Next one. This one comes from bitter twenty one. Said, is radar basically texting over signal, and can I send a message from signal to radar? Yeah. So that's one of the nice things here. Since we're we're kinda leveraging the radar protocol and the radar network, it works to message

all of your existing signal contacts and users. So the the normal way that I would see someone using this is make a backup in signal,

get that recovery key, log in to RADAR, restore your backup with that recovery key, and you can just keep messaging in every chat, every group chat, every DM, whatever, with all of the signal users that you're already connected with. None of that needs to change.

If any of you or anyone listening to this has messaged me on signal, over the last six months, you've been messaging me on radar. Like, I've been using radar to send and receive all of my signal messages for my public account for many months now.

And that's really the beauty of open standards and and using the signal network is you don't have to start fresh terms of network effect. You don't have to start start from scratch. So, yeah, you can just message other signal users and radar users. Obviously, you can only pay radar users. But yep.

Cool. This one could be a deep one, so feel free to kind of just give a a brief answer. But how does the unilateral exit work with Spark and and RADAR, and how are you gonna implement that in the future if it's not already there, which I don't think it is. Correct me if I'm wrong.

Yeah. No. It's not there right now. So, yeah, I'll just give the TLDR. I know there's been a lot on, Twitter from competitors about unilateral exit in Spark this week.

The the TLDR is you can unilaterally exit on Spark right now. It requires a CLI app, which you just use your seed, and you can unilaterally exit. Open arms actually has been doing a ton of awesome work in the Bitcoin space for years,

detailed how that worked. He built his own tool to make it a little bit simpler as well. Wrote a lot of research around it. So if you wanna dig into that, maybe we can link that later on.

Right now, you can't do it directly in RADAR just like you can't do it directly in CAKE. I am as frustrated by that as you are. I've been pushing Breeze and Spark to build that out in their SDKs for many months, and it's been delayed quite a bit. So

I want it to I mean, it is important for people to realize that it's only, like, a a fire escape. It's not something you would ever use unless Spark themselves, like, the it all of these Spark operators went away overnight.

That would be the way that you would get your money out. So it is important to have. It is not something that you should ever use unless you absolutely have to because it will always be fee prohibitive.

But we definitely will have it in the future. You will be able to unilaterally exit from radar and cake. It's being worked on right now as we speak. Awesome. Rivian Stokes is asking what is the business model? How is the RADAR team gonna make money and sustain the project?

Yeah. So, in the short term, obviously, the onramping and offramping, like I mentioned, that's the straightforward one when people wanna add funds into the app. Or withdrawal, we'll take a little bit of a cut of those.

We have a lot of other plans centered around the stable balances thing that I mentioned before, where if users to keep their balance in stablecoins on Bitcoin rather than on Bitcoin itself, there's some some revenue that we can earn and share with the user with those stablecoins.

So that is is an option that we're exploring as well. But in the short term, it'll be that the the on and off ramps similar to Cake Wallet and every other Bitcoin wallet on the the fiat side.

Alright. Nice. Bon is asking, basically, is Radar gonna be on par with the the usual security features, updates, and and whatnot from the main signal clients? And if yes, like, is there gonna be a delay between, you know, a signal patch in

a critical update, and then you guys kind of implementing that so that you can protect all of the the users. Like, I'm guessing there has to be a delay there just because of the way, like, how it works. But yeah. Yeah. What's your thoughts? Yeah. I mean, you're right.

There's there's no way there would not be a delay because, obviously, they're gonna they're gonna ship that and push the code at the same time. So, thankfully, the way that it's split up, there's basically the the front end side of signal and the back end lib signal.

We're staying up to date with upstream lib signal, which is where all of the actual, like, protocol level, the security and privacy stuff lives. We won't work as hard to stay up to date with the UI side, partly because, we wanna do some things differently, partly because

with all the changes that we've made, it's really hard to stay upstream on the the UI more broader client side. But with the the lib signal underlying protocol side, that one, definitely will be working very hard to stay up to date with, and, that one's not as complex to stay up to date with.

Cool. The next one comes from the Daniel. And he said that after installed on iOS, incoming voice calls to signal on his Mac desktop no longer get routed to his phone, and he couldn't find a setting for it.

And he's gonna consider uninstalling it so he can figure it out because it's a feature that he really likes from the the main signal client.

Oh, that's an odd one. The only thing I could think of is maybe that your desktop was still linked to

your signal app and not your radar app. I've been using the desktop app with radar for, like I said, many months, and calls do come through in in q and a, and I've had calls, in these last months that have been coming through on the desktop, but with radar as underlying device.

So it should work for that. I'm not sure what would be up with that, but definitely reach out to us, support@radar.chat, we'll we'll try to try to help you out. Alright. A bit of a more of a spicy one from Bitcoin Brappan pointing the finger at Spark privacy concerns. I said the Spark server is

closed source and holds all transaction data, and unilateral exit is really complex and almost impossible to do. I know you've just covered that one, so maybe leave that one out. But he just basically wants your thoughts on the kind of privacy aspects of of integrating with the Spark network.

Yeah. I mean, the

it always comes down to, like, what what are the actual benefits or downsides here? Like, unilateral exit, obviously, I covered that somewhat. There's a little bit of a misunderstanding here that Lightspark doesn't share the leaves. It's not true. They do.

It's just wallets don't cache them because there's no need to cache them outside of unilateral exit, and we don't have unilateral exit in the SDK, so we don't cache them right now. It's a little bit of a chicken before the egg problem. There's nothing about Lightspark not sharing the leaves. It's absolutely not how this works.

They have to share the leaf data with you for you to make payments. So we have everything we need from a protocol perspective, from a Lightspark perspective to do unilateral exit. So it's just building up the SDKs in a way that's that's useful and works well for users. So that will come.

That aside, the Spark server being closed source, there's one piece of it that is closed source, which is obviously a little bit annoying. The protocol itself is completely open and open source, and anyone could run that.

I need to dig a little bit more into the SSP claims that, like, some like Matthew are are making about that being closed source because from my understanding, all the pieces you would need to run a Spark entity are open source. The only part that isn't is how LightSparc runs the the Lightning side of it, but that's

irrelevant. Anyone could run a an SSP could run the Lightning side of it because it's just atomic swaps. It's accepting payments within the Spark environment and making Lightning payments as a result. So the other thing, holding all transaction data.

Yeah. All of these layer twos, the privacy sucks. You trust the the operator to not publish your transaction data. That's how ARC works. That's how BARC works. That's how Arcade works.

That's just the reality of these systems. And it's better than Bitcoin on chain because, hopefully, they don't publish it, and you have good privacy from outside observers. If they do publish it, you're back to essentially an on chain level of privacy, which obviously is not great, but is,

yeah, is something we just kinda have to deal with, unfortunately, in the tools that we have available on Bitcoin today. Next one comes from Mark g. And he said, has anybody independent of the KQL team done any code review, to, you know, make him feel more comfortable to put his signal kind of details in into this, new app?

Not at this point. No. I mean, no official, like, third party audit or anything like that. The I think the most important piece to remember about this is this is a like, under the hood, it's a fork of the signal client.

We're not touching any of the messaging protocol, the privacy protocol, anything like that. All we've essentially done is use the underlying mobile coin payments rails and shifted them to use Bitcoin via Spark.

So there's nothing changed on the messaging or the privacy or the security side. And because signal is a is a network, we can't just change things, unilaterally and have them still work. They would break anyways if we completely change something about the the messaging protocol itself.

So nothing has been touched there, But, obviously, long term, we we will want some review of that code. Hopefully, other people will build around this or play around with it. We can get some audits as well. Yeah. I think the cool part about this is and it's obviously not a com you know, end to end foolproof

solution, but anybody with a $20 a month Claude code or ChatGPT

account can, you know, have a cursory check that there's nothing outright malicious in any of this open source code. Like, it's never ever been easier to do that despite, you know, not being a developer. So maybe Mark can be can be the the pioneer there. Speaking of Mark, there's another one from him.

He wants to know, did you include any of the Mollie code, especially Mollie's at rest database encryption? And maybe just a quick primer on what Mollie is for for those that don't know. Yeah. So Mollie is the the other main, like, signal alternate client. They've been around for years and kinda took the approach of

not changing a ton in terms of, like, the the day to day user experience looks like, like, but more hardening on the app side, on the data storage side, all of that. So we have not done anything with Molly's code, mostly because the target audience here is not the the hardcore user.

It's the regular user who wants to use Signal but wants to be able to make payments really easily. So we're not targeting as much of the advanced functionality that Molly is. Moly is also Android only.

They don't they don't build anything for iOS, and we want to be on both platforms. So that's another limitation there. But we'll definitely be thinking about if there's anything from them that we want to fold in as a feature that more advanced users can enable. But I think it is important to think about this quite differently from,

like, a cake wallet or some of the more advanced tooling that we've made or other people are making in the space, where this is something we want just regular people to be using

and getting the benefits of Bitcoin from, and not necessarily something that has all the tools and gadgets and tweaks that you could have in a in an app like this. Awesome. Alright. Down to the last two.

This one comes from Rips. When I send stats in radar, is the recipient's identity, phone number, UID, username, profile key, all of that good stuff sent to any payment related back end? Or is the payment layer only given a lightning invoice and or payment request?

Yeah. That's one of the really beautiful things here is those they're they're very distinct. So signal the only thing that they see is a message has been sent. The the beauty of the signal protocol, obviously, in an encrypted metadata is

very well protected. They don't know who's sending a message to who. They don't know anything about the details. So they just see a message. That's the only thing. They can't tell that it's a payment in any way. On the the payment side, Spark, via the the LightSpark Spark entity,

all that they see is someone paid someone else on Spark. They have no idea that this is from Radar, much less which user is associated with it. Obviously, we don't send any of the user's payment details or, profile details with the payment. There's no reason to do that anyways.

They recognize it in their local wallet. We don't need to send some identifier or attach their ID or something to the payment. So

LightSpark see nothing about this being even radar related, much less who is sending a payment to who, and signals see nothing about this even being a payment. They just see that a message has been sent. That's one of the really nice things here.

Also, RADAR, like us, the company, we see literally nothing because we don't run any of this infrastructure. So we have no visibility into your messaging, into your payments, into the connection between the two. We got nothing.

Beautiful. Alright. We'll make this one the last one because we are a couple of minutes over. Comes from macro future. You kind of already answered it, but let me know if there's anything else to add.

While keeping it simple for normies, will RADAR Wallet still add features like tap to pay and fiat debit cards so you can spend right from the app?

Yeah. I think the short answer, like we talked about throughout, is generally no.

There's limits anyways on being able to do things like that. Like, in iOS, you can't just do tap to pay. You can't just have a debit card wallet that you can spend from in in an app. There's no way to actually do that because it has to go through Apple Pay.

On Android, obviously, there's a little bit more flexibility, but even then, you can't actually do tap to pay debit cards without going through Google Pay as well. So, no, I think the the main

thing that we'll think about is, like Max mentioned, Cake Pay, maybe the ability to to buy a gift card and use it elsewhere or buy a debit card and use it elsewhere could be something that we would add. But, normally, I think it would be on and off ramping, trying to make that feel as close to, like, the Cash App style depositing

flow. That's gonna be the the way that we expect that to be. But, again, since this isn't a a wallet with the goal of being your everyday spending wallet,

it's the goal of this is the the funds that you use to send and receive value between people that you're chatting with. Not that this should replace a cake wallet or an Envoy or whatever.

It's really something that's that's separate and standalone, and I don't want it to be the you can do everything in radar functionality because the app would just get super bloated. So very intentionally, we're keeping it very lean lean and mean.

Glad to hear it. Alright. Well, just signpost people to where they can get started, where can they download it, and, yeah, then we'll wrap this up. Yeah. So go to radar.chat. I didn't get to talk about this at all, but I had a ton of fun. I got to build that website from scratch, with help from my team. You mean Claude? But

I I yes. I put my my servant AI agents to work on it. Yeah. We had a cloud. But it was a ton of fun, as somebody who could not build a website from scratch like that. It was a a good learning experience and good chance to show how powerful this stuff really can be. So, yeah, radar.chat.

Had a ton of fun building that. You can learn everything about the app, download it from there as well. Then just follow us on socials at radar chat on pretty much every social media platform as well. But

yeah. Thank you all. It's been a fun one. Good stuff. Thank you, buddy. Yeah. Very excited to see it out and looking forward to carrying on playing with it. It's really great. Hats off to to you and the team. And thank you to everybody for joining us, for submitting

all of your questions live and pre submitted. And as always, we'll be back at the exact same time next week. Hope you all have an awesome weekend. Thank you for listening to Freedom Tech Friday.

To everyone who boosted, asked questions, and participated in the show, we appreciate you all. Make sure to join us next week on Friday at 9AM EST and 2PM London. Thanks to Seth, Max, and q for keeping it ungovernable.

And thank you to Cake Wallet Foundation and my Nim Box for keeping the ungovernable misfits going. Make sure to check out ungovernablemisfits.com to see mister Crown's incredible skills and artwork.

Listen to the other shows in the feed to hear Kareem's world class editing skills. Thanks to expatriotic for keeping us up to date with Boost's XMR chats and sending in topics. John, great name and great guy, never change and never stop keeping us up to date with mining news or

continuing to grow the Mestadel. Finally, a big thanks to the unsung hero, our Canadian overlord Jordan, for trying to keep the ungovernable in check and for the endless work he puts in behind the scenes.

We love you all. Stay ungovernable.