Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Nodesignal - Deine Bitcoin-Frequenz

Nodesignal - Deine Bitcoin-Frequenz artwork

Nodesignal-Talk - E256 - Chatting Wasabi & Bitcoin Privacy

Oct 24, 20251 hr 38 minAudio
ShareXLinkedInFacebookWhatsAppEmail

In der heutigen Folge spricht Jan-Paul mit Clement, einem Contributor beim Wasabi-Projekt. Wir haben uns für ein entspanntes Gespräch bei Sonnenschein auf einer Terrasse am Meer getroffen und über einen bunten Strauß von Themen gesprochen: die Transition von Wasabi von einem profit-orientierten Unternehmen zu einem Open Source-Projekt, das Coinjoin-Protokoll WabiSabi, warum Privatsphäre in Bitcoin so schwierig ist, wie Wasabi Nostr für Software-Updates verwendet, welche Bedeutung KI in Bitcoin haben könnte, Silent Payments in Wasabi, uvm… Hinweis: Das Gespräch findet anders als sonst gewohnt auf Englisch statt. Ein Transkript liegt der Folge wie immer bei. Von und mit: - Jan-Paul - Clement - Actionslave Produziert und geschnitten: Thorsten Hier könnt ihr uns eine Spende über Lightning da lassen: ⚡️nodesignal@getalby.com Zusätzlich haben wir auch einen Silent Payment Link: sp1qq0a2rles9y32ffmj0eawvjglgqsgj7hq99ers580l98k42a7rh9szq3sa50fh2e5lwf22fxcjy0qw88u72vlj328qr39da245sq4nrskuqvvv5l4 Neben dem Podcast findet ihr uns auch auf YouTube Für Feedback und weitergehenden Diskussionen kommt gerne in die Telegramgruppe von Nodesignal und bewertet uns bei Spotify und Apple Podcasts, das hilft uns sehr. Folgt uns auch gerne bei Nostr:npub1n0devk3h2l3rx6vmt24a3lz4hsxp7j8rn3x44jkx6daj7j8jzc0q2u02cy und Twitter. Blockzeit: 918456 WasabiWallet Wie funktionieren Coinjoin mit Wasabi-Wallet WabiSabi Step-by-Step LiquiSabi (Öffentliche Coinjoin-Koordinatoren) Silent Payments (gute Erklärung von Bitbox) Timestamps: (00:00:00) Intro (00:00:22) Einführung in Wasabi Wallet und Bitcoin Privacy (00:02:35) Die Entwicklung von ZeroLink zu WabiSabi (00:05:43) CoinJoin und seine Bedeutung für Bitcoin Privacy (00:16:43) Die Transition zu einem Open Source Projekt (00:31:25) Nostr-Protokoll und seine Rolle in Wasabi (00:35:03) Interaktion mit dem Wasabi-Dämon (00:39:05) API und Benutzeroberflächen (00:43:26) Integration von AI und Bitcoin (00:46:56) Bitcoin und AI: Eine Symbiose (00:53:06) Privatsphäre und Coinjoin in Bitcoin (00:59:05) Multiparty-Transaktionen und WabiSabi (01:06:38) Bitcoin und Adressgrenzen (01:09:45) Privatsphäre und Wasabi Wallet (01:15:47) WabiSabi und Transaktionskosten (01:17:24) Musteranalyse und Privatsphäre (01:19:14) Coinjoin und Wallet-Nutzung (01:23:10) Silent Payments und Wallet-Integration (01:27:40) Technische Herausforderungen bei Silent Payments (01:36:26) Verabschiedung und Outro

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Nodesignal, deine Bitcoin-Frequenz. Herzlich willkommen bei Nodesignal, deine Bitcoin-Frequenz. Heute mit mir, dem Jan-Paul. Und ich habe heute einen Gast, einen geschätzten Kollegen von mir. Er wird sich gleich vorstellen, Clement. Und wir werden über Wasabi sprechen. Das Gespräch wird auf Englisch stattfinden, also stellt eure Lauscher auf und hört uns gut zu. Clement!

It's so good to see you. I'm really glad to be here as well. Hello, Jan. Hey, hey, Clément, Clément. So, Clément, maybe you can introduce a little bit yourself. So, who are you and what's your relation to the Wasabi project? Okay. Hello, I'm Clément. I'm a software developer and I really like working on Bitcoin and specifically Beacon Privacy. I have the chance to be able to contribute for the last three years on Wasabi Wallet project, which is a Bitcoin wallet specialized in privacy. Really good Bitcoin wallet. At least we try to. We try to build it great. Yes. It has a lot of features now. It has been a first commercial project that I was not running. But then I started maintaining the project after the company that was building it. ZK Snacks closed its door. I was maintaining with Luca Santivero, which is the lead maintainer of the project now.

And we try to work toward making great privacy tools for Bitcoin. And what do you do? How do you contribute to that project? Wasabi was software built for a business, at least in that insight. So it had a lot of processes, a lot of components to solve niche concerns of users and some stuff that was non-standard. all the codes for the project in general.

To be fully compatible with open source, with being fully open source and on GitHub and standard wallet projects like Sparrow or Blue Wallet. To be able to work without a strong backing company that was making a lot of money, but rather to have very simple processes, simple code-based components and be able to build fast and also be replicated very easily. It's becoming easier and easier to fork Wasabi. And this is really something we want to achieve. Okay, okay. Let's talk about this transition that you did. So maybe we can dive a little deeper into what was the company like three years ago when CK Snacks was actually running Wasabi. Oh no, wait, maybe. Let's talk.

Briefly, what is Wasabi? We haven't introduced Wasabi yet. I'm sorry. No, no, no. I'm asking the questions, right? So what is Wasabi? Wasabi is a very old Bitcoin wallet, one of the first to focus on privacy and one of the first to introduce CoinJoin technology. So technology to earn privacy on your coins and break heuristics between inputs and outputs, break links in order to protect your privacy. First using the Zerolink protocol, which is pretty standard CoinJoin protocol in Wasabi One. It was a really beloved software at this time, a bit like Sparrow is today for the Bitcoin community. And people really like to use and to interact with it.

Really great, you know. At its time, it was a really great project. And it had a lot of volume really quick. And so there was money starting to flow in to maybe try to structure itself and build a really great privacy tool for Bitcoin. And with that mindset, the founder at the time, the guy working on the project, which was not my case, I joined later. But decided to invest into helping a research project that was led by a really strong researcher, cryptographer, like nothing much. And other members that were in-house of ZK-Snacks, the company that was starting to build itself at this time. And built the Wabi-Sabi engine, which is a new, an alternative, let's say, better alternative at ZeroLink.

It's an alternative. So did I get it right? So you started the Wasabi project with the Zero Link protocol, which helped to enhance privacy. And now you're... So, at that point of time that we're currently talking about, now you switched from ZeroLink to Wabi Sabi. Yes. All right. Okay, so maybe you can tell us briefly, so what is the ZeroLink protocol, just very briefly, and then why you decided to go to Wabi Sabi and what it does. There are a lot of reasons, but the main one in the case, what was wanted to be achieved in building Wabi Sabi.

was mainly to use non-standard output amounts. So in the context of a CoinJoin, instead of all coins in the output needing to be the exact same amount, WebCity was built in order to have a protocol that will work with arbitrary denominations as outputs and so be much more versatile in how a CoinJoin is being used. And this is why Webisabi was made. It's made thanks to strong cryptography stuff. You can explain. You can explain. I'm really interested in that. I don't understand in a way a real cryptographer like Yuval or Lucas or even Nopara, which built the Wasabi, which is the main founder, the leader of the Wasabi project at the beginning. And yeah, I joined right when Webisabi launched.

Okay, so it was the final years of the project as a company. So I've seen the project being developed when... When I was in the more corporate phase, it was really great for this project and for Bitcoin in general, because of Bitcoin privacy, because there were a lot of money flowing into building a really great privacy solution for Bitcoin, a really great software, and trying to pour money into that goal. But this comes at a cost, which is that building corporate privacy by a corporate is really difficult. It is really difficult for compliance reasons.

And you enter a rabbit hole that is really, really hard and that does not work. Okay, okay. For me, it still is not clear. Can you maybe explain to me what is the Zero Link Protocol? Maybe we can start there. Why do you do it? The only way on Bitcoin you will be able to earn privacy is to be able to build a transaction between several peers, several people. But you have to do it in a secure way that is non-custodial. You will not be at risk of losing your phones.

building a transaction with other people. Yes, that's very important, right? Okay. There are other solutions, right? Where you, for a brief period of time, trust a third party and then get back and have a similar result to a CoinJoin. But in your case, you want to build a protocol that allows you to keep custody while creating the transaction and also while receiving the transaction. Yes, that is the CoinJoin protocol. Yes. That is how Conjoin works. And you need a protocol for that. In that case, ZeroLink protocol was the first used in Wasabi, Wasabi 1. It has many weaknesses. The main one, I explained earlier, is the amount decomposition. You have to always, every participant of the transaction...

I have to create similarly value outputs. Wait, explaining those topics really early about Wasabi is not comfortable for me because I don't know that well Wasabi 1. I focused a lot on Wasabi 2, but Zerolink has many weaknesses. But you have to see a CoinJoin, a transaction that is built between several people. Like, this is fine? This is super fine. Okay. Let's chill. Let's relax. You are right. Yeah, let's just go back. All right. Okay. All right. So, okay, I'm sorry. I didn't know that you were not that, you know, sure to talk about the Zerolink protocol. It's just for me, you know, I've heard the term Zerolink protocol. I have a basic understanding of...

how a CoinJoin works, or what it is, what it does, or what it should achieve, right? So there is an idea that is called CoinJoin, which is the multi-party transaction. Now the question is, how do we actually implement this? Like, how do we do this? How do we make it work so that we keep our coins, we keep control, and we achieve privacy? Okay. So basically, at its sense, a CoinJoin is a kind of short-lived e-cash system. You will mint... An e-cash through a central party, the coordinator, you mint an e-cash token, but this token is only valid for the current transaction.

So you will commit your fund like a stake in Ethereum. You will commit your fund toward minting that e-cash. That e-cash is custodial because it's owned by the coordinator. However, you know that you'll be able to redeem it because you redeem it in the very same transaction. Yeah, because you provide the inputs and also provide the output addresses. And when you provide the input, you receive credentials that allow you... to register your output of similar value. So that way you know that you will always be able to control the destination of what you commit. So I commit one Bitcoin, I want Yann to receive 0.5 and I want 0.5 to go for HRF or whatever. I know I will be cryptographically able to do this. It's only worth because it's within a single transaction. It's an atomic operation and so you always know you will receive.

Okay, you create in this process a kind of e-cache token, you call it. We know what e-cache is, so we can build tokens. What I'm not seeing right now is how does it work? Or is it true? So that's what's in my head right now is in this token, there are somehow information or no, I'm not sure what is in this. Like, how do I make sure? How do I keep the control? And why do I need this token then? How does it work?

Das ist eine gute Frage. It is a mathematical proof. It's a credential that only you can compute. That is unique to you. It's like some kind of private key that is bounded to a value and that belongs only to you. Nobody can forge it or fake it. So this is how a transaction works. You commit your input. Theoretically, if someone had that token.

Yes, but if someone randomly guesses your seed trades on Bitcoin, you will use your phones. You see, this is the same kind of security. It is cryptographically secure. Even if it seems forgeable, it's not because it's so random. Yeah, I get that. No, no, the question was actually like, if someone steals my token, right? Ah, yes, you lose your phone. Okay, I lose my phone. Okay, so it's very important that we have this token. Yes. Afterward, it's a complex cryptography process. I'm not a cryptographer. Okay, it's fine. As far as we understand. Okay, yes. But you can commit the funds you want and send it to the destination you want. And thanks to a lot of crypto magic. Crypto magic is good. Yes, that has been researched a lot and worked a lot.

You send the phone where you want, but most importantly, nobody can know them. And also, this is a good advantage of CoinJoin, even though the central coordinator, so third party, provides you the credentials and so receives your input, is not able to know the value of what you are registering and trying to redeem. So nobody knows exactly how many coins you commit and will receive. In general, to the Coinjan transaction. Okay. So you are able to claim your outputs. Okay. I commit one Bitcoin. I claim my output. But nobody will be able to know that those two outputs are linked and that are yours. This only works because not even the, because the value are hidden.

from the coordinator itself. And this was also really important in building Coinjohn protocols like Wabi Sabi, the one powering Wasabi 2. Okay, so you joined to build or to help build Wabi Sabi? No, no, as I mentioned, I joined later. Oh, yeah, right. Yeah, okay. Everything was built and the project was launching Wasabi 2, which is already a huge user base that was able to, that was loving using Wasabi 1, but then Wasabi 2 was developed. And this solution incorporated a better CoinJoin engine, WabiSabi, which was the new, the one that has been researched on. So better CoinJoin engine.

People want to switch to Wasabi 2. However, the user experience of this wallet was heavily different. Why? Because Wasabi 2 is built on the fact that everything should be automatic on Bitcoin and behind the scene. You arrive, you want to coin join your fund, you click on a button to start the process and all the complexity I was mentioning is happening behind the scenes and just working. On Wasabi 1, you had much, much, much more control. Okay, and really be able to select which coin you wanted to participate. It was a bit similar to why Sparrow is loved, as I mentioned, is because it offers a really good granular control. And so Wasabi2 forced people to go from a solution like that to someone much more abstract and even so automatic, handled by black boxes, you know. And this is a huge issue because you...

Ich muss wissen, was passiert. Es ist Bitcoin, you know. Du musst verstehen und machen die finalen Entscheidung, was passiert. Okay, so es war nicht accepted by die Gemeinschaft? Exactly. Der Projekt hat viele Community Backlash bekommen. Also, moving toward a more corporate business received Backlash. Why? Because when you do business, you need to do Compliance. Ja, und du musst auf eine Firma registrieren. Du musst auf eine Firma registrieren. Es ist wirklich schwer. Leute, die denken, es ist einfach, sind verstanden. Ich war nicht an alle involviert, aber ich habe gesehen, es war wirklich schwer.

And of course, you have to make choices, like chain analysis choices, to check the inputs that are coming into the pool, the liquidity pool, to be sure that they are not linked to commonly known attacks. Wasabi received a colossal amount of backlash due to this. While the product was really being improved, you know, the general reaction about it was... Node so enthusiastic. Maybe for good reasons. Even though Web32 was a great product. Does privacy on Bitcoin need corporate structure like this? It does not work. You cannot. Okay. Is it because if you build it as a company, then you are immediately under regulatory scrutiny, so to say? Because, well, you're building a tool.

to enhance Bitcoin privacy. So the regulator will have a very close eye on you. So this forces you basically to oblige. How do you say this? Okay, I know I'm being watched by the government or by whoever is watching you. So I need to conform. And that's why we... Or not we, but Wasabi then had to do, not Wasabi, like who had to... ZK Snacks. ZK Snacks, the company, exactly. So they use Chain Analysis to know who's participating in the coin joins that ZK Snacks is facilitating and building the tool for. Yes, yes, that is exactly it. And you understand why, like, is the worth of...

Es ist wirklich schwer, und es ist wirklich schwer für die Firma zu beenden, zu versuchen, zu verabschieden. Denn so lange als du ein Service steigst, du bist für dieses Service. Und es ist wirklich, wirklich schwer, weil es auf Bitcoin-Bitcoin ist wirklich schwer. Powerful service, you know, in a macro scale. Imagine what it can do, you know. It has implications that you don't even understand big money and things like that, you know, and you cannot pretend to understand. You will need a really huge team of high-level lawyers, like what we see for all the complaints around Tether, companies like Tether, for example. It's really, really hard, you know.

So it sucks for the company, but it also sucks for the users, right? Why? Because who uses powerful Bitcoin privacy services? It's the cypherpunk, you know? Okay, okay. I thought you were going into the direction of drug dealers. No, no, no, no, no, no, no, no. As I mentioned it... You cannot control the use cases on the macro scale of a technology of the kind, okay? What you said is the same as who can use AI, the drug dealers. Of course they can, but it's because this technology is so strong that of course they will want to make use of it. The same happens with Bitcoin privacy, okay? Because Bitcoin is so incredibly powerful that it goes well beyond what I personally understand and what you understand, you know?

Privacy. The implications of this are also crazy in how our world works today. So this is why it is really hard to build this kind of software. You cannot understand who will use your service for and for what. And if you handle the service. You are responsible for it, and you understand it's really, really risky for users. It also sucks to use a service for this that has high links to compliance. I mean, it's not the point, you know? So it's the worth of both worlds, really. Yeah, yeah. Okay, got it. All right. Yeah, but then, I mean, I think everybody knows that the story is that CK Snacks had to close down, right? Uh-huh.

The general ecosystem got so nasty because in the privacy field of Bitcoin, some lawyers, some developers are being investigated and even to prison and facing huge, huge legal risk. Sometimes you don't really understand why, you know, or at least it's not clear. What can you do? You freak out. Ja. Und du musst es. Es ist einfach die Realität der Welt du leben. Es ist nicht ein guter Business, ehrlich gesagt. Es ist eine Privacy-Business. Ja, und das ist warum wir keine Majorer Akteure wirklich pushen und bilden große Lösungen. Currently, wenn du ein Privacy-Projekt hast, musst du

Node focused on privacy, but on something else. And privacy has a side effect of this, you know? Like we see with stuff like Lightning, for example. Exactly the use case. Or Arc, okay? Arc, we can talk about later if you want. Happy to. Let's let it flow. Let's go where it takes us. Alright, so I think we understand the problem that CK Snacks had. And we've already reported on that, so our listeners know what happened to the other companies. But Wasabi still exists today, so how? Indeed, Wasabi still exists. Wasabi has always been separated into two entities. The CoinJoin company, the CoinJoin service.

ZDK Snacks. ZDK Snacks was earning a lot of money from the Conjoint Service and as a result funded the development of Wasabi. But at the end of the day, Wasabi is an open source project. Okay. It does not belong to ZDK Snacks in any way. And it's a project that is... MIT, fully open source. It can be replicated, can be cloned, no problem. On GitHub, we are happy to help always. So Wasabi continued as an open source project, but of course it came with huge challenge because while the underlying project is open source, it has been built for years.

By a company, so it has the process maybe of a company or at least components that are built in a corporate way, you know? Yeah. And so changing a project, transitioning from something that requires a lot of the developer to maintain towards something that will be really... easy to fork and to maintain, to improve, be more stable, be more secure, you know, to make it really a really good open source project. And this is the transition I really worked a lot on. Yeah, okay. So that's super interesting. Like, how do you transition from a corporate project to an open source project? And what...

Maybe, what were you trying to achieve? At the very first moment, if I understood it right, that's when you joined the company. You started contributing to the project of Wasabi at that moment when this transition had to take place. Let's say yes. I already contributed to the project in the past and that's why I was going to do it. But I was along with Lucas Antivero, which is the lead maintainer of Wasabi, Lantivero. He's a really cool guy. Extremely talented. You know, he just understands how Bitcoin Wallet works and how to integrate crypto stuff and to make it really...

secure and reliable. The answer of how you transition is you have to reduce complexity all the time, all the time. Reduce complexity, make the things basic. as basic as possible. And this is really, really important in software development. Instead of building everything custom everywhere, you need to centralize everything and to build a really great, powerful modular architecture. Okay? And when you are a corporate, you might be focused on some immediate business needs, you know, and try to push away without a strong design decision underlying and this kind of stuff that can happen. Or you might want to solve a problem.

Was ist das Problem? Weil du musst. Aber in fact, es ist kein Interessant Problem zu lösen und es ist ein komplexes Stück von Software zu lösen. Wir wollen das nicht so machen. Du musst alles reduzieren. Wir removed 1,000, 1,000 of code lines. Wir removed oder removed a lot of flow handled by the backend. So reduced a lot of data we send to the client so the client can rely on third party. We made it available with a prune node, so it was easy for people to run. In the past, in Wasabi, we had a custom local Bitcoin Core node installation. We removed all this to make this standard through the RPC. All kinds of work like that, methodic work to reduce complexity everywhere and be able to maintain the project much easier and by a handful of people making sporty contributions. Okay. So for us, what was really important?

was for clients to always have access to the Wasabi client. For users to always have access to their client. It means to never be, to never require to export their seed, their Bitcoin seed to another wallet, like Electrum or Blue Wallet or whatever. Why? Because by doing so, they will lose a lot of the privacy that Wasabi provides. Wasabi provides privacy on many, many levels, like with using block.

Blockfilter for synchronization and labeling, these kind of features. And we know that people will really be, the privacy of our users will be degraded if for some reason the Wasabi client stops being available. So for us, it was really important for the client to be really reliable. Okay. But reliable in terms of availability. Yes. I'm a user of Wasabi. I have this wallet installed. Let's say I have the wallet installed. What do you mean with availability? What needs to be available? You need to be able to send your phones, access to them, see them. Okay. You never, you cannot be blocked because we do not provide an information that you need. For example, let's say we provide, we as a backend server, we provide the exchange rate. Okay. Of Bitcoin.

If out of a sudden we stop providing you this information, then your client won't work very well. You will never be able to understand how much you are sending. It's not good. If we send you the block filters and we stop sending you the block filters, then it will be bricked and you will not be able to access your phones. This is really what we want to avoid. Also, it might mean that you need a security update because we found a critical vulnerability in Wasabi. Okay. It can happen. It can happen. Who knows? But who knows? But you still need to be able to update Wasabi. So you still need to be able to update. Otherwise, we found a vulnerability. You are not able to update because for one or other reason, your client couldn't connect to our update server.

Und dann können wir die Update nicht verabschieden, und deswegen können wir die Update nicht verabschieden. Und die Hackern können das nicht verabschieden. Ja, okay, so Sie haben die RISK der Exploitation, weil an einem Moment die Vulnerabilität wird verabschiedet. Oder mit dem Update, wahrscheinlich, oder nach dem Update. Anyway. There is risk of exploitation if you are not updating your current Wasabi clients to the most recent person. All software are like this, right? You need to make the security update. So it's important for us to, you know, keep those kind of flow always available. And for example, in the case of Wasabi, what we've done recently was to stop serving the updates from a server. Okay, a proper server, which was wasabiwallet.io.

So if for some reason nobody was able to push on this DNS because the DNS was seized or whatever, whatever can happen, you know, then you will still be able to receive those updates because now we use Noster as a way to pass the message of the update being available to the client. The way it works is that the client listens to a Noster. PubKey for events. And whenever there is an update available, someone publishes an event using the private key. Is there a specific event that you are using? You can use any kind of event because you only check the same address. Okay.

Okay, so you're listening to the NPAP. And while listening to the NPAP, at some point you will notice, you will see a message, an event in Noster that tells you, okay, there is an update available. So this is like the information flow, right? So this is how you are informed about an available update. How do I find the update? If I'm not able, because what was the name of the WasabiWallet.io, if that's not available or I cannot reach it. How do you make sure that I'm still able to download the newest version? Yeah, because we include whatever server holds the update, you know. So instead of whatever.io, we can say it's GitHub, et cetera, et cetera. Now we use another private key. So we use cryptography to create this event. So we can manage the key in the same way you manage a Bitcoin key, you know. So we don't have to use a service, DNS, that can be seized. It's not only seized because...

This is the main reason you can lose the DNS, but there are many reasons why you can lose the DNS. And in that event, we do not want to incur those kinds of risks for our users. See, this is an example, but do you see the general direction of Wasabi? Of what we have been building with Wasabi now, because now we reach a really good state at doing so. To be really reliable and to work without any backend server intervention. and to be a simple and working piece of software. Okay. But it's still an ongoing task, of course. Okay. So, okay. Did I get it right that you are able then, instead of uploading or putting it on a server, the next version of the Wasabi client, but you can just distribute it to different servers. You can, at any point, you can use an ABS server or a VPS server, whatever you have available, and you can provide that newest update.

The user is informed through the Noster protocol because he sees the event and he will also find the link to the servers where he can download the newest version. Yes. All right. That's cool. Yes. That's pretty cool. That's a pretty cool use of Noster. I think we're one of the first software to do so. And it really showcases how you can use simple protocol like this, like Noster, to build really strong... In this case, in crypto in general, it's very little understood how a supply chain attack can be an issue. And this is a huge risk of crypto, in my opinion. The supply chain is risky, it's not.

Sometimes not well built by the industry, software industry. And so on some platform like GitHub, you are at risk of having a supply chain incident. In fact, Wasabi had one as a matter of fact. Okay. And which means that malware was published. On GitHub. On GitHub. Of course, it didn't have the signing key of Wasabi, but still people will love downloading it, you know. Software was published.

And then, of course, you need a way to protect against that. It's a major issue in the software industry. We've seen the problem a couple of weeks ago, I think, or one month ago, maybe, where a major Node.js, NPM. Oh, yeah, the NPM. The exploitation, right? Yes. Node a lot of loss in crypto, but you see the kind of risks are really strong. With Noster, we very much improved this while making this easier for our clients and more reliable. It's crazy. Noster is incredible. What you can build with that is crazy.

Do you have any other ideas what you want to build on Noster? No, no. No, no. For Wasabi, in the context of Wasabi and in symbiosis with Bitcoin in general, what will work really well for Noster is a contact list. In the same way the Samurai Wallet did before. I don't remember the name of their protocol. It was different. But a contact list will be really useful on Bitcoin. You are able to send Bitcoin to everyone you know, to services you know. So it will really improve the UX. Yeah. Okay. We had another topic, right? What one is...

Okay, so we talked about how to download the newest version. That's one of the things that you did in this transition to become an open source company. Is there anything else that we should talk about? Sorry, can you? On the topic of the transition. From the corporate project to the open source project, we talked now about how you implemented a way to make the news updates more available, reducing the risk of seizing WasabiWallet.io and making the updates no longer available for users. And what else did you build?

We are building a lot of improvement into this kind of direction. But it was just an example to... What's a daemon?

A daemon, it's a job that runs, a process that runs on your computer that has no graphical interface. It's a service, if you prefer. Okay. And Wasabi is... an UI powered by this daemon that runs on your computer. But you can access this from alternative UIs as well or alternative ways. Like you can build a script to interact with your wallet. If you want, you can build another wallet that will be built on top of the daemon. So it's the core of Wasabi that has an available API which is called the RPC.

Software, yes. And you are able to communicate through it. Access to its internal functionalities. You know, this is really useful to pilot your Wasabi. For example, I have a website where I run a website called Liquisabi for Wasabi statistics. Anyways, and on this website, I have a really simple component that showcases how the daemon works. It's a donate button that is private. Okay?

Because you click on donate and it makes a request to Wasabi daemon. Okay. Receives a new Bitcoin address and displays it. And that's it. Okay. So it's really simple that you access your daemon in the same way you would access a Bitcoin node. If you want to know, you interact with this like that. And so you can build really cool application on top of it. I think this is the future of Bitcoin wallet. Wait, so did I get this right? So you have a donation button on your website and when you click on donate, it interacts with the Wasabi D, with the Wasabi Demon. Yes, yes. All right. And this Wasabi Demon will then give you a new address that belongs to your wallet. Yes. That's what it does. Okay, so you're able to receive and each time, make sure that each time you generate a new address, right? That's what the Wasabi Demon makes sure.

Other software make it much better, like BC Pay Server. You know, this is not crazy stuff, but just to showcase that you can pilot your Wasabd, as you mentioned, and therefore build more complex applications on top of it. You can build really cool stuff, and if you push very well, you can probably build alternative UI, you know? So a really different way of interacting with Wasabd, more built-in for you. your own UI for the project powered by the daemon. Yeah, I think this is the first time that I understood something about the daemon because is it, what's the name of the French lightning wallet? The Phoenix, right? So there is a mobile wallet, Phoenix wallet, very popular and they also have the Phoenix D and I never understood, okay, how do I get to run, get this Phoenix D running on my mobile, on my laptop? Okay, so there is no UI.

Okay, so I need to somehow install the daemon. It can run, but I need to... How do I access this? Like on the CLI? Yeah. On a command line interface? Yes. Ah, okay. It's a standard API, so you can access whatever you want to access an API for. You can, for example, plug it into your chat, into Cloud or ChatGPT if you want, you know, because it's just an API. Ah, okay, an API. So maybe we need to explain what's an API. I have a basic understanding. I'm sorry, it's an endpoint. Okay, so it's a root software can use to fetch, to make HTTP requests.

And make a post request, basically. Okay, wait. So since the Wasabi D, that's running on your computer. Yes. And what you can do is you can have any UI. It can be Wasabi, but can be anything else that knows this endpoint, this point where I can ask a question, basically, in very simple terms. So, I don't know, get new address, right? So I can ask this endpoint. I can send a message to this endpoint. Tell him, okay, I need a new address. And the return, the answer will be the address, right? And this is what an API is. And that's what is used. But this is internally, right? This is on my own laptop. So I'm not calling a website because you mentioned HTTPS. But you have your laptop and your service running. And yes, locally you can interact with it. Of course, it's like a Bitcoin node. Bitcoin node is exactly the same. Yeah, okay.

These are things that I'm still learning about and still trying to understand. So I'm super thankful. Me too. Let me tell you, me too. Fool is the one that thinks he understands Bitcoin. Except he really knows his stuff because Bitcoin is hard. It really, really is. There are a lot of rabbit holes and also... But all this using daemons, using API is becoming easier and easier. Why? Because we have automatic services, automatic agents like AI or whatever that interact and the alternative UI that...

Interact with this stuff really well. So maybe even if now it's hard for you as less technical maybe to understand how to use a daemon, in the future it will be much easier for you and for everyone to automatically build layers of abstractions like this and so implementation for the API, you know, because the AI helps you, the AI is really very good at doing this task. It's very good at interacting with a daemon over an API, right? We do not recommend to build your own UI with an AI agent to build your own UI to interact with a Wasabi daemon. That can be very dangerous. Okay, okay, yes. Yes, yes, yes. Wasabi is a work in progress, right?

These system solutions are really hard to build and long to build. And we are willing to be very reliable and useful, building alternative UI that works very well for you. In the context of what I mean, it is indeed not a good idea to use AI agent for that because you will lose a lot of your privacy, right? You should use a local agent. But it was really to explain you that while it sounds... Because I come here and mention the daemon, and that is very cool in Wasabi, and we push a lot to make it better. But you think, oh, but I don't understand how to use that. So I will never be able to make use of this, you know?

Yes, but in the future, it will be much easier for you to interact because of all the help you will receive. Maybe we can provide Wasabi demon documentation that you can then feed inside your agent, you know. Ah, okay, so he learns how to interact with the Wasabi demon. And then you have a way of, just by natural language, interacting with Wasabi. Yes, exactly this. Because you will put the documentation in natural language to the chat, to Claude or ChatGPT or whatever. Yeah. Okay. Boom. And then it will know exactly how to use it. And you ask him a question, like, please create a script to send my phone to Jan. And well, Claude will be able to give you the script. You put it inside, you execute it on your local machine.

You just click on run. Basically, it runs on your local machine and is able to interact with the daemon and your wallet. And you see, it's a complete alternative way of using wallets. Of course, it's a really long ongoing work, right? Because there are a lot of risks doing that. You have to handle everything well. If I make a prompt and the script is send all my money to a hacker and I don't proofread and understand what will be the consequences of the script I'm executing.

This is really bad, okay? It cannot happen. So the wallet can need to show you exactly the implication of the action you are performing and request you for confirmation and stuff like this. What is doing a Bitcoin wallet now? It's just a new way for you to... Interact with, to create your own UI, if you prefer. Your own way to interact with Wasabi Wallet. With this kind of system, Wasabi will be very good only if it's really small, easy to understand, interoperable, you know. That's why we are simplifying everything, making it as atomic as possible.

Would it also make sense to feed your personal agent, your private agent that you have, maybe also the source code? Download it from GitHub and tell him, hey, here's the source code and the documentation. Please learn about this. Of course. This is how it will work. In the future, this flow will always get better and better, become really good. And therefore, you will interact with this kind of documentation and documents. Without even noticing it. And maybe we can say the same about Bitcoin. Okay. Okay. Right now you have to use it really on a click in and you know that you are using Bitcoin when you are making a transaction in the future. Well, you might very well use Bitcoin under the hood and being completely abstracted from you. You don't even know you are using Bitcoin, but in fact, under the hood, this is how it works. You know, it's the same for AI agents.

I can't imagine a future where I am not using a wallet and at least trying to understand what I'm creating, what kind of transaction I'm creating where I can see, okay, there's this transaction and I sign it and send it. You will always have to see this. But let's say I buy something on Amazon. I tell my agent I want to buy something on Amazon. Okay? It's not crazy to see that in... Three years, let's say three years. You ask this question, only this prompt, please buy this chair on Amazon, okay? Directly, you receive it.

At your place. Directly your order is confirmed and paid and everything was done in just one prompt. The whole process. You know, it's a simple process. You buy. Okay. You pay by your payment method and it's come to you. Well, maybe this transaction will be sent in Bitcoin. However, it's a Bitcoin really, really hot wallet. that you have specifically set just for this, you know. But if under the wood it can use Bitcoin and you don't confirm it, and that's it. You can just have a confirmation. If you prefer, you can have confirmation for this transaction, blah, blah, blah, blah, blah. But at the end of the day, I think this is the future we are going towards. Really great interoperability of systems between themselves. Okay.

We went from Wasabi to AI. I am really sorry. No, no, I know, I know. This is very close to your heart, this topic. Indeed, I think crypto and AI are extremely fascinating and are playing very, very well together. Okay, how come? How come? Yeah. How come? Let's go there. Okay. You are an AI. You are an AI agent. Okay. I am an AI agent. Yes. You are Jan-Paul. Okay. There is no Claude. Here is Jan-Paul. I'm really sorry for any German word I might pronounce. No, that's fine. That's fine. Okay. So I am an agent. Yes. You are an agent. You want, you need.

To pay something. Because you know that the user, his intent is to pay, to buy something. So you need to use a currency. Yes. Yes. What is easier to use? Fiat or crypto? It's of course crypto. Es ist sehr, sehr einfach. An Automativen system ist wirklich gut an handling private keys und diese Art. Bitcoin ist extrem einfach. Das ist die Art. Bitcoin ist wirklich einfach. Das ist die Art.

are able to be sent really easily by automated system. We see that in a lot of, already a lot of really, really impressive services are built on top of Bitcoin automated stuff. Wait, are you saying, so it's closer to an AI, no, wait, okay, so it's closer to use crypto for an AI instead of a bank, right? Because if I want to do fiat transactions, I need to go through a bank. Yeah, I need to go through a bank or a third party and it's more complicated because they are actually in control of the money and I have to instruct them, hey, send this money to this IBAN or whatever it is, address. And it's easier because the I as an AI agent are able to control the keys and send money, right? That's way easier than instructing a bank to execute this service for me. Yes. Oh, okay. That's exactly very well put.

It's a really simple system. Imagine how a bank works. It's really complex. But the heart of crypto is that it's really simple. Of course, the implementation and blah, blah, blah is really, really complex, but it is really easy to be used by any kind of automated system. And the only real problem with crypto is the user interface, the way the user is able to interact with those systems as they exist today. Ah, okay. But in the future. You will be able to provide intent in a way that is much better understood by the machine, by using a chat client, for example, a local model or a huge model or whatever. You will be able to interact with automatic system much, much better. So without any UX burden, you know, that right now you can have by finding the right button and understanding what is a new TXO, you know. And also it's a lot of work to implement something that is user-friendly, right?

We see this in the good wallets like Sparrow are really good wallets, but the UI is far from the easy, happy to go wallet of Satoshi solution, right? There's a huge difference. Clearly in crypto in general, this is not only true for Bitcoin, but for all crypto, the UX is very clunky for payments. And for the user, interacting with crypto interface is really hard. Why? Because crypto is made for machine. And what is going? Machine, agent, are really good at interacting with the system and understanding what the user wants, you know? So it's really, of course, it will be. We will interact that way with probably all our stuff. But for crypto, it makes a lot of sense. Especially the payment case. In the payment case, but yes, especially in the payment case. Okay, okay. Interesting.

That's something we are starting to see, by the way, in Bitcoin. Albi's Bitcoin Lightning Wallet. Yes, huge fan. Okay, same. Nice. And they are working on AI as we speak. They built an MCP server, which is a way for clients to connect to each other. It's pretty cool. I think we will see more and more development into this area. Did you see... So, I saw, just recently in Berlin, I saw Albi, they were reporting on this, what is it, on this MCP server that they are building and their use case was the payment using Bitrefill, buying a gift card there and, yeah, receiving the gift card. Yes. This was really interesting. Pretty cool, huh? Yeah, super cool. And so, the redemption of, the way...

The way you use your Bitcoin by using this kind of systems, oh, it's a UX lift. It's a paradise, you know, in comparison to what we know today, it's always clunky. And even the very best wallet are a bit clunky to use because of the nature of crypto. I think we cannot reach a huge widespread usage because Interacting with crypto is too hard. It's too hard. But I think this is a problem that the world in general will solve. Or at least is. Will be a problem of the past. Yes. At some point. Three, five years. Always a problem, but at least they're very much improved. Yes. Yes. Okay. Okay. All right. All right.

Can we talk a bit about the state of privacy in Bitcoin? Of course. Okay, so what's your take? What's the state of privacy in Bitcoin? What a bold question. The problem of privacy is you don't want to be the one that builds the privacy system. If it's too good, it will be a problem for you. And you want to build cool stuff, you know? Right now, I think privacy on Bitcoin is quite low, actually. But Wasabi is still a very good solution for privacy.

It's in fact the main solution right now for Bitcoin privacy in terms of volume. So for the record... So the most used. There are other solutions, but they don't have the volume that Wasabi has. Yes, exactly. Let me explain this a bit more because this is important. When I mentioned that the company was closed, that case next. Wasabi didn't start supporting CoinJoin, because Wasabi is only a client. It is not running any service. You can plug in whatever service you want in Wasabi. By default, it was the service from ZK Snack. They closed, there was no default, but then the liquidity regrouped toward alternative services that were launched before. Yes. So this is called a coordinator, those kind of services.

And today, some of the coordinators have really huge liquidity, but really, really huge. I think like about 3,000 Bitcoin per month are using... Are in CoinJoints. Yes. Okay. New Bitcoins. New? Yes. Additional. Okay, so, and, you know, you can keep your Bitcoins in a CoinJoint for a longer time, as long as you want. So... The 3,000 is just the addition to the existing pool of coins in a coin joint. There is in and out, but 3,000, what you talk about is the liquidity pool and it depends when the people spend.

Basically, when they spend their private output, so they become non-private. So the liquidity pool. So it's always going in and out. But in total, about it's about. I'm not sure about the number. I actually track those numbers on my website, on LiquiSavie. But because it's public information, they publish all this. This also works through Noster. Another good news from Noster. Okay, nice. Yes, yes. So the coordinators published? Their... Service. Yeah, they advertise their service. The service. Okay. They advertise the service on Noster.

Und so, client can connect to them. Okay. And for me, that check the monitor, the liquidity and what happens. I just monitor every messages those servers send. Yeah. Okay. So I'm able to know when I monitor because sometimes might not go down anyway. But when I can monitor, I track all the publicly available liquidity on Wasabi. No, using the Wabisabi CoinJune engine. However. You can also have private coordinators, right? Because it's a protocol, if you have a use case where you want to join among only your friends, okay, you can very much do so. Or for a business reason or for whatever reason you want to make join between a certain group of people, you can create your coordinator, advertise it to your personal friends or whatever.

Are there people doing that? Yeah, I don't know. This is the cool thing about Wasabi. Nobody knows. Nobody knows. Or nobody knows for sure. I mean, this sounds really fascinating because I can easily get a group of 10, 15 friends together and say, hey, let's do our private Coinjoins. Yeah, of course. Of course, it makes sense. And not only on Coinjoin. Coinjoin is only a subset of what you can do with Wapisabi. Why? Webisabi ist ein Multi-Party Transaktion System. Okay? Okay. CoinJoin ist ein Typ von Multi-Party Transaktion System, wo jeder in und auskommt. Ja. Aber wir können einen anderen Typ, wo ich in und auskommt, ist ein Payment, zum Beispiel. Ja.

In fact, we have this already in Wasabi. In Wasabi, you can, there is no UI, but with a daemon. Why? Because the UI will be very clunky. Yeah, okay, okay. Anyway. But is it mainly because you are focusing on building the Wasabi engine and have less focus on the Wasabi wallet? No, we have much, much more focus on the Wasabi wallet. Okay. We only maintain the Wasabi engine, but we actively develop the Wasabi wallet. Okay, okay. And we maintain the... Webisabi-Engine. Why? Because there can be privacy risks or security reasons why it needs an update. So we keep updating. But Webisabi is a protocol.

It's a way of communicating with people, okay? Maybe there are completely different implementations of Webisabi. In fact, BTC Pay Server also has a Webisabi client on BTC Pay Server. It is not working now since transition to Pluginv2, but it exists. Existed. It existed, and also Trezor. On all the Trezor suite, there was an app that required a lot of research and it was really hard to do, but you are able to sign a coin join with your hardware wallet, Trezor. Again, not available right now for many reasons, but you are able to do that. Webisabi is a multi-party transaction protocol.

that can be used in a huge range of for a huge range of things. So yeah, maybe there are people having private community of WSB. Can you give me more examples of these multi-party transactions? So count join is one type. A payment could be a second type. Yes. And what else? Anark. Okay, okay, okay. It is a multi-party transaction. Okay, yeah. In fact, Anarch is very close to what Webisabi CoinJoin is. Okay, but it's hard to go into details because I don't know very well myself. But it's also really a fascinating use case of this. Lightning channel opening is also one. You have a communication protocol between payments, but at the end of the day, it's not a fundamental difference, you know. There are many types of multi-party transactions.

Okay, but currently you only support Coinjoins in Wasabi? So Wabi Sabi, yes, is expert on Coinjoins right now. At least it's implementation. Am I making a mistake here? Because you're always saying Wabi Sabi and Wasabi. Maybe I'm not clear of what is what. In my head, Wasabi is the wallet or the client, the UI to interact with Wabi Sabi. Yes, yes. Okay, okay. That's it, right? And Wasabi is... Wow. What is... It's a protocol. It's a protocol to build transaction with people that is... Okay, okay, okay. Everybody who follows this protocol can interact, but he doesn't have to use Wasabi. He can also use another UI. All right. Okay, okay. So, okay. So, all right, all right. So, it's a protocol that we can agree on or...

We can align on and say, okay, we're using the same protocol. And then we can do certain types of things. Like, for example, we can do a coin join or any other multiparty. But that needs to be provided by Wabi Sabi, right? Yes, Wabi Sabi is how it works for the people. It's like HTTP, if you prefer. It's how the communication occurs between the different parties and what information you have to provide, these kind of things. So is the Wabi Sabi engine then just a protocol? Is it just... Yeah, the engine is the implementation we have in the client. Poor choice of naming, but... Yeah. Wasabi is why you can build... Wasabi is why you can build transactions with other people. We use that for Coingeon. And on Wasabi, remember, you can have outputs that are of any value.

It does not matter the value of your output. And because of this, it has a lot of use cases. You can use that for a lot of use cases. And for example, you can use it to make a payment, for example. Let's say you buy something, they give you the address. Well, you can instruct to make a Wabi-Sabi coin joint, Wabi-Sabi transaction. But instead of receiving back your output. Send it to the address you provide. And so you make the payment inside the CoinJoin. You see, this is another application of how a transaction of the kind can be useful. Yes. Those are all transactions between several parties, multi-party transactions, specifically CoinJoin, and specifically for Wabi Savi, a CoinJoin to output that can be of different value. Okay.

So you can make payment. Maybe in the future, you also can open Lightning, a Lightning channel through a CoinJoin output or more complex scripts. It can have many use cases, but for now, Bitcoin is at... In the current state of Bitcoin development, we are only at the very, very beginning of usage of multi-party transactions. Why? Because it's very, very hard to do so. Because it's hard to coordinate, right? Exactly. People have to...

behave in a certain order and provide the right information at the right time, you know, for it to be both private and safe and worse. So you need a set of interactions that is set in stone, you know, and every developer knows that for an app, this is really hard because if only one person does not make one of those actions, okay, The round fails, the transaction fails, and you have to start this process again. And when you do so, you incur some risk. It's really complex how it works under the hood. There are a huge, huge rabbit hole.

Because you think it might be more or less simple, but no. And this is why it's really tough to build software on Bitcoin. Because when you want to build use cases like this, you have to think about a lot of stuff. Wasabi is far from perfect. As I mentioned, it's a work in progress. There are many, many things that can be improved in the way where Bitcoin is being used and in everything, you know? I'm still trying to understand. Can we maybe talk about an example of complexities or these rabbit holes that you mentioned? Just so that I understand. Currently, at first, I thought...

Okay, so we have a protocol. So there are rules to follow. I understand there are certain steps that need to be taken in a certain order. Everything is organized by this protocol, right? So everybody knows how to participate in this multi-party transaction. Yes. In my head, it was like, well, that can't be too hard. I mean, if there is a very clear specification, who needs to do what, at what point in time, what he needs to provide and so on, that shouldn't be that hard. Let me give you one of the main problems of Wasabi today. It's a way that can be used to degrade your privacy.

basically, and we need a way to go around it. It's that when a round fails, so when someone misbehaves and forgets to send something and disrupts the whole process, you have to start again, okay? But let's say you already registered the output you want to send your addresses in, okay? You already registered your output and then you have to start again because it failed. Ah, okay, yeah, yeah. Okay? Now you have to register your output again, okay? Because the whole process starts again. But then do you reuse the same address that the one that you just registered in the previous round? Or do you create a new fresh Bitcoin address? Right now we are reusing the same address.

Why? Because you need to, because of gap limit and how B32 and B39 work, you need to reuse the same address, otherwise it will create a huge UX burden. Like you will not be able to synchronize easily on all wallets because of the gap limits. Okay, because it just takes more time to run a new round with new addresses? No, it does not take more time. But currently our derivation path work in Bitcoin is that your seed generates a number that will be able to generate keys one by one following a certain order. You can generate if you want 100 and receive on the 100s, let's say, and keep all the first one blank. But in order to know...

Whether or not a wallet a key holds money, you have to test it. Yeah, you have to scan, basically. So if you are a client, when do you stop? Because maybe I have received a payment on the address 1 trillion, but I will not scan 1 trillion address. No. Do you understand? So we need a limit in how many we scan. By default in Bitcoin, this limit, a widespread usage, is 21. Usually wallets, at least a standard one, maybe it changed today, but standard one will use 21 as a min gap limit. I think it's the absolute minimum in Bitcoin. And this min gap limit is what? It's like the number of addresses that your client, your wallet will search for. Are there any funds on these addresses? And after 21, it stops? After 21, without seeing any coin.

When he found the coin, it resets and scans the next 21. Yes, you see? So he scans, scans, scans, nothing, nothing. Oh, on the 10th, there is something. So scan, scan, scan, scan. I get it. So usually clients reuse address 1, then 2, then 3, 4, 5. So there is no problem. But let's say a coin join round fails 100 times in a row. Okay? Well, then you have to register 100 different addresses. Output addresses, okay. Yes, all right. And you see, working with Bitcoin has always this kind of complexity involved somewhere. Okay, just so I get it. So the problem is, if a series of rounds fails, and each time we would generate a new address, it may be that the...

The address where actual funds are, the wallet will not find because it has a defined gap limit. It will search the first 21. If it's at 22, you're out of luck. Your wallet doesn't see it. Yes. I mean, you can always, you can, I think. You can control this gap limit. You can also say, hey, control, but this is again an UX burden, right? So, of course, you can, but there will be a lot of users that might suffer a lot from it. Yeah, but why don't you just say, okay, we know that we need to generate, there is a possibility that, you know, a bunch of rounds will fail. Why don't you, as Wasabi, then say, okay, our min gap limit is 1,000 or 2,000.

We can, but then what if I restore my seed in Ethereum? In a Sparrow wallet, for example. Electrum, I wanted to say. No worries. Or import my seed into Sparrow wallet and the gap limit is lower, then I don't see any funds and I panic. And you panic, and panicking is okay, because then you will change. If you panic, it's okay. But let's say it's a seed from 10 years ago, okay? And you recover and you see nothing. You will think, oh, fuck, I have nothing. Oh, it's empty. And so you might lose your Bitcoin. So in Wasabi, okay, it's a really simplified explanation. This topic is complex, okay? It's not clear description that I just made, but...

No, it's good. Because of problems like this, you really have to, privacy solutions on Bitcoin are really hard to business. Wasabi, for example, for this problem, we always put the same addresses, always. And this is an issue of the current implementation of Wasabi, probably the biggest one. Why? Because we didn't implement the solution for this. And so you can degrade your privacy. Yeah, okay, I get it. If the coordinator fails too many rounds in a row. Yeah. You face issues that you understand that it's hard to enter into developing and maintaining those projects. This is another huge challenge. I think the main challenge in Bitcoin FOSS ecosystem, fully free and open source ecosystem, is that entering projects is hard understanding the whole rabbit hole, as you mentioned, and the problems that can arise.

You have to be really committed, right, to do that. And this is also why, for us, it was extremely important to make the codebase as easy as possible and to make this transition toward being smaller and better organized, you see. So for the project to survive, because now it will be, it might... Be easier for us to find other people interesting into working and understanding quickly how the software works. You know, when you go and there is a piece of software and you see it's a mess and you don't understand shit, you're like, no, I'm not going to use that. You know, you can use, but to improve actively, you will not. And Bitcoin needs maintainers of a project like this. It's really important. Why? Because it pushes all the industry into the right direction. Right now, Wasabi might be the best.

we have for Bitcoin privacy, at least thanks to its liquidity. Okay. But... In the meantime, it's fine. It's okay. In the meantime, other and better privacy solutions are being developed. So you see to keep momentum on Bitcoin privacy and don't make it taboo where nobody works on it. This is a really huge risk for Bitcoin privacy. And a project like ARK for sure will help a lot. We will help a lot. We will see how it unfolds.

Yeah, that's still to be seen, but we are seeing positive signs. I don't know, you've probably heard about their stunt at the Botti Honey Badger. Yes, the live demo. Yeah, the live demo where they gave all the merchants the PRS terminals. The merchants were actually using ARK while accepting payments for food and drinks and so on. Yeah, it might be closer than we think, ARK. And this might be a really great privacy solution as well. Sorry.

This might improve a lot of privacy for a lot of people. This is also a huge misconception about, I think, a lot of privacy enthusiasts. We always try to make privacy perfect, but we are far from reaching that. Far. In Bitcoin, you say? Yes, but in general. Yeah, okay. In general. But in Bitcoin specifically, yes. We are far, far from reaching this accomplishment. And for now, what? I will not wait and do nothing, you know.

A privacy solution is imperfect, but is still one of the best, or at least the best in some use cases, then it's a correct solution. And it's nice that it exists, you know, because even if it's imperfect, it helps a lot the users. It makes sense to use it. Yeah, I think we're seeing, at least in the people that I talk to, that more and more people are interested in their Bitcoin privacy. And I mean... It is what it is. Most Bitcoiners hold their coins on some exchanges or don't even know about privacy. They are happy that they have their hardware wallets and use it. Privacy is a personal choice. It's always a UX burden, so you have to...

You need to decide for yourself how much you want to invest of your time and knowledge and resources into your privacy solution, what is best for your needs. Wasabi is really cheap for what it allows. Right now, with the liquidity it has and the solution, you can reach a privacy that is pretty great, meaning it's really hard to follow input and output link for a really small price. The coordinator that is used the most right now does not charge anything. any coordination fee, so any fee to participate in service. He still receives money. I track this data. The reason is a bit complex because on Wasabi, you sometimes need, it's sometimes more expensive, more expensive to get back some Bitcoin than to withdraw them, than to leave them to whatever, you know, forget about them. Like let's say to receive 100 sats.

You will need to pay 1,000 sats. Yeah, yeah, it can happen. Yes, because of how it works, it can happen. And it's not a bad thing, anyway. So in those cases... This amount is abandoned by the client. And right now, the coordinator can do whatever he wants with this amount. So he can choose to have it for himself. But for users, using Wasabi is extremely cheap.

To achieve a great privacy or current mining fee rate, you pay only a few dollars per transaction and Webisabi transaction can have a lot of inputs. In fact, the average for a Webisabi transaction is about 300 inputs. Und 300 output. Okay? So it's massive. Thanks to that, you earn a lot of privacy. Then you remix for a couple of times. It really is powerful. It's not a complete solution for privacy. Okay? Nodehing is perfect. And because...

What is really powerful right now on Bitcoin to degrade the privacy of people is to do pattern matching analysis. Okay, what's that? You have amount matching analysis. You have Wabi Sabi, the CoinJoin liquidity pool as a black box. You don't try to go see into this, but when you look at the amount of money that flows in. and flows out. And you try to extract that it's a user who the coins belong to considering the amounts of money and the patterns. Let's say I put 1.234 Bitcoin in. Okay? Yeah.

And I see that one week later, there is 1.234 Bitcoin out. You know, I can imagine that it's the same guy, right, as an external observer. This is really risky. And this is why PostMix tools are important, which mean tools to control the way you send Bitcoin. When you make a payment in Bitcoin, you have to take care about what input to use. to not reveal too much information. For example, it's really bad in Bitcoin if you send your whole balance in the same transaction, you know, because it's really easy to make amount matching. If you use Wasabi as a mixer, which means...

Das ist ein Coinjoin, nicht ein Mixer. Ja, das ist ein Coinjoin, aber wenn du es benutzt, wie du es benutzt, wie du es benutzt, wie du es benutzt, und dann du es benutzt. Ja. Okay, das wird eine Menge Informationen über dich, weil deine Usage von Bitcoin ist falsch. Du solltest Bitcoin Wasabi benutzen als ein Wallet, das bedeutet, dass du es von Zeit zu Zeit fundiert. Ich weiß nicht, wenn du dein Geld bekommst, oder was du es benutzt. Du sendest dein Geld dort. And then you participate into CoinJoin. Your money will be slowly private. Then you need to pay your rent. So you pay your rent. You receive change maybe. And after that, the change for the transaction is CoinJoin again, you see. And then, so it's really using it as a wallet, never sending your whole balance. Okay, so what you're saying is it's better to use, it's not only about Wasabi, but in general for CoinJoin,

Don't use the service just for the CoinJoin and then move funds from your hardware wallet in and then after that, move it back to your hardware wallet. Instead... Sorry, but hardware wallet is fine because it does not leave any on-chain footprint. The hardware wallet doesn't? Wait, if you're sending a transaction? Hardware wallet for on-chain on the blockchain is the same. Nobody knows that this address belongs to you, okay? You send the transaction, but nobody knows anything about this transaction, so it does not add any issues.

Oh, however, what you really must avoid is to send your whole balance at the same time. Okay. I'm not sure if I'm getting the point of why it's a problem if I send my whole stack of Bitcoin into a CoinJoin. I will tell you. I will tell you. Well, let's say I analyze the blockchain because I'm a blockchain analyst. Okay. I see you every month on June 5th. There are five Bitcoins that comes in a CoinJoin. Okay. And I see that every month on the 6th, there is exactly five Bitcoins that goes into this address. Okay. In this case, I can know the CoinJoin had no effect because I can just ignore the CoinJoin.

Und sagen, oh, das ist der gleiche User, das ist der Link. Und dann weiter folgt der Trailer. Ja, okay. After das. Wenn es immer wieder die gleichen Patterns gibt, dann ist es leicht zu degradieren die Privatsphäre der Menschen. So das ist warum man immer immer die Wallet benutzt, das bedeutet, receive Geld all the time, pay your stuff. and take care of bad patterns and try to maybe go for other privacy solutions, like go for some phones on Lightning or things like that, you know. Privacy is an accumulation of steps. There is no solution perfect. So if you conjoin a significant amount for you, after that, you need to understand that if you use this...

A huge chunk of this amount, your privacy will be highly degraded from this operation. This is money in and out. You take so in and by time to time you pay, you use. Okay, wait. So you're basically saying the best privacy is achieved by using Bitcoin and using a client like Wasabi because it has a coin join in it and uses it for incoming payments and for outgoing payments. And that will over time increase. your privacy. Yes, it's not over time. It's in an instant process. You could use your all balance, but by doing so, you would undermine the usefulness of the system because of those pattern matching problems. However, yes, if you use Bitcoin and you do not use Wasabi, it means that you are less private than someone that uses Wasabi.

Okay. It's just, it is all, for now, it is an important stone of using Bitcoin the most privately as you can. Okay. Other wallets are pretty good. Like the samurai client that gets remade at Shigaru or even joint market. Okay. Those systems are also really interesting solution. But at the end of the day, what I mean, you should also at some point. Add Wasabi into this. You should conjoin with one of Wabi-Sabi coordinators, basically, to increase further your privacy. Node doing it is just losing privacy. I got a little bit confused at some point and I lost track of my thoughts. Sorry. I'm sorry. No, no. There was a question I had.

I lost it. Fuck. Anyway, I think it's a really passionating topic, but you see how hard it is. This is why you should use the tools that are provided in the way the maintainer, developer... Wasabi?

It already has? Like send and receive? No, no, no. Only send? Yes. Wasabi can send to silent payment addresses. It has been released like about six months ago now, I think. So we are one of the few wallets. But there is blue wallet also that allows to send silent payment and cake wallet. Cake wallet for now is the only one that really supports send and receive. And it's pretty cool that they build that. Implementation is a bit clunky, but it is a very good start for... For this tech, really, really glad. And Wasabi, we implemented the Sun Service and are in the process of implementing Receive as well. However, it is a really complex thing to achieve because you need a really powerful indexer, which means it's...

Software, Remote Software, Server, that interacts with a node and provides you information. In this case, with Wabi, we already have this, which is our backend. It's an indexer, in fact, and because it provides block filters. So there is a server, it interacts with a node, creates the block filter, and then serves them to the client. Okay, so the client can receive them. But this is what an indexer is. And for silent payments, you need to add an extra layer of information there, which are called the tweak. It's some information you need to recognize that the payment is yours and make it. It's an information you need for silent payment. As a receiver, right? Yes. We're talking about the receiving side. The receiving side is hard. Yes. Because the way I understand it is...

What you publish is like a master silent payment receive address. And the user then creates with his transaction to this silent payment address, he creates the final destination address, right? And now it's not clear for the wallet or it's hard for the wallet to scan if I receive the payment, right? Because I don't know if this address belongs to me, right? In your words, that's basically it, yes. Okay, okay. Basically. But it was pretty nice, but the technical words are not there, but it's the idea, yes. Basically, your client by itself cannot have access to this information because you need information that are contained in the block.

In the Bitcoin block. However, clients do not receive Bitcoin blocks except full node integration. Therefore, you require extra information that a server has to send you. Or you can run your own node and receive your own block and analyze them. And in this case, you're... Bitcoin node becomes your indexer. In fact, this is where we are going to Wasabi and this is why we will be able to have a silent payment received in not that crazy amount of time because you will just run your Bitcoin node, act with Wasabi as an alternative UI for your Bitcoin node and be able to generate the silent payment tweaks. So the extra piece of information you need to receive silent payment. Okay.

Wait, I always thought the problem is that the scanning for a received payment is so hard. It is hard because you need extra information. You need information computed by the node. By my node. Yes, but you need to have access to the tweak, to a blog basically to compute this information. What is the tweak then? I'm not an expert. Okay. Yeah, but if you have an idea of what it is. It is a huge number that contains all the scripts for the current scripts that are tweaked, which means changed. Changed with a function to a private key.

It's a way for your receiver private key to manipulate the information contained inside all transactions in the Bitcoin block and to receive the script of the outputs. Okay, I hope I didn't make mistake myself. I didn't understand the problem. I'm sorry. It's okay, but you need extra information. You need to see the transactions, basically. Yeah, but when I run my own node and, you know, I have my own mempool, so basically know all the transactions that are in the block, and if not, I can request my peers to give me the transactions that are missing in this block, right? So I have already, as a node runner, a clear view of what is in the block, right?

So far, so right. You have the full list of what is in the block. And so this is why if you have access to the full node, you see the transaction and then you can check whether or not you receive the silent payment. Because only you can check and only a full node can add the information you need. So basically you need to read this one by one. And what are the tweaks is a way for a remote server to send you. to send you data that will abstract the need of the Bitcoin node, basically. The tweaks are a way to... Don't use your own node, but instead use a remote one without degrading your privacy. I'm lost.

Sorry, it's a really complex topic. I'm just trying to understand why. Because we are seeing some wallets that support sending to silent payments. Yes. But not many wallets. And you mentioned Cake Wallet. It allows to receive silent payments, but it's not really good at it. I don't know. No, in the case of K8, it is good at it. It works very well. It's just annoying to synchronize. Also, because the data that it requires is really heavy. And they changed the Electrum server to 40. I don't remember. Okay. It's clunky to use, but it works. The cryptography, et cetera, works. It is hard to build a good indexer, which means a remote server that can send you the information you need.

that a payment is yours and that you have the key to unlock it. Basically, because you need to compute this information, it's extra information. But if you use your own node, it's very easier. It's become very easy. Very easy. It's just a cryptographic solution. Why aren't we seeing more solutions that require you to run your own node, but then you can receive silent payments? What wallet right now requires you to run your own node?

Almost no one. It is really rare to have an alternative UI for Bitcoin Core. And Wasabi is becoming that and becoming very, very good at it. It's becoming a way to interact with your node, with the Wasabi UI, to make payment, compute request information, all this. It's called the block-only mode. Block-only wallets are pretty rare, in fact. People don't want them because it's really like the user don't. Ja, okay, I get that point.

To use it in a light wallet is quite hard, as you have to send extra information. Light wallet means that I'm not connected to my own note, but to note to some third-party provider. It can be, I don't know. There are many. All right, okay. As a solution, you can do it very easily in a way that is by losing your privacy because you can send your key to a server and the server can tell you why you have those phones because the server is connected to a node. Yeah. But then the server will know your phone. So it makes sense. That does not make sense. So this is why you don't see that many receive sites on silent payment right now. However, it will come because it's a really interesting solution.

With your own node, it's really easy. We are also building a better indexer that we hope can be replicated and used across the industry. Many people, not many, but people are working on that. It also plays very well with other development we see Bitcoin going to, like BIP353. It's a BIP to have some kind of readable URL. Yes. And that it resolves. It resolves to a Bitcoin address. Yes. So you can have like a username on Bitcoin, like I'm Jan-Paul. And just by giving this name, you can derive destination addresses. Like Jan-Paul at wasabiwallet.io, for example. And when the wallet will send.

He tried to resolve your address from the DNS, from the DNS server. So I asked JanPaul.io for the address I need to send to, you know, and it arrives. It's like LN URL. And it works extremely well with silent payment because what is the main issue from doing that? A URL, a DNS that resolves to your address is that you have no privacy against the server because the server in this case was the way Ja, we'll obviously see all the addresses that you're generating. Yes, because it provides them to you. But if it receives, if instead of providing a normal address through this scheme, you provide a silent payment address. Ah, okay. The way silent payment works is that even the DNS that provided you this address.

will not be able to know the forms that are being sent to the silent payment address. Yeah, because he doesn't see it. He just gives out the silent payment receive address and then the transactor, the one making the transaction, the payment, he will finally generate the silent payment, the payment itself or construct his transaction and only he knows then the output address. The sender. Only he knows the Apple, not the server. Yes, not the server. Because he only has the silent payment. Yes, only the sender and the receiver. Node only other people have sent to this address in the past. No, because it always changes, you know. So it's only the sender and the receiver.

And nobody can know. And so it's very cool. It works very well together. For sure, we want this kind of use case for Bitcoin. It's incredible UX. Because what does it mean? It means even without asking you directly, I can just write your contact name, yanpaul at wasabiwallet.io and send to you. Without nobody knowing except you. So a private way, not even the server I requested the information from. So, you know, those kind of silent payments is a really cool development. And this is why we are building stuff like the Indexer. So it can, you know, always push for those kind of...

cool technology in the Bitcoin ecosystem, make really small, impactful tools to be able to build better software and better UX on top of Bitcoin. Maintaining a wallet is fascinating. What's fascinating you? Problems you face are quite hard, quite new. And you understand new way people have to interact with money, with assets, all the burden that they face. So you understand very well how Bitcoin works.

Do you understand how people interact with Bitcoin and how they interact with Bitcoin? they will want to do and try to receive feedback and these kind of things. It's a passionate field to contribute in and a lot of great open source projects as well that you can contribute and contributing is not always, you know, providing code but finding an issue is contributing, you know, because it helps, it fucking helps, I can tell you. Or changing a bit of a doc or you see stuff like this.

Ah, nice. All right, Clément, so thank you so much for taking the time to talk to you. I would really like to be able to talk with you and we were listening to this podcast. Thank you for having me. It was a long time since... Yeah, it was a long time since we talked. Yeah, but unfortunately, I was a little bit too stoned for this talk. I had a hard time focusing and, you know, keeping the conversation like very natural. I don't know, I felt a little bit like, oh, it's a podcast, not a conversation, not the thing that I was aiming for. For me, I think it was really cool. Yeah. Oh, nice. All right. Yes. You enjoyed it. And I think the podcast will be really cool.

Ja, ich denke, in fact, ich denke, es ist sehr schwierig für uns zu erklären, warum Wasabi, die Richtung wir versuchen, warum Wasabi ist cool, weil es viele, viele Dinge, die man muss verstehen. Ja, ja. Ja, ja, ja. Für uns, um zu sprechen, war es eine sehr gute Möglichkeit. Oh, nice. All right, Clem, ich werde den Stop button klicken und dann we're out.

Open the transcript file

Hosts and Guests

Hosts

  • Actionslave Host Feed-stated
  • Jan-Paul Host Feed-stated

Guests

  • Clement Guest Feed-stated

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Nodesignal-Talk - E302 - libbitcoin is coming

    Nov 13, 202656 minVideo

    In der heutigen Folge sprechen Jan-Paul und Thorsten mit Kevin (Eynhaender) über Libbitcoin, die zweite, von Grund auf neu gebaute Umsetzung des Bitcoin-Regelwerks neben Bitcoin Core. Wir klären, was Libbitcoin ist und...

    Listen to the audio

    Credit the people on this episode

  2. Nodesignal-Buchclub - E301 - Cryptoeconomics #7 - Valido, ergo sum - Sicherheit und Ökonomie im Netzwerk der Nodes

    Nov 6, 20262 hr 1 minVideo

    In der heutigen Folge sprechen actionslave, Zetti und Calso im Nodesignal-Buchclub über Eric Voskuils „Cryptoeconomics - Fundamental Principles of Bitcoin“ (deutsch: „Kryptoökonomie“, übersetzt). Wer sichert Bitcoin...

    Listen to the audio

    Credit the people on this episode

  3. Nodesignal-Recap - Oktober 2026

    Nov 4, 20265 minAudio

    Dreihundert Folgen Nodesignal, und das Whitepaper, auf dem alles aufbaut, steht bei den Hosts vor allem eingerahmt im Regal. Ein ziemlich ehrlicher Moment zum Jubiläum. Wie Blöcke, die aufeinander aufbauen, ziehen sich...

    Credit the people on this episode

  4. Nodesignal-Spezial - E300 - 18 Jahre Bitcoin Whitepaper

    Oct 30, 202644 minVideo

    In der heutigen Folge sprechen Thorsten ⚡️ und zettizettler zum 18. Geburtstag des Bitcoin-Whitepapers am 31.10.2026 über die Geschichte und den Inhalt des legendären neun Seiten langen Papiers von Satoshi Nakamoto....

    Listen to the audio

    Credit the people on this episode

  5. Nodesignal-Techboost - E299 - Gemischter Satz (Schwerpunkte Hopp/Bark)

    Oct 23, 20261 hr 10 minVideo

    In der heutigen Folge sprechen zettizettler, Thorsten und actionslave über den Nodesignal-Player Hopp, aktuelle Technews aus der Bitcoin- und Lightning-Welt und einen Deepdive: Jan-Paul zeigt, wie man die Bark Wallet...

    Listen to the audio

    Credit the people on this episode