WEBVTT - Automatic transcript; recognition may contain errors. Reviewed for technical wording and speaker labels. Times match the published episode.

00:00:20.620 --> 00:00:25.500
<v Aaron van Wirdum>Live from Utrecht, this is Bitcoin Explained. Hello. Hey, Sjors.

00:00:25.800 --> 00:00:26.100
<v Sjors Provoost>What's up?

00:00:27.630 --> 00:00:29.410
<v Aaron van Wirdum>Our favorite guest is back, Ruben.

00:00:29.990 --> 00:00:30.850
<v Ruben Somsen>Hello, I'm back.

00:00:30.870 --> 00:00:31.910
<v Aaron van Wirdum>Hey, Ruben. How are you?

00:00:32.170 --> 00:00:32.730
<v Ruben Somsen>Good to be back.

00:00:32.730 --> 00:00:33.170
<v Aaron van Wirdum>How have you been?

00:00:33.290 --> 00:00:34.230
<v Ruben Somsen>I'm doing great.

00:00:35.560 --> 00:00:40.780
<v Aaron van Wirdum>Thanks for being back. So you're our sidechain expert, kind of?

00:00:40.960 --> 00:00:41.120
<v Ruben Somsen>Yeah.

00:00:41.360 --> 00:00:42.700
<v Aaron van Wirdum>How do you describe yourself?

00:00:43.420 --> 00:00:48.380
<v Ruben Somsen>I change it every day, so there's no... Yeah, I guess sidechain expert is a good

00:00:48.380 --> 00:00:48.980
<v Ruben Somsen>way of putting it.

00:00:49.220 --> 00:00:50.200
<v Aaron van Wirdum>Layer 2 expert, maybe?

00:00:50.200 --> 00:00:53.860
<v Ruben Somsen>Layer 2, yeah. Definitely, yeah, that all fits.

00:00:54.940 --> 00:00:56.420
<v Sjors Provoost>Complicated other things expert.

00:00:56.720 --> 00:01:01.500
<v Ruben Somsen>I think someone described me as a sidechain architect, I think. That was kind of

00:01:01.500 --> 00:01:03.260
<v Ruben Somsen>funny. Architect, I like it.

00:01:03.660 --> 00:01:07.100
<v Aaron van Wirdum>So it's good you're back today because we're going to discuss something layer

00:01:07.100 --> 00:01:12.950
<v Aaron van Wirdum>two-ish, namely federated eCash. First of all,

00:01:13.050 --> 00:01:15.610
<v Aaron van Wirdum>why are we discussing federated eCash today, Sjors?

00:01:15.930 --> 00:01:21.490
<v Sjors Provoost>Well, because there was a blog post in November 2021 about it.

00:01:21.850 --> 00:01:27.450
<v Sjors Provoost>And then somebody randomly brought up eCash in another chat that I'm in last

00:01:27.450 --> 00:01:29.410
<v Sjors Provoost>week. So I think maybe we should cover that.

00:01:30.310 --> 00:01:32.610
<v Aaron van Wirdum>Wait, is the blog post from a year ago? Is that what you said?

00:01:32.850 --> 00:01:34.370
<v Sjors Provoost>November. Just a few months.

00:01:34.590 --> 00:01:35.470
<v Aaron van Wirdum>Oh, a few months ago.

00:01:35.670 --> 00:01:38.130
<v Ruben Somsen>And it's a post by Blockstream specifically.

00:01:38.530 --> 00:01:43.910
<v Aaron van Wirdum>Yeah, so Blockstream is going to fund a federated eCash project. Is that right?

00:01:44.490 --> 00:01:49.450
<v Sjors Provoost>Yes. I think that it's going to sponsor the developer who works on that project.

00:01:49.830 --> 00:01:55.690
<v Ruben Somsen>Yeah, his name is Eric. And he's basically researching the project or researching

00:01:55.690 --> 00:01:58.710
<v Ruben Somsen>eCash. And Blockstream is funding it.

00:02:01.870 --> 00:02:06.590
<v Aaron van Wirdum>Right. So I don't know if you know this, Sjors, but I actually, we discussed this

00:02:06.590 --> 00:02:12.220
<v Aaron van Wirdum>on the show before, or at least I did kinda on the episode,

00:02:12.520 --> 00:02:18.050
<v Aaron van Wirdum>the Bitcoin Beach episode I did with Nicolas Burtey. They have this shared

00:02:18.050 --> 00:02:22.550
<v Aaron van Wirdum>custody solution for their Lightning wallet. And then during the podcast, I sort

00:02:22.550 --> 00:02:27.250
<v Aaron van Wirdum>of mentioned, you know what would be great for this? If you use Chaumian eCash

00:02:27.250 --> 00:02:31.190
<v Aaron van Wirdum>for this system to add privacy. So I'm very happy to learn that someone is

00:02:31.190 --> 00:02:32.850
<v Aaron van Wirdum>actually building this. That's excellent.

00:02:33.030 --> 00:02:34.750
<v Sjors Provoost>So really it's your idea.

00:02:35.110 --> 00:02:37.430
<v Aaron van Wirdum>I think I came up with it basically.

00:02:37.810 --> 00:02:38.270
<v Ruben Somsen>Clearly.

00:02:39.820 --> 00:02:41.900
<v Aaron van Wirdum>That's a joke in case people are not sure.

00:02:42.140 --> 00:02:42.480
<v Ruben Somsen>[unclear].

00:02:42.600 --> 00:02:47.700
<v Sjors Provoost>[unclear] get to explaining it, but it does seem like it actually improves

00:02:47.700 --> 00:02:52.400
<v Sjors Provoost>upon... The thing that we're about to discuss is a useful improvement upon

00:02:52.400 --> 00:02:53.380
<v Sjors Provoost>custodial wallets.

00:02:53.560 --> 00:02:53.680
<v Ruben Somsen>Yeah.

00:02:54.880 --> 00:02:59.440
<v Aaron van Wirdum>Yeah, first, last intro question before we get into it. So Eric was already

00:02:59.440 --> 00:03:04.580
<v Aaron van Wirdum>building this for a while before Blockstream started to throw money at it or?

00:03:04.720 --> 00:03:10.420
<v Ruben Somsen>I'm not sure how it got started. I think, I guess he was interested in the topic

00:03:10.420 --> 00:03:15.500
<v Ruben Somsen>and I guess he got in touch with Blockstream and my guess would be that he was

00:03:15.500 --> 00:03:18.980
<v Ruben Somsen>already like interested in working on it. And I know at least a lot of the

00:03:18.980 --> 00:03:23.330
<v Ruben Somsen>Blockstream people have always been very pro eCash. So it's not very surprising

00:03:23.330 --> 00:03:27.150
<v Ruben Somsen>to me that they are interested in funding something like this. So I think they

00:03:27.150 --> 00:03:32.510
<v Ruben Somsen>just got together and the interests aligned and there you go. I think that's what happened.

00:03:33.390 --> 00:03:36.510
<v Aaron van Wirdum>Yeah, eCash definitely seems like a good solution to be built on top of Bitcoin

00:03:36.510 --> 00:03:42.690
<v Aaron van Wirdum>to me. So let's get into eCash itself. What is eCash? It's yours.

00:03:43.210 --> 00:03:48.430
<v Sjors Provoost>In a nutshell, we have to go back in time to, I don't know, 1981 or something

00:03:48.430 --> 00:03:54.410
<v Sjors Provoost>around that time when David Chaum published a paper. He's a cryptographer, which

00:03:54.410 --> 00:03:58.550
<v Sjors Provoost>I think of something like blinded signatures in blah, blah, blah, electronic

00:03:58.550 --> 00:03:59.390
<v Sjors Provoost>cash, blah, blah, blah.

00:04:01.090 --> 00:04:05.510
<v Sjors Provoost>In a nutshell, what the system that he proposed and eventually built with

00:04:05.510 --> 00:04:10.930
<v Sjors Provoost>DigiCash, what it did is the bank or a bank issues

00:04:10.930 --> 00:04:16.110
<v Sjors Provoost>IOU tokens. And those tokens, you could see them as a piece of text.

00:04:16.870 --> 00:04:21.050
<v Sjors Provoost>And we'll explain how those tokens are made. And you can actually send those

00:04:21.050 --> 00:04:22.630
<v Sjors Provoost>tokens to other people on the internet.

00:04:23.970 --> 00:04:26.670
<v Sjors Provoost>And they can then redeem those tokens if they want to.

00:04:26.890 --> 00:04:31.970
<v Aaron van Wirdum>Yeah, you speak about tokens, but the point here is that eCash was essentially

00:04:31.970 --> 00:04:37.930
<v Aaron van Wirdum>a technology layer to be used by banks. So the actual money is

00:04:37.930 --> 00:04:42.390
<v Aaron van Wirdum>still dollars or euros or whatever the bank. you know, whatever the bank accounts

00:04:42.390 --> 00:04:47.190
<v Aaron van Wirdum>are using. And then they issue tokens that basically represent a dollar and they

00:04:47.190 --> 00:04:49.730
<v Aaron van Wirdum>can be exchanged at the bank for a dollar, right?

00:04:49.930 --> 00:04:50.370
<v Sjors Provoost>That's right.

00:04:50.530 --> 00:04:54.450
<v Ruben Somsen>And I think, you know, the goal was sort of, I think also to think of it as

00:04:54.450 --> 00:04:59.070
<v Ruben Somsen>regular cash, right? Where just a digital version of having a dollar bill in your

00:04:59.070 --> 00:05:01.670
<v Ruben Somsen>hands and giving it to somebody else, roughly.

00:05:01.910 --> 00:05:06.870
<v Sjors Provoost>And with the main advantage of it being somewhat anonymous. So the bank would

00:05:06.870 --> 00:05:12.120
<v Sjors Provoost>give you... digital dollar bills in a way that they will not know what actually

00:05:12.120 --> 00:05:17.600
<v Sjors Provoost>is happening to these bills. So if the bank gives me a dollar bill or this

00:05:17.600 --> 00:05:21.740
<v Sjors Provoost>digital dollar bill and then I give it to Ruben, then the bank does not actually

00:05:21.740 --> 00:05:25.120
<v Sjors Provoost>know that I gave it to Ruben. They'll know that they gave me a dollar and they'll

00:05:25.120 --> 00:05:29.580
<v Sjors Provoost>know that Ruben redeemed a dollar with them. But assuming there's more people

00:05:29.580 --> 00:05:33.040
<v Sjors Provoost>using the system, they will not be able to tell which dollar is which.

00:05:33.590 --> 00:05:36.010
<v Aaron van Wirdum>Yeah, they won't be able to tell who paid who essentially.

00:05:36.510 --> 00:05:40.510
<v Sjors Provoost>And now you might ask yourself, oh my God, they actually invent Bitcoin that long

00:05:40.510 --> 00:05:46.470
<v Sjors Provoost>ago? And the answer is no, because they have this double spend problem. And the

00:05:46.470 --> 00:05:50.430
<v Sjors Provoost>way they deal with the double spend problem is that when you receive coins, you

00:05:50.430 --> 00:05:54.370
<v Sjors Provoost>have to actually tell the bank, hey, I just received this coin. Please make sure

00:05:54.370 --> 00:05:58.970
<v Sjors Provoost>nobody else receives this coin ever. So that's the centralized party has to make

00:05:58.970 --> 00:06:03.550
<v Sjors Provoost>sure that coins can only be used once. Because I think it's easiest to think

00:06:03.550 --> 00:06:06.990
<v Sjors Provoost>about these tokens as just a piece of text. And you can copy a piece of text

00:06:06.990 --> 00:06:09.890
<v Sjors Provoost>around, so there's nothing stopping me from giving the same piece of text to

00:06:09.890 --> 00:06:14.310
<v Sjors Provoost>Ruben and to give it to Aaron. But as long as both of them immediately check with

00:06:14.310 --> 00:06:18.110
<v Sjors Provoost>the bank, hey, I just received this token, the bank will make sure that the

00:06:18.110 --> 00:06:21.770
<v Sjors Provoost>second person will get a warning, like saying, hey, you did not actually get any

00:06:21.770 --> 00:06:25.190
<v Sjors Provoost>money, you should not offer this service. So that's how they solved the double

00:06:25.190 --> 00:06:26.930
<v Sjors Provoost>spend problem. And now the question is...

00:06:26.930 --> 00:06:32.450
<v Aaron van Wirdum>What you're saying is it's still required... a central party to sort of manage

00:06:32.450 --> 00:06:33.070
<v Aaron van Wirdum>everything right?

00:06:33.070 --> 00:06:36.890
<v Sjors Provoost>Yeah, and to synchronously manage it, right? they have to be online all the time

00:06:36.890 --> 00:06:39.210
<v Sjors Provoost>otherwise the whole payment system grinds to a halt right?

00:06:39.210 --> 00:06:43.930
<v Aaron van Wirdum>But to your point I would say well, I wouldn't just say that I think that's a

00:06:43.930 --> 00:06:48.010
<v Aaron van Wirdum>fact this e-cash was the first digital currency was sort of the predecessor the

00:06:48.010 --> 00:06:49.350
<v Aaron van Wirdum>first predecessor to Bitcoin.

00:06:49.350 --> 00:06:54.350
<v Sjors Provoost>The first digital cash right so so as distinct from a digital bank account which

00:06:54.350 --> 00:06:59.010
<v Sjors Provoost>a digital bank account, it just means that the bank knows exactly which dollar

00:06:59.010 --> 00:07:00.250
<v Sjors Provoost>goes to which other person.

00:07:00.530 --> 00:07:04.310
<v Aaron van Wirdum>Yeah, my point being, if you sort of backtrace where Bitcoin came from, then I

00:07:04.310 --> 00:07:08.950
<v Aaron van Wirdum>think it's fair to say eCash is sort of the first attempt of doing something like that.

00:07:09.070 --> 00:07:09.490
<v Sjors Provoost>Yeah, for sure.

00:07:09.650 --> 00:07:13.530
<v Aaron van Wirdum>So you mentioned that it offers privacy, and I want to get into that real quick.

00:07:13.530 --> 00:07:15.690
<v Aaron van Wirdum>So how does this actually work?

00:07:15.830 --> 00:07:21.130
<v Sjors Provoost>Yeah, that's amazing, right? Because you would imagine that if you just have a

00:07:21.130 --> 00:07:26.240
<v Sjors Provoost>piece of text, then the bank... writes the piece of text, gives it to the first

00:07:26.240 --> 00:07:29.720
<v Sjors Provoost>user, and then they give it to the other user. So the bank knows exactly what

00:07:29.720 --> 00:07:31.100
<v Sjors Provoost>piece of text they wrote.

00:07:31.380 --> 00:07:34.800
<v Aaron van Wirdum>Let's say throughout this conversation, for clarity, I'm the bank. All right?

00:07:35.320 --> 00:07:36.180
<v Sjors Provoost>Oh, you're the bank.

00:07:36.300 --> 00:07:40.660
<v Aaron van Wirdum>I'm the bank. So I'm issuing something to you, Sjors. I'm issuing a note to you.

00:07:41.060 --> 00:07:46.260
<v Aaron van Wirdum>Sjors, you pay Ruben. Ruben pays me. And then I can usually, if we don't take the

00:07:46.260 --> 00:07:52.260
<v Aaron van Wirdum>privacy, anonymity measures, then I can see, hey, this is the note that I gave to

00:07:52.260 --> 00:07:55.980
<v Aaron van Wirdum>Sjors. So therefore, Sjors must have paid Ruben and there's no privacy [unclear].

00:07:56.280 --> 00:07:57.540
<v Sjors Provoost>Because there might be a serial number on it.

00:07:57.880 --> 00:08:00.680
<v Aaron van Wirdum>So this needs to be solved somehow. So how was that solved?

00:08:00.960 --> 00:08:02.140
<v Sjors Provoost>Ta-da! Yeah.

00:08:02.860 --> 00:08:08.860
<v Ruben Somsen>Okay, so basically how that's solved is by blind signatures. So what happens

00:08:08.860 --> 00:08:14.440
<v Ruben Somsen>is the first person comes and gets a note from the bank. So in this case, Aaron,

00:08:14.620 --> 00:08:20.040
<v Ruben Somsen>you give a note to Sjors. But the trick is that

00:08:20.040 --> 00:08:25.800
<v Ruben Somsen>it's actually a number that Sjors picked, and he blinds that number, so you

00:08:25.800 --> 00:08:30.940
<v Ruben Somsen>can't actually see it. And then you put your signature on the blinded value. And

00:08:30.940 --> 00:08:35.920
<v Ruben Somsen>then Sjors, he can go and unblind that value after you signed it. And so now

00:08:35.920 --> 00:08:40.220
<v Ruben Somsen>Sjors has his number that you signed, but you never saw because the only thing

00:08:40.220 --> 00:08:45.610
<v Ruben Somsen>you saw was the blinded number. And then later, Sjors gives the number to me. And

00:08:45.610 --> 00:08:50.530
<v Ruben Somsen>now both me and Sjors have the number. So that's not enough. If I just received a

00:08:50.530 --> 00:08:55.410
<v Ruben Somsen>number from Sjors, well, now it's kind of both our coin. So I go and I show a

00:08:55.410 --> 00:09:01.310
<v Ruben Somsen>number to you, Aaron. And now you see the number and you see that you

00:09:01.310 --> 00:09:05.530
<v Ruben Somsen>signed it, but you don't recognize it because the previous one was blinded. And

00:09:05.530 --> 00:09:11.180
<v Ruben Somsen>after you receive it, you either credit me a dollar or now we do the same thing.

00:09:11.300 --> 00:09:15.120
<v Ruben Somsen>We create a new number. So I create a number. I blind it. I give it to you. You

00:09:15.120 --> 00:09:19.140
<v Ruben Somsen>sign it. I unblind it. And now I have a new token. That's basically how it works.

00:09:19.140 --> 00:09:22.980
<v Aaron van Wirdum>Yeah, and you're using the word blinding here but that's basically just doing

00:09:22.980 --> 00:09:25.600
<v Aaron van Wirdum>some sort of mathematical formula with a secret number right?

00:09:25.600 --> 00:09:30.560
<v Ruben Somsen>Yeah, you can think of it as, uh, adding two numbers together, two big numbers,

00:09:30.560 --> 00:09:36.100
<v Ruben Somsen>uh, and then after you sign it, somehow one of the two numbers can be subtracted

00:09:36.100 --> 00:09:38.000
<v Ruben Somsen>again That's not literally how it works, but…

00:09:38.190 --> 00:09:43.730
<v Sjors Provoost>Yeah, or a physical analogy that's being used is this carbon copy paper. So

00:09:43.730 --> 00:09:46.970
<v Sjors Provoost>I don't know if people still remember what paper forms are.

00:09:47.030 --> 00:09:47.850
<v Aaron van Wirdum>You're old, Sjors.

00:09:48.130 --> 00:09:52.050
<v Sjors Provoost>But well, if you drive a car, then you might still encounter these pieces of

00:09:52.050 --> 00:09:55.010
<v Sjors Provoost>paper. So if you, in Europe anyway, if you crash your car into somebody else or

00:09:55.010 --> 00:09:59.070
<v Sjors Provoost>vice versa, you have to fill in an insurance form and you draw a picture of the

00:09:59.070 --> 00:10:02.930
<v Sjors Provoost>situation on the form. And then there's a piece of paper below it, which is

00:10:02.930 --> 00:10:07.240
<v Sjors Provoost>called the carbon copy. And that's where CC in email comes from, which will have

00:10:07.240 --> 00:10:10.460
<v Sjors Provoost>the same text on it because your pen physically pushes through the paper. It's

00:10:10.460 --> 00:10:16.220
<v Sjors Provoost>crazy. But the analogy here would be you could put a piece of carbon, this carbon

00:10:16.220 --> 00:10:20.680
<v Sjors Provoost>paper, inside an envelope, and then you would write on the envelope, on the

00:10:20.680 --> 00:10:25.700
<v Sjors Provoost>outside of the envelope, your signature. And that means that whatever was on the

00:10:25.700 --> 00:10:28.600
<v Sjors Provoost>inside of the envelope now has your signature on it. So you kind of make a carte

00:10:28.600 --> 00:10:33.620
<v Sjors Provoost>blanche signature. Of course, it wouldn't be carte blanche. There is a way to

00:10:33.620 --> 00:10:37.720
<v Sjors Provoost>guarantee that you're not signing for $100 when you're only getting one. But

00:10:37.720 --> 00:10:43.280
<v Sjors Provoost>that's the idea. The bank knows they signed something that is a bank note. And

00:10:43.280 --> 00:10:47.360
<v Sjors Provoost>you can prove to other people that the bank showed it. But the bank does not know

00:10:47.360 --> 00:10:51.460
<v Sjors Provoost>which note they signed because they can't see inside the envelope. And unlike a

00:10:51.460 --> 00:10:53.040
<v Sjors Provoost>real envelope, they can't actually open it.

00:10:53.440 --> 00:10:57.980
<v Ruben Somsen>And so maybe one good thing to add here is that the anonymity set is actually

00:10:57.980 --> 00:11:03.760
<v Ruben Somsen>depending on the value. So if you issue a $1 note, then everybody else who has a

00:11:03.760 --> 00:11:08.560
<v Ruben Somsen>$1 note is within the same anonymity set. And if there's a $2 note, then you have

00:11:08.560 --> 00:11:13.280
<v Ruben Somsen>yet another anonymity set. And because the bank cannot really distinguish,

00:11:13.740 --> 00:11:19.520
<v Ruben Somsen>you know, it signs something and it can't really distinguish who it came from.

00:11:19.640 --> 00:11:22.440
<v Ruben Somsen>The way you distinguish the values, well, there are multiple ways of doing that,

00:11:22.500 --> 00:11:26.620
<v Ruben Somsen>but one way of doing that is to have the bank just put a different signature on a

00:11:26.620 --> 00:11:27.360
<v Ruben Somsen>different value note.

00:11:27.520 --> 00:11:30.120
<v Sjors Provoost>But now you're moving beyond what David Chaum did, I think.

00:11:30.380 --> 00:11:32.260
<v Ruben Somsen>That is possible, yeah.

00:11:32.400 --> 00:11:36.240
<v Sjors Provoost>We're not actually entirely sure, but as far as I understand it, the DigiCash

00:11:36.240 --> 00:11:39.720
<v Sjors Provoost>system had coins of one fixed value and they were all the same value.

00:11:39.860 --> 00:11:40.900
<v Ruben Somsen>Yeah, that wasn't the original paper.

00:11:41.080 --> 00:11:43.660
<v Sjors Provoost>Yeah, and then later on there were proposals where you could have different

00:11:43.660 --> 00:11:48.020
<v Sjors Provoost>values and then you have to go through a whole bunch of magic to make… so that

00:11:48.020 --> 00:11:51.440
<v Sjors Provoost>you can make notes of different values, but it just boils down to having a very

00:11:51.440 --> 00:11:52.360
<v Sjors Provoost>large bag of coins.

00:11:52.360 --> 00:11:57.040
<v Ruben Somsen>Yeah, well, so it's not necessarily a lot of magic because you can just have the

00:11:57.040 --> 00:12:01.380
<v Ruben Somsen>bank have a different key and that would be sufficient so then every key is

00:12:01.380 --> 00:12:02.800
<v Ruben Somsen>representative of a value?

00:12:02.800 --> 00:12:03.260
<v Sjors Provoost>Yes,

00:12:03.260 --> 00:12:06.700
<v Ruben Somsen>so that would be basically enough, but there are lots of different schemes.

00:12:06.700 --> 00:12:07.120
<v Ruben Somsen>that's true.

00:12:07.120 --> 00:12:11.180
<v Aaron van Wirdum>Anyways, getting back to the main point, the trick is essentially, Sjors, you

00:12:12.460 --> 00:12:16.520
<v Aaron van Wirdum>create a piece of currency, essentially, but then you scramble it with a secret

00:12:16.520 --> 00:12:21.120
<v Aaron van Wirdum>number. You send it to me. I sign it. And the magic is that you can unscramble it

00:12:21.120 --> 00:12:26.100
<v Aaron van Wirdum>while the signature is still valid I can still see that, yep, I signed this, I

00:12:26.100 --> 00:12:31.080
<v Aaron van Wirdum>signed the scrambled version of this, and therefore this is a valid note and when

00:12:31.080 --> 00:12:35.880
<v Aaron van Wirdum>Ruben hands it to me I'll give him a real Bitcoin in exchange in this case or in

00:12:35.880 --> 00:12:36.680
<v Aaron van Wirdum>Chaum's case a dollar.

00:12:36.680 --> 00:12:40.540
<v Sjors Provoost>And that means in the case of the bank, they know that, how many, how many notes

00:12:40.540 --> 00:12:44.260
<v Sjors Provoost>they issued, so somebody cannot forge more notes, right?

00:12:44.260 --> 00:12:50.060
<v Aaron van Wirdum>Yeah, okay, so that's uh, e-cash now we're getting into

00:12:50.060 --> 00:12:55.260
<v Aaron van Wirdum>sort of this new Bitcoin version of it. I think in general it works

00:12:56.050 --> 00:13:00.470
<v Aaron van Wirdum>the same, right? The blinding mechanism and the way transactions work and that's

00:13:00.470 --> 00:13:05.410
<v Aaron van Wirdum>essentially the same. But there's a new aspect to it, which is the federated part

00:13:05.410 --> 00:13:06.290
<v Aaron van Wirdum>of it, right?

00:13:06.510 --> 00:13:06.650
<v Ruben Somsen>Yeah.

00:13:07.330 --> 00:13:09.690
<v Sjors Provoost>And the fact that you're pegging in and out of Bitcoin.

00:13:10.910 --> 00:13:14.550
<v Aaron van Wirdum>Yeah, we're not using dollars or euros anymore. We're using Bitcoin. But I think

00:13:14.550 --> 00:13:18.730
<v Aaron van Wirdum>the interesting part to zoom into now is the federated part. So what does that mean?

00:13:19.310 --> 00:13:24.850
<v Ruben Somsen>Yeah. So the federated part is basically that because you can hold Bitcoins with

00:13:24.850 --> 00:13:30.250
<v Ruben Somsen>more than one person, you can have the mint or the bank, as we called it,

00:13:31.200 --> 00:13:37.060
<v Ruben Somsen>we can have that entity also be some kind of multisig thing, multisig entity of

00:13:37.060 --> 00:13:40.940
<v Ruben Somsen>multiple people. So maybe the three of us, we can come together and we can say

00:13:40.940 --> 00:13:45.420
<v Ruben Somsen>like, hey, we are going to start Mint. And then anyone who trusts us can deposit

00:13:45.420 --> 00:13:48.060
<v Ruben Somsen>some coins and we give them tokens that we sign.

00:13:48.260 --> 00:13:53.910
<v Aaron van Wirdum>Yeah, so to take one… To get back to our previous example, I was the bank in the

00:13:53.910 --> 00:13:58.550
<v Aaron van Wirdum>previous example. In this example, I am basically replaced by a multisig of

00:13:58.550 --> 00:13:59.410
<v Aaron van Wirdum>multiple people.

00:13:59.550 --> 00:14:01.550
<v Ruben Somsen>Yeah. So let's say it's the three of us, for instance.

00:14:01.650 --> 00:14:01.790
<v Aaron van Wirdum>Sure.

00:14:01.910 --> 00:14:06.450
<v Ruben Somsen>And then we have a two of three multisig. So for someone to enter into the

00:14:06.450 --> 00:14:12.360
<v Ruben Somsen>system, they might send us 100 satoshis. And then we might give them a hundred

00:14:12.360 --> 00:14:15.940
<v Ruben Somsen>signatures where each signature is worth one Satoshi, for example.

00:14:16.060 --> 00:14:19.400
<v Sjors Provoost>Or we give them one signature that's worth a hundred Satoshis. So there's some

00:14:19.400 --> 00:14:21.040
<v Sjors Provoost>flexibility in the denomination. Yeah.

00:14:21.240 --> 00:14:23.160
<v Ruben Somsen>Or 10 worth 10, et cetera. Yeah.

00:14:25.740 --> 00:14:31.720
<v Ruben Somsen>So when we do that, that signature is also a multisignature of the three of us.

00:14:32.160 --> 00:14:34.160
<v Ruben Somsen>So the signature itself…

00:14:34.160 --> 00:14:35.220
<v Aaron van Wirdum>So the blind signature.

00:14:35.540 --> 00:14:39.960
<v Ruben Somsen>The blind signature, yeah, is also a multisignature. So that means that the three

00:14:39.960 --> 00:14:44.160
<v Ruben Somsen>of us, we at least know like, okay, well, it's not just Aaron who suddenly is

00:14:44.160 --> 00:14:47.580
<v Ruben Somsen>creating a bunch of these tokens. The three of us will have to have signed off on

00:14:47.580 --> 00:14:50.140
<v Ruben Somsen>it or two or three if you want some kind of threshold signature scheme.

00:14:51.400 --> 00:14:56.930
<v Ruben Somsen>And… that basically adds to the security where now instead of having to trust one

00:14:56.930 --> 00:15:02.910
<v Ruben Somsen>entity, both the currency that's backing it, which is the Bitcoin, is held in

00:15:02.910 --> 00:15:08.790
<v Ruben Somsen>a multisig and the issuance of new tokens on this blind e-cash system,

00:15:09.030 --> 00:15:10.010
<v Ruben Somsen>they are also a multisig.

00:15:10.320 --> 00:15:14.680
<v Aaron van Wirdum>Right. So it's safer. That's essentially the point of doing it federated as

00:15:14.680 --> 00:15:16.880
<v Aaron van Wirdum>opposed to just a single signature solution.

00:15:17.300 --> 00:15:20.960
<v Sjors Provoost>And then the question is, what can you actually do with these tokens? Well, if,

00:15:21.100 --> 00:15:25.800
<v Sjors Provoost>you know, within the community, people can use it if they trust the, basically

00:15:25.800 --> 00:15:31.120
<v Sjors Provoost>the quorum or the, yeah. If they trust a group that signed it, they can use it

00:15:31.120 --> 00:15:35.000
<v Sjors Provoost>because they know what these tokens are worth and they can just move them around

00:15:35.000 --> 00:15:37.680
<v Sjors Provoost>as it would be with other eCash systems.

00:15:37.940 --> 00:15:43.480
<v Aaron van Wirdum>Well, so let's make this very concrete. The three of us have this... We

00:15:43.480 --> 00:15:49.420
<v Aaron van Wirdum>have a multisig mint, the three of us. We're issuing tokens and we're getting

00:15:49.420 --> 00:15:50.880
<v Aaron van Wirdum>Bitcoin in exchange for that.

00:15:51.080 --> 00:15:51.520
<v Sjors Provoost>Yep.

00:15:51.740 --> 00:15:56.690
<v Aaron van Wirdum>Right? And so the recipient of that token can pay… whoever will

00:15:56.690 --> 00:15:59.550
<v Aaron van Wirdum>accept the token, essentially, right?

00:15:59.750 --> 00:16:05.050
<v Sjors Provoost>Yeah, anybody who trusts the token. And that really relies on them trusting the

00:16:05.050 --> 00:16:05.770
<v Sjors Provoost>Federation.

00:16:06.230 --> 00:16:11.270
<v Aaron van Wirdum>And what's the benefit exactly? Why use this instead of Lightning, for example?

00:16:12.870 --> 00:16:18.570
<v Ruben Somsen>Yeah, so I think... One of the things you should compare it to is, I think, a

00:16:18.570 --> 00:16:22.850
<v Ruben Somsen>centralized thing, where if you just have full custody, you give full custody

00:16:22.850 --> 00:16:27.690
<v Ruben Somsen>over to Coinbase, for instance, or we've seen a bunch of these Lightning wallets

00:16:27.690 --> 00:16:32.450
<v Ruben Somsen>that are actually custodial. So you basically have a custodial relationship with

00:16:32.450 --> 00:16:38.110
<v Ruben Somsen>one entity. And if that's the case, you can do better with this federation,

00:16:38.130 --> 00:16:42.390
<v Ruben Somsen>and you can do better with these anonymous tokens, where if you have an e-cash

00:16:42.390 --> 00:16:47.470
<v Ruben Somsen>system, you can at least within all the people, all the people that are trusting

00:16:47.470 --> 00:16:53.450
<v Ruben Somsen>the same entity or the same federation, between those people, you can now send

00:16:53.450 --> 00:16:57.150
<v Ruben Somsen>anonymously without the federation itself actually knowing where those tokens are

00:16:57.150 --> 00:16:59.830
<v Ruben Somsen>going. So that's a big improvement, I would say.

00:17:00.330 --> 00:17:04.810
<v Sjors Provoost>Yeah, so it's a more private custodial wallet, but with the same drawbacks as a

00:17:04.810 --> 00:17:10.710
<v Sjors Provoost>custodial wallet in that as a user, you don't know if it has full reserve or

00:17:10.710 --> 00:17:15.710
<v Sjors Provoost>not. The same goes with a normal custodial wallet. But the advantage is because

00:17:15.710 --> 00:17:19.050
<v Sjors Provoost>you're not doing anything on-chain other than making your first deposit and

00:17:19.050 --> 00:17:22.490
<v Sjors Provoost>eventually taking coins out, you have very low transaction fees.

00:17:22.970 --> 00:17:23.150
<v Ruben Somsen>Yeah.

00:17:23.350 --> 00:17:27.270
<v Sjors Provoost>But there's also an obvious downside, which is that, well, you can't use those

00:17:27.270 --> 00:17:31.770
<v Sjors Provoost>tokens outside people who trust that particular federation. And the way this is

00:17:31.770 --> 00:17:35.410
<v Sjors Provoost>designed, there could be hundreds of different federations. Every family could

00:17:35.410 --> 00:17:37.850
<v Sjors Provoost>have their own federation or every country could.

00:17:38.470 --> 00:17:42.770
<v Aaron van Wirdum>Well, I think in that sense, the Bitcoin Beach wallet is a pretty good example. I

00:17:42.770 --> 00:17:47.210
<v Aaron van Wirdum>was at Bitcoin Beach for a while in El Salvador and I did use the Bitcoin Beach

00:17:47.210 --> 00:17:51.290
<v Aaron van Wirdum>wallet because it was just a bit easier. And I'm not putting my life savings

00:17:51.290 --> 00:17:54.930
<v Aaron van Wirdum>there because I know it's custodial, but it was definitely the fastest and

00:17:54.930 --> 00:17:59.890
<v Aaron van Wirdum>easiest way to just pay for your breakfast and walk around town and get a Coke.

00:17:59.890 --> 00:18:05.450
<v Sjors Provoost>And so in this new situation, you would again deposit your regular Bitcoin from

00:18:05.450 --> 00:18:10.060
<v Sjors Provoost>another wallet into the Bitcoin Beach system. But they would then give you these

00:18:10.060 --> 00:18:14.960
<v Sjors Provoost>Chaumian eCash tokens so that you can now pay people without them knowing who

00:18:14.960 --> 00:18:15.400
<v Sjors Provoost>you're paying.

00:18:15.720 --> 00:18:19.200
<v Aaron van Wirdum>Exactly, yeah. The biggest drawback was privacy. Whoever was controlling the

00:18:19.200 --> 00:18:22.540
<v Aaron van Wirdum>funds or managing the wallets could see exactly where I was having breakfast or

00:18:22.540 --> 00:18:24.360
<v Aaron van Wirdum>where I was buying my drinks.

00:18:24.560 --> 00:18:28.640
<v Sjors Provoost>And then the next step that is, I think, a pretty smart leap, although it has

00:18:28.640 --> 00:18:32.080
<v Sjors Provoost>actually not been completely developed. So we'll have to see if that leap is

00:18:32.080 --> 00:18:36.320
<v Sjors Provoost>vaporware or whether it's going to be real. That is that this federation will now

00:18:36.320 --> 00:18:39.560
<v Sjors Provoost>make arbitrary Lightning payments for you.

00:18:39.840 --> 00:18:39.920
<v Ruben Somsen>Yeah.

00:18:40.280 --> 00:18:46.040
<v Sjors Provoost>And that means that if you want to pay somebody on the Lightning network, yeah,

00:18:46.100 --> 00:18:49.540
<v Sjors Provoost>you can do that. You'll send your tokens. You'll essentially burn your tokens

00:18:49.540 --> 00:18:53.840
<v Sjors Provoost>back into the federation and they'll do the Lightning payment for you. And this

00:18:53.840 --> 00:18:58.860
<v Sjors Provoost>is nice because running a Lightning node by yourself is not super easy. So the

00:18:58.860 --> 00:19:03.780
<v Sjors Provoost>idea of having a joint lightning node with even just with 10 people makes sense.

00:19:03.780 --> 00:19:08.060
<v Sjors Provoost>And you can use these tokens as a way to sort of bridge between that.

00:19:08.060 --> 00:19:13.800
<v Aaron van Wirdum>Yeah, the point here is being, so if you own these tokens, so you could

00:19:13.800 --> 00:19:19.040
<v Aaron van Wirdum>withdraw, you could redeem the tokens for Bitcoin and then send the Bitcoin or

00:19:19.040 --> 00:19:23.570
<v Aaron van Wirdum>Lightning. But what you're saying is the trick here would be if you want to pay

00:19:23.570 --> 00:19:27.250
<v Aaron van Wirdum>someone else, you only have these tokens, then there's some sort of trick where

00:19:28.750 --> 00:19:33.090
<v Aaron van Wirdum>the redemption is sort of the same thing as a payment to the other person.

00:19:33.190 --> 00:19:37.330
<v Sjors Provoost>Yeah, I mean, redeeming money, like in the original eCash example, you would

00:19:37.330 --> 00:19:41.450
<v Sjors Provoost>redeem coins and then your bank would give you a balance. In this case, you would

00:19:41.450 --> 00:19:46.020
<v Sjors Provoost>redeem coins and then they make a Lightning payment to the destination. And you

00:19:46.020 --> 00:19:49.520
<v Sjors Provoost>can probably use various different schemes depending on how much you want to

00:19:49.520 --> 00:19:52.760
<v Sjors Provoost>trust the federation to actually do your Lightning, but you're already trusting

00:19:52.760 --> 00:19:56.600
<v Sjors Provoost>them to redeem your coins. So you might as well trust them to make a Lightning

00:19:56.600 --> 00:20:00.200
<v Sjors Provoost>payment for you. But this really scales well, right? Because you could also have

00:20:00.200 --> 00:20:03.840
<v Sjors Provoost>the federation do a [unclear] payment, but then you might as well just have your

00:20:03.840 --> 00:20:07.820
<v Sjors Provoost>own non-custodial wallet because for every payment to the outside world, there is

00:20:07.820 --> 00:20:11.600
<v Sjors Provoost>exactly one Bitcoin transaction. So there's no advantage to putting your coins

00:20:11.600 --> 00:20:15.370
<v Sjors Provoost>into a federation and then paying from the federation other than maybe some

00:20:15.370 --> 00:20:15.770
<v Sjors Provoost>privacy.

00:20:16.190 --> 00:20:16.250
<v Ruben Somsen>Yeah.

00:20:16.790 --> 00:20:20.730
<v Sjors Provoost>So Lightning does give that advantage of scale where one Lightning node, which

00:20:20.730 --> 00:20:25.370
<v Sjors Provoost>might have 10 channels or whatever it is, can handle the outgoing payments for a

00:20:25.370 --> 00:20:27.940
<v Sjors Provoost>large group of people. Sharing the overhead.

00:20:28.440 --> 00:20:34.200
<v Ruben Somsen>So there is one thing that I should clarify here because there is the theoretical

00:20:34.200 --> 00:20:39.880
<v Ruben Somsen>model where the federation controls a Lightning channel and then you can peg out

00:20:39.880 --> 00:20:44.020
<v Ruben Somsen>through that channel. But that actually in practice is very complicated because

00:20:44.020 --> 00:20:48.240
<v Ruben Somsen>now you would have to have a, you know, Lightning is a two of two multisig, but

00:20:48.240 --> 00:20:53.010
<v Ruben Somsen>now one of those two is federation. And that is actually very complicated in

00:20:53.010 --> 00:20:58.450
<v Ruben Somsen>practice for the federation to run the channel itself. So actually the

00:20:58.450 --> 00:21:03.790
<v Ruben Somsen>solution that Eric is working on now is one where

00:21:03.790 --> 00:21:08.310
<v Ruben Somsen>instead of having the federation itself control the channel,

00:21:08.490 --> 00:21:14.450
<v Ruben Somsen>he actually suggests we can basically create a token that

00:21:14.450 --> 00:21:18.390
<v Ruben Somsen>has some smart contracting features that are very similar to the Lightning

00:21:18.390 --> 00:21:22.980
<v Ruben Somsen>Network, how the Lightning Network works itself. So basically, you can open a

00:21:22.980 --> 00:21:28.300
<v Ruben Somsen>channel that only has the amount of value that you want to send out on top of the

00:21:28.300 --> 00:21:34.100
<v Ruben Somsen>federated eCash system. And then you make that one payment and

00:21:34.100 --> 00:21:38.300
<v Ruben Somsen>then your channel is basically empty, so your channel closes again. And that

00:21:38.300 --> 00:21:43.460
<v Ruben Somsen>allows basically anyone to sort of play the intermediary, where you could think

00:21:43.460 --> 00:21:47.600
<v Ruben Somsen>of it similar to maybe the Liquid network that we've discussed on, I don't know

00:21:47.600 --> 00:21:48.380
<v Ruben Somsen>which episode, maybe.

00:21:49.000 --> 00:21:50.760
<v Aaron van Wirdum>[unclear]

00:21:51.120 --> 00:21:55.820
<v Sjors Provoost>I don't think we have discussed the Liquid network. We've mentioned it, but we

00:21:55.820 --> 00:21:56.800
<v Sjors Provoost>haven't done a full episode.

00:21:56.940 --> 00:21:58.000
<v Ruben Somsen>Yeah, okay, maybe not a full episode.

00:22:00.240 --> 00:22:05.400
<v Ruben Somsen>The Liquid Network is, just for people that know it then, at least, is kind of a

00:22:05.400 --> 00:22:08.940
<v Ruben Somsen>separate blockchain that is also controlled by a federation. But anyone could

00:22:08.940 --> 00:22:13.680
<v Ruben Somsen>open a Lightning channel on top of Liquid and then connect that to the Bitcoin

00:22:13.680 --> 00:22:19.680
<v Ruben Somsen>Lightning Network and then send out of Liquid into the Bitcoin Lightning Network.

00:22:19.860 --> 00:22:23.680
<v Ruben Somsen>And this is kind of a similar thing where you do the same thing, except the

00:22:23.680 --> 00:22:27.960
<v Ruben Somsen>channel now kind of exists inside of the eCash system.

00:22:28.510 --> 00:22:31.730
<v Sjors Provoost>Yeah, but I guess the big picture way of putting this would be, say, well, you

00:22:31.730 --> 00:22:35.210
<v Sjors Provoost>could have some sort of hypothetical Lightning node that is run by the whole

00:22:35.210 --> 00:22:40.490
<v Sjors Provoost>federation. This is difficult. It'd be nice if one person can run a Lightning

00:22:40.490 --> 00:22:44.710
<v Sjors Provoost>node and then interact with the federation by accepting these tokens. And then,

00:22:44.710 --> 00:22:48.150
<v Sjors Provoost>you know, there's different ways to do that. And one would be to use smart

00:22:48.150 --> 00:22:48.690
<v Sjors Provoost>contracts.

00:22:48.910 --> 00:22:49.050
<v Ruben Somsen>Yeah.

00:22:49.790 --> 00:22:51.910
<v Sjors Provoost>But in the end, yeah, that's nice.

00:22:52.170 --> 00:22:52.270
<v Ruben Somsen>Yeah.

00:22:52.530 --> 00:22:58.460
<v Sjors Provoost>And maybe, you know, as a big picture— big picture thing, one of the

00:22:58.460 --> 00:23:03.540
<v Sjors Provoost>things with the original DigiCash-like systems or eCash systems is that every

00:23:03.540 --> 00:23:08.080
<v Sjors Provoost>merchant has to accept the specific little cash token in order for it to be

00:23:08.080 --> 00:23:13.320
<v Sjors Provoost>useful. So you need to win the network effect game. They almost won that because

00:23:13.320 --> 00:23:18.420
<v Sjors Provoost>they almost had a deal with Microsoft that would have put DigiCash on every PC

00:23:18.420 --> 00:23:24.390
<v Sjors Provoost>out there. So that's pretty cool. But in this case, with this new proposal,

00:23:24.470 --> 00:23:29.070
<v Sjors Provoost>you don't need that big of a network effect because as long as you can exit the

00:23:29.070 --> 00:23:32.630
<v Sjors Provoost>federation through Lightning, you can interact with anybody who takes Lightning,

00:23:32.630 --> 00:23:38.430
<v Sjors Provoost>which already has a much larger network effect than your little federation

00:23:38.430 --> 00:23:43.450
<v Sjors Provoost>has. So that means you can do these federations at a much smaller

00:23:43.450 --> 00:23:44.450
<v Sjors Provoost>scale.

00:23:44.710 --> 00:23:50.240
<v Ruben Somsen>Yeah, and maybe to bring back kind of a practical example, you could have a group

00:23:50.240 --> 00:23:54.260
<v Ruben Somsen>of people that, you know, trust each other pretty well and they create a

00:23:54.260 --> 00:23:57.760
<v Ruben Somsen>federation and, you know, maybe it's a local community and maybe like Bitcoin

00:23:57.760 --> 00:24:02.510
<v Ruben Somsen>Beach. And then really, as long as there's one person within that community who's

00:24:02.510 --> 00:24:07.490
<v Ruben Somsen>willing to run a Lightning node and trust both the federation and trust the

00:24:07.490 --> 00:24:11.890
<v Ruben Somsen>eCash, as well as that person being connected to the rest of the Lightning

00:24:11.890 --> 00:24:16.150
<v Ruben Somsen>network, now you can send out payments out of the Lightning network. And then you

00:24:16.150 --> 00:24:19.730
<v Ruben Somsen>can imagine that on the other side, maybe there's yet another eCash system with

00:24:19.730 --> 00:24:23.030
<v Ruben Somsen>another person who is doing the same thing. And now you can send from one

00:24:23.030 --> 00:24:28.120
<v Ruben Somsen>federation to another federation. And you sort of have this entirely… the system

00:24:28.120 --> 00:24:28.800
<v Ruben Somsen>that is sort of connected.

00:24:28.860 --> 00:24:30.480
<v Aaron van Wirdum>Ecosystem of federations, yeah.

00:24:32.140 --> 00:24:34.960
<v Aaron van Wirdum>Do we call this layer three? Is this layer three, Ruben?

00:24:35.100 --> 00:24:37.200
<v Ruben Somsen>It's a 2.7, I think.

00:24:40.760 --> 00:24:44.440
<v Sjors Provoost>And that would be nice if all custodial wallets actually just switched to a

00:24:44.440 --> 00:24:48.720
<v Sjors Provoost>system like this so that there'd be good privacy in custodial wallets.

00:24:49.040 --> 00:24:54.620
<v Sjors Provoost>Unfortunately, if they're based in most countries, being too private would

00:24:54.620 --> 00:24:59.740
<v Sjors Provoost>actually cause some regulatory issues for them, to put it mildly. So they may not

00:24:59.740 --> 00:25:04.200
<v Sjors Provoost>be incentivized to offer this type of privacy to their customers. But that's sort

00:25:04.200 --> 00:25:07.920
<v Sjors Provoost>of a regulatory battle that is difficult to win. I mean, there's a reason banks

00:25:07.920 --> 00:25:11.800
<v Sjors Provoost>don't use Chaumian eCash. I think it's because, not because they can't, it's not

00:25:11.800 --> 00:25:15.120
<v Sjors Provoost>because they don't have the developers, it's just because they can't offer

00:25:15.120 --> 00:25:18.660
<v Sjors Provoost>privacy to their customers. They don't want to, for regulatory reasons, they

00:25:18.660 --> 00:25:24.090
<v Sjors Provoost>don't want to for selling user data reasons. So it really probably boils down to

00:25:24.090 --> 00:25:27.990
<v Sjors Provoost>people deciding themselves to set up these federations between friends or other

00:25:27.990 --> 00:25:28.670
<v Sjors Provoost>trusted groups.

00:25:28.970 --> 00:25:34.270
<v Ruben Somsen>Yeah. And that is, I think, sort of the limitation of the technology, right?

00:25:34.370 --> 00:25:39.630
<v Ruben Somsen>Where you are custodial if you run a federation like that. So you can't really

00:25:39.630 --> 00:25:42.250
<v Ruben Somsen>grow too big. If you grow too big, it's very likely that you're going to get

00:25:42.250 --> 00:25:46.310
<v Ruben Somsen>regulatory scrutiny on you. So that makes it difficult unless you maybe have a

00:25:46.310 --> 00:25:49.140
<v Ruben Somsen>multi-country federation, but those are kind of difficult too.

00:25:49.380 --> 00:25:52.920
<v Sjors Provoost>And you also run into trust issues, right? Because with three friends, you might

00:25:52.920 --> 00:25:58.670
<v Sjors Provoost>still trust that the system is solvent, but with some random

00:25:58.670 --> 00:26:02.190
<v Sjors Provoost>people running, you might not trust that.

00:26:02.230 --> 00:26:06.410
<v Aaron van Wirdum>Let's zoom into that for a second, because this is one of the main drawbacks, is

00:26:06.410 --> 00:26:11.990
<v Aaron van Wirdum>that you do have to trust the Mint, the Federation in this case. But

00:26:11.990 --> 00:26:17.510
<v Aaron van Wirdum>is that something that could potentially be solved with provable reserves or

00:26:17.510 --> 00:26:18.910
<v Aaron van Wirdum>that kind of…

00:26:19.370 --> 00:26:24.070
<v Ruben Somsen>So, yeah, so unfortunately, it's sort of the trade-off of getting this really

00:26:24.070 --> 00:26:28.490
<v Ruben Somsen>good privacy. The privacy is basically so good that you can't audit the supply.

00:26:28.690 --> 00:26:30.850
<v Ruben Somsen>That's basically how you can see it.

00:26:30.950 --> 00:26:34.150
<v Sjors Provoost>Right, because in theory, you could audit the supply by, for example, when you

00:26:34.150 --> 00:26:38.790
<v Sjors Provoost>mint a coin, you would mention which UTXO it's minted from. And then if enough

00:26:38.790 --> 00:26:43.150
<v Sjors Provoost>people say, hey, I got a coin from this UTXO, and I got a coin from this UTXO,

00:26:43.210 --> 00:26:46.450
<v Sjors Provoost>and if that adds up to more than the value of the UTXO, well, then you kind of

00:26:46.450 --> 00:26:52.330
<v Sjors Provoost>caught them lying. Essentially. But you don't want to

00:26:52.330 --> 00:26:56.210
<v Sjors Provoost>actually be able to link the UTXO to these specific tokens because that defeats

00:26:56.210 --> 00:26:57.690
<v Sjors Provoost>the whole privacy point of it.

00:26:57.730 --> 00:27:01.290
<v Ruben Somsen>Yeah, it would sort of become basically like a blockchain, right? Where you have

00:27:01.290 --> 00:27:05.070
<v Ruben Somsen>a history of transactions and sure, there are pseudonyms and maybe you can have

00:27:05.070 --> 00:27:07.490
<v Ruben Somsen>something like confidential transactions to make it more anonymous, but there are

00:27:07.490 --> 00:27:13.310
<v Ruben Somsen>still links. So you don't get that perfect privacy. But that also, so that means

00:27:13.310 --> 00:27:17.330
<v Ruben Somsen>also that you, because you can't audit the supply, you know, one of the things

00:27:17.330 --> 00:27:22.770
<v Ruben Somsen>that I think is also a limitation here is that if the federation wants, they can

00:27:22.770 --> 00:27:28.530
<v Ruben Somsen>actually secretly cheat where instead of them just taking all the on-chain

00:27:28.530 --> 00:27:32.430
<v Ruben Somsen>Bitcoin and just moving it elsewhere, which would be visible, right? Because you

00:27:32.430 --> 00:27:35.550
<v Ruben Somsen>would see the Bitcoins move on the Bitcoin blockchain and you'd be like, hey,

00:27:35.650 --> 00:27:41.110
<v Ruben Somsen>that's a lot of Bitcoins are moving. They could also inflate the number of tokens

00:27:41.110 --> 00:27:46.930
<v Ruben Somsen>and that would also be invisible. And then basically the e-cash

00:27:46.930 --> 00:27:49.190
<v Ruben Somsen>federation would be running a fractional reserve.

00:27:50.340 --> 00:27:50.780
<v Sjors Provoost>Yeah.

00:27:52.980 --> 00:27:57.620
<v Aaron van Wirdum>One of the things you mentioned, or no, one of the things in the show notes,

00:27:57.740 --> 00:28:01.600
<v Aaron van Wirdum>which I'm not sure if we still need to get into our specific use cases or any

00:28:01.600 --> 00:28:05.480
<v Aaron van Wirdum>specific use cases of this that we need to mention or have we gone over that?

00:28:05.620 --> 00:28:09.460
<v Ruben Somsen>I feel like we've covered it, right? And so maybe one thing I can add here is

00:28:09.460 --> 00:28:15.220
<v Ruben Somsen>that, you know, I'm seeing like when it clicked for me, why I think eCash is

00:28:15.220 --> 00:28:19.600
<v Ruben Somsen>useful and necessary in Bitcoin today is actually because we've been seeing a lot

00:28:19.600 --> 00:28:23.950
<v Ruben Somsen>of these custodial Lightning wallets pop up. And they're pretty popular. They're

00:28:23.950 --> 00:28:29.810
<v Ruben Somsen>pretty easy to use. So I think it's the perfect niche to like just, as of what is

00:28:29.810 --> 00:28:34.630
<v Ruben Somsen>happening right now, I think, yeah, that's just straight up an improvement. Even

00:28:34.630 --> 00:28:38.390
<v Ruben Somsen>if the federation is a federation of one, I still think it's an improvement

00:28:38.390 --> 00:28:42.750
<v Ruben Somsen>because at least everybody who trusts that single custodian can now anonymously

00:28:42.750 --> 00:28:43.890
<v Ruben Somsen>transfer between them.

00:28:44.150 --> 00:28:47.050
<v Sjors Provoost>Exactly. Because we've been talking about federations all the time, but it could

00:28:47.050 --> 00:28:48.270
<v Sjors Provoost>be an N-of-one federation.

00:28:48.490 --> 00:28:48.630
<v Ruben Somsen>Yeah.

00:28:49.130 --> 00:28:50.550
<v Aaron van Wirdum>Right. Okay.

00:28:52.020 --> 00:28:58.020
<v Aaron van Wirdum>Sjors, you wanted to break this down now. You wanted to attack

00:28:58.020 --> 00:28:59.800
<v Aaron van Wirdum>the privacy of this system. Is that right?

00:29:01.510 --> 00:29:06.830
<v Sjors Provoost>Well, yeah, a little bit. So we mentioned something about denominations, so that

00:29:06.830 --> 00:29:11.010
<v Sjors Provoost>we think that the original system had only one denomination. Maybe, was it cent?

00:29:11.170 --> 00:29:11.770
<v Sjors Provoost>Maybe, I don't know.

00:29:13.460 --> 00:29:17.460
<v Sjors Provoost>But there have been proposals, and the new system that's proposed by Blockstream

00:29:17.460 --> 00:29:22.910
<v Sjors Provoost>and folks and Eric has multiple notes, just like your normal cash. You might have

00:29:22.910 --> 00:29:28.350
<v Sjors Provoost>a $1 note and a $10 note. And so you can provide change by issuing multiple

00:29:28.350 --> 00:29:33.150
<v Sjors Provoost>notes. But in Bitcoin, we have precise amounts. So you might wonder why you

00:29:33.150 --> 00:29:37.050
<v Sjors Provoost>wouldn't just issue notes with precise amounts. And there's, I would say, two

00:29:37.050 --> 00:29:42.350
<v Sjors Provoost>objections to that. One is that it becomes cryptographically more difficult to do

00:29:42.350 --> 00:29:46.750
<v Sjors Provoost>because the bank is blindly signing. And if you want the bank to also not know

00:29:46.750 --> 00:29:52.150
<v Sjors Provoost>the amount, well, that's a bit of a problem. So, yeah, and there are some

00:29:52.150 --> 00:29:53.290
<v Sjors Provoost>solutions to that, right?

00:29:53.490 --> 00:29:55.390
<v Ruben Somsen>Yeah, Brands credentials is one of them.

00:29:55.670 --> 00:29:59.190
<v Aaron van Wirdum>The problem with the amounts, and I think it was mentioned, but just to spell

00:29:59.190 --> 00:30:04.930
<v Aaron van Wirdum>this out, is if I issue exactly 1.023,

00:30:05.110 --> 00:30:10.120
<v Aaron van Wirdum>blah, blah, blah. And that exact amount is withdrawn by Ruben later, then I can

00:30:10.120 --> 00:30:13.140
<v Aaron van Wirdum>obviously link the amounts and I still know who paid who, even though the blind

00:30:13.140 --> 00:30:13.940
<v Aaron van Wirdum>signature was used.

00:30:14.200 --> 00:30:17.160
<v Sjors Provoost>Yeah, well, that was the second objection I wanted to bring up. So it's more

00:30:17.160 --> 00:30:20.280
<v Sjors Provoost>difficult to issue these things in the first place because of the blind signature

00:30:20.280 --> 00:30:25.500
<v Sjors Provoost>ritual. And it completely destroys privacy because, yeah, you're sending very

00:30:25.500 --> 00:30:30.540
<v Sjors Provoost>recognizable amounts across the wire. So one of the, in general with these eCash

00:30:30.540 --> 00:30:36.300
<v Sjors Provoost>systems, you can start, a bank could try to correlate uh, payments to people

00:30:36.300 --> 00:30:40.240
<v Sjors Provoost>by carefully watching how much, you know, because every time you receive it, you

00:30:40.240 --> 00:30:44.720
<v Sjors Provoost>immediately have to verify it So if money changes hands very frequently, you

00:30:44.720 --> 00:30:49.540
<v Sjors Provoost>might be able to infer where the money is moving, though in principle, you don't,

00:30:49.540 --> 00:30:55.280
<v Sjors Provoost>you know, in, at first glance, you know nothing because a bank issues coins, so

00:30:55.280 --> 00:30:59.240
<v Sjors Provoost>they know how much coins they issued. So Aaron, in this case the bank, you know

00:30:59.240 --> 00:31:05.000
<v Sjors Provoost>how much you issued to me, say $20, but you have no idea if and when I spent them

00:31:05.000 --> 00:31:09.820
<v Sjors Provoost>because I don't tell you. And Ruben receives these notes. Now, if the three of us

00:31:09.820 --> 00:31:14.340
<v Sjors Provoost>are the only ones on the network, then the very fact that Ruben redeems a note,

00:31:14.520 --> 00:31:17.980
<v Sjors Provoost>even though he never bought one, means that he got it from me. And then you know

00:31:17.980 --> 00:31:23.540
<v Sjors Provoost>that I have 19 and he has one. And this type of thing, if the network is bigger

00:31:23.540 --> 00:31:27.770
<v Sjors Provoost>and there's multiple customers, it's… It's much more difficult. It becomes noise.

00:31:28.030 --> 00:31:31.770
<v Sjors Provoost>But if you're smart enough with data, you might still be able to infer things.

00:31:32.350 --> 00:31:36.450
<v Sjors Provoost>Just like the chain analysis companies out there can monitor the blockchain. And

00:31:36.450 --> 00:31:39.770
<v Sjors Provoost>even though they don't know for sure which part is changing, which part is not,

00:31:40.200 --> 00:31:42.020
<v Sjors Provoost>they can somewhat infer things.

00:31:42.200 --> 00:31:46.160
<v Ruben Somsen>Yeah, just to add a small wrinkle, like even in this case where there's three

00:31:46.160 --> 00:31:51.580
<v Ruben Somsen>people and you have 20 for tokens, you sent one to me, even then you could like

00:31:51.580 --> 00:31:56.630
<v Ruben Somsen>try to increase the anonymity by just redeeming your own token. Right. So even in

00:31:56.630 --> 00:32:00.150
<v Ruben Somsen>that scenario, maybe there could still be some privacy. But yeah.

00:32:00.490 --> 00:32:03.970
<v Sjors Provoost>But I mean, the thing is, you know, when Chaum originally proposed these things.

00:32:04.270 --> 00:32:04.390
<v Ruben Somsen>Yeah.

00:32:04.530 --> 00:32:09.470
<v Sjors Provoost>Things were quite different. This rat race or rat race, arms race, I guess,

00:32:09.570 --> 00:32:15.030
<v Sjors Provoost>between the privacy people and the surveillance people was not started yet. So

00:32:15.030 --> 00:32:18.270
<v Sjors Provoost>they may have been slightly naive about it. Just like people thought Bitcoin was

00:32:18.270 --> 00:32:20.070
<v Sjors Provoost>going to be much more private than it turned out to be.

00:32:20.370 --> 00:32:20.470
<v Ruben Somsen>Yeah.

00:32:21.870 --> 00:32:25.210
<v Sjors Provoost>And what that rat race would look like, yeah, I could imagine that wallets would

00:32:25.210 --> 00:32:30.090
<v Sjors Provoost>start deliberately redeeming their own coins or waiting a little bit longer. And

00:32:30.090 --> 00:32:33.350
<v Sjors Provoost>you'd have to think about what the denomination should be if you have multiple

00:32:33.350 --> 00:32:39.190
<v Sjors Provoost>denominations. Should you have too many $100 coins? Maybe not, maybe yes. Yeah,

00:32:39.190 --> 00:32:40.770
<v Sjors Provoost>um, that sort of stuff.

00:32:40.770 --> 00:32:45.250
<v Ruben Somsen>So I think the, uh, the strongest point that, that you made, Sjors, earlier when

00:32:45.250 --> 00:32:50.230
<v Ruben Somsen>we were discussing this before the show, uh was that you need a Tor connection,

00:32:50.230 --> 00:32:54.690
<v Ruben Somsen>basically, where you, every time you redeem a token, you don't want to connect

00:32:54.690 --> 00:32:59.830
<v Ruben Somsen>with the same IP to the, to the mints, because if you do, then you are leaking a

00:32:59.830 --> 00:33:03.050
<v Ruben Somsen>lot of information. Whereas if every time you connect to the mints, you, you

00:33:03.050 --> 00:33:07.280
<v Ruben Somsen>present yourself as a different IP, as a different person. That really helps a

00:33:07.280 --> 00:33:07.960
<v Ruben Somsen>lot, I think.

00:33:08.080 --> 00:33:12.060
<v Sjors Provoost>Though I would also say that if custodial wallets allowed you to have totally

00:33:12.060 --> 00:33:17.660
<v Sjors Provoost>anonymous accounts with Tor, then we might not even need these type of solutions.

00:33:18.520 --> 00:33:23.820
<v Sjors Provoost>So there is the problem of most custodial services not liking the idea of having

00:33:23.820 --> 00:33:28.660
<v Sjors Provoost>totally anonymous customers depositing random money. But this, again, might be a

00:33:28.660 --> 00:33:32.460
<v Sjors Provoost>matter of scale. If it's just you and your family, it might be okay if you're

00:33:32.460 --> 00:33:36.360
<v Sjors Provoost>using Tor. Though then again, maybe you don't need to use Tor if it's just you

00:33:36.360 --> 00:33:36.820
<v Sjors Provoost>and your family.

00:33:36.900 --> 00:33:37.420
<v Ruben Somsen>That's funny too.

00:33:37.540 --> 00:33:43.380
<v Sjors Provoost>So these are interesting questions. And of course, HTTPS was invented since the

00:33:43.380 --> 00:33:44.100
<v Sjors Provoost>Chaum thing too.

00:33:45.620 --> 00:33:48.920
<v Sjors Provoost>At the time, I think if you were doing this with your bank, your bank could

00:33:48.920 --> 00:33:51.740
<v Sjors Provoost>literally see what you were, or your internet provider could literally see what

00:33:51.740 --> 00:33:56.530
<v Sjors Provoost>you were doing because internet traffic was not encrypted, whereas now it is. So

00:33:56.530 --> 00:33:57.730
<v Sjors Provoost>this already helps a little bit.

00:33:58.010 --> 00:33:58.430
<v Ruben Somsen>Yeah.

00:33:58.630 --> 00:34:01.990
<v Sjors Provoost>Okay. I think we've covered pretty much what we wanted to do, right?

00:34:02.270 --> 00:34:02.430
<v Ruben Somsen>Yeah.

00:34:02.870 --> 00:34:08.070
<v Aaron van Wirdum>I mean, the other thing that's in my notes here is ideal properties of digital

00:34:08.070 --> 00:34:11.130
<v Aaron van Wirdum>cash. Did you want to get into that or not?

00:34:11.330 --> 00:34:14.570
<v Sjors Provoost>I could very briefly mention this. So there's a paper that Ruben found. I think

00:34:14.570 --> 00:34:19.830
<v Sjors Provoost>it's a lecture note from probably 2009 from a UK university somewhere where

00:34:19.830 --> 00:34:25.760
<v Sjors Provoost>somebody listed... sort of the top seven wishlist things in a digital

00:34:25.760 --> 00:34:30.000
<v Sjors Provoost>cash system. So although this is probably from 2009, it looks like they were not

00:34:30.000 --> 00:34:30.880
<v Sjors Provoost>aware of Bitcoin yet.

00:34:31.060 --> 00:34:34.100
<v Aaron van Wirdum>And is this all focused on privacy or not necessarily?

00:34:34.740 --> 00:34:40.540
<v Sjors Provoost>Well, so digital cash, he would define it as being able to make payments that are

00:34:40.540 --> 00:34:41.840
<v Sjors Provoost>indeed private.

00:34:42.080 --> 00:34:42.520
<v Aaron van Wirdum>Right.

00:34:42.740 --> 00:34:47.120
<v Sjors Provoost>So whereas PayPal is not digital cash, it's more like a digital bank account

00:34:47.120 --> 00:34:49.600
<v Sjors Provoost>because the payments are completely traceable.

00:34:49.900 --> 00:34:50.040
<v Ruben Somsen>Yeah.

00:34:50.260 --> 00:34:54.580
<v Sjors Provoost>And so... He would say, ideally such a system, and he says there is no such system.

00:34:54.580 --> 00:34:59.480
<v Aaron van Wirdum>I think that's worth pointing out because throughout the whole block size debate

00:34:59.480 --> 00:35:04.020
<v Aaron van Wirdum>and all of that, still people think that digital cash refers to the cost of

00:35:04.020 --> 00:35:07.880
<v Aaron van Wirdum>transaction, but that was never, at least not the original meaning of digital

00:35:07.880 --> 00:35:09.360
<v Aaron van Wirdum>cash. It was always about privacy.

00:35:09.500 --> 00:35:13.360
<v Sjors Provoost>It depends on what you want, right? I mean, In this case, digital cash has the

00:35:13.360 --> 00:35:14.340
<v Sjors Provoost>emphasis on cash.

00:35:15.820 --> 00:35:16.980
<v Sjors Provoost>And not cash...

00:35:16.980 --> 00:35:18.600
<v Aaron van Wirdum>Cash and privacy, Sjors, right?

00:35:18.680 --> 00:35:23.020
<v Sjors Provoost>Yeah. Well, yeah, because the cash is private. Others would say...

00:35:23.020 --> 00:35:23.940
<v Aaron van Wirdum>That's my point, we agree.

00:35:24.580 --> 00:35:27.920
<v Sjors Provoost>Exactly, and others would say, no, it's about being cheap, but being cheap can be

00:35:27.920 --> 00:35:28.720
<v Sjors Provoost>done with the database.

00:35:28.960 --> 00:35:32.140
<v Aaron van Wirdum>Anyways, what we're referring to, what we're talking about here is privacy.

00:35:32.500 --> 00:35:38.380
<v Sjors Provoost>Yeah, so privacy would be secure, so you're able to not fake these coins. Well,

00:35:38.580 --> 00:35:40.800
<v Sjors Provoost>that's pretty much solved with digital signatures in general.

00:35:42.130 --> 00:35:47.990
<v Sjors Provoost>It should be anonymous, which kind of means like two people, like I pay Ruben and

00:35:47.990 --> 00:35:51.410
<v Sjors Provoost>Ruben doesn't know who I am. I don't know who Ruben is. And the bank doesn't know

00:35:51.410 --> 00:35:55.570
<v Sjors Provoost>who either of us is. That would be ideal. Now, the system we discussed with the

00:35:55.570 --> 00:35:59.250
<v Sjors Provoost>original cash system, that would not be the case. The bank would know who I am.

00:35:59.430 --> 00:36:02.730
<v Sjors Provoost>The bank would know who Ruben is, but they kind of don't know that we

00:36:02.730 --> 00:36:04.190
<v Sjors Provoost>transferred, that we transacted.

00:36:04.330 --> 00:36:08.620
<v Ruben Somsen>Yeah, I mean, not necessarily, right? Like it depends, I guess, on that. If you

00:36:08.620 --> 00:36:11.760
<v Ruben Somsen>assume a trust relationship between the bank and every individual person, then

00:36:11.760 --> 00:36:16.320
<v Ruben Somsen>yes. But you could also, maybe if the bank is crazy enough to allow anonymous

00:36:16.320 --> 00:36:18.420
<v Ruben Somsen>people, then that wouldn't even be necessary.

00:36:18.720 --> 00:36:20.760
<v Sjors Provoost>Something like Tether could exist.

00:36:22.520 --> 00:36:28.000
<v Sjors Provoost>It's portable. So that means you can use it everywhere. I guess

00:36:28.000 --> 00:36:32.080
<v Sjors Provoost>portable is something we take for granted now that we all have mobile phones. So

00:36:32.080 --> 00:36:34.820
<v Sjors Provoost>maybe we don't really have to go into this. It's two-way.

00:36:35.730 --> 00:36:40.410
<v Ruben Somsen>Well, I mean, one thing I find interesting about the portable one is, so it's

00:36:40.410 --> 00:36:44.130
<v Ruben Somsen>portable in the sense, I think that gold would be very heavy to transfer. It

00:36:44.130 --> 00:36:49.470
<v Ruben Somsen>would be very difficult to transfer over long distances. And, you know, having a

00:36:49.470 --> 00:36:54.030
<v Ruben Somsen>digital cash is like this thing that you can easily transfer. But, you know, one

00:36:54.030 --> 00:36:58.270
<v Ruben Somsen>thing that's sort of funny is that I do think for the Bitcoin blockchain, at

00:36:58.270 --> 00:37:01.990
<v Ruben Somsen>least, the block size is sort of constrained on portability, you could say. It's

00:37:01.990 --> 00:37:07.530
<v Ruben Somsen>not literally portability, but there's a limit to how many people can transfer,

00:37:07.530 --> 00:37:12.710
<v Ruben Somsen>uh, their bitcoins, um, and, and obviously if you pay enough you get to transfer

00:37:12.710 --> 00:37:15.890
<v Ruben Somsen>your bitcoins, but that is, I think, sort of a portability limit.

00:37:16.210 --> 00:37:22.150
<v Sjors Provoost>Well, no system is perfect. So the other thing is they call it two-way, and

00:37:22.150 --> 00:37:25.430
<v Sjors Provoost>then the second term is peer-to-peer, and that makes it more clear. So with Visa

00:37:25.430 --> 00:37:29.390
<v Sjors Provoost>and MasterCard, you have merchants who sign up with the network as a merchant,

00:37:29.390 --> 00:37:33.630
<v Sjors Provoost>and you have customers who sign up as a customer. So two customers cannot send

00:37:33.630 --> 00:37:38.700
<v Sjors Provoost>money between their two credit cards. Now, there have actually been some prepaid

00:37:38.700 --> 00:37:42.320
<v Sjors Provoost>debit card systems out there in more recent years with fintech companies that do

00:37:42.320 --> 00:37:46.480
<v Sjors Provoost>let you essentially use credit cards as a peer-to-peer system. So there were

00:37:46.480 --> 00:37:51.120
<v Sjors Provoost>workarounds for it. But this was considered a big problem. And, you know, the

00:37:51.120 --> 00:37:55.800
<v Sjors Provoost>eCash system solved that because anybody can send the cash to anybody else. And

00:37:55.800 --> 00:37:59.060
<v Sjors Provoost>so does Bitcoin, of course. Everybody can send Bitcoin to everybody else. It

00:37:59.060 --> 00:38:04.920
<v Sjors Provoost>should be offline capable. Now, offline… There seems to be more defined,

00:38:05.160 --> 00:38:09.840
<v Sjors Provoost>not so much as not having internet, but more about not having access to the third

00:38:09.840 --> 00:38:14.800
<v Sjors Provoost>party. So they say, well, you can't make a payment if your e-cash bank is offline

00:38:14.800 --> 00:38:19.520
<v Sjors Provoost>even for a second because you can't verify it. And I guess what at least Bitcoin

00:38:19.520 --> 00:38:24.280
<v Sjors Provoost>lets you do is… not— both parties don't have to be online at exactly the same

00:38:24.280 --> 00:38:28.960
<v Sjors Provoost>time. And the blockchain has to respond at some time, at some point, but it

00:38:28.960 --> 00:38:32.340
<v Sjors Provoost>doesn't immediately have to respond because you have to wait six confirmations

00:38:32.340 --> 00:38:36.280
<v Sjors Provoost>anyway. So it at least removes the requirement of being online simultaneously.

00:38:36.720 --> 00:38:42.640
<v Sjors Provoost>Whereas, you know, a lot of pin systems or terminals in shops, they really

00:38:42.640 --> 00:38:47.560
<v Sjors Provoost>have to be on and connected to the bank and every other central party involved in

00:38:47.560 --> 00:38:49.180
<v Sjors Provoost>that whole process or the whole thing doesn't work.

00:38:49.400 --> 00:38:54.240
<v Ruben Somsen>Yeah, I will add to that, that at least for eCash, there have been attempts to

00:38:54.240 --> 00:38:58.740
<v Ruben Somsen>make it literally offline where you can just go to a merchant. And I think it

00:38:58.740 --> 00:39:01.720
<v Ruben Somsen>also makes sense at the time because, you know, internet was less widespread than

00:39:01.720 --> 00:39:04.140
<v Ruben Somsen>it is today, to literally…

00:39:04.140 --> 00:39:07.940
<v Aaron van Wirdum>Your computer was still making a lot of noise in order to get online.

00:39:08.440 --> 00:39:09.260
<v Ruben Somsen>Exactly, yeah.

00:39:09.280 --> 00:39:10.620
<v Aaron van Wirdum>We're talking about early 80s.

00:39:10.760 --> 00:39:15.540
<v Ruben Somsen>Yeah, terrible 28k modem that I had was lovely to listen to.

00:39:15.680 --> 00:39:16.820
<v Sjors Provoost>I think we're talking mid-90s.

00:39:17.120 --> 00:39:17.600
<v Ruben Somsen>Yes.

00:39:19.100 --> 00:39:25.080
<v Ruben Somsen>But yeah, so the idea of actually being able to go to a shop,

00:39:25.240 --> 00:39:30.520
<v Ruben Somsen>not be online, give a token and then not have to worry about, like, basically

00:39:30.520 --> 00:39:34.140
<v Ruben Somsen>double spending. I think this was solved in kind of a weird way where the token

00:39:34.140 --> 00:39:37.660
<v Ruben Somsen>sort of had my name on it, but only if I double spent the token would, would the,

00:39:37.660 --> 00:39:40.460
<v Ruben Somsen>my name be revealed, therefore I'm disincentivized from…

00:39:40.460 --> 00:39:44.480
<v Sjors Provoost>Yeah, There's two ways to deal with it, right? One is to punish afterwards, yeah,

00:39:44.480 --> 00:39:49.940
<v Sjors Provoost>and the other is to make it physically sort of impossible with trusted hardware,

00:39:49.940 --> 00:39:53.500
<v Sjors Provoost>except, you know, trusted hardware is a can of worms. Yeah, but that's of course

00:39:53.500 --> 00:39:57.370
<v Sjors Provoost>in, in Bitcoin we have the OPENDIME yeah, where you can technically give some

00:39:57.370 --> 00:40:00.430
<v Sjors Provoost>money offline, although not really because you can't check the balance without

00:40:00.430 --> 00:40:06.410
<v Sjors Provoost>being online anyway. So it's not perfect. And then number

00:40:06.410 --> 00:40:11.630
<v Sjors Provoost>six was wide acceptability. So we kind of talked about that. Bitcoin still has,

00:40:11.730 --> 00:40:15.450
<v Sjors Provoost>of course, this problem of getting a bigger network, but it is at least globally

00:40:15.450 --> 00:40:16.450
<v Sjors Provoost>known and recognized.

00:40:18.370 --> 00:40:23.030
<v Ruben Somsen>I think it kind of goes hand to hand with number seven, which I think was user

00:40:23.030 --> 00:40:28.870
<v Ruben Somsen>friendliness. And I think the more user-friendly it is, the more widespread

00:40:28.870 --> 00:40:31.010
<v Ruben Somsen>it will be. I think those two kind of go together.

00:40:31.230 --> 00:40:36.270
<v Sjors Provoost>But I think an interesting aspect of those two, I guess, is that you can have

00:40:36.270 --> 00:40:39.490
<v Sjors Provoost>small federations, as we discussed. You can have small federations and still

00:40:39.490 --> 00:40:43.850
<v Sjors Provoost>interact with everybody in the world that speaks Lightning. So that's a nice way

00:40:43.850 --> 00:40:49.670
<v Sjors Provoost>to avoid this phenomena where Visa and MasterCard, if you want to compete with

00:40:49.670 --> 00:40:53.470
<v Sjors Provoost>them, you have a big problem because you need to convince every merchant out there.

00:40:54.860 --> 00:40:55.220
<v Ruben Somsen>Yeah.

00:40:55.380 --> 00:40:58.520
<v Sjors Provoost>And if you want to compete with Bitcoin, you also have a big problem because now

00:40:58.520 --> 00:40:59.640
<v Sjors Provoost>you have to compete with this coin.

00:40:59.940 --> 00:41:02.740
<v Ruben Somsen>Yeah. And that's really thanks to the Lightning network. And it's really nice,

00:41:02.860 --> 00:41:06.540
<v Ruben Somsen>like a nice feature of the Lightning network that it's, it's sort of, it works on

00:41:06.540 --> 00:41:11.560
<v Ruben Somsen>every chain or in this case, not really a chain, but any, any kind of system that

00:41:11.560 --> 00:41:14.480
<v Ruben Somsen>has some smart contracting, you can kind of put the Lightning network on there

00:41:14.480 --> 00:41:18.920
<v Ruben Somsen>and you can have it be a glue that connects everything, everything together.

00:41:19.040 --> 00:41:19.560
<v Ruben Somsen>That's really nice.

00:41:20.140 --> 00:41:24.740
<v Sjors Provoost>Yeah, maybe, I mean, I think the Bitcoin itself already gets you there. Yeah,

00:41:24.740 --> 00:41:28.500
<v Sjors Provoost>but, and I guess this federation system, you could do it without cryptocurrency

00:41:28.500 --> 00:41:30.340
<v Sjors Provoost>too, right? So yeah.

00:41:30.340 --> 00:41:31.480
<v Ruben Somsen>It's all, it's all possible.

00:41:31.480 --> 00:41:34.780
<v Aaron van Wirdum>Yeah, so that was a pretty long digression, I think.

00:41:34.780 --> 00:41:35.460
<v Ruben Somsen>Yeah.

00:41:35.460 --> 00:41:40.950
<v Aaron van Wirdum>But interesting, and I was wrong about the privacy part. So this was about all of

00:41:40.950 --> 00:41:45.980
<v Aaron van Wirdum>the privacy, uh, digital cash features, like you said, apparently just how to

00:41:45.980 --> 00:41:47.680
<v Aaron van Wirdum>reproduce cash digitally.

00:41:48.270 --> 00:41:53.770
<v Sjors Provoost>Yeah, that's a challenge. And I would say Bitcoin solves it better than eCash

00:41:53.770 --> 00:41:58.870
<v Sjors Provoost>did, but the combination might be even better. So that's pretty cool.

00:41:59.010 --> 00:42:03.710
<v Ruben Somsen>Yeah, I still think there are nice use cases for all different types of layer two

00:42:03.710 --> 00:42:04.470
<v Ruben Somsen>solutions, basically.

00:42:05.360 --> 00:42:05.900
<v Sjors Provoost>All right.

00:42:06.020 --> 00:42:08.300
<v Aaron van Wirdum>All right. I think that's it. That ties it together for me.

00:42:08.520 --> 00:42:13.460
<v Ruben Somsen>Yeah, so I think just one thing to clarify, at least for those who are super

00:42:13.460 --> 00:42:17.940
<v Ruben Somsen>interested in the tiny little details, I think. So there is a version of eCash

00:42:17.940 --> 00:42:23.860
<v Ruben Somsen>that's called Brands credentials and other variants as well, I think. So those do

00:42:23.860 --> 00:42:29.580
<v Ruben Somsen>allow variable amounts without this problem of every amount being its own

00:42:29.580 --> 00:42:33.240
<v Ruben Somsen>anonymity set. But that, unfortunately, doesn't really work, or at least not

00:42:33.240 --> 00:42:39.000
<v Ruben Somsen>easily. It's not easy to make it work in a federation setting. So that's why it's

00:42:39.000 --> 00:42:42.940
<v Ruben Somsen>not being used. Maybe in the future, we'll think of the proper cryptography to

00:42:42.940 --> 00:42:47.100
<v Ruben Somsen>allow that to be used. But as of right now, that seems a little complicated.

00:42:47.640 --> 00:42:51.260
<v Sjors Provoost>All right. Well, then, in that case, thank you for listening to Bitcoin

00:42:51.260 --> 00:42:52.140
<v Sjors Provoost>Explained.

00:42:52.360 --> 00:42:52.940
<v Aaron van Wirdum>There you go.

