WEBVTT

1
00:00:20.400 --> 00:00:43.520
Welcome to the Citizen Bitcoin Podcast. I'm Brady, and I'm sharing my journey learning Bitcoin, hoping it makes yours a bit easier. And what is up out there, Bitcoiners. I just enjoyed a lovely chat with Ketominer from the Nodl team, and I'm excited to share it with you. But before we dive in, this week's open source shout out is to the Tor Project.

2
00:00:43.520 --> 00:01:05.360
Tor is short for the Onion Router, and just like the internet, Tor started as a US military project. Now it's a nonprofit project that provides this privacy-preserving technology for all of us to use. The Tor network disguises your identity by moving your traffic across different Tor servers and encrypting that traffic so it isn't traced back to you.

3
00:01:05.360 --> 00:01:32.880
The Tor network has become an important part of Bitcoin privacy. Bitcoin and Lightning nodes can be run over Tor, and the Lightning Protocol itself uses a version of Onion Routing natively. Bitcoiners regularly rely on the Tor network to help preserve our anonymity and protect our privacy. You can support Tor by donating to the project at donate.torproject.org and by running a relay node.

4
00:01:32.880 --> 00:01:38.720
Just search Guide to Running a Tor Relay Node on DuckDuckGo to get started.

5
00:01:39.060 --> 00:01:40.500
All right, let's dive into this one.

6
00:01:47.480 --> 00:02:11.800
Ketominer is the cypherpunk and prolific Bitcoin builder who created the Nodl, the popular plug and play personal Bitcoin assistant. In this episode, Kido and I get nostalgic about the early days of personal computing and the internet. We, of course, discuss the Nodl, the latest news with that project, and of course, other projects that Ketominer is working on.

7
00:02:11.800 --> 00:02:32.200
We also discuss the Lightning Network and Privacy. Look, I've got a ton of respect for the Bitcoin builders, and Ketominer is one of the greats. I'm excited to share this one with you. Alright, here we go.

8
00:02:32.200 --> 00:02:52.440
I'm excited to welcome Ketominer to the Citizen Bitcoin podcast today. Michael, how's it going? I'm glad to see you're still alive after these five conferences you hit in a row. Hi, glad to be here with you today. Yeah, yeah. So you just got back from this long stretch of five conferences you were telling me about, and I mean that's quite the haul.

9
00:02:52.440 --> 00:03:14.360
I went to the Bitcoin 2019, it was, you know, just a week of utter madness. I came home absolutely exhausted. I can't imagine doing that five times in a couple within a couple months. Yeah, so the good thing is it's all in Europe, so the distances are shorter, but yeah, it was pretty exhausting, and you know, all the after parties are taking the best of us.

10
00:03:14.360 --> 00:03:32.360
But you know, that's that's really when you go to those conferences, that's really where the fun stuff happens, the great conversations and the good connections. Yeah, totally enough. Actually, we met at Bitcoin 2019, so Yep, we did. We had we were you were up at the rooftop beefsteak, right? Yep.

11
00:03:32.360 --> 00:04:10.720
Yep, yep. That was a good time. It really was. All right, let's start off. I'm just curious about you know, I've had some time to talk to you, I've listened to a couple of podcast episodes you've done with the TFTC guys and Stephan Livera and I'm just curious about how you got into the whole computer scene it sounds like you've kind of been in it for since you were you know pretty young so how do you how'd you become the cypherpunked that you are today you know actually every time someone asks me I try to remember how I ended up being passionate about computers and I can't really remember what I know is that I like read all the computer books in the local library when I was seven

12
00:04:10.880 --> 00:04:49.520
Eight years old and started programming on them on a notepad on a piece of paper because I didn't have a computer at home but the big why I have no idea actually and then I like discovered some magazines it was early times of hacking like phone cards you know for payphones yeah so that's how I started being interested in electronics and working around the system I guess wasn't that called freaking that the hacking payphones yeah it's it's a branch of freaking freaking was more about like hacking using those sounds injected

13
00:04:49.520 --> 00:05:21.240
In your phone line but yeah I mean the phone cards are one one type of freaking probably yeah and then I went to HCPP 200 seventeen and that's basically how I discovered what I really was was looking for because I spent like 20 years in open open source software and I tried like to be more on the hacker side than on the really open source developer side, and it this community didn't really accept that.

14
00:05:21.240 --> 00:05:44.440
It was the big days of DVDs hacking with the CSS, the software to crack the DVDs encryption, right? Yeah, and I never found anyone to hear me in this community, and yeah, a few I mean almost 20 years later, I discovered this cypherpunk and crypto anarchist community, and I found really what I was looking for.

15
00:05:44.440 --> 00:06:02.680
Nice. What was what was the first machine that you can remember coding on? The Armstrad CPC 6128. It it's a Z80-based computer, which we bought used from some friends, and actually gave it back because it didn't work.

16
00:06:03.960 --> 00:06:23.000
And then my parents bought me 286 based into Armstrad PC. Nice 286. Yeah, with one mega of RAM, one full mega RAM. A whole megabyte. That's like a third of a pop song, an MP3.

17
00:06:23.800 --> 00:06:49.240
That's awesome. So what was your first language? Then were you coding in basic? I guess I assume this was like a DAS-based. Yeah, it was basic. Then then I moved to Pascal. Me too, yeah. With Windows, I moved to C and C actually, Microsoft C. And then more or less at that time I discovered Linux because I we didn't have internet at home, so we were going like every week.

18
00:06:49.240 --> 00:07:08.360
I didn't live in a big city yet, and we were going like every week to the like internet cafe to download documentations and stuff when out of Easter was cool as a search engine, and I discovered this weird operating system that I didn't recognize on the computer, so I asked them like, what was that and where can I get it?

19
00:07:09.960 --> 00:07:29.520
And they advised me like to go, you go to that library, they have like CD packs, so it was packs like of six CDs with all the Linux distros that existed at the time. Like they were pulled from the internet every three months, so I made a new pack. How the was that called Info Magic, I think packs.

20
00:07:29.520 --> 00:07:49.520
That's pretty cool. Yeah, and basically on six CDs you could have like 100 different Linux distributions because it was that small. And then from that you had to copy them to diskettes because Linux couldn't boot on a CD. So yeah, those 3.5 inch discs. Yeah, fun times, fun times.

21
00:07:49.520 --> 00:08:11.040
Yeah, those are good times, man. Those are good times. I remember building games on Pascal and just having a great time. I spent a couple summers that way, and it was just absolutely engrossing. In a similar way that Bitcoin, you know, is I think for both of us and most of our listeners, that it just sort of sucks you in.

22
00:08:11.040 --> 00:08:35.200
And you know, it just it's it's fun to kind of live live through that again because the whole PC revolution and the internet, that was like you know, my childhood all the way up through my teens, and you know, getting to see it all happen again with Bitcoin is pretty awesome. Yeah, I feel like we are leaving the times like the probably late 60s, early 70s to early 80s now in Bitcoin.

23
00:08:35.200 --> 00:09:03.400
Yeah, I mean I'd say I would compare like the Casa node and the Nodl to sort of the early PCs, like the you know, 1984 Mac, the Macintosh was launched. So yeah, that sounds about right, like early 80s. Yeah, I thought I always have this scene, you know, at the Comdex when the first Apple II was shown and Heart and Catchfire TV show which I love that show which retraces the history of callback in the first season.

24
00:09:03.400 --> 00:09:25.480
Like this is really I feel this is where we are now with Bitcoin. Yeah, yeah, that that scene where Joe walks into the hotel room at Comdex and he sees the Apple, the Mac boot up and it and it says, you know, it says the Mac speaks, it says hello, I am Macintosh, and he's just like it speaks, and that moment was pretty pretty great.

25
00:09:25.480 --> 00:09:51.480
And Halt and Catch Fire, fantastic show. One of my probably my favorite, actually, of all time. So for the for the record, actually when we when we build the Nodo, we are thinking like how will people find out the IP address of the box if they don't have this nodo.loco address working. And one idea was to use the speaker out to just continuously repeat the IP address if you connect the speaker.

26
00:09:51.640 --> 00:10:09.880
We didn't go with that after all, but yeah, it's one of the stupid ideas we had early on. You gotta love those brainstorming sessions and come up with stuff like that. That's awesome. So I mean you've been around computing for a while, obviously you've seen you know, from from the beginning of the PC revolution up through the you know, beginning of the internet.

27
00:10:09.880 --> 00:10:33.080
I'm sure that you were working with you know, like 2400 bod modem modems and stuff like that back in the day too, right? Actually it started with a six 56k modem. Oh really? You jumped right up there. Yeah, I said my parents didn't want internet at home. After they didn't want a computer and finally accepted to have one, they didn't want the internet, the heavier internet.

28
00:10:33.080 --> 00:11:03.200
Not only because of the costs, but also because of the time consumption, and they were pretty right about that. Right. And then I finally after graduating high school, I got my first laptop with Modem, and that was about when we could buy a non-limited internet access through Modem, so I could like just spend all my nights on the on the internet and carefully listing in the other room if someone goes to the phone to disconnect just before they pick up the phone.

29
00:11:03.680 --> 00:11:25.680
So they don't hear the screeching, yeah. And then you're caught. No, when everybody disappears from IRC because someone picked up the phone and then you log back in. Yeah, yeah. Yeah. So I mean that that's only been 35 years, you know. It's been amazing the progress that we've seen. We all carry around supercomputers in our pocket now that are permanently connected to the internet.

30
00:11:25.680 --> 00:11:47.040
You know, Bitcoin is 10 yeah, it's been 10 years of that 35 years. And you know, really just getting started on that front. So I don't know, where do you where do you see us going? I mean, this this such a compact progress, progress so compact now, happening so quickly. What do you think the next few decades look like for man and machine?

31
00:11:47.040 --> 00:12:20.720
I would not even go more than one decade, probably because it's going so fast it's hard to imagine. But I mean I have that dream that in 10 years we'll be wearing four nodes on our wrist as a watch, and we have this low-orbit satellite connection always on on this on this full node, and our critical financial life will be going through that device, and more like we see more and more applications running on top of Bitcoin and Lightning, it's not only payment anymore.

32
00:12:20.720 --> 00:12:39.400
Yeah, I mean we I don't know if you followed what happened in Berlin, but one of our partners actually introduced an application called Sphinx Chat. It's a chat app over Lightning. So basically, you get the WeChat functionality, which is chat and payment, but entirely built over Lightning. Red.

33
00:12:40.120 --> 00:13:04.840
So you can just interact with your friends, send money, request money, send messages, group messages. We are working on a way to make voice and video work on top of that as well. Wow. Using like Lightning as a signaling protocol and building layers on top of that. That's crazy. How does that work? So actually it works something called something called key send, which is not yet merged in in LNC.

34
00:13:04.920 --> 00:13:26.120
Yeah, I've been hearing about that. But which allows you, yeah, it's spontaneous payment. So it allows you to send a message without the other person requesting it. As long as you have a channel and the new Onion format TLV allows to add like extra data in the Onion. Okay. So we can embed messages and other information in that.

35
00:13:26.120 --> 00:13:45.720
And yeah, basically the idea is like to use Lightning as a signaling protocol and then build like a peer-to-peer connection or or through a third-party server. I mean still work in progress. Now the we have a working demo of the chat part and payment, obviously, but we the other things will probably come later.

36
00:13:45.720 --> 00:14:03.880
Oh man, that's really that's really exciting and interesting. I'm definitely gonna have to look more into that. And I did hear you know, definitely hear chatter about it, but I hadn't watched the videos yet. That's really amazing. That's kind of blowing my mind a little bit. And with some other of our partners who is get better, it's the whole cost averaging company based in Europe.

37
00:14:03.880 --> 00:14:26.320
You send a wire transfer, you receive Bitcoin on your wallet. We worked on a demo using Kysen as well to do the same with Lightning. So you basically you in Europe we have something called CPA instant. It's like wire transfer which takes a few seconds and just a few seconds later you receive the Satoshi in your white lightning wallet.

38
00:14:26.320 --> 00:14:48.560
Wow so something kind of like what Jack Mollard is working on with Zap where you can Yeah totally totally that's awesome. Yeah and it's just happening so fast it's amazing the progress and I mean you know lightning is what I mean I don't even what a year year and a half old at this point that's been around. Yeah it's a year and a half in on Mainnet I think right yeah that's amazing.

39
00:14:48.560 --> 00:15:08.480
Yeah so let's all right let's dive into the Nodl. There's so much to talk about talk about progress. Speaking of progress, I mean, you know the Nautil was I think I received mine well that's a whole story. My my box got lost in the in the in the mail fortunately it it made its way back to you because I we thought it might have been like stolen by some like mail person.

40
00:15:08.720 --> 00:15:38.080
Yeah it would have been the first one we lost and two two months later it came back home. Yeah and you guys were kind enough to send me a box without even having that that back in your hands I was really relieved to see that you guys weren't out the you know out the box. So yeah so I've had mine for quite a while now you know been playing with it and hooking it up to various wallets and opening channels and trying to get some routing going on through it and I mean it's it's just a great piece a great machine.

41
00:15:38.080 --> 00:15:59.960
I the uptime on it I don't I don't think it's been down since I first booted it up which means it's been like you know many six months or something like that. And you guys have only been shipping for I mean you've been shipping for like less than a year now, right? I mean it's not even been a year. Yeah, totally. We started the pre-orders for the first version a little more than a year ago, and we started shipping in December.

42
00:15:59.960 --> 00:16:27.400
Yeah, so you guys haven't even been shipping for a year yet. And here we are with the announcement of the Samurai edition. You and the Samurai team have paired up to release a brand new edition. The red box is sexy as hell, it's looking great. And it's the specs on it are amazing. Can you tell us about the hardware specs and some of the what you also guys tweeted a few days ago about some of the physical security aspects of the of the box as well?

43
00:16:27.400 --> 00:16:48.200
Yeah, so the main difference between the original model and the samurai is that the samurai oh by the way, we just settled on calling it the Nodo dojo after all. Okay. So that will be the official name. It has a six-core CPU as opposed to the four calls of the original model.

44
00:16:48.200 --> 00:17:07.080
It has a double storage, so everything is redundant when you write any information brought to the two SSDs, so two unterabyte SSDs. The SSDs are fully encrypted. So you when you start the device, you need to provide your encryption key.

45
00:17:07.080 --> 00:17:25.880
There will be different ways of doing that, but the most simple one is to log in into the UI and just type it. So if someone steals your device, they will not be able to access the even the public keys inside. Nice. Without the encryption key.

46
00:17:25.880 --> 00:17:51.440
And also since we have the Wii OPO mixer on it, we have the private key, so it's really critical to encrypt everything. Yeah. And so one of the new features we announced this week is there will be a physical kill switch. If someone tries to open the box, the encryption keys gone. And so that that way, even if someone gets physical access and tries to remove the drive, he will not be able to access the keys.

47
00:17:51.440 --> 00:17:52.240
Nice.

48
00:17:52.960 --> 00:17:57.500
And yeah, and one upgrade we came up pretty late

49
00:17:57.760 --> 00:18:16.080
On is we add an additional hole on the back of the device, like an antenna mount for future expansion. For example, if you want to make a LoRa one or Gotena relay, or if you want to have a block sat receiver in the box. That's amazing. Yeah, that's that's really cool.

50
00:18:16.080 --> 00:18:36.320
I think it's super forward-thinking. So yeah, so the box itself could connect to a mesh network, for instance. Yeah, yeah, that's the idea. So we don't have a date on those features, but we want to make the physical box as ready as possible to be expanded. Yeah, I mean, this machine is equipped to you know stay around for a while.

51
00:18:36.320 --> 00:18:56.800
Like this could be four or five years, you know, lifespan. So yeah, and it's an expensive device, so we have to think about people buying it, and they they will not buy that for one or two years. Right. I also read that it's expandable inside, like there's some slots for expanding some functionality.

52
00:18:56.800 --> 00:19:19.440
What are those about? Yeah, so basically the board on which is attached the kill switch, which I just actually finished designing five minutes before this recording, and sent to production. Nice. Is is a user-removable board, and it will be replaceable, for example, with an internal UPS board.

53
00:19:19.440 --> 00:19:38.200
To have a battery backup. It's not meant to have a long battery life just to cleanly shut down the device, because when you pull the power you may corrupt the data, and the recovery is not always possible, especially with Lightning.

54
00:19:38.200 --> 00:19:59.480
So yeah, instead of buying an external UPS, like for it will probably not be cheaper, but at least it will be all fitting in one box. And also like the redundant storage makes it easier to upgrade the storage capacity if you need at some point, you just replace one drive, you wait it for two to retync, and then you change the second drive.

55
00:19:59.480 --> 00:20:19.160
So, yeah, it's it's really in my opinion, it's a long-lasting device. So obviously it'll come with the samurai dojo software. Are you always also gonna include dojo like make it an option for Noto 1 users as well? Yeah, totally. You have two ways to get Dojo on the on the current device.

56
00:20:19.160 --> 00:20:39.400
You can you will be able to just install it as all the other apps for free, or you will be able to get it for a fee with the samurai support, which I encourage you to get because it can be tricky sometimes to set up your wallet. It will not be a high fee, it will probably be something around 50 bucks.

57
00:20:39.400 --> 00:21:00.040
And you get permanent samurai support. Very cool. What other applications have you guys been talking about adding as options? One of the latest additions we had now with that we enabled access to all the APIs running on the box, is to be able to use fully nodded Suter.

58
00:21:00.040 --> 00:21:19.200
So it's an iOS client to access the information of your Bitcoin nodes. No, so that's not for Lightning, just for Bitcoin D. Also it I think it allows to make watch-only wallets and can serve as a basic explorer.

59
00:21:20.160 --> 00:21:41.280
So just by scanning a QR code or tapping a link on another UI, you will be able to pair it to Tor and access it from wherever you are in the world. Nice. Yeah, that's like the basically the biggest addition we had recently. And of course, we stay compatible with all the lightning wallets like Zap, Zeus and all that guys.

60
00:21:41.280 --> 00:22:02.720
Zap is releasing the Tor connections very soon too. So we'll be able to do the same. Because currently you have to run a VPN on your on your box to access Zap remotely. Right. And very soon you'll be able to do that over to. Yeah, then that's just so much easier. Just like plug in an onion address as a setting and you're good to go.

61
00:22:02.720 --> 00:22:21.840
Yeah. And yeah, features we promised that we're working on are a block explorer and probably mempool.space now that it's open source. So basically anything you need for your Bitcoin live will be running on the box and you will never have to use any third-party external service.

62
00:22:21.920 --> 00:22:40.880
Oh, that's fantastic. Well, have you guys considered adding other or alternative like Bitcoin and Lightning implementations as options instead of like right now it's Bitcoin D and L and D. But yeah, have you thought about adding any other alternative implementations?

63
00:22:41.280 --> 00:23:01.560
Yeah, we have the we have like a long term goal to cover as many alternatives as possible for the users. Yes. But actually, below behind I mean, except Bitcoin Core, I don't think people really want to run anything else. Maybe BTCD for UN Sure.

64
00:23:02.360 --> 00:23:12.600
Or maybe some like alternative folks of Bitcoin Core. I don't know. But yes, for Lightning, we'll definitely add at least C Lightning.

65
00:23:13.220 --> 00:23:15.420
Many people are asking for that

66
00:23:15.720 --> 00:23:35.480
And it provides like slightly different functionalities and it has a different architecture from LND. We don't exclude other implementations, although it's not planned yet. I mean, C lighting is a sure thing for the coming weeks. The other ones less so.

67
00:23:35.640 --> 00:24:05.400
Okay. I could imagine like if you know if the nodals kind of get a lot are out there and attach to the network, both like CASA and NOTLE I could see having that software available. So if something happened like UASF and the users were sort of, you know, almost like threatening to use a different implementation, different software to kind of exert their control and preference.

68
00:24:05.680 --> 00:24:28.120
Have you ever thought about that playing out? And you, as the proprietor of this business, being able to push out software, make it available for users to choose to install, could you see yourself making some alternative implementations available to Nodl users in a scenario like that, like a UASF scenario?

69
00:24:28.840 --> 00:24:54.800
Yeah, we'll definitely not choose for our users, and we'll be we'll be trying to be as fast as possible to provide the possibility to vote by running the implementation I prefer. Yeah, very cool. All right. So I've heard you mention a few times, like in Telegram and maybe in some podcasts or something, or maybe recent talks you've given this idea of the Nodal Cloud.

70
00:24:54.800 --> 00:25:21.200
Can you talk about what you mean by that? Yeah, so it's it's actually something pretty vague because it includes many things. But the most obvious one is like a Nodo box as a pay as you go renter service. So you get exactly the same UI, exactly the same functionalities, except it's running on a server we own, and you rent monthly for a fee.

71
00:25:21.200 --> 00:25:48.720
It can also be a good way to discover the product if you're not sure that you want one. You just rent an instance for a month, you try it out, and if you like it, or you keep the cloud instance or you buy the box, and yeah, so that's like the most obvious application, and then we have like more not directly nodo-related services, which will be also included in the Nodo Cloud name.

72
00:25:48.720 --> 00:26:10.160
One is renting servers for BTC pay server, the same as they do now with Lunar Node. We intend to provide exactly the same service, so like a very easy to use web installer. You just rent an instance, you set some parameters, and you have your BTC pay server running on the cloud, like a dedicated VPS server.

73
00:26:10.160 --> 00:26:45.400
And then we have like more enterprise grade services like renting a BTC-based server, but as full multi-tier enterprise application. So we have like a this big shared BTC pay server on which you can create an account. You can still get get lightning because we dedicate one LND for each customer, so it's not like on other platforms where you can't use Lightning if you have a shared instance and it's running on a web cluster, have two front ends, two load balancers, you have a database cluster running on the back.

74
00:26:45.400 --> 00:27:19.560
We can make that a geo cluster, like between multiple data centers in multiple countries, and provide a really high level of redundancy and uptime. And finally we have the modern rack, which is like a more enterprise grade hardware. It goes from a small one rack unit device with two servers inside to like custom made big servers, and this will be available both as a renter model, as a pay and rent model.

75
00:27:19.560 --> 00:27:40.600
So basically, if you prefer to own your own hardware for many reasons, like if you go bankrupt and it got seized, that's not ideal for you. So we probably want to buy it, you will be able to buy it and still host it with us or to host it wherever you want. Yeah, so you guys are thinking big, like enterprise level services for the for the Nodal business.

76
00:27:40.600 --> 00:27:59.400
And I know that you're you know, kind of imagining the NOTL box right now, really targeted toward small businesses who want to have you know self-sovereign economic transactions, and I know obviously it's been kind of taken up by Bitcoin sort of hobbyists and tinkerers as well right now.

77
00:27:59.400 --> 00:28:20.560
But you're really looking at the Nodal business as like really enterprise focused down the line. Yeah, I don't know when it will happen, but it's pretty obvious that it will happen. But when some big company like big ornament store or big physical store calls or looks for someone who can provide a solution for them, we want you we just want to be ready.

78
00:28:20.560 --> 00:28:53.600
Yeah, right. So you've launched a service called host for coins. Is this sort of part of that like larger vision of the Nodal Cloud where you're you know providing hosting services that are anonymous and paid for only with Bitcoin, etc.? Yeah, it's a little on the side. So actually I'm running a hosting company which is a like classic fiat company, and I wanted to diversify and actually the classic hosting customers are like always complaining and not understanding many things.

79
00:28:53.600 --> 00:29:21.200
It's very hard to compete with people like Amazon or Google. So I thought let's make something different and let's propose something to Bitcoiners who don't want to spend their money at Amazon and Google and just provide them service. The anonymity of it actually is maybe not the most important feature, but the fact that we accept only Bitcoin payments, like filters out most of the noise.

80
00:29:21.200 --> 00:29:41.120
We don't even require a valid email address, so that was a big problem in the beginning. We actually have two customers, we don't know who that is. They didn't provide a valid email address, and they we just can't send them the credentials to connect to the servers. So very quickly, yeah.

81
00:29:41.120 --> 00:30:03.640
We very quickly quickly implemented the chat system in the website, but apparently I still didn't reconnect. So hopefully one day they will remember that they paid for something and come back. So you guys are using you have your own hardware, like it's co-located hardware, I assume that you but it's it's owned by you and operated by you.

82
00:30:03.640 --> 00:30:28.680
Yeah, totally. So we collocate in several data centers in Europe. We are planning to expand in in the US, and all the hardware is owned by us under different entities. Yeah, and we try to at least have a network presence in privacy-friendly jurisdictions like Switzerland.

83
00:30:28.680 --> 00:30:47.880
So that's not yet possible on the website, but very soon you will be able to choose the country in which you want your server to be very virtually located. Physically, it can be in a totally different place, but the entry point of the network and the IP address will be located in the country of your choice.

84
00:30:47.880 --> 00:31:06.200
Very nice, very nice. You m you tweeted about something like an all-in-one SAT box plan for 2020. What was that about? Yeah, so many people are asking, like basically for the same kind of device as the Nodo, maybe slightly bigger, like a satellite set up box.

85
00:31:06.200 --> 00:31:32.680
Yeah. But really all in one. So the first idea was all the nodes will support blocks at anyway, but as an external add-on. That's why in the new red and black boxes we decided to include a few small holes that will allow you to put this device actually inside the box and route the wire from inside out, okay.

86
00:31:32.680 --> 00:31:51.440
Which is not very pretty, but at least it will be more in one. But to really answer these questions of having an all-in-one box, we are planning like to make a bigger box with a satellite receiver inside, probably other features. Maybe like more rugged designs to be placed outside.

87
00:31:51.440 --> 00:32:11.600
I don't know. I don't have a precise idea yet of what it will be, but we really want to collaborate with Blockstream and make something like dedicated to an off-the-grid Bitcoin format. Yeah, I mean I love seeing this stuff happen. Like the mesh networks and the satellite receivers connected to a box.

88
00:32:11.600 --> 00:32:33.200
Like this is the kind of thing that makes you know Bitcoin anti-fragile and to some kind of great black swan event that might happen where you know the internet itself like is goes down in like large re large parts of the world or whatever or is just blocked like in the case of China in the firewall and just like literally lock it down.

89
00:32:33.200 --> 00:33:07.840
But then you could you know just point a satellite receiver at the sky and plug it into your SAT box and be back online. Yeah and actually on the hosting side we are trying to build something that is similar. All our data centers are connected with private links. It doesn't go through the internet. So even if we lose like let's say for example we lose internet access in Paris we can still get out through Geneva or Frankfurt it's all like meshed with with private independent things.

90
00:33:07.840 --> 00:33:29.480
Wow cool and hopefully like I made a talk in Romania recently where I introduced a project I had two years ago, which was to build like a huge independent network for crypto and yeah, the base idea of that was to finance it with an ICO, and obviously it didn't happen.

91
00:33:29.480 --> 00:33:53.560
So now we are trying to do it very slowly with our own money and anyway build this network. We m we met some pretty interesting people along the way, not from the Bitcoin space at all, but people who are very sensitive to the topics, and they're helping us a lot by providing like very discounted services and helping us build this network.

92
00:33:53.560 --> 00:34:12.200
So, this is like a like an alternative to the internet, like running Bitcoin, the Bitcoin network on a like a literally a separate physical network that's separated completely from the internet. Yeah, yeah. Our data centers are totally independent of the of the internet, they communicate with each other without the internet.

93
00:34:12.520 --> 00:34:43.640
We could even imagine like placing a satellite dish on one of the data centers and have our own like SAT SAT node and receive the double team satellite and stream it from there to the to our other servers. And for the chat app demo, we actually used lighting nodes which were like not directly connected to the internet, they were like behind the router, like you would have your home router with a network as a translation which uses only one public IP.

94
00:34:43.640 --> 00:35:04.520
So basically, these nodes like they they don't have a public IP, they don't expose the public IP, they are not on toll, so you can't reach them from the outside, but they can still reach you. And between themselves they form separate mesh. So, yeah, we're working like on ideas to build more private Bitcoin networks.

95
00:35:04.520 --> 00:35:23.120
It's very cool. There was some recent buzz on Twitter about the CASA and NOTL dashboard passwords being transmitted through unencrypted HTTP on local networks like your local Wi-Fi network. And I know that you guys made some like had some response to that.

96
00:35:23.120 --> 00:35:41.360
What what not like changes will Nodl be making in response to that? So for some time already we are running over HTTPS, but it's a self-signed certificate. So your browser prompts you to ask you to verify it, and you can't. So you have to trust anyway what your browser says.

97
00:35:41.460 --> 00:36:09.700
But I mean, at least it's encrypted between the box and you, so it's, let's say, less bad than not encrypted at all. The main problem with CASA was that they are actually showing you the seed for the Lightning Node over HTTP, which we don't and always refuse to do. The only way you can get the seed from a Nodl is to plug a USB drive in the back and it will be PGP encrypted.

98
00:36:11.080 --> 00:36:30.580
So that's one very big difference. And yeah, overall, the other issue was, which we share with them, is the default password for console access, which in our case is slightly worse because we open SSH by default.

99
00:36:31.660 --> 00:36:47.020
So basically, if you didn't read the quick start guide to the end and didn't change your SSH password, anyone on your network can SSH into your device and get the private keys or privacy or public keys

100
00:36:47.200 --> 00:37:08.520
So like many issues, privacy and potential loss of money, or just destroy your device. So how we will be addressing that is that every device will be coming with random generated SSH password, which you will get at least on the piece of paper in the box.

101
00:37:08.520 --> 00:37:29.320
Maybe you will get it in a separate way, like encrypted email or something. I don't know yet how we'll be doing that. And anyway, you would be prompted to change that password first time you connect. So only we will know your password. Hopefully we don't have access to your private network, so we'll not be able to do anything with it anyway.

102
00:37:29.880 --> 00:37:52.680
And anyone visiting you will not have this password. Right, that makes sense. All right, so yeah, I you know, I think it's I'm actually gonna be talking with Jeremy Welch next week. And so I'll be asking him about that as well. And it's is there like would there be a way to accomplish this without HTTPS?

103
00:37:52.680 --> 00:38:15.560
Is there some kind of like targeted encryption that could be used? From I don't know, because the browser is probably not equipped on that end to do encryption except for HTTPS to the box. I guess without like thick client like an app it would be very tricky to achieve.

104
00:38:15.560 --> 00:38:36.440
Someone proposed on on Twitter like to use client and server certificates with a CA certification authority. But yeah, it it is becoming very complicated. I mean, we are still aiming to be used by like normal people, not computer geeks.

105
00:38:36.440 --> 00:39:06.320
And the people who will be able to use such a complicated encryption scheme would would be able to build the box themselves anyway, so that's not our customer. Yeah, I mean there's always these trade-offs between usability and security, and you gotta walk that line. Well what's funny, what's funny about all this story with which happened with Casa is actually that the password part was not the critical side of it.

106
00:39:06.320 --> 00:39:28.320
Actually someone reported to me that someone from the support made him run after logging in with this default password, make him run a script like from a tiny URL link and directly pipe it into bash. So basically that what it does is pulling some script from the internet and running it running it without using it.

107
00:39:28.320 --> 00:39:48.800
Yeah, but actually people completely missed this point and focused on the password part. But I had a chat with Jeremy about that part, and apparently it's some brogue support person who that who did that and it will not happen again. Yeah, it wasn't supposed to happen, which makes sense.

108
00:39:49.360 --> 00:40:10.880
Yeah. Cool. All right, so let's let's just talk about lightning in general for a little bit. I know you were at the first ever Lightning conference in Berlin recently. How was that? It was incredible. I mean Bitcoin conferences are are mind-blowing by default because you can meet people which you would not never meet in real life.

109
00:40:10.880 --> 00:40:36.440
But that was like 10 times a Bitcoin conference. And the team from FUMO and the other people organizing that are very very good at organizing events. I've been at the Lightning Hack Day in Munich before, and they always find like the best place to do that. If I make you really feel good, and you have like these hacking spaces where you can just sit and do some work.

110
00:40:36.440 --> 00:41:13.320
Nice. Which I used a lot. I didn't see many talks, actually. I have to catch up on the talks still. I've seen like two talks probably. Yeah, and like people are just doing things all the time. Like these small lightning ATMs, which you can exchange coins for satoshis, the beer tap, the cocktail machine, the scooter, some crazy art contraptions activated by lightning, like in in every corners of the room there is something happening.

111
00:41:13.320 --> 00:41:40.520
That's awesome. Anything that was like that jumped out to you, like an I some idea or something that was fresh that was new and interesting that maybe came up in conversation or anything. So I had a few talks on the side and actually discovered that many people are like forking lightning software, like LND especially, and adding some very interesting functionalities I'm probably not supposed to talk about.

112
00:41:40.520 --> 00:42:02.680
Okay. But yeah, a lot of like I mean for this chat app that we are running, we have our own custom version, and yeah, many things are like happening which are not publicized, and yeah, basically like I think in the coming months it will be going faster and faster.

113
00:42:02.680 --> 00:42:26.880
Yeah, so there's just lots of experimentation going on out there, and we in the general Bitcoin public will be seeing it in the in the coming months, the fruits of that experimentation. And I think Bitcoin 2020 will be a big big thing too, because we are like I think many teams, including us, are using that event as like a target for for doing new things and showing them.

114
00:42:26.880 --> 00:42:46.960
Yeah, so we're gonna get lots of new announcements there. I've already got my ticket. Bitcoin 2020, everybody. Be there for sure if you can. It's it's just a it's amazing to meet Bitcoiners in person and got your your conviction will just like you know go sky high if it can go any higher than it is already.

115
00:42:46.960 --> 00:43:06.080
It definitely did for me. What do you I mean of the lightning improvements that that we know about that are public and discussed and that are on the table, not yet implemented. What do you think are the most important improvements on the horizon for lightning?

116
00:43:06.320 --> 00:43:32.240
For me, the really most important thing we need is the multipath payments. I always forget the technical name for that, but AMP, I think. Yeah, yeah, that yeah, this is really critical because like it's so frustrating when you have like 10 million Satoshis in your channels and you can't pay 100,000 just because you don't have a channel with the correct destination.

117
00:43:32.240 --> 00:43:51.600
Yeah. I mean, you don't have liquid enough liquidity on one channel to do it. Right. So yeah, I think this is really the most important thing we are missing. Yeah, I agree completely. And I mean that's the biggest noticeable challenge for end users is routing failures.

118
00:43:51.600 --> 00:44:11.160
And I think that that is the number one thing that's holding or that's probably causing those routing failures, is just there's not that many options for the to find a route, right? Because you have to have that and there are many there are many routing bugs actually. It it tends to be better in zero eight of LND.

119
00:44:11.160 --> 00:44:34.680
But we zero six zero seven, we had like a lot of routing failures. You run query route, it says it found a route, and then you make a payment and it doesn't find the same route. Right. It happens all the time, all the time, and it's very frustrating. Yeah, just to go to show that we're still at early days, and it's only been you know 18 months since Zen's Lightning has gone on mainnet.

120
00:44:34.680 --> 00:44:53.160
It's still technically the implementations are technically in beta. So just gotta remind everybody every once in a while that you know this is new software and engineering takes time. Yeah, and the second most important thing is probably increasing the limits, which people did independently anyway.

121
00:44:54.760 --> 00:45:15.160
Of course with the recent CVE, it's shown that maybe people are right keeping the limits. Right. So you don't lose too much money, but I mean it probably wasn't exploited. What I heard is that like one person was set up to do it but didn't.

122
00:45:15.160 --> 00:45:39.480
So yeah, I mean I think we should be a little bit more reckless, maybe. Can you give us can you give us a brief summary of that recent lightning CVE bug? Yeah, very brief because I'm too stupid to understand it fully, but basically you could found a channel and lie on the real founding on the channel.

123
00:45:39.480 --> 00:45:59.360
So let's say I'm making a two million channel, two million such channel, but actually it's only one million. And basically no implementation was checking that. Wow, okay. It wasn't written in the spec because when you read the spec, it's obvious for you that you should be checking that the channel was founded properly.

124
00:45:59.360 --> 00:46:17.600
But it apparently it was so obvious that no one did it. Yeah, okay. And it seems like the responsible disclosure process went pretty well with the bug and all the implementations were able to coordinate and issue fixes and publicize the need to upgrade.

125
00:46:17.680 --> 00:46:36.560
Yeah, and the improvements otherwise on on lightning are so big in every release that you get other incentives to upgrade anyway, and the fact that they publicize the problem only one month later, like push to the last people who didn't upgrade to upgrade.

126
00:46:36.560 --> 00:46:58.800
We were already, for example, one month before it was public, without even knowing that there is an issue. Right. So and you had already, I mean you had already sent out Nodal updates. So as soon as it was announced, like the latest Nodl update was already like past the past the bug, right?

127
00:46:58.800 --> 00:47:20.160
Yeah, yeah. Yeah, yeah. You tweeted something coming out of that lightning conference about that you called the executable signing initiative, with several other you know well knowing well-known lightning you know devs and people who are working on on building lightning apps and in businesses.

128
00:47:20.400 --> 00:47:58.680
Yeah, so what's this about? So that's coming from Stadicus, who is the original creator of Raspbi Bolt, which led to Raspblitz, and now working at bit at Shift Crypto Security on the Bixbox Bitbox base full mode and we were talking and figured out actually that they deliver their firmware like as a single image which contains all the programs, so Bitcoin D, C Lightning and then other things, and actually when you install Bitcoin through the like usual procedure, you download

129
00:47:58.680 --> 00:48:21.800
The package, you check the signatures and then you unpack the package and you put whatever files you find inside on your system, but no one ever tells you that what you actually unpacked from the package is really coming from the package. For example, you could imagine having a malicious software running on your computer that replaces the files on the fly when they are written on the disk.

130
00:48:21.800 --> 00:48:47.880
And so probably the package manager checks at the end if the unpacked files match some checksums which are in the description of the package, but it's very easy to lie to that. And if in case like them like various like they distribute the full system and software like as a single image, they don't even go through the package installation process.

131
00:48:47.880 --> 00:49:13.080
So we like thought well how could we guarantee to the users that the Bitcoin D L and D C Lightning and other software running on your box is actually what you think it is. So since we are competitors, it feels pretty easy to convince people that we are not colluding into pushing some malicious version of the software.

132
00:49:13.080 --> 00:49:38.960
Yeah, and we want to co-sign the executable files that are running on the systems. So basically you can run a few comments on your computer or on your model on your buildbox base or on your other device to verify that the binary files that are executed on your device are actually matching the signature which we did.

133
00:49:39.360 --> 00:49:52.880
And for that we are trying to use a software made by Frank Brown, who is one of the more hardcore cypherpunks in the space, which allows for co-signing of software.

134
00:49:53.280 --> 00:50:03.640
It's a pretty elaborate system. You can do N in M signatures. One of the base ideas is that the people should be geographically distributed.

135
00:50:03.920 --> 00:50:08.160
So one person can't be coerced into signing something which is not true.

136
00:50:08.160 --> 00:50:15.200
Sure. Because it's hard to make an attack on all the people at the same time.

137
00:50:17.040 --> 00:50:36.880
So yeah, we are at least three teams currently willing to do that, and I hope although we'll join us. That's great. That makes great sense to me. So I mean you guys are just basically reviewing each other's work and then saying, hey, this is like the legitimate binary of this of this team, you know, this particular package.

138
00:50:36.880 --> 00:50:56.560
Like it's not there's nothing malicious in here, and you guys are all competing each other, so it's you know less likely that anybody would perceive that you guys are colluding with each other, which makes sense. Yeah, right on, cool. So I also saw that you picked up the new HTC phone that has comes with a full Bitcoin node.

139
00:50:56.560 --> 00:51:15.240
You mentioned that you used to work for HTC as well. What were your impressions of the phone? And you know, do you think do you think this is the future of Bitcoin full nodes that are on phones? Or do you think it would be more secure and practical to have like a phone connected to a box at home, like you're like a Nodl.

140
00:51:15.240 --> 00:51:20.360
So the first impression, so the device was released at the Lightning Conference.

141
00:51:20.360 --> 00:51:23.080
I actually bought the two very first ones.

142
00:51:23.400 --> 00:51:24.440
Nice.

143
00:51:24.520 --> 00:51:27.420
That were ever sold in the world.

144
00:51:27.880 --> 00:51:48.920
And first impression was very good. Like, of course, the demo effect, they show you all the good pieces without going into details. So basically, you one thing which is maybe not clear for everyone is that obviously it doesn't have enough storage to run a full node, so you have to buy a very expensive big SD card.

145
00:51:48.920 --> 00:52:12.920
The good surprise was that actually the prices of big SD cards have fallen, and I could get one for less than 60 euros. Oh nice, that's not too bad. Roughly $70 for 400 gigs, which should last for a few years, maybe one year at least. You have to go to the initial sync, which was advertised as being between one and two weeks.

146
00:52:12.920 --> 00:52:49.920
I started mine yesterday evening. I'm looking at it right now, it's 38% synced. So I think I should be done on Monday, which is much faster than that advertised. Wow. And then there is all this Zion system, which is like this secure software that they run on the so it doesn't have a secure chip, like dedicated secure chip, but in ARM processors, you get a secure enclave, which is better than nothing, but but less good than a secure chip.

147
00:52:49.920 --> 00:53:15.200
Yeah, but still it's not that bad. And basically, when you are doing any operation requiring manipulating like your seed phrase or private keys or signing a transaction, you get such a weird screen which is not Android at all, which is like taking over Android, which is very limited, like it doesn't even have a current blinking cursor yet.

148
00:53:15.200 --> 00:53:43.200
So when you have to type your seed, you don't know in which box you're typing, it's pretty funny. And yeah, so it disables totally access to Android, you can't even swipe like to see your settings or anything or notifications. You get a message at the bottom of the screen that you are running in the secure environment, and supposedly everything which happens there is invisible to any malware that could be running on your device.

149
00:53:43.200 --> 00:54:06.000
Okay. Bad sides, so it's when you start initializing this phone or it tells you that it's early software and that it's beta and that you should be careful. They have a very good telegram support channel actually, so I already went there to complain on about many things.

150
00:54:06.640 --> 00:54:30.120
One being that when I first tried, it was like failing and restarting the synchronization like every half an hour, never passed one percent. And they just told me like you should format your SD card in the device, and then I remembered some old memories from back when I was working at HTC, and yeah.

151
00:54:30.120 --> 00:54:54.040
Actually, if you think about it, any camera or phone manufacturer tells you to always format the card in the device you will be using it in. Right. And since then the scene is going flawlessly, I hope it will finish. Another thing is like I tried to receive, I didn't send any money yet to the device, but I tried to receive, and the addresses on it are not even SegWit.

152
00:54:54.040 --> 00:55:16.760
Okay. I will be very loud about this when I finally I hope it at least supports SegWit for sending, even if it doesn't for receiving, but I'm not sure it will be. Is it the future? I'm not sure because like every time you pull out your phone to pay for something, you have to wait for sync.

153
00:55:16.760 --> 00:55:39.240
Yeah. Even if it runs in the background, I don't know if it I mean it will be consuming a lot of data. We'll see how it goes. They plan to implement lightning, maybe that will be better functionality, but at the end of the day, I think I will be just using it to access my dojo at home from somewhere wallet.

154
00:55:39.240 --> 00:56:03.640
What I'm planning to try is to at least use the internal Bitcoin D. So I've seen that it's support store to enable incoming connections. That's good. I don't know if it's peer-to-peer connections or RPC. If it's RPC, I'm planning to try like to run a local samurai wallet and use the full node or the phone itself for samurai.

155
00:56:03.640 --> 00:56:35.040
And one crazy idea would be to run dojo directly on the phone, so you would have like a all-in-one samurai and backend on one phone. That would be ideal in my opinion. Yeah, that'd be that's amazing. It does make sense, at least for now, maybe there's a kind of a transition phase to have a dedicated box at home, like a nodal or a casa or whatever you're running your laptop with a node launcher and then connect to it through a wallet on your phone.

156
00:56:35.040 --> 00:56:55.360
So you know that you have the always on you know always up to s up to synced and more you know space for data and just and better processing power maybe. Yeah I'm a strong believer in the in the remote control model in which your phone is just a remote control for your box running at home or in some secure place.

157
00:56:55.360 --> 00:57:33.440
Yeah I mean it seems generally more secure even if you're isolating the actions of like send and receive and storing seeds in a in a you know some kind of secure enclave or a secure chip that having it on your mobile device one I mean you can you can it's easier to get stolen right but two there's just a lot of it's exposed to a lot of you know other software and malware and potential you know then then yeah and even even very basic things like battery life I mean it would probably be terrible once

158
00:57:33.440 --> 00:58:00.760
Using it fully synchronized. Yeah absolutely makes sense all right let's finish up with this I you know I know that you're obviously big proponent of privacy, a defender of privacy, it's important to you. You have integrated Tor with with every service on the Nodl you know, it's it's kind of it seems to be an ideal that you that you hold up.

159
00:58:00.760 --> 00:58:35.800
What do you think about the promise of Bitcoin for privacy in general for all of us, like to improve the state of our privacy and kind of fight against this era of state of surveillance panopticon that we're in right now? As we know the base layer doesn't provide any privacy, so you have to run some additional tools on top of that, at least mixing I try to mix anything I can, any any money coming into my wallet or the Nodo Corporate wallet is going through mixing.

160
00:58:35.800 --> 00:59:02.120
We try we are using Realpool, so we are not paying for remixing, so we are trying to keep it mixing as long as possible until we need to spend. Yeah. Layer two probably provides a much better level of privacy, and with building this lightning private nodes and providing Tor only access to them, I think we can improve a lot of things.

161
00:59:02.120 --> 00:59:40.280
Actually, I'm I had a chat earlier with someone, and we are talking about using VPNs and Tor, and my general advice was like use Tor to access hidden services or onion addresses, but better use classic VPN service for accessing public websites because as soon as you use Tor for accessing, like I don't know, paying of electricity or your bank or just going on Google or YouTube, you expose yourself as a Tor user, which is

162
00:59:40.280 --> 01:00:08.800
Never very good because you're going through a Tor exit node. So unless the service provides a Tor Onion address, I would rather I would rather use the just a classic VPN. But for anything Bitcoin related Tor is the way to go because you can you can probably run full ETOR without even ever using any ClearNet service.

163
01:00:09.200 --> 01:00:30.880
We are actually trying to go into the direction in which you will be able to activate a setting on your Nodo which would totally block any Clearnet connection going out from the box. Very cool. But it's hard to do that in a way that it still works. Some services are very hard to torify.

164
01:00:30.880 --> 01:00:58.240
Yeah. But I mean maybe six months maybe one year we'll we'll get there. Very cool. Yeah I really appreciate that dedication to privacy and making it accessible to people in what is you know what a plug and play box basically it's been a great experience that we have a lot of users and even not users but just people who are like DMing us on Twitter and asking like did you think about this thing?

165
01:00:58.240 --> 01:01:22.480
How would you mitigate that? Like one stupid thing is when you connect the box to your network it's called Nodo.local and one guy told me like that's cool but actually your router which is probably provided by your ISP sees this name and your other computers which might be full of malware and spyware see this name.

166
01:01:22.480 --> 01:01:55.880
So maybe you should use like some generic name which doesn't make it obvious that it's a Bitcoin phone node. Yeah. So that's something we won't be doing as well from now on. Very cool. It takes it takes a village as they say, and yeah, the telegram group for Nautil is just always active, always going, and I can go in there and search through the history and I've found I haven't really had to ask many questions there, just a few, because I've been able to search through history and find answers to everything that I had questions about and the documentation you know that's on the on the website.

167
01:01:55.880 --> 01:02:15.000
The combination of those two answered all my questions for me and I've got everything running that I you know wanted to get going. So I'm looking forward to getting the dojo software and hooking up the samurai and using Whirlpool. I've been using Wasabi for the most part. And yeah, so I'm looking forward to kind of dipping my toe into the samurai world.

168
01:02:15.000 --> 01:02:29.080
Yeah, man. All right, thanks so much for the time today. I'll let you get off and finally finish your day. I know you've had a long one. I appreciate you staying up and hanging out with me and talking bitcoin. I think everyone's gonna enjoy it. Thanks for having me. All right, take care.

169
01:02:36.040 --> 01:02:56.440
All right, all right, all right. Thanks to Keto Minor for his time. I really do appreciate it. Some of my favorite podcasts are always hearing from the great builders out there, the builders who are creating our Bitcoin present and future. It's amazing to talk to them to watch what they're doing and just to be a part of it.

170
01:02:56.440 --> 01:03:16.720
So what questions arose for you during this discussion? Let us know on Bitcoin Twitter. Keto is at Kito Miner, K-E-T-O-M-I-N-E-R. And I am at Citizen Bitcoin. Tag us both. Let us know what you thought. Ask questions. Just let your fellow Bitcoiners know what you enjoyed about the episode.

171
01:03:16.720 --> 01:03:35.360
That's really the best way to support the show is to share it and spread it around. I've got a couple more Bitcoin builders lined up to talk to in coming episodes, including Cory Klippsten of the soon-to-launch GiveBitcoin, and Jeremy Welch, founder and CEO of Casa.

172
01:03:35.360 --> 01:03:45.600
Really excited about that one. I wanted to get both of the plug and play node providers on the show relatively close to each other, so we can hear from them.

173
01:03:45.740 --> 01:03:50.840
I am a customer of both of their businesses and it'll be awesome to hear from Jeremy as well.

174
01:03:51.280 --> 01:04:01.120
So be sure you're subscribed so you don't miss those. And if you're new to the podcast, I invite you to dig into the growing archive for some great episodes.

175
01:04:01.460 --> 01:04:05.600
I'm so excited to be here with you at the dawn of this Bitcoin renaissance.

176
01:04:06.240 --> 01:04:27.200
That's it for this week. Take care out there, Bitcoiners, wherever you happen to be in the world.
