WEBVTT

1
00:00:20.800 --> 00:00:40.080
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 how's it going out there, Bitcoiners? Wherever you are in the world today, it's another beautiful day at the dawn of the Bitcoin Renaissance. I've got a great conversation with Jeremy Welch, founder and CEO of CASA for you all today.

2
00:00:40.080 --> 00:01:01.920
But before we dive into this great one, I've got a word from our sponsor of this episode. Give Bitcoin is creating a clever new way to turn your pre-coiner friends and family into well-educated hodlers. You can give them time-locked Bitcoin. It's time-locked for at least one year up to five years, and your hodler to be friend will receive month by month for that first year a world-class Bitcoin education.

3
00:01:01.920 --> 00:01:29.600
I'll be giving Bitcoin and that world-class education to friends and family using GiveBitcoin this Christmas, and I encourage you to do the same. I think it's the ultimate gift that keeps on giving, and unlike most holiday gifts, it certainly will not be forgotten a decade from now. You'll, in fact, be an absolute hero. GiveBitcoin has solved the pre-coiner to bitcoiner equation. It's give plus time lock plus educate equals bitcoiner. The beta was officially launched last week. You can find it at beta.givebitcoin.io.

4
00:01:29.600 --> 00:01:48.560
So check out GiveBitcoin right now and start minting new hodlers in your life. Alright, let's go.

5
00:01:48.560 --> 00:02:09.160
Jeremy Welch is founder and CEO of CASA, a Bitcoin company making security and self-sovereignty accessible to everyone. In this episode, Jeremy and I discuss the founding and building of Casa. We get into the details of CASA products like the Key Master, Seedless Multi-Sig, the Casa Node, and their new Bitcoin inheritance product, Covenant.

6
00:02:09.160 --> 00:02:29.000
We also discuss the Lightning Network, security, privacy, and a Bitcoin future. I enjoyed this conversation with Jeremy immensely. Hope you all enjoy it as well. Let's dive into this one.

7
00:02:29.000 --> 00:02:49.880
All right, I am super excited to welcome Jeremy Welch, founder and CEO of Casa, one of the best Bitcoin companies out there. Jeremy, welcome, man. How's it going? Going well. Thanks for having me on, Brady. You know, my my listeners definitely know at this point that I'm an enthusiastic CASA customer. I mentioned Casa a lot on the podcast. My Casa OneNode was in the first batch that was delivered out about a year ago now.

8
00:02:49.880 --> 00:03:09.560
Amazing. Amazing. Yeah, it came with the gold two of three seedless multi-sig, which is you know 10x better than any multi-sig experience that came before it for sure. You've added Tor support, SATSAP. You've announced the Casa Node 2. You guys have just put been putting out like an impressive output of you know high-level product over the past year.

9
00:03:09.560 --> 00:03:28.440
I'm sure it's been a bit of a blur for you, but like how's you know your experience been the past year? Kind of putting all this stuff out of CASA. It's been great. You know, I'm I'm extremely lucky to be able to work with and learn from not only some of the smartest people kind of in the Bitcoin space, but just like smartest people in the world.

10
00:03:28.440 --> 00:03:48.480
You know, it's it's it's always it's one thing to be able to kind of pursue passion projects and pursue something that's already an interesting project. It's another thing to be able to just work with amazing people, period, on anything. And so I've I've been very lucky. It's been a lot of work, it's been a lot a lot of stress, a lot of stress and a lot of travel.

11
00:03:48.480 --> 00:04:09.680
I think I did over 150, 175,000 miles, just like crazy amounts of travel with a lot of well a lot of different cities and because we have customers all over the world now, and then we have team that our team is fully distributed. And so because of that, there's just it's a lot of work, but we've been very, very happy with the output and with the customer.

12
00:04:09.680 --> 00:04:27.840
I think the most rewarding thing, I think that people don't realize how how the thing that keeps us going is knowing that our customers are enthusiastic and excited and you know love the products and give us that feedback, right? Like that that's what makes it worth it. So yeah, so it's it's been a great year though.

13
00:04:27.840 --> 00:04:52.320
So what what is your professional background? Is Casa the first company you founded? Casa is not the first company I founded. I've been building companies now for over a decade and in a variety of different roles, but I in a f I founded a few companies. So the if we go back about right at a decade, I was actually pretty heavily in the ad tech industry.

14
00:04:52.320 --> 00:05:19.200
I had dropped out of school, and I was at I went to Duke and I studied political philosophy there. I am technical. I you know, I grew up programming and I worked at an ISP in high school, but I specifically ended up studying political philosophy, income systems theory, and I'm really really interested in cybernetics and it's kind of a product view on the world, but I like you know, you have these systems and if you change like one piece, like if you insert Bitcoin into the system, right?

15
00:05:19.200 --> 00:05:38.440
Like what what happened? And so I've taken a lens or taking a view towards thinking in those terms, but you know, steering back to this comp question of companies, I left school because I just wasn't as as engaged as and I got kind of addicted to startups. And I joined this company called Invite Media.

16
00:05:38.440 --> 00:05:57.640
We were building a demand side platform which is for advertising, which you can think of as a Bloomberg terminal or just kind of almost like e trade. It just makes it really easy to buy ads. Sure, sure. And we sold that into large advertising agencies. And then we sold that company to Google in 2010. I was an early employee. I wasn't a founder there, but I learned a lot from the founders.

17
00:05:57.640 --> 00:06:35.720
I worked closely with them. And I was a Ford deployed engineer there and then worked on some product stuff around data sales. So I was inside the belly of the beast right like I saw a ton about how how the data sales work how data collection works how everything worked at at Google and then left after a year went back and finished up school it was around that time that I found Bitcoin and then did a you know series of projects after that that led up to creating CASA and created CASA you know again I'd seen the kind of cycle of raising money and dealing with investors and building product and building

18
00:06:35.720 --> 00:07:07.560
Teams CASA was specifically a problem that I had and that I was concerned about long term custody and also you know I think there's still a bunch of massive opportunities in terms of new architectures of building new types of apps. We don't believe that Bitcoin is only a financial revolution we in in kind of a civilization level revolution if you think of like capitalism as this lower level operating system piece but I we think of Bitcoin as being also kind of a computing revolution and so a lot of things are getting going to change out of this.

19
00:07:07.640 --> 00:07:27.200
So y you mentioned, you know, you kind of brought us up to the Bitcoin moment. What was your red pill moment and you know, who were some of the Bitcoiners that helped you get up to speed on what's happening? Yeah, I would say that that there wasn't there wasn't kind of a singular red pill moment for me. I found a white paper.

20
00:07:27.200 --> 00:07:56.720
This was in around 2012, middle of 2012. I went through kind of a couple waves of learning about it, initially investing and thinking about it, and you know, again, from a philosophical standpoint, I did a lot of reading. I was already reading you know, a lot of philosophy papers through school and one of the one of the notable things about philosophy papers is that they're frequently very short and succinct, right?

21
00:07:56.720 --> 00:08:24.240
They like they make their point, there's no additional fluff, and same thing with most academic papers. So that was one of the beautiful things about when I encountered the white paper the first time. It was just kind of directly reading that and thinking about it as as a core material, like that it I was impressed not just with the system design and with the architecture and with the kind of thes that were being drawn out and that it was working, I was also really impressed with how it was presented, right?

22
00:08:24.240 --> 00:09:02.280
It was it was it was kind of a revolution on multiple fronts for me, and that it just felt so succinct and forward. And then I ended up connecting, I was kind of just just quiet and on forums and other not really connecting with people in the real world, and then I connected with Matt Carollo, who was at the time was at UNC, which was a you know, fifteen miles away, and we put this together this Bitcoin event at Duke, this little Bitcoin conference, and we were trying to educate other people and try to get more people involved and trying to kind of create a meet space, like real space community around it, because most of the people that I was engaging

23
00:09:02.280 --> 00:09:36.840
With at the time were were you know through twenty thirteen were just online and so it was it it kind of came in waves for me. It was like the initial breakthrough, the initial thinking, the initial understanding and then several more waves through twenty thirteen writing some you know some of the waves and crashes that we went through and then into 2014, you know, meeting Matt who who worked as a as a core contributor and just talk having a ton of conversations with him and just kind of continuing to get deeper and deeper and deeper the whole way along.

24
00:09:37.160 --> 00:09:58.520
And I remember sitting I you know it it's I've I've evaluated and seen like I remember sitting there at the Ethereum pre-sale and not buying in and not not my my core thought around Ethereum is there was like a weird thought around from an investing perspective versus a philosophical perspective and this will be like a probably a controversial statement.

25
00:09:58.520 --> 00:10:18.040
But I do believe that like there are you know we can re-architect a lot of applications in new ways and more distributed ways. And so the kind of spirit of Ethereum of saying hey we want to be able to architect apps in this more distributed way like I thought that was really cool.

26
00:10:18.040 --> 00:10:36.520
But from an investment perspective at the time I remember thinking like well, you know, if it's not it should be possible for Ethereum to operate at you know it should be it should be possible for Nether to be at like one dollar or two dollars or fifty cents in the system to still operate.

27
00:10:36.520 --> 00:11:09.440
Like it's not there's not a hard cap. There's not a security model that requires the price to be very high. So it'll probably be a bad investment. Right. And I and I remember you again like this was just waves kind of through and you asked about red pill moments there wasn't any singular one but I you know I was trying to kind of come at these the kind of questions that were being raised from first principle view from like really thinking through the kind of core pitches and not just from kind of who was building what or who was what the flashy pieces around this were.

28
00:11:09.440 --> 00:11:28.000
And I was just very lucky to run into a lot of different people along the way and have had a you know a lot of fortunate experiences to understand all this stuff from multiple angles. Yeah it definitely seems like the rabbit hole is sort of endless and we're all just you know getting red pilled over and over again.

29
00:11:28.000 --> 00:12:04.800
And I think it's just going to continue that way, you know, for the next decade or two as as this thing kind of grows up and matures into whatever the hell it's going to become you know yeah totally I agree with that. Yeah. I mean I think it's gonna be I think it's gonna be several decades worth of I don't think that most people have a full grasp on what a most people already don't have a full grasp on what how fundamental capitalism is to the kind of organization or structure of our civilization much less a view as to how Bitcoin would affect that core position.

30
00:12:04.800 --> 00:12:42.920
And so I think that that to really get at what the impact will be you have to start getting at what where things already are with with just kind of dependence on capitalism and growth position we're already in and so there's there there are gonna be waves of this stuff and they're gonna be you know we've already seen it's happened much faster than I thought it would in terms of kind of broader awareness especially amongst government and amongst some of the bigger players in the world yeah but especially during some of the crises that are bound to happen the next few years we're gonna see we're gonna see these like you

31
00:12:42.920 --> 00:13:21.000
Know waves of understanding happen so it's gonna be it's gonna be an interesting ride yeah absolutely it it has been already and it's just fun to be aboard and part of it and watch it all happen like it's just it's fun to get up every day now that you know I've got Bitcoin in my life just you know working on it more and more spending more and more time on it taking up more of my brain cycles and it's kind of amazing how it just gets into your mind and does its thing and just incentivizes its you know its own growth so beautifully totally yeah all right let's get back to Casa for a bit you know the products and services are amazing but

32
00:13:21.000 --> 00:13:42.120
The reason that I insta ordered that that Casa One node and the gold service as soon as it you know came out on Twitter is the team that you've built around you know Jameson Lopp, Elena Venova, Kelly Lyons, Nick Newman, Brian Lockhart on product and I think your designers deserve a particular shout out they're amazing. Scott Hurst and Derek Derek Huey they're they're just rocking it out man.

33
00:13:42.440 --> 00:14:21.440
Beautiful stuff. So can you can you talk a bit about how you approached building the team at Casa? Like what about your pitch resonated with some of the best people in the business? Yeah. So again all those people I'm I'm very fortunate to be able to learn from from these people and the many many other engineers and operations team and everybody I'm very very fortunate to kind of work with and support and learn from these folks but I the way you know we had we when you're building a company you have these kind of core functions and then you also have like very specialized functions and you it's

34
00:14:21.440 --> 00:14:42.560
Always kind of an art more than a science in terms of how you build up a team. Some of it is luck and opportunity some of it is persistence some of it is you know you have a specific need but the way that you shape that need like sometimes one person can kind of fill two needs sometimes one person can can only feel one need but they do it so deeply that that it's it's just like an absolute fit.

35
00:14:42.560 --> 00:15:06.240
And so each person that has joined the team has been very different in terms of how they joined the team. You know the core pitch has always stayed the same in terms of our long term pitch. Yeah. But each person is is definitely been very different. And so like you know I've known there's some people so Scott Hurf for instance our head of design is one of the best designers in the world.

36
00:15:06.240 --> 00:15:44.480
It's it's it's crazy that we are able to work with him. But he's been a friend of mine for a long time for over over a decade and we've just jammed on product and you know we always catch up several times a year and he just so happened to be kind of shifting out of one role and around the time that we were looking for design and I was particularly passionate about I think that this that core private key management and the applications built around private keys and private keys as identifiers and as login etc are are you know represents this new opportunity that will really drive

37
00:15:44.480 --> 00:16:07.240
The next 20, 30, 40, 50 plus years of the internet and of software. Right. And so and so I kind of presented it to him that way as you know, you're you're gonna be on the ground the first, which is both kind of scary, but also a real challenge and really exciting for designers to be able to bring the core process and principles that they already have into these new areas that just need a lot of help.

38
00:16:07.240 --> 00:16:29.080
It's like it's like you know, you're you're a medic and you're getting thrown right into a war zone effectively, right? Like there's there's gonna be no shortage of people or into the emergency room. There's gonna be no shortage of opportunities to practice your trade and apply, and but it will also be very intense. And so you know, he he knew Derek and he brought up him and they've had a phenomenal time with them.

39
00:16:29.080 --> 00:16:48.280
Jameson was was slightly different too. We needed someone that was gonna be mixed of backend server side security. I knew of Jamison. We actually we lived in we both lived in for a little while in Raleigh Durham, but we didn't know each other at that time. And I actually reached out to him kind of cold.

40
00:16:48.280 --> 00:17:09.320
We both were kind of in the Carolinas, we were working part of the time in Charleston, and I was traveling a bunch of New York and San Francisco. And I knew that he was he was a bit go at the time. But I kind of reached out Cole and said, look, like you know, we're building multi-sig tools. You've been working on multi-sig for a long time on the business side.

41
00:17:09.320 --> 00:17:36.200
You know, I'm sure you have questions and problems and things you'd like to build on the personal side, you know, we should definitely have discussion. And he was immediately receptive and we it took us you know several months to align and just think through kind of everything we could build together. But that was another one that was like it was kind of unique in in that we had enough overlap that we were able to connect and then but then it took us a while.

42
00:17:36.200 --> 00:18:00.720
You know, it w there there was already the kind of like potential was just there, right? Like the path that we were going on was also a path that he saw benefit from improving multi-sig broadly and bringing better security broadly and he'd been working on the institutional side and now he brought it over to the personal side and so yeah I mean it's it's just been different with everyone and but the kind of core vision has stayed the same.

43
00:18:00.960 --> 00:18:19.040
I'd love to hear a little bit more about the Casa Node 2. Sure. I ordered mine I'm looking forward to getting it. It's a significant hardware upgrade. The Raspberry is like 50% faster than the Raspberry on all the benchmarks. There's an SSD on the software side there's the all new node OS.

44
00:18:19.040 --> 00:18:40.800
So can yeah can you just talk about more about the functionality four gigs of RAM which is very far over the one gig that the first one had. Yeah man that's a forex. Yeah we're we're excited about the new Casa node we you know we when we first launched the Casa Node one I mean it was really first of its time right like nobody nobody was doing that.

45
00:18:40.800 --> 00:19:14.880
There were a few node companies, Bitcoin node companies that are out there, but kind of at a mix of the usability level which was the goal was to be something more Apple like that even my grandmother could set up if she wanted to at that level and then also kind of bridging gap and especially around lightning experience there really was nothing else like that. And we made we tested a bunch like we do with with all of the products that we build we tested a bunch and we made the choice around the Raspberry Pi board Raspberry Pi 3 because you know you're a startup you have limited resources you want to invest time in in the things that are really going to have the highest leverage.

46
00:19:14.880 --> 00:19:36.440
And for us, that wasn't you know kind of core board level or and even around the board. We actually did test some of the other faster boards, Pi and 64 boards that were out at the time, and but they were just they were unreliable. They they sometimes would fail. We saw a bunch of failures in our tests, and the Raspberry Pi 3 had been out a long time and had just really rock solid reliability.

47
00:19:36.440 --> 00:19:58.120
Right. But it was just a little slower. Yeah. So we went with that one originally, and then we just knew that there was a lot of software work to be done around the experience around the UI, around making it easy to onboard setup, get running, to use Tor and you know connect from outside to get to something like a SATF app, right?

48
00:19:58.200 --> 00:20:20.040
Like all of this kind of the full stack experience just wasn't possible, nobody was doing it. But we saw it as critical to being able to be able to explain to people, and especially kind of less hardcore Bitcoiners or more mainstream type people on why why it was beneficial to use CASA and why it was beneficial to run a node, period, not even just not even if you're running CASA.

49
00:20:20.040 --> 00:20:46.360
And so the node blew up and we did we kind of or bucketed a big chunk of them already for our major multi-sig, kind of more premium customers, and then we opened some to the community and we just sold a ton of them. And so we immediately started investing more on on the node and into software, but we knew we knew that at the time like there were a bunch of choices that we knew were issues.

50
00:20:46.360 --> 00:21:05.640
We knew like the we got a lot of flack around the little cable that came out and reconnected. Yeah, but the case, I mean the box was just like really clean, it was really nice, it was really easy to get into and out of. And it made it very easy, like without having to use a screwdriver to assemble, disassemble, you know, if there were issues.

51
00:21:05.640 --> 00:21:43.680
And so we you know, we went with it. But it's it's funny, like people have kind of found fall-up and all these things that we know we already know it's an issue, like we wouldn't ship it if we didn't know that the issue was there but but it was a worthwhile trade-off so the nice thing about where we are with the cost of node too now is that we're finally able to kind of take aggregate all these things that we already knew were issues and that we already have thought about and been aware of and then kind of start smoothing those out and simplifying those devices always been built for people to be an early device a you know it's still very reckless lightning period using any kind of node is still very reckless there are lots

52
00:21:43.680 --> 00:22:21.760
Of kind of open question security wise routing your own transactions is going to be a thing but it's still very early in that space too and so we've we've kept that distinctly separate from the rest of the multi-sig product which is built the key master product which is is built you know just for super high end security and you know sinking with your hardware keys and for protecting you know millions of dollars worth of Bitcoin yeah do you think the node will ever be like able to be connected to the multi-sig wallet so that like you know the transactions are being verified on your own node et cetera

53
00:22:21.920 --> 00:22:58.200
Like absolutely absolutely that that's the goal that's the goal. Yeah I mean the goal is for this all to shift into a singular or a full stack platform right the goal is that you are able to run some of this infrastructure on your own you know we can help out or we can support and you may have failover with some centralized or some some cloud options I wouldn't even call it centralized it's just cloud because it's it could even be in your local city in the cloud but it's it's you know I we want to have this kind of more edge computing and cloud computing mix.

54
00:22:58.200 --> 00:23:23.000
And I do think though that that having that dependency or having the ability to choose to route everything through your node is is the right way to do it. The problem with that right now is that there's still a lot, a lot, a lot of issues with connectivity. Certain functions on Bitcoin and it depends on which which version of Bitcoin you run, but certain versions of Bitcoin if you are running over RPC there are certain security issues that come up.

55
00:23:23.000 --> 00:23:53.480
So connectivity to Bitcoin becomes a little bit more of an issue. We were able to actually smooth out some of that a little easier with lightning before Bitcoin and then there's like there's constructing the transaction making sure that you're that you are that the full kind of construction and management of the transaction happens properly which is all of our key master side and then when you kind of bridge the gap between that and connecting to your node you know it again there's a lot that can go wrong.

56
00:23:53.480 --> 00:24:31.480
We also don't have we don't have any we view a lot of the external analytics platform you know most of the devices you have in your home everything from phones to your TVs to like all these other products even your car they have these analytics packages that enable the end manufacturer to monitor effectively monitor the device from anywhere and we don't have any of that right so so we're operating off of a function where customers reach out to us if they have a major issue and that just makes the product development process much harder but it also makes the security process much harder because we have to test a lot of the edge cases

57
00:24:31.560 --> 00:24:59.680
Well before it ever gets into a customer yeah, because you guys can't really like you guys can't really you know connect to the nodes directly. I mean you can, but that's obviously like a last you know, last gasp kind of situation that you want to you want to do. So you want to try to keep like prevent that from happening at all. Yeah, and you can view it as like there are all of these pitfalls that people don't see where that we are seeing and that we're being very careful about, and it's a very narrow road to walk.

58
00:25:00.240 --> 00:25:24.160
So you know, we do have this ability to where you can like hit a button and send logs and they're encrypted. And you know, we can we can help debug off of that, but you're you're making an individual choice, and we're still don't have like a direct connection to the device. You know, any any usability improvements, you have to be again very careful with the trade-off and security too.

59
00:25:24.160 --> 00:25:44.400
And we've done that kind of at every level and are aware of the exact position that that we've built, but it is a very, very fine line to walk, very, very careful consideration and in terms of what we're providing to customers right now and what we want to provide in the future and kind of getting the path to get there while minimizing any you know risk of loss.

60
00:25:44.400 --> 00:26:11.600
Yeah. So you I mean you guys have customers who a lot of customers who aren't necessarily super technical but do have an advanced understanding of Bitcoin and maybe want some more advanced features like UTXO selection or like tools to help with routing payments, or like you know, maybe even running a routing node, block explorer powered by your own node, easy way to DCA straight to your own multi-sig, maybe even like mixing services, stuff like that.

61
00:26:11.600 --> 00:26:36.840
I mean I know that's all like you know, down the road to kind of stuff, but what's your position on even adding or considering some of this more like advanced functionality you know, and trying to like balance that with the usability to you know spur the mass adoption that you guys are, you know, kind of the mass audience you're trying to get to? Sure. I mean, I think that the way to think about it is that we want to enable as many apps and custom configurations as possible on the node.

62
00:26:36.840 --> 00:27:03.640
You can do that in one of two ways. You can do that in a way to where you build everything super custom, or you're just running, you know, existing open source software. You might make it a little bit easier to run by kind of having a wrapper around it in some capacity, but you're you're just running something existing and you're using the existing open source UI, and you're not adding any any any kind of additional functionality.

63
00:27:03.640 --> 00:27:25.960
And you know that is a path to take, and that's perfectly valid. On our on our side, the way we think of it is we are trying to take a little bit more of an Apple style approach in the sense of really trying to think through kind of a full stack, what are the unique things you can do, and something like Stats App is like a perfect example of that, where you can get these unique experiences in terms of payment and it just works, right?

64
00:27:25.960 --> 00:27:50.920
And you don't have to think about it. So the those custom configuration options and some of the custom apps or or some of the just like, hey, let me install whichever app I want. Some of the trade-off with that is that you know, then you have these edge cases that pop up because you have these kind of a not an infinite but a near-infinite set of possible configurations, right?

65
00:27:50.920 --> 00:28:11.960
So what we've tried to do with with our stack is is you know, you can you can open the device and you can modify things anytime and you can play on the command line, but in a default state, we are creating kind of X number of options that for the more average mass market user, it's it's it's more than enough for them, but it's also it's like easy to use.

66
00:28:11.960 --> 00:28:35.520
And for someone that's not that technical, it works very well. There were already options on the market where you could just build your own node and you could use a lot of the open source tech and run that. And so the path to getting there to still offering those more advanced options while still maintaining the usability is actually a path of doing something like an SDK or like an app store.

67
00:28:35.520 --> 00:28:54.320
You know, it's not a path of just building the individual apps and just shipping them, it's actually a path of making it easier for anyone to build an app or build you know integration into the CASA node. And so that's that's part of the challenge with what we're doing is like you know, we're we're operating off of significant scale.

68
00:28:54.320 --> 00:29:24.880
We've shipped to over 65 countries and we've shipped a lot of nodes. So we're operating off of significant scale one, two, with like a very wide array of kind of usability and developer and kind of user experience, both technical and non. And then on top of that, like kind of multiple applications and multiple configuration options, and the this the way to do that at scale reliably is to is to then have a common interfacing layer to the node.

69
00:29:24.880 --> 00:29:54.720
And so it's not always you know super custom for every single app doing very specific things, it's actually all of those apps are using a kind of common language or a common SDK or a common API layer. So that's that's where we're headed is building towards that. You know, and we in and you will see as a result of us taking this approach, you will probably see and continue to see some other companies you know release a few features a little faster than us, but our goal is that when we do release those features, again, it just works.

70
00:29:54.720 --> 00:30:21.000
And you do have some of that long-term scalability that's important. And that's again what we recommended. You know, there's several other companies in space, Nodal and others that we've recommended if you want, you know, some of the more custom configuration options. You can grab some of those today and they work. There are some trade-offs at times that things go wrong, or you know, whether it's it it it's device failure or just configuration, and you have to why there's a there's a lot that they can go wrong as you start adding more complexity.

71
00:30:21.000 --> 00:30:50.600
But and you're not kind of operating on those simple foundations. But some people want that. Some people want the more advanced configuration options. And they're willing to deal with the kind of setup process along the way. But we are our goal again is to bring the simplicity and kind of advanced functionality, but in a way that is much easier to support, much easier to scale, much easier bring to kind of a wide audience, and doing that is we have to be do that a very specific way.

72
00:30:50.600 --> 00:31:09.880
Yeah, that makes good sense, and that's like really exciting to hear. Yeah, I mean, I can see that, I can see the vision, and I you know, it watching it unfold over the next few years is gonna be really fun. On the SATS app, like it pairs with your lightning node. I can send and receive on on Lightning with the SATS app.

73
00:31:09.880 --> 00:31:29.160
I've used it, you know, dozens of times at this point, maybe even a hundred times. The SATS tag is really cool. But yeah, like, oh, and I gotta mention to you, because you'll get a kick out of this. The node heartbeat is like part of our family's morning now. So we get up in the morning, we're doing we're doing breakfast at the table and stuff.

74
00:31:29.160 --> 00:31:50.320
I set the phone on the table, and the kids, you know, they each have to do it, you know, two times. So we send two heartbeats every morning. That's awesome. Yeah, they love it. And so it's and they they've been starting to learn more about Bitcoin because of it. And this I don't know, it's like this sort of intangible thing that you know, it's one of those, I guess you know, Steve Jobs would call it like a something a delightful, you know, kind of user experience.

75
00:31:50.320 --> 00:32:16.160
It's just like a little delightful thing. So it, you know, congrats on that. It's pretty cool. Yeah, totally. And that's and that's a really good example. The heartbeat is a really good example of that kind of design approach because it is something that is so subtle, it's actually fairly simple to execute, but doing it at scale and doing it in the right way, doing it in a secure way, is all very hard.

76
00:32:16.160 --> 00:32:35.040
Like, you know, there are probably 50 or 60 or 100 different pitfalls that you could fall into that we evaluated and didn't fall into in the along the way to build such a simple thing. And it seems like it, you know, whenever you look at it in hindsight, it seems like one of these features, it's like, oh yeah, duh, that makes sense.

77
00:32:35.040 --> 00:32:56.960
Right. You know, it's it's probably you know, code-wise, it's probably easy to implement. But I can't tell you how many hours I mean that so from from to give you an example of kind of concept to execution on on heartbeat. Heartbeat was an idea that I actually stumbled into and came up with probably three years ago.

78
00:32:56.960 --> 00:33:16.400
Probably three years ago, and then we built the like the very first. So we actually had a right now we're on Casa Node V2. We launched the CASA node last year. The year prior to that, we actually had another version that was our very first version, which we just called the KAFA computer.

79
00:33:16.400 --> 00:33:40.440
And it wasn't we didn't really release it publicly. We did a bunch of experimenting and definitely saw a bunch of people that were interested in the device, but we knew that there were some key management challenges around it, and we wanted to tackle that first and dig into that first. But around that first device, we realized that there would be these issues of uptime and needing to make sure your device was running.

80
00:33:40.440 --> 00:33:58.680
And it was around that time that as I was like mapping things out, I was like, Oh, that would be great if you could do this kind of regular ping. And there were a bunch of different variations on how you could do it. But at the time we didn't we really didn't have an option. You know, Lightning wasn't wasn't I don't even know if the lightning paper was out.

81
00:33:58.680 --> 00:34:24.520
I don't think lightning paper was out then. Yeah, I don't think it was out then. So lightning wasn't even a part of it. Then we got around, you know, one two full two full years later, and we everything is already built, right? And we were sitting there around talking about some of the different problems with the node and when you went to go do payments and the simplicity of SATA.

82
00:34:24.520 --> 00:34:53.640
And we were just kind of going back and forth on like, oh man, I guess there's this uptime thing, it'd be great if there were and I as as I was like literally or someone on the team was literally saying, Oh, it'd be great if there was a way you could I was like, holy shit, wait a second, we do have something around this because I thought about this like two years ago. So I went back and found my old nodes and we got those out, and then we looked at a bunch of the you know tech that we had today and everything we already had built around the cost of node and lightning, and then we came up with the solution that you see now.

83
00:34:53.640 --> 00:35:19.680
And we did there were there are variations to where you could do it a little more automatically, but then that actually takes away some of the engagement and awareness of the user. So it there's an interesting thing to where some people have said, okay, why don't you just make this automatic every day? And the reason, part of the reason for that is it's not just about doing a regular ping, it's actually about the interaction and awareness of the user to be aware, like, yeah, my node's running, I'm confident in my node, it's up.

84
00:35:19.680 --> 00:35:39.920
It's the uptime is great, and I don't need to check it. And if you just automate it all the time, then there's less of that that awareness. Sure. There's also a side of even you know, doing it in a way that was we did it in a way that was privacy preserving, and that actually took us a while to do it over tour.

85
00:35:39.920 --> 00:35:59.600
And there are ways to do it, so it's actually a little more invasive and could potentially do more, but there's just a lot of nuance there. So I just think that that's a good, you know. I'm glad you brought that up. There's just a lot packed into it. It seems like such a simple, simple feature, but it is something that is that is it was very hard to build.

86
00:35:59.600 --> 00:36:21.600
It took you know over two years to come to fruition, and you know, towards the end of that build out, it was a full team. Like everybody had, you know, kind of pieces of ideas and problems they were solving leading up to that, and it was a full team effort to get it that simple. And we're hoping to do that. We want to do that with the ability to build on top of Cost Node, we're gonna do that with other types of applications.

87
00:36:21.600 --> 00:36:45.040
We're just you know, Costa ultimately is a security and privacy company, and the way we've you know set up the business model is it's around like you do kind of pay a flat yearly fee and we just give you this toolkit, and then we want to build more experiences in that, you know, similar to the node, similar to the heartbeats, to make security an easier and more engaged process for you know for people globally.

88
00:36:45.040 --> 00:37:17.480
Yeah, man. So what what is the future for SATSAP? Like, what do you if you can, you know, divulge any whatever generalities or anything? Like what what else are you guys gonna do with it in the coming years? I think SATSAP is is, you know, you can think of it as a little bit more of the same, but also a little bit of expansion in the sense that you know, a lot of the one one approach around design is that you actually want to kind of use the same toolkit and same narrow focus and just do more things with it.

89
00:37:17.480 --> 00:37:37.480
But you don't what you gotta be really careful not to like bolt on some you end up with this kind of Frankenstein if you just start bolting on random features. So yeah. We think of SATSAP, the focus of the app is supposed to be super simple you know, Bitcoin payments and earning. And so you can earn SATS back.

90
00:37:37.480 --> 00:38:01.720
You can do that in a couple different ways, mostly around the node, connecting the node, running regular heartbeats. We do have some other ideas for stuff we want to do in terms of earning SAS back, and so we are working on some different options for that. We've talked about whether we want to do embed neutrino and make it easier to run lightning even if you didn't have a full node.

91
00:38:01.720 --> 00:38:21.480
We're not really going down that path yet, but that is an option. Right now you can download it and if you don't have a node, you just run a regular Bitcoin wallet, but it's still non-custodial. There's a lot. There's there's other integrations with other liquidity services that we can make it easier to just, you know, manage your node and also have, you know, any of the liquidity questions.

92
00:38:21.480 --> 00:38:54.720
We don't want to provide any liquidity services ourselves, but we would make it easier to plug into some of these other companies that are working on problems around that. So you know, you're talking about adding more features around managing the node and managing lightning and managing Bitcoin and then also kind of more ways to earn and more experiences around that while also keeping it just pretty narrowly focused and tight around the simplified experience and then we're trying to embed more and more on the more complicated in-depth experience, kind of at the key master level and getting into multi-sig.

93
00:38:54.720 --> 00:39:19.120
That's awesome, man. Yeah, well let's talk about multi-sig a little bit more. Like today the my app just updated, and so I've now I've got the option to move migrate my my mobile key over to a second hardware wallet, which is cool. Definitely going to be taking advantage of that. So yeah, I mean, what's what have you like heard from customers about their experience with with multi-sig?

94
00:39:19.120 --> 00:39:45.360
I mean, mine has been great, it's been super easy. Have have people who are you know aren't maybe as technical or whatever, like gotten back to you and you know, reported great user experiences, and maybe what are some of the like the you know, maybe suggestions for improvements that you've been hearing? Sure. So a lot of people, first off, just a lot of people don't understand the full purpose of multi-sig or the reason why it's important, and so yeah, we have had to do some education around that.

95
00:39:45.360 --> 00:40:09.440
James Amopp just recently posted a an overview of Shamir's secret sharing and why and a lot of that pitfalls around that is similar to the heartbeat cost cost of node, and you know, we've evaluated just about everything in the space, and there's a lot of different combinations of Shamires that you know people try to use.

96
00:40:09.440 --> 00:40:28.800
There's even different combinations of multi-sig with Shamir, there's different kinds of models around the different kind of models around, you know. Do you have do you yourself manage all of your keys? Do you give a key to a family member? Do you give keys to other business partners?

97
00:40:28.800 --> 00:41:05.320
Do you have you know an outside company or an outside lawyer manage a key and then you manage keys, and we evaluate a lot of different options before settling on where we are now. And we did bake that into a report called the wealth security protocol. We're lucky to have you know another fantastic person in the space, Jacob Lyles, who wrote the Glacier Protocol, which is one of what was multi-sig standards and multi-sig protocols way back, and a lot of early exchanges actually used his, their their model to do their early cold storage.

98
00:41:05.320 --> 00:41:30.280
Jacob joined the team about a year ago and worked with us to help us build out a really clear documentation around the model that we built, and that's in this wealth security protocol. So it outlines the 13 different threats against your Bitcoin and how multi-sig mitigates those and all the different design choices we made and all the design choices we you know we did make in a sense of like the things that we decided not to do and why.

99
00:41:30.280 --> 00:41:49.240
So I just outlined that because there's a lot that we can cover here in that quite in this question. And there is a full document. It's it's about I think it's about a 40 page document that covers a lot of this. So we encourage everybody. If you just type wealth security protocol or cost of wealth security protocol in Google, you'll see it. And it is you can download it. I think on our website, I think it requires an email.

100
00:41:49.240 --> 00:42:10.840
We can go to GitHub and get the full PDF, and we have it, you know, it's up. You can grab it. So there's a lot to dig in there. And then, but in terms of the feedback that we've received, a lot of it has been very positive. A lot of people excited to finally have security options, again, similar to the heartbeat, similar to the node. We didn't want to ship something that we didn't think was at a security level.

101
00:42:10.840 --> 00:42:28.880
And for us, you know, we only make money if people are secure and happy and you know have money to continue buying from us, right? We don't have a business model mixed in. We're not making money off of trades, we're not making money off of other types of financial products or anything. And I think that there is something really important around that.

102
00:42:28.880 --> 00:42:48.080
And so we've made very specific choices. And so we do we have gotten feedback from customers that they'd like you know the hard two harbor wallets was was a very clear one. And so we work to get that out. We also have been working on cold card support, partially Bitcoin transactions.

103
00:42:48.080 --> 00:43:16.480
So that is coming, that's been a big request. You know, we do have more coming in the new year, and we're we're we're building easier and easier access. And I think what we've seen what we've seen too is that we've seen people that start with the basic two of three multi-sig and then very clearly see why multi-sig is important, and then they say, hey, I actually want to upgrade and get full three of five because I understand that why that extra amount of security and why all this is kind of balanced the way it is.

104
00:43:16.480 --> 00:43:37.280
And so we're we're seeing that too. But it's you know, again, if you have questions around multi-sig and around the threats, you know, that document is there. We cover a ton of stuff there. You can always email me or message me too, or ask on Twitter. We're always happy to discuss this stuff, but there's just like this a there's a very deep well on all these stuff.

105
00:43:37.680 --> 00:43:56.480
Yeah, I've reviewed that document and it is super impressive. And I'll I'll link to it in the show notes too, so you can just be a click away and check it out. I definitely recommend all the listeners to take a look at that because like even if you're not a CASA customer or even considering being a cost customer right now, like that is an amazing overview of like why you should be using multi-sig, you know.

106
00:43:56.480 --> 00:44:17.800
Yeah, totally. Yeah, and that's that's the important thing is it's like we were really trying to get into just the kind of core threats and why we chose this out of anything else. There are lots of other options that could be used security wise, but we chose all this stuff for very, very, very specific reasons. There are other options out there and there's you know you do have Glacier Protocol, which is one of the oldest.

107
00:44:17.800 --> 00:44:39.320
You can just use even Electrum and we actually do recommend so as a backup option we do have several options when you're using our service we have several options on how you can recover your funds even if we're not there and so we do recommend some of these other open source tools but people could use those even if they didn't want to use us.

108
00:44:39.320 --> 00:45:01.960
It's just by using us you get a little bit of added protection in terms of the way the user interface is built, the multi-platform support that again there are certain threats that that that that helps protect you against yeah I mean you there's another new product that we should talk about you guys are just dropping them left and right Covenant which is definitely related to multi-sig.

109
00:45:01.960 --> 00:45:24.760
It's a new cost of service to make Bitcoin inheritance easier. So yeah tell us about Covenant and what you know how does Covenant kind of stand out compared to what's available out there for Bitcoin inheritance. Yeah so so Covenant is really first of its kind around longer term considerations of inheritance and it's really an extension of the existing multi-sig product.

110
00:45:24.760 --> 00:45:45.360
So you know we view multi-sig as being as more and more of it is a standardized and people are used to kind of swapping out keys and using different key types, more things will be built into this, more functions will be found for it. You know you could have a multi-sigs key set that's somehow tied to the deed of a building or something.

111
00:45:45.360 --> 00:46:10.560
I mean there's like a lot that can be done in terms of just using cryptographic signatures and but one of the most near term other solutions you know you have to start at the side of just okay I'm just protecting and holding and my funds right I'm just hodling and that's kind of problem set one and then I need to be able to transfer easily and I need to be able to recover easily like those are all kind of problem number one.

112
00:46:10.560 --> 00:46:29.040
And then once you have that and once you can protect yourself over the course of years or months or decades then you eventually get to this problem of inheritance of okay if something bad happens how do I continue my usage of those funds or make sure those funds get to the people that I want them to.

113
00:46:30.000 --> 00:46:50.000
And so that is then a is a is a related but slightly separate problem and the big challenge the biggest challenge with inheritance is that there are there are you know really even more pitfalls around inheritance than there are around just kind of singular storage for yourself.

114
00:46:50.480 --> 00:47:20.520
And the reason for that is that you know it's similar to a people people will talk about how like a prediction market can eventually turn into an assassination market, right? Because if you start if you start using prediction markets and thinking about you know the odds of different events happening eventually you know it it can become an assassination market there are these perverse incentives that if you set up a an inheritance program wrong, it actually can create incentive to off somebody, right?

115
00:47:20.520 --> 00:47:38.840
Sure. It can create a it can create an incentive to where certain people are aware of your setup enough that they then have incentive because the resources on the line are large enough that it could incentivize someone to actually you know take you out. And that's that's a terrifying thought.

116
00:47:38.840 --> 00:48:04.760
And there are there are you know a lot of other considerations like that that we've just been modeling out and thinking through and threats. And so you the balances that you have to strike is that you want on the one hand, you want to protect it the person, you want to make it transferable at the right time, but not before. And you don't want to create these negative incentives that could cause you know any one actor to try to take action against that end user.

117
00:48:04.760 --> 00:48:35.640
And there's a very, very, very all of this is just logic, but there's a very, very small subset of solutions that kind of meet all those requirements. And so that's also something that Jacob has been working on for us. And we just announced the service, and you know, it is we've one thing that we arrived at is that to trade off between using a three of five and a three of six, three of six that allows you to just have an extra key that goes to a lawyer, inheritance lawyer.

118
00:48:35.640 --> 00:49:00.040
We do think that that's actually an important part of it right now. There are lots of, you know, when family members get involved, it's easy to think, oh, I'll just hand several of these to my family members or friends, and then they can help with the transfer. But I it's it it is the again, you get into these situations to where you could cause a rift or could cause someone to try to attack you that you just didn't even anticipate because so much in terms of resources could be on the line.

119
00:49:00.040 --> 00:49:22.480
Yeah, and families families are just complicated too. Yeah, families are already complicated already. It's it's another thing. I mean, how many movies do you do you need to watch to where there's some you know big inheritance on the line and then everybody's at each other's throats, right? And somebody killed somebody or somebody did this dastardly thing and sabotage somebody.

120
00:49:22.480 --> 00:49:41.280
There's tons of movies on this, and I as the price of Bitcoin rises, there's gonna be probably many more movies on this. Yeah, and we're trying to minimize the number of movies or stories that ever get written because I think that I think that that again you have to strike that balance between making it accessible but not not creating new risks.

121
00:49:41.280 --> 00:50:03.680
Yeah. And yeah, so that's what we've done with Covenant. And there we're we're releasing more details. We've already started pilots with some customers and but it's been a nine or ten month process of m mapping out all these different risks and yeah, and making it accessible, making it secure, making it you know, easy to protect users, but also not opening up new threats.

122
00:50:03.920 --> 00:50:34.960
Yeah, I mean, there's you know, I'm super convicted about Bitcoin at this point, and there's like really very few things that concern or worry me, but the physical threats, you know, potential physical threats of you know, that that potential consequence of holding your own Bitcoin of having a bare asset, is you know, it's scary. I mean, we are far removed from an age where people were holding, you know, their own their own wealth themselves and had the risk personal had to take the personal responsibility to protect and defend that.

123
00:50:34.960 --> 00:50:54.800
You know, yeah, so it's just it's a it's a whole different world. There's a way so more so many more ways to you know attack somebody. I know Jameson has been through this personally and ex you know put forth like tons and tons of just effort and time to try to reclaim some of his privacy and protect his family.

124
00:50:54.800 --> 00:51:32.920
So yeah, I mean that really worries me a lot. And I think do you think like do you think that that's gonna affect Bitcoin adoption like like negatively enough where like it could really you know maybe even prevent Bitcoin from becoming you know global money like or to some extent anyway how worried do you think people are going to be about this stuff and how worried are you about this kind of shit going down how can and how can like Casa Multi sig like how does it help mitigate that stuff I think that the challenge around it and this this kind of brings us back to these questions of civilizational change.

125
00:51:32.920 --> 00:52:11.000
Yeah we have seen these and they're effectively just like phase shifts it's like going you know having a material that goes from from solid to liquid to gas right you have these kind of phase shifts that are going to happen that have happened historically we haven't seen one in a long time but they do happen and I think that that Bitcoin does represent something in terms of a next phase shift and so there will always be trade offs with using Bitcoin there will always be security trade offs but there will

126
00:52:11.000 --> 00:52:37.200
Always be like power trade offs too and if you look at if you look at the kind of billionaires of our day most of them have personal security most of them have layers upon layers of security in terms of their way their assets are set up yeah most of them have layers of security in terms of the way their corporations are set up.

127
00:52:37.520 --> 00:52:55.600
Most of them have had, you know, most of them that survived have had at least a few attacks in some capacity. It might be a it might be a child or a pet or someone else that was kidnapped. It might be a kind of corporate rage. Yeah, that's like that's the worst nightmare right there, right? Yeah.

128
00:52:55.600 --> 00:53:12.080
Yeah. I mean, it's like there's a lot. There's a lot. And what this just comes down to, what I'm getting at is that anytime you have something valuable, a certain portion of the population is going to want to take it from you. And that's just a reality of what we face.

129
00:53:12.680 --> 00:53:20.120
And I think that we try to be very careful around our community of just making people aware of those risks,

130
00:53:20.240 --> 00:53:22.320
Of the realities of those risks.

131
00:53:22.800 --> 00:53:41.020
But it is a very real thing. And so I think that what we're seeing is like, you know, the weird thing about technology is that what technology makes possible is that it can take both benefits and problems of a very narrow set and actually bring them to most everybody.

132
00:53:41.520 --> 00:54:02.480
So we used to have we used to be in a world where, in terms of food, you basically ate what was in front of you. You never had many options or choices. And you know, we all the majority of the population basically just worked a physical job and ate what was available to them and that was it.

133
00:54:02.480 --> 00:54:29.800
And it was only the kind of small wealthy few that had choice of all these different options and could even get really fat, right? Or get obese. And now we've had because of technology, because of food technology, because of the ability for us to produce a lot. Now people all over the world, not not in every country, but in all in in many different countries, now we have this much bigger issue of people having to make choices around the food that they eat.

134
00:54:29.800 --> 00:54:59.480
Where you go back a century and this wasn't even really a choice. So we're gonna see other cases of this to where you know, right now these major security issues or major wealth issues are just the realm of billionaires and not even really 10 or 20 of millionaires, it's like billionaires. And then it's gonna shift to a point where because of the power that's afforded to you by having this much wealth or this much power around your own assets, it does become some of those concerns become more widespread.

135
00:54:59.880 --> 00:55:20.760
Yeah. Yeah, and it's yeah, it's some definitely something I worry about from time to time. I get anxious about it and thinking about it. And you know, it's one of the reasons why I've got you know my Bitcoin locked up in Casa Multi-sig and my hardware wallets are out of the house, you know. And yeah, I just yeah, it's it's another reason why.

136
00:55:20.760 --> 00:55:43.960
I mean, obviously, like me being a public figure in Bitcoin is is also something. I mean, we're all out here kind of on the front lines, the entrepreneurs, the content creators, the educators, and then you know, that kind of opening ourselves up to that. I mean, we need people to do that to make this thing happen. But I totally get the you know, stay pseudonymous and keep your private, like stay as private as you possibly can.

137
00:55:43.960 --> 00:56:06.120
Because you know, once you're out, it's super hard, as Jameson has has made clear in in many like several presentations he's made, like it's super hard to take that back once you're out. Yeah. And I will say that it's like it's not gonna be sustainable to stay fully hidden forever. I think that there will be parts of our lives that we'll be able to hide for a long time.

138
00:56:06.120 --> 00:56:24.880
But do we you have to assume that even if you do every possible thing to go entirely off the grid, that you will have you know some layers of breaches or some layers of you know awareness and it could come down to like maybe it's not a broad public awareness, but maybe there are other people you work with, right?

139
00:56:24.880 --> 00:56:47.200
Or maybe there are other family members, there are other friends. You know, there there are layers to this, and I think that that you know we don't want to live in a world to where the only protection you have is just by being a total ghost. Yeah. We do think that there are that we do think that it's smart for people to be aware of their privacy and to increase their privacy.

140
00:56:47.200 --> 00:57:11.920
And we've we've been thinking about even about tools that we could even provide to help people not just secure their Bitcoin, but almost secure their privacy data and think about like all their data and think about increasing their privacy, right? We've we've been thinking some about that. And so I think that I think that but the approach there is that you should still have you should have a range of options to where right now it's just like black or white.

141
00:57:11.920 --> 00:57:31.520
And we think that you know, in the case to where you did want to lead still a somewhat more public life, you should still have some security options, and multi-sig is one of those things that kind of gives you superpowers by by the incentives, the incentives that are built around it just mean that you have a you know much higher barrier of protection.

142
00:57:31.520 --> 00:58:00.600
Yeah, yeah. I want to ask you about this. There were recently some criticisms leveled on Twitter and about security vulnerabilities with the Casa node. And sure I heard Niggs Nigzabo mentioned the discussion, even on what Bitcoin did last week. Right. Yeah, can so can you can you walk us through these criticisms and Casa's response to them and maybe talk more generally about how CASA makes decisions about the trade-offs between complexity and security.

143
00:58:00.600 --> 00:58:37.880
Yeah, yeah. This is this is a great point. And we are always happy to address all this stuff publicly, and we encourage people to raise always raise questions and raise issues. In this particular case, we kind of had had a situation to where someone that raised totally false statements before, has lied about us before, had kind of raised another issue that we were aware of and that we've talked to customers about and that you know the broader population was aware of, and this is all not new stuff to KASA customers, but it got blown out of proportion and got blown into people bringing up things that again, you know, this this was a public discussion.

144
00:58:37.880 --> 00:58:57.240
We've had it before, and a lot of false statements, a lot of false statements floating around. I'll kind of like bucket it and into kind of the basics of what happened and the choices that we made, and then this kind of secondary discussion in terms of the trade-offs of really security and usability.

145
00:58:57.240 --> 00:59:27.640
So the first side on on actually kind of the questions of what happened is there's a case to where a CASA node right now doesn't run on HTTPS. So if you're on your local network, it doesn't run on HTTPS, and we all were aware whenever we put that out, I mean it was a very conscious decision, and the way to solve that to run it on HTTPS is by you know, if you're running a local device, you have to do what's called a self signed certificate.

146
00:59:27.640 --> 00:59:57.680
That self signed certificate is a whole can of worms. It also it actually can create, we had several people point this out publicly, or several people point this out kind of in the chain of conversation. We were not the only ones to point this out, but that that doing self-signed certificates opens a whole can of worms and can be can actually create a false sense of security because if it's done improperly, you can end up in this case to where you think that everything's secure, you think everything's working, but you could still have a breach.

147
00:59:57.680 --> 01:00:22.160
So and you also don't want users to get used to or thinking that they are totally secure, right? To where if there was a self-signed certificate, there was still potential of a breach, but it just appears to them that there is no risk, then they actually get more comfortable than they need to be. Where we have always, especially around the cost of node product, we have always represented this publicly that it is still a very early stage product.

148
01:00:22.160 --> 01:00:42.640
People should only put on you know lightning in very early stage, Bitcoin still is very early stage. You know, the cost node itself, like all this stuff is still very risky. And so that's a very different consideration from our key master product to where there's been a lot more on the on the testing side and then also just on the security side, they're just built for very different purposes.

149
01:00:42.640 --> 01:01:01.920
And so we made this choice. We said, look, like we'll we're gonna use HTTP, we're gonna stick with that. We will make customers aware of the trade-offs and of the issues and the discussion, and we were very transparent of that. You know, right when the we had people asking about this right when the device came out over a year ago, and we talked about it all publicly then.

150
01:01:01.920 --> 01:01:38.440
So again, all this got blown out of proportion, wasn't anything new. And where this got back to is that it's just this discussion of kind of usability and security. And w what the what it comes down to is that you're always, you know, you're always having to make choices or make options for an end user, and you have do have some users that want to dig down into the technical nitty-gritty and make the and use I would say features or use options that they want to customize down to the finest detail.

151
01:01:38.440 --> 01:01:56.520
But the majority of people don't have time to go through all of that. So that's why they that's why they are become a costly customer, you know. Well, yeah, I mean but our job is to provide a secure enough option while also making the customer very clearly aware of the risk.

152
01:01:56.520 --> 01:02:15.400
And that's exactly what we've done. We've done that from day one. We've made the customer very clearly aware of the risks, and we've also been very transparent around our design decisions and why we made them. And we've been very, you know, we've been very careful in the decisions that we made there. Because we don't want customers to shoot themselves in the foot.

153
01:02:15.400 --> 01:02:38.440
We also don't want them to expose themselves to kind of new types of issues. And so you know, if you want to get down to saying, okay, well, what's the absolute most secure secure device, secure computer, the most secure computer out there is one that does not have a power cable that is buried underground in a cement box that is not even used, right?

154
01:02:38.440 --> 01:03:00.760
Like that's that's the most secure computer. And in any other scenario, you're gonna be in a case to where there are going to be attackers, it's just gonna be trade-offs in terms of where those attackers are, where they can come in, how they're gonna access your device. And so we settle down to this case of okay, like when whenever you're within the your your home network, you do need to be aware of what's on that network.

155
01:03:00.760 --> 01:03:32.720
But ultimately, you know, even most of most home routers are actually configured very similar to the way that we configured our device. So we didn't think it was anything new because most home routers are also in a similar case around this this kind of https http issue but we also you know we are thinking of improvements and we launched Tor and we are thinking of ways that you could actually do kind of more of your setup and more of your controls and we already allow you to fully control everything over Tor and that would solve some of these issues.

156
01:03:32.720 --> 01:03:55.200
It's just not an easy solution because then you open up you know if you want if you want the customer to do self-signed certificates you end up in a case to where they're gonna have to do you know way more configuration than many of them signed up to do and in some cases even command line work right and so it so there is this balance there's this balance of strike and we've been very public about that we will continue to be very public about that.

157
01:03:55.840 --> 01:04:33.760
And the kind of important thing around this though again is that we're always public about these conversations and then we continue to be and yeah and I think that that's kind of where we were so we were we were kind of surprised that it blew up because again it was a it was a conversation that we'd already had with our customers and most of our customers were like messaging us privately saying hey like this is the same question we already discussed and we're like yeah we already discussed this so that was what why there was a little bit of delay even in response from us is because we were like why you know why is this even coming up this is you know these some of these are false statements some of these are are true but they're aware you know we're aware of the issue so it's just it's just an odd thing.

158
01:04:33.760 --> 01:04:54.840
All right cool that that's great. I mean I'm glad that we had a chance to address that and you know it's been out there so I just you know I didn't want to publish this episode without you know at least talking about it. Oh of course of course and again we're always we're always we're always very public, very transparent, very open to discussing any of these questions and issues from customers.

159
01:04:54.840 --> 01:05:14.440
We always try to make customers aware of the calculated risks that they are making. And we do this across all of our products. I mean, we walk through customers in terms of on on both Tmaster. There are very different security m models from Key Master to the Casa Node. There are always improvements that we can make and we do those.

160
01:05:14.440 --> 01:05:35.240
And we are always, you know, the first ones to message customers if there is a real issue. And there was actually a real issue around Lightning and an update to Lightning just a few months ago, right? And we were very quick to message customers, make sure that they were aware of the issue, make sure they were aware that they needed to upgrade, we provided the upgrade.

161
01:05:35.240 --> 01:05:57.320
And so we were always continued to do that. All right. Let's let's let's talk a little bit about lightning just in general. I know you know, Cost is obviously building heavily on Lightning. There's just so much happening so fast. A couple episodes ago, Keto Minor mentioned to us that at after the Berlin Lightning Conference, he was just absolutely stoked.

162
01:05:57.320 --> 01:06:21.320
And there's a lot of exciting work kind of happening behind the scenes right now. So yeah, what are like what are you excited about on Lightning? What do you see happening in the next year or two? I mean, I'm I'm excited broadly about Lightning. There's still a ton of problems to solve, both around liquidity, around onboarding, around actual use cases and functions.

163
01:06:21.320 --> 01:06:42.120
There's a lot to do. And we you know, we obviously are supporting where we can. We also have a ton to just support more broadly around privacy and security generally. Lightning is a part of that. But I would just say that that I don't think that Lightning is gonna be just a one or two year and then everything's gonna work and everybody's gonna be on Lightning.

164
01:06:42.120 --> 01:07:06.640
I mean, I think it's gonna be several years before it really builds up, but we will have several significant several significant improvements in just the next year or two. Again, around the problems around liquidity, around, you know, both both the simplicity of opening up both inbound and outbound channels around just getting started with Lightning.

165
01:07:09.200 --> 01:07:28.960
I think that's also important. Even the kind of kind of SPV way around neutrino, I think is fine in temporary cases, but I think it's dangerous to get to build over dependence there. And so you want you want to kind of use this spectrum and then lean towards the most security or get to the most secure option you can kind of as soon as possible.

166
01:07:28.960 --> 01:07:34.320
But there are also like a bunch of important privacy improvements that come from using Lightning regularly.

167
01:07:34.640 --> 01:07:44.980
All of those are good things, but it will take, I think, a few years for us to really see the massive improvements that are going to be getting us to tens of millions of users.

168
01:07:46.080 --> 01:07:47.760
Yeah, totally agree.

169
01:07:47.840 --> 01:07:52.800
So yeah, you guys are, CASA's supported by or invested,

170
01:07:53.360 --> 01:07:57.920
I guess I should say Boost VC is invested in Casa. One of your VC investors.

171
01:07:58.900 --> 01:08:14.100
You know, I saw you tweet about them. And so I took a look. They seem like to be like a super unique VC firm. Their thesis on their website is sci-fi technology. That's what they invest in. Their call to action is like, if you're building an incredible superpower, contact us for an investment,

172
01:08:14.480 --> 01:08:33.960
Which I love. Yeah, so can you talk more a little bit more about Boost VC and like talk about what it's been like to be a part of that kind of ecosystem of these super forward-looking sci-fi type companies? Sure. So Brayton, Adam, Maddie, the rest of the team there are all awesome.

173
01:08:33.960 --> 01:08:58.520
Would highly encourage anybody to apply there that if they have, you know, I they they think in big ideas, right? And we approached them with the big idea of even launching nodes and doing kind of major premium key management. Nobody was doing this stuff, and they got it pretty quick, understood the need, and backed us, and we were we were very thrilled to be able to work with them.

174
01:08:58.520 --> 01:09:19.000
Adam's dad is also a big Bitcoin believer, Mr. Draper, and has been kind of long in the space. And so they are they are big Bitcoin bulls and have thought long and hard about the space and have been around the space. I think we're the first kind of accelerator major investor kind of early stage around Bitcoin.

175
01:09:19.000 --> 01:09:54.600
They were very public about it. And so I you know they again they've kind of been around the space for a long time and just thrilled to work with them. We have a we have a great set of investors across the board. You have Lair Hippo, who Lair Hippo is has long been in they're in New York City and they led our seed round, and they've they've been in a bunch of kind of direct to consumer brands and also kind of more premium brands, everything from like your caster mattresses, all bird shoes, a bunch of a bunch of different brand.

176
01:09:54.600 --> 01:10:16.160
They they really understand branding and they really understand kind of core consumer quality products. And that's a very different offering from super technical companies. And so they bring lens to us that that we just get a kind of a really good feedback perspective from them that's it's different from Boost VC, and it's you know valuable in a much different way.

177
01:10:16.320 --> 01:10:37.280
But Julio over there and Eric Hippo, we've we've just and their entire team, we've we've it's been phenomenal working with them. We've also had Compound VC, which Josh Nushbaum who they've done a bunch of Bitcoin related investments and are big bulls, and then Charles Hudson was another one of our early backers, really before anybody.

178
01:10:37.280 --> 01:11:07.840
He was the first kind of institutional, and he does a lot of pre-seed rounds. And he is there in San Francisco, Melton Demir's, Elise Khalid, the Casa Island guys, who Matt Nick, we've got a great group of investors, and there are just many many that I'm I'm leaving off in in terms of angels and in terms of funds and but phenomenal group, and everybody I've been it's been very encouraging for me to see and see the number of people that are thinking this far about the future and they grapple with the real questions too.

179
01:11:07.840 --> 01:11:29.840
I mean, it's not just they're not doing us as hey, you know, let's just build another kind of large cash churning company. You know, they they get it, they get it that this is kind of civilization changing stuff and that the implications are high, and so are very careful and thoughtful about their analysis, and we appreciate that because there are other firms out there that have not been that way and have been a little bit more careless.

180
01:11:29.840 --> 01:11:50.800
And so we've we've been very very lucky to be working with some some great investors. That's awesome, man. I'm mindful that you have to head out soon. So I'd like to just just hear a bit about I know you kind of like to nerd out on some of this future tech stuff, and like cybernetics and biohacking.

181
01:11:50.800 --> 01:12:15.240
I recently watched that unnatural selection series on Netflix about biohacking. It was kind of blowing my mind. Yeah, so just like give us some a taste of like your sort of like you know future daydreams of the future like what's it going to be like how does Bitcoin fit into all of that too. Yeah so I think of the future is actually like way more in our control than most people think.

182
01:12:15.240 --> 01:12:40.680
Yeah. And I think like the best lesson that I can give people or the best the best kind of realization that I've had around that is that the future is just it's way more in your control than you think. And the future is created it's not it's not just kind of set in stone. And from that perspective, you know thinking hard about the future and about where we want it to go is actually really important.

183
01:12:40.680 --> 01:13:02.920
And so what what cybernetics is what cybernetics actually refers to is just control systems or control loop systems. And the easiest example is a is a an AC unit in a house where you have a thermometer or a temperature gauge that just checks the temperature and then turns on or turns off a heater or a cooler based on the temperature.

184
01:13:02.920 --> 01:13:36.440
So if you're in the middle of winter and you know you've got it set to be 65 or 70 then and the temperature in the house drops below it drops to you know 64 and the heater is going to turn on and it's gonna get it back to 65 and then it's gonna turn off right and there's and then there's a circle there there's a cycle to where it basically you know the temperature checks if if it's not hot enough it turns on it gets hot enough and it turns off and it checks again and then it turns on, then turns off, and it just kind of goes through that loop, that control loop over and over and over again.

185
01:13:36.440 --> 01:14:01.200
And so I think that thinking about cybernetics is like we're going through thousands of these like cycles in our everyday lives. So you can think of the that whenever you plug the phone in in the evening, right, before you go to bed and you charge the phone and then you wake up and it's fully charged. Even you can simplify cybernetics down to like even just climbing into a bed and onto a mattress to sleep, right?

186
01:14:01.200 --> 01:14:21.040
In a specific room every night is like that's a cybernetic process in a sense because it's like you're going to a specific piece of technology, a bed, a mattress that is designed specifically for sleep to give you this ideal type of sleep, and you're waking up at a later point and then you do it every single day, every single night, right?

187
01:14:21.040 --> 01:14:47.680
So it is a loop, right? It's a loop in a sense. And I think that the thing that I would encourage people to think about, and the thing that I think about a lot is is how do we make better loops in a sense? How do we make better process? How do we make the world and our kind of day-to-day lives better? It is easy to get distracted with this kind of fully future-facing picture that is never connected to reality and is going to be really hard to get to.

188
01:14:47.680 --> 01:15:12.320
And so I encourage people to think of like, okay, like how can I get to this kind of future state with this future product, and how can I reach that in a very very detailed way. And there are, you know, it may take a while, but it's it's possible to do. So the way we think about Bitcoin is Bitcoin is one of these technologies that already in it in its existence is this kind of sci-fi technology.

189
01:15:12.320 --> 01:15:33.880
The fact that it's even possible for all these different different players, different types of users to interact with the system in a fully distributed way to where no single user kind of has monopoly control and is changing all permissions, et cetera, is is that's already kind of sci it's not even science fiction, it's science fact, right?

190
01:15:33.880 --> 01:15:54.920
It's it is it is it remarkable that it is even possible. And now we need to think of other ways that other systems can also change to kind of build dependence on that or make use of the fact that it exists. And so in thinking in terms of cybernetics and in terms of designing the future is things like you know multi-sig.

191
01:15:54.920 --> 01:16:15.960
Like we as a company, we kind of took this position that we had all these companies, all these people telling us hey multi-sig is like not going to be viable, nobody's gonna use this, it's too hard, everybody's just gonna go use centralized custodians. And that's we feel like that's like saying hey, don't ever use Bitcoin just use the US dollar.

192
01:16:15.960 --> 01:16:38.520
You know the US dollar is much easier for people to access. It's it's it's already in their wallets, like don't even touch Bitcoin. I mean it's like it's like a similar argument. It's like there there are yeah it's it's a little more challenging but the way that it becomes to the that you get to the point. There was a point when the first US dollars were printed that they weren't widespread and there were other dominant currencies in the world.

193
01:16:39.000 --> 01:17:06.920
And so if you don't see a path forward you can't get to that future towards a better state and we genuinely believe that Bitcoin is not only better money, it's actually a better computing and better kind of approach to systems design. And that's what's important and we need to think about how to take social networks and how to take productivity applications and how to take you know general computing how to take our cars and how to take like all these other systems that are out there that are so heavily dependent on centralized control.

194
01:17:07.240 --> 01:17:26.240
We need to think of ways to kind of break those free. And so that's that's just where I would position it in terms of in terms of thinking about the future, thinking about cybernetics. Think about a better future for yourself and your family and your kids and think about ways that you can you can make that future a reality.

195
01:17:26.240 --> 01:17:46.560
Don't get so caught up. It's great to have long-term plans, but don't get so caught up in in fantasies that will take, you know, that you won't even be able to achieve in your lifetime. But do think about the science fiction futures that you can, you know, within a few years or within even decades, right? But with enough distinct steps that you could actually get to.

196
01:17:46.640 --> 01:18:05.760
Yeah, that makes sense. And it's I think Bitcoin is making the achievement of those goals and dreams, you know, just way more possible. Having those those resources available, this the follow-on effects of sound money that I've talked a lot on this podcast about you know, enable that all that stuff to happen.

197
01:18:05.760 --> 01:18:24.080
So it's kind of an amazing future that that we're looking forward to. And you know, I call this the dawn of the Bitcoin Renaissance, and it it's amazing to be here. Yep. I mean it's it. I mean that's it. So awesome. All right, man. Well, thanks for having me on. This was a ton of fun, really appreciate it. Is there anything though you want to end with to let listeners know about?

198
01:18:24.080 --> 01:18:52.640
You know, not much. I mean, it's you can go to keys.casa to check out more about Casa's offerings. We do offer a security and privacy subscription, which includes kind of the full toolkit that you'll need with both multi-sig and the Casa Node at different levels. We offer multi-sig, whether you're storing, you know, a few thousand dollars worth or whether you're storing millions worth, we have security solutions there to make it easier and to give you the best possible security across the board.

199
01:18:52.640 --> 01:19:13.320
You can email membership at team.casa, and we're happy to go through and do kind of full demos of the products. You can also just download Key Master, SATS app and order a CAFA node and kind of have the full experience. But let me know if you have questions. I'm just Jeremy and Team.cotha or I'm Jeremy R. Welch on Twitter. And then we're Casa Hodl on Twitter as well.

200
01:19:13.320 --> 01:19:35.000
But you know, feel free to reach out if you've got any other questions. And again, thanks for having me on. Thanks, Jeremy. Take care, man. Keep up the great work. All right, thanks. All right, thanks to Jeremy for his time and to you for listening.

201
01:19:35.000 --> 01:19:56.680
I always love to hear your thoughts, questions, feedback, painful criticisms if you have them. Tweet whatever is on your mind. You can tag me at citizenbitcoin. Jeremy is at Jeremy R Welch. That's J-E-R E-M-Y-R-W-E-L-C-H. You can support the podcast by sharing it on Bitcoin Twitter or with your family and friends.

202
01:19:56.680 --> 01:20:14.840
Send them some Bitcoin and some Bitcoin education with GiveBitcoin and tell them to subscribe to the Citizen Bitcoin podcast, and together we'll help you turn them into wisened hodlers. This week's open source shout-out is LND. L D is the leading lightning protocol implementation, powering most of the lightning apps out there.

203
01:20:14.840 --> 01:20:36.080
Shout out to Roast Beef and Connor leading the work on that project. But there are 201 contributors to this open source project at this point. You can support the project by running betas, providing feedback and code on the project's GitHub. Alright, that's it for this week. Take care out there, Bitcoiners, wherever you happen to be in the world.
