S6 E5: Stadicus on Full Nodes, BitBox02 & MultiSig Setups
Search this conversation
0:49Vlad CosteaHello there and welcome to Season 6, Episode 5 of the Bitcoin Takeover Podcast. As always, I am Vlad. It's a very beautiful September morning here in Europe and I'm talking to Stadicus, who is best known for his work on the full node implementation RaspiBolt, which is a precursor of RaspiBlitz. And he also works at Shift Crypto these days, works on the BitBox02 hardware wallet, and was supposed to release a full node that probably due to the pandemic did not make it yet or ever. I don't know about that. We're about to find out. I'm very happy to have you, Stadicus. Welcome to the Bitcoin Takeover Podcast.
1:35StadicusIt's because...
1:36Vlad CosteaOh, sorry, I muted you. It was my mistake. I muted you during the intro music, just so it doesn't catch any sounds in the background.
1:45StadicusAll good. Go ahead. It's been too long since we talked and I'm very happy to be here.
1:51Vlad CosteaYeah, of course you are. You get to talk about all of these news and also your involvement in the Bitcoin space and full node world, because that's a microcosm of itself. So tell me about RaspiBolt, because not many people know about it, but it's still very popular among full node enthusiasts.
2:13StadicusYeah, so this is basically how I got into the public Bitcoin space. I would call myself a Bitcoin minimalist, but a full node maximalist. I very early on when I started out discovered that I want to not rely on third parties to tell me what happens on the blockchain. Running my own node was pretty obvious to me. And I just went ahead and set up like Bitcoin Core and all the related software on a Raspberry Pi. Documented my own learnings on the way. I started out without knowing too much about it, but kept track and released Medium articles and then moved over to GitHub.
2:59And now I think in the end it is a pretty good, well-documented setup, how you can run your own Bitcoin full node with Lightning, with an Electrum server, just so you can like be a direct participant to the Bitcoin ecosystem without relying on other parties to, well, do it for you. Also, I think it helped a lot that when I started out, it was hard to still have an impact on-chain Bitcoin, but Lightning was at that time just emerging. So I had a lot of fun there as well, like building the first public Lightning node on a Raspberry Pi.
3:48And I think that got a lot of traction. I mean, in the beginning, it was just Lightning testnet. There wasn't even a Lightning mainnet. And so it evolved over time.
4:01Vlad CosteaSo when was this and when did you start working specifically on RaspiBolt?
4:06StadicusI think it was probably summer of 2017, but this is a bit like obscure to me already, so much happened since then. Just when Lightning came out on testnet mainly.
4:24Vlad CosteaSo it was during the scaling wars when Bcash was being created and there was that debate about SegWit2x and there was the testnet of the Lightning Network getting deployed. Yeah, it was around. You were one of the first people to get into it and create an implementation that's based on something as simple as the Raspberry Pi.
4:46StadicusYeah, I guess that's true. I wouldn't really call it an implementation. It's just like writing a guide and stringing together really great products that I have not really built, right? So, but I think it helped a lot of people to understand how to set it up properly, how to not be afraid of the Linux command line, how to do everything yourself. And I think that's probably also the biggest difference to the plug and play nodes that you see today. The RaspiBolt is really about the learning experience.
5:30So you start off with a standard operating system, Ubuntu or Raspbian, and you do everything yourself. You don't rely on any scripts. You don't rely on any user interface. You configure everything yourself. That of course has a huge impact to understand what you're actually doing. I cheer for every full node that is more plug and play, the more the better. And I also get that most people don't really want to do everything from scratch. So it needs some intrinsic motivation to learn Linux as well. But if you make it through, I think it's a good learning experience.
6:16Vlad CosteaOkay, so let's put this into context because as you said, you created something like a dashboard which put together many pieces of software like Bitcoin Core and possibly I think you're using the client of Lightning Labs...
6:31StadicusLND. Yeah, that's correct.
6:33Vlad CosteaAnd you put them together and you created this all-in-one experience, which uses the Linux command line. And then some companies like Casa basically took what you have done, at least conceptually, and they put it together in a box and sold it for $300. And I suppose that was one of the first instances when we had full Bitcoin and Lightning nodes being sold as a product that's plug and play.
7:01StadicusYeah, that might be a bit harsh. I mean, it's not a secret how Linux works and how you properly configure Bitcoin Core and LND, everything as systemd services so they run in the background, right when the device starts. So I guess they would easily have been able to do that themselves without peeking on my guide. But yeah, I think it was just like the first public guide. Also shout out to Damian Mee. He was also very active in that space at that point in time and I learned a lot from him as well.
7:41And I think one of maybe the differences between, for example, the Casa node and the RaspiBolt: for me the full node, the Bitcoin full node, was always at least as important as the Lightning client. So I always wanted to be able to verify my own transactions as well, even when using a hardware wallet or something like that. And with the Casa node, you're not able to do that. It's basically just a Lightning node. Of course, it has Bitcoin Core as a base, but you're not able to run your own, like, Electrum client or whatever against it.
8:23So for me, I think I've put more focus on the Bitcoin on-chain stuff, because I think that's really, really important. And other full nodes, Lightning full nodes, have more of the focus of good UI, UX and more of the Lightning part.
8:44Vlad CosteaWell, I agree with you to some extent and maybe it was harsh, but it's no coincidence that they also use the Raspberry Pi 3B. At the time, I think it was the latest model. And they use that as opposed to something like an Intel NUC, which is like a mini computer that's based on Intel processors and possibly is more powerful.
9:09StadicusYeah, I guess so. Well, it's also more expensive, but I mean, the Raspberry Pi, I've been tinkering with Raspberry Pis for a long time, running RetroPie, like all the old Nintendo systems on it. I use it as a streaming client at home. So it's really versatile little piece of chips and I really like it. So it was the obvious choice for me as well.
9:39Vlad CosteaIt's actually incredible what you can do with this very small piece of hardware that fits on your palm. And you can do just so much. You can use it as a gaming console, as you said. You can use it as a Tor relay. As a node, you can run Bitcoin Core. Maybe it's not the fastest unit, but now with 8GB of RAM in the top Raspberry Pi 4, that's a lot more than you actually need and it can do a lot of operations that used to cost a lot to do, at least in hardware terms.
10:21StadicusMaybe fast forward a bit, when I later joined Shift Crypto to build the BitBox Base, which is also like the full node we wanted to build, because then we had the same questions. Do we want to use a Raspberry Pi? At that time it was still the Raspberry Pi 3, so not as powerful. So in that instance, we opted to use a different system on a chip like the RockPro64, which is way more powerful and was able to sync everything in like under two days, which is impossible with the Raspberry Pi 3.
11:00But now the Raspberry Pi 4 is out for quite some time and is almost as powerful. It can do it maybe in three or four days, which is good enough. So yeah, I mean, hardware is evolving as well, and I'm very glad that the Raspberry Pi still keeps up because it's really the easiest piece of hardware to do for hobbyists. It has good support, even if there are some closed source things going on there, which might not be optimal, but it's good enough.
11:37Vlad CosteaYeah, I feel like we should get to that part where you got hired at Shift Crypto. But before that, you mentioned the BitBox Base, which is a major leap in terms of all-in-one boxes for Bitcoin nodes, and I remember seeing it in Berlin at the Lightning Conference last October. And it was looking very nice. It had this very futuristic black case. And we spoke about it and you explained to me that inside it, there's also a secure chip element, just like in the hardware wallet developed by Shift Crypto.
12:16And it was, as you said, running that RockPro64 unit, which was making it faster. I remember Jameson Lopp looking at it and thinking, "Ah, possibly this is better than the Casa Node 2," which was not out at the time.
12:33StadicusOkay, don't know about that. But yeah, I mean, it was an awesome time. At the moment, the BitBox Base is on hold, but I spent about a year really diving deep into that, building it up from the ground, but with security in mind first. So first do like the really low level Linux configuration, putting a lot of effort in the basic configuration scripts, all the update mechanism, so that you cannot like brick the device once it's out in the wild. That would have been my worst nightmare, I guess.
13:15We really wanted to have it also on-chain first, of course with Lightning after that. And we got pretty far. I mean, we had the beta program. We shipped devices. It looked really nice with a glass top, with a screen. There was actually an adapted BitBox02 inside that gave you a system status. And the plan is or was that it would have been able to act a bit as your own personal HSM, which I still think might be a possibility one day, for example, to act as a co-signer in a multisig setup, acting to certain predefined rules.
14:04But of course, that's a very complex topic and we didn't want to have that from the start. But just having the adapted version of the BitBox in it would have allowed us to have it tested and going out and then do some gradual feature upgrades over time. So that was pretty ambitious. Maybe we took on too much at the time. Hardware is also pretty expensive to develop, especially if you're doing custom stuff like we did. We didn't rely on any like standard cases or whatever. So maybe it was too perfectionist in a way, which would have resulted in too high of a price point.
14:50And I mean, we need to be honest, like the market that is going to buy a product like that is still super niche. So like, we put a lot of money in it, but at some point in time, as a startup, you also need to remind yourself that focus is key. And I think we realized that there's still so much work to do. And in the end, we decided to put it on hold for now and to really focus on the hardware wallets we're building, the BitBox02.
15:26It was of course personally very disappointing to me. For the company, it makes total sense. And for me as part of the company, it also makes total sense. So I'm still working actively there and taking on additional responsibilities, so no hard feelings.
15:47Vlad CosteaOkay, so for the non-technical people listening to this, who probably got lost earlier, what is HSM?
15:55StadicusSo an HSM is a loosely defined term. Usually it means hardware security module. And if you just use it in the term as it is used by the industry, it usually means like a pretty expensive security appliance that you mount in a rack. It speaks certain protocols and actually, it's like a hardware wallet, but it is able to act more autonomous. So you're able to program it to put in rules. It is able to sign or do whatever security magic it is supposed to do on its own.
16:39So let's say you have a Bitcoin hot wallet as a company or as an exchange. You're pretty certainly relying on HSMs to not have the private keys exposed to the computers that are connected to the internet. But of course, you cannot have somebody signing transactions all the time. So the HSM can take that role and is protected with various levels of security, software, hardware, all that stuff. It should self-destruct, for example, if you try to tamper with it or open the case or whatever. So that's more of the enterprise HSM. But it's loosely defined, so you could actually call a BitBox or other hardware wallets like a consumer HSM as well.
17:37Vlad CosteaOkay, so it's like the Ethereum of hardware wallets or something.
17:42StadicusWell, I wouldn't... I think it's an important piece of hardware, but usually they're super expensive if you go for the enterprise thingy and not necessarily much better for Bitcoin. But of course, there's like a ton of other application where you need to have like secure hardware or keys or whatever identities protected by hardware. And this is where HSM or hardware security modules come in.
18:10Vlad CosteaI feel like we have taken a step back since the pandemic has started. Or possibly a lot of steps, because it was so exciting back in October and there were lots of companies announcing full node products. There was a full node phone, which I have right here on my desk and I started up last week. And it sucks right now because there are no security updates. There's nothing going on. You can only use the full node. And I'm talking about the HTC Exodus 1S. The full node only works under a proprietary wallet and you cannot connect it to any external wallets, which kind of defeats the purpose of running a full node if, you know, it's within a walled garden.
18:58But I also remember signing up to the beta testing for the BitBox Base, which was your project for the full node implementation, and I was denied, possibly because I was working for Bitcoin Magazine at the time and you didn't want to leak problems to the press or something, which I can understand. But I was just very excited and I even wrote a comparison. It was one of my last articles at Bitcoin Magazine. I wrote a comparison between the existing types of full node products. And there was a lot going on.
19:35And nowadays you only have myNode, which was possibly wise enough to open source the entire project. And you have RaspiBlitz, which is the continuation of your RaspiBolt project. And I'm about to ask about the difference between RaspiBolt and RaspiBlitz. And you also have, I think, Nodl, but I'm not sure how well they do, how many units they sell. Yeah, I think the market has narrowed down. That's what I'm trying to say. Yeah, there was a lot of opportunity back then and I don't know what happened, but it has gotten worse.
20:13StadicusI guess for most projects, finding a revenue model is pretty hard. So Nodl actually sells physical devices. That's great, but it's also hard. myNode is having their premium model that unlocks additional features. I hope that's working out for them. I think they also do physical devices, but that's more of, I think, the setup. You could easily do it yourself. The RaspiBlitz was always a community-driven project, which is great. It was actually built for usage at hack days, so you could easily spin up your own full node and Lightning node within a certain, a reasonable amount of time, which is not possible with the RaspiBolt, where you do everything yourself.
21:08And the one project I'm really excited about is nix-bitcoin. It hasn't really got a lot of press yet. But I think for me personally, it aligns the most with my own like convictions, because they really do everything security related first, on-chain first, Lightning now, BTCPay Server, all on top. But it seems like a super well thought through full node implementation. And if I find the time, I'd really like to dive more into that, and maybe even contribute one day if there's some need of that.
21:57Vlad CosteaSo how do you spell Nix? Is it N-I-X?
22:01StadicusYes, it actually runs on NixOS. So it's also a Linux distribution. I don't want to go too deep into it because I'm really not that well versed. But the main advantage of NixOS is that it's a reproducible Linux installation that can be configured as super minimal. So you can install the operating system on a system and you'll get exactly the same system every time and only what you need. And the whole dependency management, the whole package management is very, very well thought through and very rigid.
22:51So you can really deploy a super specific system that includes all the Bitcoin stuff with just a few scripts. I mean, the scripts are hard, but it's not like you need to write pages and pages and pages of shell script. So that's basically part of the operating system to do that and ensure the integrity of the system for you.
23:17Vlad CosteaDoesn't Pavol Rusnak or Stick from Trezor work on NixOS?
23:21StadicusI'm not sure about that. That would be very interesting.
23:25Vlad CosteaI think he does. But anyway, that's besides the point. It's just the kind of association that I made in my mind because I haven't heard much about Nix before. But let's talk about what you do at Shift Crypto right now. And I remember a conversation on Twitter between Samson Mow and Jonas Schnelli. And by the way, Jonas is part of season four, episode two, along with Jonas Beckham. Is that...
23:59StadicusDouglas Beckham and Jonas Schnelli, yes.
24:00Vlad CosteaDouglas, sorry. Jonas and Douglas. And they both talk about the BitBox and what they bring to the hardware wallet space. But in that conversation between them, Samson Mow told Schnelli, "Yeah, but you took money from Bitmain and you built your project and look what happened." And I think Jonas Schnelli said, "Yeah, but at least I built something interesting and I'm not really making any money from the project." So it's not the first time when I hear that Shift Crypto is not very profitable, but I still think that you guys are doing some very useful work. Just this week you disclosed the vulnerability in the Trezor.
24:42StadicusYeah, I mean, I don't want to get into any Twitter fights that don't really involve me. There's too much drama there anyway. But we have an awesome team. I think it's safe to say that we're not really in for the money. I mean, I came into Shift as a senior manager at PwC, so I had a pretty decent job, and I went to work for a Bitcoin company really in the depth of the bear market in 2018. So that was probably not the smartest move from a like personal security standpoint.
25:26But our hearts are really in the Bitcoin space. And this is why I'm not sure I'm actually hireable by any bigger company now, going forward. But we have a lot of different team members and different skills. Of course, we have awesome engineers like Marco that just yesterday disclosed the Trezor vulnerability. And I think that's very healthy. I'm an IT engineer myself, but I'm not like a hardcore programmer or anything like that. So I started out for the BitBox Base. I always did some technical writing, product management.
26:11And now I grew more into the product management of all the BitBox products. So this is basically my role now, making sure that the products, like the features, like the testing, all the stuff that we really need to do as a security company, like the BitBox02, the BitBox app, all the JavaScript APIs, integrations with other wallets, also HWI, just now released and merged, that this somehow aligns up and gives us the right overall product as a BitBox suite of products. This is what I try to do.
26:59Vlad CosteaYeah, it's always interesting in this open source space, because the work that you do is open source and you research on open source projects. And the code for the BitBox hardware wallet is open source. I'm not sure about that secure element, how open source it actually is. But other than that, it feels like the whole space of open source projects actually converges towards one goal. And even though you have different products which have possibly different implementations of the same ideas, it's still perpetual advancements of the same principles.
27:38StadicusYeah, so I mean, at the core, we are a Swiss open source hardware security company, right? And I think our products show that. So everything we do, like the app, the firmware, is open source. It's fully auditable. Everybody can look at the whole code base. Every change that we do to it is well documented with pull requests. And we also do reproducible builds. So you know, and you can check yourself, that the binaries that we release are actually built from the exact code base that we publish.
28:22I think this is a step that is often overlooked. You can open source everything you want, but if you then release binaries that are not reproducible, nobody can tell for sure that these are actually built from this source. You could easily have like a hidden source somewhere and build from there. And as a hardware security company, I think it's very, to us at least, it's very important to also use hardware, like secure hardware, like a secure chip. So the physical protection of our keys is also very important.
28:58If I lay my hardware wallet, the BitBox02, around somehow, and somebody would steal it, I wouldn't want him to be able to access my private keys on that. And this is really hard if you don't use secure chips. You mentioned the open source of the secure chip, so you're right, there's a tiny bit of code running on the secure chip that is like contained in the secure chip itself. I don't even know if we know what exactly goes on in there, but it doesn't really matter, because our whole security architecture is built in a way that we use the secure chip, but we don't trust it.
29:47So the secure chip never learns any secrets. We never rely on it fully. And even if the secure chip would be fully malicious and try to do all sort of shady stuff, the absolute worst case would be that we just fall back to the regular open source security model that we have. So there's really no harm in using a secure chip, but not using one is definitely not what we're going for.
30:21Vlad CosteaYou know, something that's not oftentimes talked about is the fact that the BitBox02 and the Coldcard have pretty much the same internals. They use the same exact chips, and they might have different architecture, they run different software, but they do have the same secure element chip, and I think also the same microcontroller.
30:45StadicusYeah, that might be true. I'm not too deep into the Coldcard hardware things, but the overall security architecture is similar. I think what distinguishes these wallets the most is that the Coldcard is super minimal UX-wise, which is good for certain people, but we try to make it more accessible and more usable for regular people as well. So with the BitBox app, with the firmware updates that you can automatically do, with like connecting it to your computer while still staying safe and isolated, this is, I think, the UX we're going for, while the Coldcard is more of a super focused niche product in my mind.
31:41I use it myself, but in everyday use, I kind of prefer the BitBox02.
31:50Vlad CosteaYeah, I can understand what you're saying. And the Coldcard sometimes can get so complicated that you possibly, if you're a newbie user, you set it up using a YouTube guide or something like that, and then when you want to use your coins and move them around, it's possible that you do something stupid and you mess up the system yourself, because you're not sure how to retrieve your funds. And I suppose it's a good idea from time to time, like once every six months, to at least practice accessing your funds.
32:25To remember how you can move them if it's ever needed, or else you risk, like, let's say that you HODL for five years and you're not going to remember what kind of setup you have done. And if it's too complex for you to remember how to access your coins, it's going to be a nightmare.
32:44StadicusYeah, that's a very good point. I think I often say that simplicity is also part of security. So that holds true for, of course, your regular setup, like everyday use, but also for more advanced cold storage solutions. So I'm all about hardware wallets and not going the custom implementation, Glacier Protocol, take laptops and take out the Wi-Fi cards route. I think that's super hard, and you can badly mess up things if you're not careful. And of course, I also once wrote an article about Bitcoin inheritance.
33:31You should always try to make sure that if you get hit by a bus tomorrow, your heirs are still able to retrieve the funds. And if your security setup relies on it to be also a bit obscure and hidden and really hard to access, the coins might just be lost. So not having the option to do any mistakes is of course also a very important part of having a secure setup.
34:07Vlad CosteaYeah, and going back to the idea of full nodes, what I like about the BitBox02 is that you have the option in the app to access your full node as opposed to the full node of Shift Crypto. And that's not something that you're going to see Ledger do. And I admire that. And you also have coin control, which means that you manage your own UTXOs. These are in the advanced menu, but you can just tick one box, you can see them there. You can experiment with them. And I think it's a very good step towards teaching newbie users how to become truly sovereign.
34:48StadicusYeah, so I mean, the BitBox app itself is pretty minimal by design. Less distractions, less potential to compromise your security with some advanced stuff. But we do have the advanced user switch or the advanced user options where you can enable additional stuff like Tor integration, connect your own backend, a Bitcoin full node backend, and the coin control you mentioned. So we're building that out as well.
35:20So we're not only focusing on beginners, but I think beginners, people that will come into this space, hopefully over the next years, they really should have a secure, open source, reliable hardware wallet to go to and to use without having to go through all these hoops. And if they feel like it, if they learn about why using coin control is important in certain setups, like after you CoinJoined your coins with Wasabi, shout out to Max, that will be on your show soon as well, they should have the option to do that. But I think it's also fair to say that the BitBox app is never going to have all the features, for example, that the Electrum Bitcoin wallet has.
36:20And it doesn't need to. I think super advanced power users, they would rather rely on a hardware wallet independent wallet anyway, to have the option to do multi-vendor multisig and all that stuff. So for us, it's also very important to have all these integrations into Electrum, or by supporting the Hardware Wallet Interface, HWI, that will enable us to be compatible with Wasabi, for example. Shout out to Max again. And going down this route, I think, is also pretty important.
37:02Vlad CosteaYeah, and I feel like we should get more into the full node discussion, as I suppose this is the main topic of our conversation here. And you suggested something along the lines of how do consumer wallets query the blockchain? And what do you mean by this?
37:22StadicusSo in my experience, let's start with: you're new into Bitcoin, you get a wallet, be it a software wallet or a hardware wallet. You receive your coins, you send your coins, all good. And in my experience, not many people realize that they're not really participating directly in the Bitcoin network. So they still rely on the wallet not only to run on their computer and create the transactions for them or receive the coins, but they're actually just talking to a backend somewhere, run probably by the manufacturer or the programmer of the wallet.
38:18And they're actually trusting this third party. And this is not, I think, what Bitcoin is all about. So if I want Bitcoin to be self-sovereign, I want it to be peer-to-peer, not rely on any middleman. I mean, in the end, for me, it's really free speech money. And if I then have all my transactions go through an even trusted third party, or trust this third party, like let's say the wallet manufacturer, to query the blockchain for me, that's not really a good setup, I think.
39:05Vlad CosteaYeah, so this is basically an issue of trust and the fact that most new users have no idea that when they download, I think the most popular wallet for mobiles is Blockchain, Blockchain.com, when they download that one, they have no idea that they essentially trust the wallet developers to be honest with them. And somebody like Luke Dashjr or like Peter Todd is going to say that no Bitcoin actually exists unless it's verified by your full node. And if you have to trust somebody else with displaying you your balance, it's very likely that you get fooled.
39:50Actually, I'm not sure if that has happened or if that's a common behavior, but it still can happen. And the whole idea of using Bitcoin is to constantly remove risks and remove third parties from the process, which stands between you and the custody of your own money.
40:10StadicusExactly. So I think that is what the saying "Don't trust, verify" is all about. If I use a wallet and this wallet does not talk directly to the Bitcoin blockchain, but just asks someone else what happened there, this is really bad for privacy, because that someone knows all my addresses, all my account balances, all my transactions, probably even my IP address. And I don't think that, even if they want to be honest, I doubt many companies would just shut down in protest if the police would order them to lock certain transactions or whatever.
40:49And of course, it's also about security, because if you're validating your own coins, the receiving coins, it's almost a little bit like your own personal goldsmith. So you're making sure that you actually get valid Bitcoin that are valid to your own consensus rules and not something that somebody other says is Bitcoin. So for me personally, it's about privacy and security. But of course, on a higher level perspective, it's also about making sure that Bitcoin follows the predefined rules, the consensus rules, and this also protects the Bitcoin network overall. If we have this centralization pressure that in the end there might be like five very big wallets that are run centralized and everybody relies on that, it wouldn't be too hard to just say, "Well now, okay, we do have now inflation," or, "We do now have bigger blocks."
42:07Who's gonna stop them? Because what they say is what the consensus rules are.
42:14Vlad CosteaYeah, and we have the biggest podcaster in Bitcoin, who's telling people that it's fine to not run a node, and that it's too hard anyway, and we should accept the fact that most people will not do it. And I think that's defeatist. It's a way of admitting that it's too hard, so why bother? I don't really support this kind of attitude. I'm actually thinking about doing a tutorial, like a five-minute guide on how to download Bitcoin Core. You don't have to sync the whole blockchain at first.
42:50Maybe regular people don't have 300 gigabytes on their hard drives, just like that. But if they even sync like 5 to 10 gigabytes, it's still enough to validate their own transactions, the money that's coming into their wallets. And it's also a great opportunity to learn about coin control. It's also hidden in a special option, but it's a lot simpler than people say. I think the most difficult part is to verify the PGP to make sure that it's the correct client, and to also verify the binaries and check the code to make sure that it does what it says it does.
43:31And that's the part where we have to trust. Most people will never be able to verify, including myself. But other than that, it's not rocket science. It's as simple as a point-and-click experience. You can get more advanced. You can type in command-line commands, command-line commands, that doesn't make much sense, but you can type in your own code and change the settings with that and interact with the network and check the total supply, or check to see how full the mempool is and stuff like that from your node.
44:06But you don't have to do that. Essentially, the main function is to verify incoming bitcoins to make sure that they're actually legit, and to maintain your transaction privacy, and to not give anyone your xpub, which once again is an elusive term to the same person who tells people that it's okay not to run nodes.
44:27StadicusI'm a bit torn there. I mean, I get what Peter is saying, and to some extent he's right. It's still probably too hard to run a full node. We can do better over time, and there's a lot of progress. It's especially too hard to run your own full node with a hardware wallet. But it's definitely doable. And there are many great guides out there already. And maybe a five-minute guide how to do it and how to download Bitcoin Core is really something that a lot of people would follow then.
45:00But I'm not a fan of dismissing this podcaster just outright. I mean, he's playing with us, he's creating a bit of drama, but he's also playing devil's advocate. So I don't think that's necessarily a bad thing. So a lot of people just get triggered, and he knows that, and he's playing us for outright.
45:35Vlad CosteaYeah, but I still think that when you have like 50,000 followers plus, people will take you seriously. And they will find some comfort in the idea that that person who gets taken so seriously says that he doesn't do these steps, which are essential for financial privacy. So I think the effect on newbies is that they find comfort in ignorance, and they don't feel compelled to actually learn, knowing that the guy who is their thought leader doesn't actually show signs of learning over time. That's my only issue.
46:12Other than that, he can do whatever he wants. It makes me angry when I realize that such simple concepts are not really taught to people who get into the space.
46:24StadicusTrue. On the other hand, I doubt everybody will ever run a Bitcoin full node at home. And I also think it's not necessarily needed, but it needs to be super easy to connect to a full node that you can trust. I mean, I'm the tech guy, obviously, in my extended family, and I would happily run a Bitcoin full node for all of them. And I think that would be already a great step in the right direction. If you can run a full node, you get a QR code or a super simple link to share with your friends and family, and then they can just connect to your node.
47:05That's already a big step towards decentralization without everybody needing to run a full node.
47:14Vlad CosteaYeah, I guess the conversation is a bit delicate because, on one hand, you're right about people not being technical enough. But it has become so easy. For example, Lawrence Nahum from, I think it was called GreenAddress before, now it's Blockstream Green. But he has created ABCore. And that's a very good wallet which uses your mobile phone as a full node. I think it's a pruned node up to this point. It's still something, and it's just an app that you download on your phone. It's not rocket science.
47:57StadicusOkay. Yeah, I think that's definitely a step into the right direction.
48:02Vlad CosteaAnd once you figure out how to connect it to your other wallets, that's a huge leap that we can take just by having that app installed on your phone. And people have larger apps, like, I suppose for somebody who plays Fortnite on their mobile phones, or Call of Duty, or PUBG, or what do you call it? Anyway, all of these mobile games, which are multi-gigabyte large games, it's not a big deal if they, for example, sync a gigabyte or two of the Bitcoin blockchain just to make sure that the incoming funds are legit.
48:41StadicusDefinitely.
48:42But I think, well, I mean, in the end, if you want to have an interoperability between wallets and full nodes, unfortunately, at the moment, it still works in layers. So you have to download Bitcoin Core. You need to sync it. Even if it's a pruned node, it still syncs the whole blockchain, although it then throws away the blocks that are already verified, so it doesn't take much disk space in the end, but it still takes a bit of time. And then you need to run Electrum somehow, like as a middleware that can be a full server, or what I really think is super helpful are these Electrum Personal Servers, for example by Chris Belcher, or the Bitcoin Wallet Tracker by Nadav Ivgi (shesek), which basically do the same.
49:38They just provide access for any kind of wallet like Electrum or the BitBox app or others that support the Electrum standard, and route it to Bitcoin Core. Because one of the main flaws in that setup, I think, is that Bitcoin Core is not really meant to be used with other wallets, so it's mainly built for the internal wallet and, yeah, that's not really how people use it these days. So you need this middleware. But there are a lot of options. But thinking in layers is just too hard.
50:21I think it should be like a one-click connect, that's it. I'm sure we're getting there. So many great people working on that, on Bitcoin Core with the hardware wallet interface, but also in like the Bitcoin Wallet Tracker, which is pretty new and pretty nice. But it's still quite a way to go still.
50:45Vlad CosteaPart of me is happy that we didn't get big blocks, because it's still easy to run a full node on consumer-grade electronics. You don't need computation more powerful than the Raspberry Pi. And in terms of storage, even today, it's more than enough to have a 500 gigabyte SSD, preferably. It's still early in the morning. I have a very bad pronunciation, but I was about to get to the Lightning part. Because it's a big debate nowadays.
51:18I saw a tweet from somebody who was asking, and that somebody was actually a Lightning business, asking, "So what happens if Lightning goes bust and all of our efforts of making this work just end up getting nowhere?" Because in the last few months, there wasn't as much development as there was in the last couple of years. It seems like we have reached a point of stagnation. And it's not just stagnation of development, because developers are actively working on projects. I think Lightning Labs has raised some money at the beginning of the year to continue development.
52:00But it's just that users don't really run their nodes and don't really make Lightning transactions as much as it was expected. And some may argue that the on-chain fees have been reasonable up to this point. And the infrastructure is better than it was three years ago or four years ago.
52:23StadicusI mean, it's not an either-or, right? So on-chain is still super usable for very cheap fees. But there will be spikes in the future, I'm sure about it. But we'll keep working on making on-chain real estate... like storage on the blockchain is really a super scarce resource and it should stay that, to be able to run your own full nodes. So there needs to be a certain price to that. And on top of that, Lightning, I think, is... I wouldn't say it's stagnating, I think it's maturing.
53:03And what people say, well, Bitcoin is old tech. I myself can no longer keep up with all the developments in Bitcoin. But for users, there's not that much progress visible, right? Because it just works how it's supposed to be. And a lot of optimization goes on under the hood, working on stuff that might be deployed in a year or so, and which will have not an exponential impact in regards to optimization, but it's still super important to do that, make it more secure, more efficient. And I think Lightning is getting to that stage as well.
53:43There was a huge spike in the beginning. And now the projects actually have to do the hard legwork, make sure everything works across multiple implementations. Now we have the atomic multipath routing getting deployed. So there are still so many pain points with using Lightning that are solved one by one. But I totally get this fear that I think Rusty of c-lightning replied to that question you mentioned: what if we build Lightning and users just don't come? And to an extent, I have the same... My biggest fear for Bitcoin overall is the same.
54:38This fear gets lower and lower over time because there's so much adoption going on. But what if Bitcoin is just the Linux of operating systems? It's the best, it's the most stable, most secure, the whole internet runs on it, but users just run Windows. And in that regard, I think we need to define what winning actually means. Do we want Bitcoin necessarily to be used by everyone? Or is it also okay for Bitcoin to be the new plumbing of the new financial system?
55:17Like Linux is the plumbing of the whole internet today and runs most of mobile phones without people actually knowing it. And I guess for me, if it comes to that, that would be okay. Of course, I still want to be able to be a self-sovereign participant in that. And if you put in some effort, you can do that. But if you don't want to, maybe you don't need to. And I think Lightning is getting to this stage as well, where it's just not as new and exciting again. But it's maturing and it's actually getting deployed in the wild for like real stuff. But of course, it's not exponential growth anymore.
56:07Vlad CosteaYeah, I remember the exciting times when people were bragging about 100% more channels being open from one day to the other. And all of these new nodes emerging in different countries across the planet. And people posting world maps of Lightning nodes being deployed every day. And it was exciting, but it seems like everything plateaued. And I haven't even seen as much Lightning activity lately. I have a tippin.me account, which I set up for tips. There was a time when I was getting tips all the time and I was exchanging them and giving them back to people and stuff like that.
56:49It seems like after Bottlepay shut down, we just entered this phase where nobody really makes Lightning transactions anymore for fun. And I think the killer app right now for Lightning, which I appreciate and which is growing, is Lightning Bounce, which is a mobile game on Android and on iOS, which I played, which I reviewed on the Bitcoin Takeover website, and which is kind of nice. It gets repetitive after a while. But for your high score in the game, you get a weekly reward of satoshis and you have to install a wallet like BlueWallet or like Wallet of Satoshi, and you withdraw the satoshis to your wallet, and that's very nice.
57:39It's like the developer, whose name is Jack, gets some money from advertisements, which he places in the game, and possibly most of the money that he makes from it, he reinvests in satoshis that are given as rewards to the players for scoring a good score. And I think that's really good and that's going to onboard a lot of people who don't necessarily care about Bitcoin...
58:05StadicusYeah.
58:06Vlad Costea...who possibly don't know anything, but they like the idea that they receive a currency that they can use to buy something else. It's not just V-Bucks in Fortnite, which is only for in-game purchases.
58:23StadicusI mean, on a very abstract level, Lightning is basically just a Bitcoin cache, and I don't mean like the Bitcoin Cash, right? But like a cache of a hard disk, or the caching that every hardware has in it, like even processors do caching. So maybe...
58:45Vlad CosteaC-A-C-H-E, yeah.
58:48StadicusExactly, like a cache. And maybe we haven't really found the right use cases just yet. I mean, I really love what Jack Mallers is doing, for example. His parents, like Bitcoin Mom and her husband, they run like a marijuana dispensary in Boulder, I think. And they're a cash-only business because they can't get a bank account. So they take Bitcoin. But many people don't have Bitcoin, so Jack built this Strike service that you can just pay in Lightning, but without having Lightning. You just need to connect your debit card to it.
59:32That's it. So that's, for me, that's a very compelling use case. And maybe in the end, we don't need to run our own Lightning full nodes at all. I'm not sure if Lightning really needs like a Raspberry Pi setup. In the end, for me, Lightning is something that screams to be run on mobile phones. But of course, you still need to have like a Bitcoin, like the on-chain part somewhere, unless you want to trust a third party again.
1:00:04But if you have a Bitcoin on-chain full node that also maybe runs a watchtower to monitor the chain, every smartphone is already able to run a full Lightning node on top of that. So you don't really need to have like LND or c-lightning or all that stuff running on your Raspberry Pi as well. So I mean, Bitcoin has evolved over time and it doesn't really care what we think the use cases are. Bitcoin just is. And I could easily imagine Lightning going the same way. It is here. It offers a service and people will actually find use cases for it.
1:00:46Maybe use cases we cannot really imagine at the moment.
1:00:52Vlad CosteaRight, and we are still very early. I know it's being said a lot, but there's still a lot to be done.
1:00:58StadicusAbsolutely.
1:00:59Vlad CosteaAnd some people are just LARPing on Twitter all day long and saying, "Yeah, we have reached this phase where Bitcoin is inevitable and everything works so fine." But developers are going to disagree and say, "There is so much that needs to be done." What we are seeing right now is just the tip of the iceberg. There's a lot that goes in the background. There's a lot of developing, a lot of testing, a lot of reviewing.
1:01:28And that's also something that newbies in the space don't understand. And that's something on which I'm writing an article right now. Because they say there's no development in Bitcoin, there's no innovation. It has been the same for such a long time. But that's not how development works. Just because you see new features being implemented on your favorite DeFi platform, it doesn't mean that they're properly tested. Their philosophy of development is to move fast and break things, and that's not something that Bitcoin can afford. You want it to be as stable and as predictable as possible. And you want everything that gets merged into a final client of Bitcoin Core to be very rigorously tested.
1:02:20StadicusAbsolutely. I mean, we need to have like atomic reactor software security when we're talking about the financial system securing billions of dollars in funds. And it might be something else if you're like running a DeFi or like a world computer. But even there, I mean, you have ridiculously high fees at the moment on Ethereum and applications just stop working. So that might be fine for them, but I wouldn't want my money to be on a platform that moves fast and breaks things. So it's really super important to be conservative.
1:03:05I mean, there needs to be progress, but it needs time. If it needs time, it should have the time to be thoroughly tested. And the same I see... I mean, we do consulting with enterprise clients as well. And there you have totally different problems with multisig and all that stuff that is just not ready for prime time yet.
1:03:32Vlad CosteaYeah, I guess our expectations as users are different. We see our favorite apps on our phones get updates, and we see operating systems getting updates all the time, and they can afford to mess up. They can afford to release a bad version of their software and then patch it. And it's an ongoing process even to them. But in the case of Bitcoin, you cannot afford to make any mistake. And there's also something interesting and perverse to some extent that's going on with development. Because you have Bitcoin Core developers who release the code and allow shitcoin developers to merge it into their own coins.
1:04:16And they can claim that they were the first to use it and the first to deploy it, but the information that gets generated in terms of feedback and what goes wrong is going to be very useful for the Bitcoin developers to figure out what they did wrong. So a lot of altcoins that claim to be the first ones to do something are nothing... Sorry, sorry for this. I pressed a button on the soundboard. So a lot of altcoins which do something for the first time are actually nothing but what's the term, lab rats or something. It's just that there needs to be some testing and feedback from users, because the testnet is not really reliable for incentives and a large number of users. If only developers use it and they know what they're doing, they're not going to make the stupid mistakes of the average consumer.
1:05:12StadicusYeah, so I mean, I guess Bitcoin Cash, and I mean BCH now forking off, in my mind, that was a pretty decent route for them to go. I think it helped them to fulfill their wildest dreams and whatever. And also let Bitcoin focus on what our vision is and not being bothered by all these guys every day and trying to influence and wreak havoc on our code base. So in the end, I think the market... in the end, the market decides what the best tool is, and I think that has been pretty clear.
1:06:00But there should be room for experiments like that. And even if it enforces or allows us to really drive home the point that a certain action is really not the right one, because we can point to certain altcoins that tried it and failed miserably.
1:06:21I think that's a good thing to have. So this is why I consider myself a Bitcoin minimalist. I just don't really care or have the time to work or be bothered with other projects. But I don't really think that there should be only one coin, because that would just leave us with all these guys in our own coin as well, without the option to do any experimentation. And in the end, I don't think that's a route that could work out ever.
1:06:56Vlad CosteaYeah, in open source software, you always need multiple teams to do some development. So you can't say that you should only have Trezor as a hardware wallet manufacturer. Because there are some limits that they have in terms of human capacity. And there are some ideas that they might not like, but somebody else is willing to try. And I think the BitBox fits a nice niche of products and adds some features that are not present in the Trezor.
1:07:29StadicusMm-hmm.
1:07:30Vlad CosteaAnd also, I think it's an in-betweener between the Trezor and the Ledger, because it has that security chip.
1:07:39StadicusYeah, I think we're in a pretty good spot with open source plus secure chip plus all the features we offer, like a really good multisig implementation and all that stuff. But in the end, I think most people in Bitcoin are more on the libertarian side.
1:08:04There's really no... A monopoly is never healthy. It makes you fat and self-confident. So competition is really, really important. As long, I mean, there can be like malicious competition, like exploiting each other or bad mouthing or having like Twitter armies wreaking havoc, but if we see us all like working towards the same goals, just with different projects, and like making sure that the overall goals are achieved, like I do with my RaspiBolt. I would never wish bad on any full node projects. The more full nodes, the better.
1:08:53So even with hardware wallets, I totally like Trezor, for example, and they are awesome in taking disclosures and working together with us. The same goes the other way around, of course. So if we work in a friendly way together with a healthy competition, I think that's the best Bitcoin can wish for. Because it makes each project stronger, harder, and protects us all against people that might not have the same goals that we have.
1:09:28Vlad CosteaYeah, that's also what Slush said during his interview. I think that was season 4, episode 7. And he said he's very much aware of all the hardware wallets, that even some of them, and this is not the case of the BitBox02, but some of them just shamelessly clone the software and create something that's not innovative in any way, but that's still useful for open source development, because they can come across an issue which maybe Trezor would have never discovered. And it's the same with the BitBox. You do research, and that's possibly the most important component and the most crucial contribution that you make into the hardware wallet space, because you constantly scrutinize the competition.
1:10:17And if you look at the bounty reward leaderboards, I suppose each company has these, except for Coldcard, who say they don't care. You see some of the same names. You see some Ledger people hacking Trezors. You see some Trezor people hacking Ledger, and you see people in the BitBox leaderboards being from all across the industry.
1:10:42StadicusMm-hmm. And I think, I mean, although we did like two independent professional security audits of the BitBox02 before we went into beta, to incentivize independent researchers, like really bright minds that might not have this as a full-time job, with a decent bug bounty program is the least every security company should do. And yeah, I mean, there can be like some arbitrary restrictions, which I don't really get, but I also don't want to get into it. But in the end, additional eyes on your code, on your security architecture, and incentivizing these people, if they should find something, to tell you first, this is really important.
1:11:33And this also shows how much you really care about your product and your users. And I know from personal experience it can be a humiliating experience. You really need to swallow your ego. But I really think you owe it to your users to own the issue, to be transparent about it and just fix it.
1:11:59Vlad CosteaYeah, and I suppose we have had some good examples of this and also some bad examples in this industry. And I don't expect you to comment on this issue, but I think one of the most essential parts about developing open source hardware and software is to allow anyone to copy your product, even though sometimes it affects you financially. Because when they copy it, they have greater incentives to find issues.
1:12:28And at the end of the day, I think the consumer will not mind to pay like 20 euro extra for your product, which is the original one and which has some actual development, as opposed to something which is a copy and only adds some features and puts it in a nice packaging to make it look like they have done something major. And we have seen, I think last week or in the last couple of weeks, a clone of the Coldcard. And the reaction of the Coinkite CEO was not that he looks forward to finding more security issues and fixing them.
1:13:11He said he was so confident in his own product, that it's perfect, that he wants to limit the licensing and basically enable anyone to look at the code, but not to use it for commercial purposes.
1:13:26StadicusI mean, for me personally, open source in the strictest, like in what actually benefits the user the most, is to be fully auditable. And I totally get that you might have additional, like some licensing on top of that. That does not really make the open source not open source again. So I can see both sides. I don't really have a strong opinion on that. But I think if you're building something really good, it's also totally fair to have like some licensing restrictions on top of that. But yeah, this is not really my issue, I'd say.
1:14:10Vlad CosteaYeah, I'm going to end this whole part of the discussion, but my argument is that the average user has no incentive to test the security. But somebody who copies your product is actually going to deal with some issues that they did not think about when they first started. And this process can be useful to actually fix some issues that your product has. So I would argue that the KeepKey was actually very good at helping Trezor improve. And everything that was released since has pushed security forward.
1:14:48StadicusYeah, maybe.
1:14:51Vlad CosteaAnd we wouldn't have discovered many issues if there weren't for other people to clone the code and try to develop some of their own products. If there was only this kind of white hat academic type of research and scrutiny, I don't think we would have discovered some real world flaws that happen when you sell a product.
1:15:16StadicusYeah, that might be true. I'm not really too deep into that, but I'm sure you'll have Slush on your podcast anytime soon again.
1:15:28Vlad CosteaI don't know about that, but... Okay, so you have suggested some questions about the BitBox02, and I feel like I ran my mouth about what kind of issues I had. So I should at least give you the chance to run yours about something which concerns your line of work. So what is the target audience for the BitBox02?
1:15:53StadicusI'm not really here to shill the BitBox02 too hard, but I'm happy to be able to highlight some of the nice features.
1:16:01Vlad CosteaBut I'm asking you to do it. So now that I'm asking you're supposed to do it, because I'm the host and you're the guest.
1:16:08StadicusYeah, so we're really trying to create a super easy to use hardware wallet. I think for most users, once you're above a certain threshold of funds you hold yourself, you should really invest in a hardware wallet. That should be a no-brainer, to put like $100 or whatever into your own personal security. But then of course it should be super easy to use, have minimal distractions. And I think we do that pretty well. It's super easy to set up. You can create the wallet backup directly on the included microSD card, so you don't need to write down all these 24 words. I think we like to call that the mnemonic anxiety.
1:17:01And I myself remember when I first set up actually my first Ledger, I had no clue what these 24 words were. I didn't know that the first four characters are enough for each word. So I really took my time. It took me at least half an hour to just write down these words. And that was a very, very scary moment for me. And that should not be part of the onboarding process. Of course, we do have the option to also export your mnemonic recovery words. For example, if you want to put it on a Cryptosteel or like just a paper backup, that should be an option.
1:17:43But I wouldn't necessarily want everybody new to Bitcoin to first be scared about that. And of course then our security architecture, I really like it as an open source company with hardware security in mind. I wrote the whole blog post how that actually works, how we are able to combine fully open source while still using a secure chip. For me, it was also a learning experience, like a lot is these days, working with so many great engineers. And it really helps my own understanding and appreciation of how the BitBox02 makes sure that the keys are also physically protected, always, without telling the secure chip any of the secrets. So I think that's important.
1:18:46Vlad CosteaAbout this onboarding, which doesn't require you to write down the words, isn't there like a risk for the SD card to get corrupted over time, or become unreliable at some point?
1:18:59StadicusSo I always say that the SD card is like the same as a paper backup. And of course, you should not only have one paper backup. It's also not encrypted, which is a bit of a discussion. But the corruption, I don't think you really solve that with selling like $20, $30 expensive SD cards. It's just way easier and more important to just make more than one backup. The SD cards we use are of course super high quality brands and the best that we see for this purpose. But you shouldn't rely fully on one SD card, of course, the same way you shouldn't rely on one paper backup.
1:19:48Vlad CosteaYeah, that makes a lot of sense, and it should be recommended somewhere in the booklet when you first do the backup.
1:19:56StadicusYeah, I'm going to pass that on. That's a good suggestion.
1:20:04The main thing is that it's super easy to just like write as many backups as you want in a very short time frame. You can just like pop in the SD card, make a backup, put it somewhere safe. Also take it out again and verify it directly. You should never put it anywhere else than the BitBox02. And if you use the integrated verify backup feature, we actually read it, check it, and then I think we write it three times again on the SD card, just to make sure that there are no like these little bit flips or whatever. So we really take a lot of care on writing it securely to the SD card. But of course, the biggest risk might be like just losing it or breaking it or whatever. SD cards usually have a time span of over 20 years. So that should be enough. And if you have two or three of them, that should be as secure as it gets.
1:21:07Vlad CosteaI've had some very bad experiences with external storage, with USB flash drives and SD cards and stuff like that, which I have had for some years. And for example, the SD card that I had in my first Android phone, I found it a couple of years ago and I wanted, you know, sometimes it's nice to run down the memory lane and see what kind of pictures I took and what I was into. But it was corrupted, and it was asking me to format the disk so I can access it.
1:21:39So that was disappointing when I realized that it happened. And it also happened to me with USB flash drives, which I was using for long-term storage, to put them in and see that message in Windows that it cannot be read and you have to format it.
1:21:55StadicusYeah, I mean, I can't comment on these specifics from afar, but there's a lot of cheap shit out there. So we really need and do make sure that we only use like quality brands and not... It's easy to get like cheap knockoffs, even with the real brand printed on it. So this is what we do, and these SD cards are really super reliable. Still, don't rely on one, make two or three copies, and then you should be really, really safe. And if you feel like this should be preserved over the next 200 years, just export the recovery words as well and put them on a Cryptosteel.
1:22:40And I've seen a picture on Twitter like you could grow your own tree around it or whatever. So it's limitless how you can then hide it and make sure that maybe your great, great, great children find it.
1:22:56Vlad CosteaOh man, this idea with the tree, you just gave me like a whole new world of possibilities in my head. Anyway, I should also ask you about the multisig, because there's been a lot of development that you have done with Shift Crypto in this field.
1:23:15StadicusSo, I mean, I guess we're running a bit out of time, but the high level gist is that for me, in my experience, I've seen a lot of people touting Bitcoin multisig as like the silver bullet. Like you need to do it, everything else is not secure. And this is just plain wrong. Multisig, if we're talking about multisig with hardware wallets, because multisig, just software wallet might be okay for some applications if you have like multiple responsibilities and stuff like that. But if we're talking about cold storage, hardware wallet multisig, it's so hard to do properly and many people don't understand what the pitfalls of these setups are.
1:24:12So for example, did you know if you use Electrum, you do your multisig setup with three hardware wallets, you write down the recovery words for every hardware wallet and you store these backups safely. Did you know that with a two out of three setup, you lose one hardware wallet. You still have the backup, but you lose a hardware wallet. Your funds are gone forever.
1:24:44Vlad CosteaYeah, I know that multisigs can really mess up stuff if you don't know what you're doing. And I saw somebody on Twitter do a 16 out of 16 multisig. And that's kind of crazy.
1:24:58StadicusYeah, it also results in super high fees. But the first issue is that you need to really make sure that you also back up your extended public keys and all that stuff, because otherwise you're just not able to reconstruct the script that has been used to lock up the coins. So just the backup itself is already heavily underestimated. Then if you receive funds, you know you need to verify the receiving address, right? Because the software wallet on your computer can just tell you, "Well, this is your address.
1:25:38Please send to this address." And if you have a malware on your computer, you just might get an address that is actually not yours, but that is controlled by the attacker. So if you have a multisig setup and Electrum tells you this is your address, it's almost impossible to verify this address. A Ledger cannot do it at all. It just says, "Well, you're on your own." It can't even display anything on the hardware wallet. And I think while there is some progress with Trezor, the main problem is that hardware wallets don't know who the cosigners are. And you can only derive the receiving address if you know who the cosigners are. So for every receiving address, you need to manually verify all the xpubs of all the cosigners on your Trezor. And that, of course, is not something users are even aware of, and if they are, it's super painful UX.
1:26:50So receiving is hard and the same goes for sending. If you're sending with a multisig setup with hardware wallets, you need to make sure that the change is coming back to you. So you're sending maybe one bitcoin to someone, but you only have a coin that is like, oh well, big numbers, but you might only have a five bitcoin coin. So you send one and you expect the transaction to send four bitcoin back to you, right? And this is, of course, again, an address that needs to be controlled by you.
1:27:25And current hardware wallets like Ledger or Trezor simply cannot verify that automatically. With Trezor, you can at least do it manually, but it's pretty well hidden. And I think this is what our advantage with the BitBox02 is. This issue is only addressable if the hardware wallet itself knows who the cosigners are, and the BitBox02 lets you store this information directly on the hardware wallet. We have 10 slots for 10 different multisig accounts that you can put a name on and store directly on the hardware wallet. And with that, you're able to use multisig in a more secure way than with any other hardware wallet like Ledger or Trezor.
1:28:21Vlad CosteaOkay, so you did mention that we are running out of time, but you have some questions from the audience and let's do it like this. We take 10 minutes for them. You try to be as concise as possible.
1:28:30StadicusI'll try.
1:28:31Vlad CosteaBut the questions seem to be kind of specific. So let me write a timestamp for this specific moment so people know to come to this exact time to see their questions answered. So Stillwater62F wants to know: "Caravan, Lily Wallet, etc. You always need to keep your.json file on the multisig setup. Since the BitBox02 has the microSD card slot, wouldn't it be an interesting feature to be able to store the JSON file on a dedicated microSD card inside the BitBox02?"
1:29:11StadicusI'm not too familiar with that setup just now. I know there are a few possible features where we could use the secure SD card setup as well, also for multisig or just passing like partially signed Bitcoin transactions between wallets. And I don't think I'm really able to answer that question. The one thing that is important to keep in mind is that you should never then like connect that SD card to your regular computer. So I'm not sure what the overall benefit would be.
1:29:53It's the job of the hardware wallet to keep your coins safe anyway. And the BitBox02 can do that because it already stores all the cosigner information on the device. So even if Lily Wallet or other multisig wallets are fully compromised, you would be able to detect that. So I'm not sure if securing this JSON file additionally would add a lot of benefit, but I'll look it up. Would be interesting to learn more about that.
1:30:27Vlad CosteaOkay, so Vicarious Drama wants to know: How many full nodes do you run? How many is too many? And should we run full nodes of mainnet and testnet?
1:30:39StadicusYeah, let's start with the last one. Testnet is heavily underrun. So I run, I think, two testnet nodes, one externally, one on a Raspberry Pi for my internal usage as well. Sometimes it's hard to find one and connect to it.
1:31:03Overall, I run a couple, but to be honest, I don't have the number in mind, maybe four or five at the moment. But they get taken down pretty quickly. So actually, while I do run a lot of full nodes, I don't think I really have a stable one. In terms of Lightning for Bitcoin stuff, definitely I have my own Tor setup that I connect to, but I don't really have a Lightning full node at the moment with stable channels. So that might be something that I should think about over time. But I mainly run Lightning on... Sorry.
1:31:43Vlad CosteaYou still have to tell us how many nodes are too many nodes.
1:31:48StadicusI think it depends on what you need it for. If you need it for your own purpose to verify on-chain transactions, one is perfectly fine. Too many nodes, maybe there's your wife that has something to say about that as well.
1:32:06Vlad CosteaOh no, so that's the ultimate signal, right? When your wife tells you, "You know, what's with all these devices and all these wires in our house?"
1:32:15StadicusExactly.
1:32:16Vlad CosteaOkay, so Goon34 wants to know if you're going to add Guggero's, G-U-G-G-E-R-O-S, chantools to RaspiBolt.
1:32:34StadicusPossibly. I see the future of the RaspiBolt more in the backend kind of space. Having it as a Lightning, not really a user-faced Lightning node, I think that's going to move to mobile anyway, but having like a stable Lightning backend with additional tools like watchtowers or these of... He's working for Lightning Labs, the one you mentioned. So these tools would be a very interesting addition in that area, where I see the RaspiBolt going.
1:33:18Vlad CosteaOkay, so you also have some other questions like: Is there a push to get BitBox02 support in Caravan?
1:33:29StadicusYes, we do push. We do want to have it there. We do offer assistance for implementation. And I guess the more people ask for it directly at Unchained Capital, the faster it gets implemented.
1:33:49Vlad CosteaOkay, so the last one from the same person, who is Vicarious Drama. What's the future direction of RaspiBolt now that there are many other node projects out there, especially easy to set up like myNodeBTC and Umbrel?
1:34:04StadicusMm-hmm. I really see the RaspiBolt more as an educational project. So if you want to go do the legwork, understand how everything interoperates under the hood. And for that, I see it more, as I mentioned, as a back-end appliance over time. So having a Lightning with some good management tools on it, that would be pretty awesome. But to me personally, on-chain always comes first. Now with Electrs, Electrum Server and all that stuff. And Lightning with the management for channel management, all that stuff on top.
1:34:48I think that is the way where I see it. But it's also like my personal side project. So I always need to make time to actively work on it. And it takes a lot of time solving issues and stuff like that as well. So I wouldn't expect any super big overhauls within the next few weeks.
1:35:15Vlad CosteaAlright, so you only have two more questions. One of them concerns whether or not you use GPG encryption on a YubiKey in your daily life.
1:35:26StadicusYes, I do. I think it's super important. I use the BitBox as a second factor authenticator, but I still use all my YubiKeys to decrypt, of course, and sign my GPG messages. All my commits to GitHub are signed with GPG and I make sure that my keys are never... It's like cold storage, hot storage again, right? So my keys are never exposed on the computer itself. I think for me that's... I mean, GPG mail is super niche. We really use it only for communicating when there are responsible disclosures with other security professionals.
1:36:11But signing my own GitHub commits, I think that's a pretty decent way of ensuring that, or just increasing the quality of the code base.
1:36:26Vlad CosteaAlright, and Enki Tech wants to know what's next for BitBox. Also, what node setup is the easiest for connecting to BitBox app?
1:36:37StadicusSo, I guess with BitBox he refers to the hardware wallet. So, hardware-wise, we're in a very good space. We're working slowly on adding additional features to the firmware, like integrating with other wallets or extending features for multi-signature setups. Where our current focus is more heavily invested is the user experience, more on the app. So we do have like monthly releases of the BitBox app and a lot of the easy to recognize improvements are more in the app, because the BitBox as it is, I think it does what it needs to do, and the user experience mainly comes from the app. What was the second question?
1:37:32Vlad CosteaSo what's next for BitBox, and there was... Wait, I should open it once again. What node setup is the easiest for connecting to BitBox app?
1:37:49StadicusHard to say. I think, I mean, the good thing is that all the plug and play nodes out there that have Electrum or Electrs or Electrum Personal Server work directly with the BitBox. So, I guess if you want to buy something, it's probably Nodl. If you want to just set it up yourself and try it out, it might be myNode. If you're more into a little bit technical stuff, more features under the hood, RaspiBlitz, of course, is awesome as well. So a lot of options. Probably depends on what your own goals are.
1:38:35Vlad CosteaI really like this last answer. It gives you all the possibilities and explains why. So, Mr. Stadicus, we have been speaking for 1 hour and 39 minutes now.
1:38:46StadicusHoly shit, that went fast.
1:38:49Vlad CosteaYeah, I know, just like the best things in life. So, how can people follow you on Twitter, contact you, ask you questions about the BitBox02, possibly about RaspiBolt and other Lightning stuff that you do on full nodes?
1:39:05StadicusSo I guess, I mean, I do run my own super minimalist one page website, which is stadicus.com. It's mainly my place to securely publish my PGP keys. You'll find everything there. And otherwise, I'm mainly on Twitter as @Stadicus3000. You can text me there. Direct messages are always open. Happy to get any feedbacks on the RaspiBolt, BitBox, Shift, whatever topics are on your mind, as long as it's Bitcoin related. And yeah, I'm happy to interact and answer questions.
1:39:46Vlad CosteaI'm happy that I got to have you on this podcast and I feel like I've learned something new today. Thank you very much for your time.
1:39:53StadicusThat was awesome. All the best to you, Vlad.
1:39:59Vlad CosteaAll the best to you and your work, because there is so much that you do and it's so underappreciated, if you ask me.
1:40:05StadicusGlad to hear. Thanks a lot.
1:40:07Vlad CosteaI'll talk to you later. Bye.
1:40:07================================================================================ Production notes: Remote video/audio recording in English with an intro music segment (guest muted during intro), soundboard use by the host, a live audience Q&A section near the end, and no sponsor reads. Correction: anthropic/claude-opus-5.5 via NanoGPT in 6 windows with a whole-episode speaker/glossary plan, the show notes, the Qwen3-ASR full pass (132 chunks) and 46 Scribe v3 re-checks of doubtful spans; [unclear] resolve pass: 1 of 1 flagged paragraphs re-checked. Automatic checks: word count vs raw, timestamps, seam duplication. Fixes: Guest A→Stadicus; removed "Thank you for watching..." hallucinations (01:26, 08:44) and stray "Thank you."; split speaker changes at 01:35/01:45 and LND interjection at 06:31; fixed RaspiBolt, SegWit2x, scaling wars, Damian Mee, hardware wallet, RetroPie, tinkering, Tor relay, RockPro64, Casa Node 2, BitBox Base, Raspberry Pi 3B, "joined Shift Crypto", "too perfectionist"; restored dropped "powerful. It can do it maybe in three or four days" from second ASR; Guest A → Stadicus; fixed RaspiBolt/RaspiBlitz, myNode, Nodl, nix-bitcoin, NixOS, Pavol Rusnak, Stick, Samson Mow, Jonas Schnelli, Douglas Beckham exchange, Trezor, BitBox02, Coldcard, BTCPay Server, HODL, "suite"; removed hallucinations ("Thank you", "Thank you for watching...", "Welcome to the episode...", "We're going to talk about...", "So, yeah, I think that's what happened"); split Vlad/Stadicus exchanges at 17:42, 23:21, 23:59; stray Mm-hmm removed; Guest A→Stadicus; removed hallucinations at 00:34:48 ("Thank you for watching…", stray "Thank you"), 00:40:49 repeated "them to do so", 00:41:12 "We're going to talk about… make money" and "That's it."; restored dropped speech (lock certain transactions, goldsmith passage) from Scribe/Qwen; fixed hardware wallets, Shift Crypto, Ledger, Luke Dashjr, sync, xpub, thought leader, effect, GreenAddress, Blockstream Green, ABCore, pruned node, Nadav Ivgi (shesek), Electrum Personal Servers; "Definitely." at 00:48:41 assigned to Stadicus; split 00:44:27 monologue with interpolated 00:45:00; Relabelled Guest A as Stadicus; split interjections ("Yeah", "Absolutely") to Stadicus; removed hallucinations ("Thank you for watching...", "Episode:", "We're not going to"); fixed RaspiBolt-era jargon: tippin.me, Bottlepay, BlueWallet, Wallet of Satoshi, V-Bucks, c-lightning, watchtower, Strike, prime time, multisig, cache spelling; restored dropped "route it to", "run their nodes", "lab rats" phrasing; Removed hallucinations ("Thank you for watching... Bye-bye", "The first thing you need to do is to create a new account", stray "Thank you."/"Bye.", "We are here at the Bitcoin.com", "This is a very important step for Bitcoin", "Boxo Tut") and restored dropped speech from second ASR/Scribe ("contribution... competition", "hardware wallet. That should be a no-brainer", "again on the SD card", "cheap knockoffs... real brand printed on it", "because I'm the host and you're the guest"); fixed speaker turns (Stadicus "Mm-hmm"/"Yeah, maybe", 01:16:01 boundary); names: Slush, Coldcard, Ledger, KeepKey, BitBox02, RaspiBolt, Cryptosteel, Coinkite; shield→shill; Guest A → Stadicus; restored dropped Vlad line about 16-of-16 multisig; removed "Thank you for watching..." hallucination at 01:29:11; fixed speaker boundaries (I'll try, Exactly, Holy shit, Thank you very much, Glad to hear); jargon/names: Trezor, hardware wallets, xpubs, chantools/Guggero's, RaspiBolt, RaspiBlitz, Electrs, Nodl, myNode, Umbrel, Unchained Capital, Lily Wallet, YubiKey, stadicus.com; "softwa