Research
Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
Home / Podcast / S5 E6 / Transcript
Transcript · S5 E6 · 57:07 · 1 May 2020

S5 E6: Nopara73 on Wasabi Wallet, P2EP, Samourai & Bitcoin Privacy

← Episode page Plain text
Machine transcript, corrected by hand. It can still contain mistakes, so the recording is what counts. Tap any timestamp to play from that moment. Use Cite to copy a timestamped link and a short attribution. Dotted words were hard to make out in the audio.

Search this conversation

0:29Vlad CosteaHello there and welcome to season 5, episode 6 of the Bitcoin Takeover podcast. I am Vlad and my guest today is nopara73, who is a wallet developer and not the developer of any wallet. He has worked on his own while traveling through Asia to develop Wasabi Wallet, which is the most popular desktop privacy wallet for Bitcoins. And it has so many great privacy features, from CoinJoins and all the way to a Tor implementation and all the way to pushing you to only use addresses.

1:22I mean, receiving addresses only one time. And it's an overall great experience. If you ask me, it's one of the best wallets ever. And in recent months, it has even added support for a full node for your hardware wallets. There's a lot going on and it's turning out to be one of the best mobile, not mobile, sorry, one of the best desktop wallets ever. And I hope that they get a mobile version too, because it's really great. So hello, Nopara.

1:53nopara73: Hi Vlad, thanks for having me.

1:57It's really good to have you. And I have been craving, basically, for somebody who can come on the show and explain what CoinJoins are and how these wallets that we have nowadays are different from the tumblers and other services that were mixing your coins in the early days.

2:23nopara73: Sure, let's get right into it. So CoinJoin is a really simple concept. When you build a Bitcoin transaction, if you don't sign it, then that Bitcoin transaction, while properly built, it is not signed, so it is invalid. And we can use this concept to get many people together to build together a Bitcoin transaction, a big one with many inputs and many, many outputs, with many users contributing to inputs. And if one of the users does not see the correct amount, the correct outputs, his desired outputs, then he's not going to sign the transaction. So the transaction is not going to be valid. This is the magic of CoinJoin, that you cannot lose your money. At least you would have to make a very, very bad implementation if anyone would lose money with CoinJoins. So this is the security aspect of CoinJoins. This is trustless.

3:36nopara73: That's CoinJoins. Privacy things are more nuanced and complex there, but I'm not sure we want to go into that, because we mainly want to talk about pay-to-endpoint here, right? Which is a special kind of CoinJoin, where both the receiver and the sender of the transactions participate together. Both the receiver and the sender of the payment participate in the same transaction, which results in interesting properties, which I don't think anyone knows exactly what it results in, but the ideas there seem very, very promising. For example, such transaction looks like just a regular Bitcoin transaction, and that can throw off blockchain analysis.

4:44I mean, that's really interesting because, as far as I could read, the first ever Bitcoin client created by Satoshi Nakamoto had this feature to send your coins to another IP address, and the other person had to be online at the same time and could receive the coins without generating an address. But as time went by, the feature has been removed. And Pay to Endpoint is somewhat similar to that concept because it's direct. It's truly peer-to-peer.

5:16nopara73: Yeah, so let me see. P2EP, the naming of it at least, has come out of a CoinJoin meeting where many privacy researchers and Bitcoin Core contributors have participated, and some of them would like to stay anonymous, so I'm just going to say those who actually gave the name in that meeting, which was, let's see, Adam Back, Matthew Haywood from Blockstream, Dan Gershony from Stratis, he's not working at Stratis anymore, who else, Adam Gibson, you know, JoinMarket, and a couple of other people.

6:16nopara73: So, and in that meeting, we thought about the idea of... I wrote a blog post a while ago which is called "Clusterfuck Wallet", where the idea was that we could make many kind of different transactions and that could throw off blockchain analysis. And I wrote that blog post based on a presentation of Adam Gibson, where one of the ideas was: what if the receiver puts some UTXOs into the transaction too, and what would happen there?

7:05nopara73: Now we know that there was a feature Satoshi implemented back then which was called Pay to IP. So you could give an IP address to someone else, and then you could negotiate the transaction with them, what kind of transactions you want to build. And well, we would have called this sort of thing what we came up with pay to IP, but that wouldn't be a very correct name, because we didn't want to constrain pay to IP to IP addresses, because you could give a domain, just a web address, like, okay, I don't have to give an example of other addresses, and also an onion domain.

8:01nopara73: So the generalization of the IP is endpoint, so it becomes pay to endpoint. And the scheme that looked the most promising that could be achieved with this pay to endpoint concept, where the receiver and the sender build up a connection with each other, is called PayJoin. We did not call it PayJoin back then. We called it the sender-receiver scheme, which is a terrible name because it doesn't... I don't know, it just sounds lame. After that, Mr. Busta from Bustabit came, wrote a BIP, a Bitcoin Improvement Proposal, where he called it BustaPay.

8:58nopara73: And then later Adam Gibson implemented it in JoinMarket and he called it PayJoin, and then the PayJoin name seemed to stick. So that's the story with the naming there. Oh yeah, and there was another side talk there, that these Samourai guys said they came up with this idea before in their internal conversations, and they're gonna call it Cahoots, or Stowaway. Yeah, Stowaway. Okay, so they did, and yeah, this is actually pretty interesting. So they did implement PayJoin after that, one of the first ones who implemented it. But they implemented it in a way where you have to show QR codes to another person in the wallet, and you have to show it multiple times.

10:09nopara73: So that's how the transmission of data is going. So for me, this is PayJoin, but this is not pay to endpoint, because you don't show the QR code to establish a connection between the receiver and sender, which would be classified as pay to endpoint, but the QR code is actually the transmission protocol, back and forth. So that's why it would be PayJoin. Although you could make the case that showing each other QR codes would classify as pay to endpoint, it's just another method.

10:58nopara73: Anyway, not important. So the thing with pay to endpoint is that it has much larger potential than PayJoin, because with pay to endpoint you could do a lot more things. For example, you could do merge avoidance, meaning the sender gives you multiple Bitcoin addresses instead of just one Bitcoin address, so that would be neat too. Or knapsack mixing, where you would optimize the possible number of subsets in the transaction, and that's how you would create your output amounts. Or just simply trying to create equal amounts.

11:49nopara73: Or one of the most exciting things about pay to endpoint would be to actually negotiate with the receiver whether you are going to send an on-chain transaction or a Lightning Network transaction, and the users of the wallet wouldn't even have to know about it, that, oh, this was a Lightning transaction or this was an on-chain Bitcoin transaction. So pretty cool things are possible here. And let me see. My concern, and it's not really a concern, my problem with the current pay-to-endpoint implementations is that they are using Bitcoin URIs, which is fine and it's working.

12:40nopara73: But I kind of have larger ambitions for it. So what I would like to see happening is that if I give you a Bitcoin address, then you can either send me the money or some magic establishes a connection between me and you, based on just that Bitcoin address. I think it's important to not ruin the existing user experience of the Bitcoin wallet, so you could just give Bitcoin addresses to each other like always, and that would be cool. That's not how it was implemented. So this Bitcoin URI stuff is already used in merchant scenarios, when you are paying to a merchant, and that works perfectly.

13:36nopara73: So I don't have problems with that in that way. And also I'm fully supporting it because, well, finally a privacy feature is implemented that not only helps your privacy, but actually helps... So people say it helps everyone else's privacy. That's not really correct. There are still patterns there, but what would be more correct to say is it helps more people's privacy.

14:13So I need to ask you about the main differences in terms of drawbacks between CoinJoins and pay to endpoint. Is any of them more efficient in terms of blockchain space and number of transactions necessary to reach privacy?

14:30nopara73: It's a good question. I mean, pay to endpoint doesn't really provide much privacy for you, does it? It provides some, but its goal isn't really to provide privacy. It's to trick blockchain analysis, to make sure it has more of an accumulating effect on the whole network's fungibility than your personal privacy, because what happens on the blockchain is still... like, even if they don't know that's a pay to endpoint transaction, they know that there are parties, those are transacting. So it's not like you would hide in an anonymity set or something.

15:27nopara73: It just makes it harder to interpret what exactly happened in the transaction. It doesn't really hide that you are transacting with who. So that's what CoinJoins... well, PayJoin is a CoinJoin. So that's what, let's say, equal amount CoinJoins do, trying to hide who pays to who in an anonymity set.

16:00Would you say that, to some extent, chain analysis can identify CoinJoins? And maybe that they don't figure out where the coins come from, but they can look at the outputs from before the CoinJoin happened and possibly find some identification there. And if there is something that they can do in this regard, then what can users do to protect themselves?

16:26nopara73: Well, it's not to some extent, it's 100% that CoinJoin is identifiable, 100%. It's not a secret, you know. It's something that's quite inherent in the privacy community that, you know, you cannot hide in a crowd without that crowd being identified. If you are using Monero, then the crowd is the Monero users. So Monero transactions can be identified and distinguished from Bitcoin transactions. So yes, that's definitely identifiable. It's more like a social problem that if you don't want to tell me how much money you have, then... Then you do CoinJoins and that makes you a criminal because you don't want to tell everyone how much money you have. You know, that's a strange logic there.

17:39Right. So, would you say that right now Wasabi Wallet is in a situation where it is censorship resistant? Because we have seen along the years many CoinJoin and tumbler implementations that were actually centralized and had a company coordinating the whole operation being shut down by government agencies or just closing down for various reasons. How is Wasabi more resistant to this kind of situation?

18:13nopara73: It isn't at all. Like, it wasn't a design goal to build something that's censorship resistant. The design goal was privacy. It's hard enough to build privacy, than to build something censorship resistant. It's a gamble, right? So until they let us protect other people's privacy, we can go on, and otherwise don't. But again, things like, let's say, JoinMarket, well, it's more decentralized because it only needs a bulletin board as a server. But again, it needs a bulletin board, which they are using IRC for.

19:04nopara73: So if you shut down the IRC, then people don't find each other. So privacy in Bitcoin right now is not censorship resistant. Monero, Zcash, these altcoins would be good examples of what is censorship resistant, because that's the function of the blockchain, to be censorship resistant. In fact, it's quite interesting. The literature of trying to build an electronic money had, well, three issues identified. And the three issues are: how do you protect your privacy on the network level? So that's where the anonymity networks, Tor, onions, mixnets, I2P, that's where all these things are trying to make advances. The other issue is how do you build money that's private? And this is where the Chaumian eCash research literature is building upon. Implementations are lagging behind because, of course, these are centralized systems, but we can take a lot of ideas from them at least.

20:42nopara73: And the third one is that how do you build money that cannot be shut down? And that's what Bitcoin solved. Now, some altcoins are trying to bring together the privacy and the decentralization into one thing, one blockchain, and good luck for them. I don't think that's the way to go, because that's not how human progress works. Human progress is building on top of pre-existing work up until the point where that mess that we created is just so much worse than the new altcoins would be that the new altcoins just take over slowly.

21:36nopara73: So, oh yeah, so there was this three direction, and with Bitcoin we solved the decentralization. The eCash guys are trying to figure out the anonymity, the fungibility part of it, and protecting your privacy with different anonymity networks is something else too. And if we could bring these three together, that would be really cool. If we could bring these three together into Bitcoin, that would be really cool.

22:11So Bitcoin is really missing privacy, but I don't think it will ever be fungible at the same time, because every coin ever created has a cryptographic hash, which demonstrates when it was created, where it was mined, what time, you know, all of these indicators. So you cannot say that one Bitcoin created today is the same as one mined in 2010. And you can discriminate between the two if you want.

22:40nopara73: You know, if you ask the same question one month ago, then I would 100% agree with you that Bitcoin privacy is kind of lost. I didn't see much advances or ways to improve it a month ago. But a month ago, we started to work on the new mixing technology with Wasabi. And it's not even this mixing technology, but just the sheer amount of research that's being done in eCash and cryptography that could help us make Bitcoin ultimately more private. Just one example would be coin swaps, the kind of coin swaps where you have to swap at the same time.

23:33nopara73: But you can make a swap preparing transaction at one time, and the other guy could even choose to spend your transaction like a year from now, and this would be completely indistinguishable from normal transactions. Now, what this would result is that you can look at the blockchain, you can make your heuristics, but you could not make any conclusion on what coin teleported where in years' time.

24:19That really does sound fascinating, and it can be useful to do this kind of swap that takes a year or more, so that nobody can actually find the link between the two transactions that happen. But how do you make sure that this doesn't get broken and somebody, for example the first person to receive the coin and before the swap happens, manages to spend it? I don't know how this scheme could work.

24:49nopara73: Tadge Dryja, one of the inventors of the Lightning Network, presented this idea for us, so there is definitely something in it. I mean, he's really smart. I can't claim I understood completely the scheme. But my point was that this broadened my horizon on what kind of things are possible to improve Bitcoin privacy, which I could never have guessed before. So I became more bullish on how Bitcoin privacy will end up in the future.

25:41So, there is always this debate about which wallet you should be using. And I have had a guest in the second episode of this season. His name is Leo Wandersleb and he works on Mycelium. When he doesn't work on Mycelium, he has created a website that's called WalletScrutiny.com. There you can find his reviews based on the verifiability of each wallet and whether or not it's open source. But he only took a look at wallets that are in the Android App Store, so only mobile ones. But it's still a big concern, right? So if you could recommend somebody who is new to Bitcoin a desktop and a mobile wallet, which ones would they be?

26:32nopara73: I would recommend... Well, that depends on: does the new person speak English? If yes, then I would recommend Wasabi. If no, then I would recommend something else that has it in his language. On mobile, I would recommend Green Wallet, both iOS and Android, because I don't have much expectations from mobile wallets, or generally in Bitcoin wallets. But what I really care about is that this works and is stable, and when you click on the send button it does not freeze or things like that, right? So that's the most important thing for me, that it does not give a heart attack to the user, and I found Green Wallet such a wallet. Oh, so that's why I think it's called Blockstream Green right now.

27:34Oh yes, Blockstream Green. But it's available on both Android and iOS. And what I like about it is that it has Tor. It has some sort of two-of-two multisig that basically offers an extra layer of protection just in case you make a bad transaction or somebody takes a hold of your wallet but doesn't have access to your email.

28:01nopara73: Yes, it is. It does some multisig stuff, and by me using it and not knowing about it, not knowing exactly what's happening there, that just means they did a terrific job in abstracting the technical details from me, the user, right?

28:27So right now, if you think about privacy wallets, you have to make a choice between Wasabi and Samourai. And if you're technically minded, you can join JoinMarket, as I guess anyone can agree that it's the more decentralized and sophisticated method of mixing your coins. But other than that, for everyday use it comes down to Samourai and Wasabi. And how would you describe the differences between your wallet and Samourai's?

29:02nopara73: So first of all, I think JoinMarket has a bad on- -ramp experience. But if you somehow figure out where to find the exe to download and run it, then it's really no different than a normal wallet. A bit more technical, but not that big of a deal. So let's just not say JoinMarket is not that user-friendly, because it's always the biggest, the largest problem that I encounter when I want to install a new JoinMarket version is to go through the walls of text and figure out where to download the binaries from. Anyway, with that out of the way, no, don't use Samourai. I, well, I'm definitely biased.

29:58nopara73: Samourai works in a way where you fire up your Samourai Wallet and you send your xpub key to their server, so their server can tell you your wallet balance and that way you can build your transactions. And this is of course not good, because if you do CoinJoins, then they can see that one of the input addresses and one of the output addresses correspond to the same xpub key without any difficulties. And I think the marketing that they are doing is trying to hide this fact pretty strongly.

30:43nopara73: And one of the newest things that they came up with is that if you are using Dojo, which is their full node integration, then you get all the benefits of CoinJoins. But that's just not true, because they have five-participant CoinJoins, and let's say four of them are using Samourai without their full node implementation. Then you don't need to be a genius to figure out which input and output pairs you cannot de-anonymize. It's exactly the one that you don't have the xpub keys for.

31:26nopara73: And for this they came up with, "Oh, but 60% of our users are using Samourai with their full node implementations," which is a ridiculous lie, which cannot be verified. But again, like, if you look at the number of people who are running a full node, a Bitcoin full node, a 100 gigabyte, 300 gigabyte thing with a lot of processing power on their laptops, and how many people are not using that, how many people are using light wallets, and how many people are using just Coinbase, the full node Bitcoin user percentage would be like 0.00001, something like that.

32:20nopara73: And that's why the 60% claim is just ridiculous. Because it does not seem so. It does not be consistent with any other experience that we had before. And anyway, like, you would have to trust them to... Oh yeah. And how do they know that anyway? Like, so does that mean... Okay, let's assume that 60% is true. That would mean you are only mixing with three other people instead of five. And also, the only way to know that is that they are actually logging your xpub keys, which means they aren't trying to throw away that information.

33:17nopara73: They are logging it. They see that in the CoinJoins, three people don't have the xpub... But anyway, I don't even have to go there, because it's just a ridiculous claim.

33:30Yeah, sometimes the discussion on Twitter is that Wasabi Wallet is only for the rich coiners, because getting into a CoinJoin will require an amount of minimum 0.1 BTC usually. Sometimes it's 0.09 something, but it rounds up in this interval. And they say that with Samourai, you can do CoinJoins with smaller amounts, so it's there for the people who don't own many bitcoins and want to do CoinJoins of their own. Can you elaborate on why there is this difference and why you need a larger amount of Bitcoin with Wasabi?

34:13nopara73: Sure, because the tech is not there unless you are cutting corners. There is this thing called denial-of-service attack on CoinJoins, which can happen in a way that, let's say in Wasabi, our minimum denomination is 0.1 Bitcoin. So if you have 10 Bitcoin, you divide it up to 0.1 Bitcoins, then you would be able to denial-of-service attack 100 rounds, and that would mean CoinJoins would not happen for two hours or something like that.

34:51nopara73: Now, if you go lower, like what is their smallest denomination, 0.005 Bitcoin, then you can divide the 10 Bitcoin down to 0.005 Bitcoin and you can make sure that no CoinJoins are happening for, I don't know, for a month or years, something like that, because that's how those protection works. If an input misbehaves, then that input gets excluded from the next CoinJoin round. And that's the DoS protection of these CoinJoin services. So why they are doing that is because no one is denial-of-service attacking, so they get away with cutting corners here. There are other ideas how to fix the denial-of-service attacks.

35:46nopara73: And in our next mixing technology, we are going to explore them properly, so we can make the minimum amount lower without actually compromising on security. And I'm cautiously optimistic that we will be able to do that.

36:10So that's quite a simple explanation, really. But Samourai has tried to make it more accessible, but it comes at the expense of risking to get more denial-of-service attacks. Is that, in plain language, what happens there?

36:21nopara73: Yes.

36:22Okay. So, I also want to ask you about the user interface of Wasabi, because it underwent many changes in the last few months. And where is it heading and what are you planning to add in the near future?

36:44nopara73: To be honest, I don't know, because two, three weeks ago I started researching. We actually hired the cryptographer István Seres, and Nothing Much, who is like Greg Maxwell. He knows everything. And I don't micromanage the software's development anymore. I don't review everything that's happening there. But generally, what I'm seeing is that whoever has good ideas and implements them, and those features, those things are clean, then it gets merged. So it's more of an organic process than a top-down approach of development, which has its drawbacks and it has its advantages. Right now, I'm concentrating on the mixing technology and let the UI, UX and code part to other people. This is how we share the work.

37:58That's actually interesting, because you are the mastermind behind the whole Wasabi Wallet project, but at the same time, it seems like you're stepping down, but doing more research. So is it possible that you'll start another privacy project, or will all of your research show and get materialized in Wasabi Wallet?

38:23nopara73: So, how I think about it is, this might be my last big journey with Wasabi Wallet. I mean, you are human too, so you might be able to connect with me in the way that I spent five years without really much weekends, working hard on this project, and I might be interested in other things too. So possibly this new mixing technology will be my last big project, and I certainly look at it as a piece of art rather than some job that has to be done.

39:10nopara73: Yeah. So what we want to do here is basically fix all the problems with Wasabi, which are, one of these you already mentioned, this minimum amount thing. The other thing would be there is a change. There is often a change in the CoinJoins which don't get anonymized. Of course we can show red coins in the wallet, which is fine, but what would be actually cool is if there would not be change, and that's what we are trying to fix. What else? It would be really cool if you could send money directly in the CoinJoins instead of just mixing to yourself. What kind of money experience is that, you know?

40:07nopara73: Mixing your money like that, that's not cool. It would be much cooler if you could send money in the CoinJoins. That's actually one of the features that I am 100% sure that we will be able to deliver. Maybe there will be some change, less, but some. Maybe there will be a minimum amount to register, but it will be much smaller. But there might be, well, anyway. So we would like to fix the user experience of gaining your privacy with Wasabi, and that's our focus now.

40:48nopara73: Also, like, it's not like we aren't paying attention to the pay-to-endpoint stuff. I mean, we are. Kukks from BTCPay Server came and put down a proof of concept implementation that I cleaned up, and then Lucas is actually fixing it up even further, so that's probably going to get into Wasabi too at some point in the next month or so. So yeah, PayJoin is definitely a really cool concept, because you're not only providing some privacy for those who are doing the PayJoin, but also for some other people who have the same transaction patterns as you.

41:34You know, it's really admirable that you have been working for five years or possibly more just on this idea of making Bitcoin more private. And I recall a conversation that I had with you, I think it was in Riga, where I asked you about something related to Liquid and you told me, "Yeah, but that's not really Bitcoin," even though Liquid has confidential transactions. But do you still think that, to some extent, moving your coins into Liquid and doing confidential transactions and returning, and possibly doing some CoinJoins, is a more efficient way of mixing?

42:15nopara73: No, not really. I mean, confidential transactions simply means the amounts are not known by other people. The amounts will still be known where you are rolling on to Liquid or rolling off of Liquid. But again, you would need some mixing on Liquid in order to be able to gain recipient and sender privacy, so to break the link. Would it be more efficient if that mixing would be there with confidential transactions? I would say yes, that would be more efficient. Now we can actually go back to what I was talking about, that Bitcoin solved the decentralization problem and eCash is solving the privacy problem.

43:19nopara73: Right, but if you roll on to Liquid, it's still decentralized, but it is not as decentralized as you would like it to be, because you would like it to be as decentralized as Bitcoin is. So that's why I can't say I'm not interested in building stuff for Liquid. It's just that's why I don't prioritize that, because Liquid is for a small set of users of Bitcoin.

43:49So do you think that ultimately something related to privacy of Bitcoin is going to happen on a sidechain? And I did see some initiatives with altcoins trying to do Mimblewimble sidechains. Is that a good idea at all, or should you fix the base layer?

44:13nopara73: Well, I mean, for sidechains, whoever came up with sidechain ideas, like, you know, the pure sidechain stuff, where the sidechain is just as trustless and decentralized as the main chain, or maybe not as decentralized, but just as trustless, that kind of sidechains, the Bitcoin protocol improvements don't seem to be happening. People don't seem to think those are good compromises to build that kind of sidechains, and that's my guess why no one is building a Mimblewimble sidechain for Bitcoin. Because again, you would have to do some federated peg or something like that, like what Blockstream is doing, which is good but not ideal.

45:16Okay, so that's a vague description to say it's good but not ideal, but I'll take it. So I have a few closing questions about what Wasabi is doing, because you have added support for hardware wallets and I think that's very nice. I think it's a lot better to connect your Ledger to Wasabi than to connect your Ledger to Ledger Live, which is like their panopticon. They can see every transaction, use their full nodes. It's not really the best design. But if you use it with Wasabi, you have network level privacy. You also get to do CoinJoins. Plus, you know, you're much more in charge and you can run your own full node.

46:04nopara73: Yes, definitely. If you use a hardware wallet with Wasabi, then you gain network-level privacy. And you are of course not exposing your xpubs to anyone. You also have coin control. The pain point here, why I was against implementing hardware wallets, but I had a brain fart and I implemented it anyway, is that CoinJoins are not possible with hardware wallets. It's not an inherently impossible thing. It is definitely possible, but I don't want to make hardware wallets implement stuff until our CoinJoin implementation is actually final.

46:51nopara73: Because that's when we know what exactly to implement into hardware wallets, right? We are doing new research into CoinJoins and I believe that will be the end-all of CoinJoins. So you will not be able to come up with a better protocol than that, except if you would want to decentralize it, which is, good luck for you. I hope you succeed. But the point is that from a privacy point of view, you won't have a better CoinJoin implementation than what we are trying to research now.

47:30nopara73: And after that is implemented, then we will finally be able to go to the hardware wallet guys and push them to implement what we need for their hardware wallets to be able to do CoinJoins.

47:49Yeah, that's ambitious, to allow anyone to do CoinJoins from the hardware wallet. But let me ask you something else, and I get back to PayJoin or pay-to-endpoint, whatever. Actually, that's the whole point, because Samson Mow has tweeted that the concept of CoinJoins has a taint, and chain analysis companies and governments think of it as something bad, and that's why it's better to call PayJoin pay-to-endpoint. Do you have any opinion on that?

48:28nopara73: Yes, yes, yes. So, pay-to-endpoint versus PayJoin. So, PayJoin is technically a CoinJoin. Pay-to-endpoint technically doesn't mean much but to have a stable connection between the sender and the receiver, and they can negotiate what kind of transactions they want to create. Why pay-to-endpoint got into this PayJoin stuff is because, well, for some, someone, he thinks pay-to-endpoint is a better name, and he's the marketing guy and not me, so he's probably right. But again, it's technically incorrect, so I would not call a PayJoin pay-to-endpoint. Like, think about this like this: every PayJoin is a pay-to-endpoint transaction, but not every pay-to-endpoint transaction is a PayJoin.

49:33That's definitely something to reflect on. So possibly we need to find a better name, as the concepts are technically different. I mean, one includes the other, but the other doesn't necessarily include the other one. So, yeah, I guess we need a better name. And my last question to you is much more general, is much more about what we do in this space. And it concerns the fact that we often say "Don't trust, verify." But unless we are technically capable to verify, or have the capacity or time to verify every line of code before running a software, then who can we trust?

50:23nopara73: You see, think about this "Don't trust, verify" as a meme. Not sure if you've seen Bitstein's presentation from BitBlockBoom 2019, and there he explained that there is a difference between rhetoric and argumentation. Argumentation is the way of figuring out the truth, and rhetoric is something that you tell people who don't want to figure out the truth. So that's what you put on your T-shirts, or that's what you tweet about, like "Don't trust, verify," "Number go up," "Million dollar Bitcoin, baby," this kind of things, which are memes, which sound good. But again, this "Don't trust, verify," if you want to go really deep into this meme, then that's a really huge rabbit hole there.

51:33nopara73: Like, take Bitcoin Core, which is the most "don't trust, verify" thing in the world. But you have to look at the source code. Do these developers look at the code of the underlying library? Well, probably, yeah, they do. But do they actually look at the assembly code to verify that everything is correct there? And anyway, it has to be run on Windows, Mac and Linux, and you can't verify that the platforms that the wallet is running on are actually really doing what you think it's doing.

52:15nopara73: So where I would say the sweet spot is, is that if the product is open source, then that's a pretty good sign that that's something that the developers want you to actually know what's happening in their wallet as you are using that. Now you can go, of course, deeper with reproducible builds. I don't know. Like, you know, it's a meme that could be a good title of a research: "What does it really mean to don't trust, verify?" Because it means a lot of things. And someone could research all the different possible things that it means.

53:15Right, so referring to Bitstein, and that's Michael Goldstein's presentation from BitBlockBoom. I think he referenced Schopenhauer's work "The Art of Controversy," where he tells the difference between dialectics and, what was the other one? So, dialectics is debating, and rhetoric, which is just memes, just a few short phrases that you tell somebody when you want to quickly escape an argument.

53:48nopara73: Yes, you know, he made me feel like a lamb between a bunch of wolves on Twitter. I mean, I actually really had no idea that he said so many things that maybe for you it seems obvious, but I was like, "Oh boy, what's happening here?" There is a whole other dimension of thinking that I did not even know about.

54:14Yeah, I mean, Twitter as a medium is limited, so you can only write 280 or something characters in one tweet, and you won't find anyone to explain all of their thoughts in tweets. So there has to be some sort of limitation, or they have to self-censor to some extent when they express their thoughts. So I can understand that tweeting and posting online memes and stuff is rhetoric, because you say something to the public and possibly they're going to find their own interpretation of what you said.

54:50But if you really want people to understand what you're doing, then you need to write long blog posts, you need to write articles and books and stuff that actually explains and advances science, you know, because otherwise we just get stuck in this endless loop of people just making fun of stuff. And I don't think that's very...

55:12nopara73: I don't think it's productive, but it saves you time sometimes, when you don't have to explain everything. You just go Satoshi and say, how does it go? "I don't have to explain it to you, sorry, that's the end of it. But if you don't believe me and don't trust me, I don't have enough time." Anyway, it's like that. Sometimes you just get tired, and you either write something short that people can read and get some idea from it, or you spend your life explaining yourself to other people without doing anything productive for yourself.

55:56Yeah, that's well said. So, thank you very much, Nopara. I think your input is invaluable in this space. You have put a lot of work into this privacy project, and I hope it comes to fruition in the way that you want and expect, because I can't think of anything in this world that is worth five years of hard work, and most of the times you didn't even get paid for it. It was just you and your time, just working on this Bitcoin project.

56:33nopara73: Yeah, thank you, Vlad. It was fun, and I definitely got everything out of Wasabi what I was hoping for. I was just hoping for to build something that has people's privacy, and I think that goal has been reached a long time ago. So yeah, new things are on the horizon. Thank you, Vlad. Thank you for having me.

56:33================================================================================ Production notes: Remote one-on-one interview in English with a non-native-speaking guest; it opens with a short music intro and contains no sponsor reads. Correction: anthropic/claude-opus-5.5 via NanoGPT in 3 windows with a whole-episode speaker/glossary plan, the show notes, the Qwen3-ASR full pass (76 chunks) and 34 Scribe v3 re-checks of doubtful spans; [unclear] resolve pass: 3 of 3 flagged paragraphs re-checked. Automatic checks: word count vs raw, timestamps, seam duplication. Fixes: Removed music notes, lone "you", "Thank you." insertions, doubled words, "S&M" and "webinar" hallucinations; restored dropped speech (CoinJoin explanation start, "onion domain", "So the generalization"); fixed nopara73, CoinJoins, Adam Back, Matthew Haywood, Dan Gershony, Bustabit/BIP, JoinMarket, Samourai Cahoots/Stowaway, Bitcoin URIs, QR codes, tumbler, Chaumian eCash, 100%; blog title marked unclear; Guest A relabelled nopara73; Speaker label Guest A → nopara73; fixed boundary shifts (Vlad's "You know, if you" moved to guest, "could work" restored, "So there is always this debate" to Vlad, "Blockstream Green" line to guest, JoinMarket "bad on-" to guest, "Sure, because the tech is not there" and "Yes." to guest). Removed "Thank you." hallucination and "I've been a guest before" mishearing; restored dropped "three other people instead of five" and "no, don't use Samourai". Fixed Tadge Dryja, Leo Wandersleb, Mycelium, WalletScrutiny.com, Green Wallet/Blockstream Green, Tor, multisig, JoinMarket, xpub, Samourai, István Seres, denial-of-service, DoS, mixing technology, altcoins, eCash; Fixed names/jargon (Wasabi, CoinJoins, Kukks, PayJoin, Mimblewimble, Blockstream, xpubs, Ledger Live, Samson Mow, Bitstein, BitBlockBoom, reproducible builds, "brain fart", Vlad); removed hallucinated "Thank you.", "Episode:", doubled-word loop; restored dropped words from second ASR ("mixing to yourself", "and that's why it's better to call PayJoin pay-to-endpoint", "advances science... endless loop"); speaker repairs at 00:43:49, 00:44:13, 00:47:49, 00:48:28, 00:55:12, 00:55:56.

← Back to the episode · All transcripts · Ask the Archive

0:000:00