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

00:00:10.700 --> 00:00:16.120
<v Aaron van Wirdum>This is Bitcoin Explained, the podcast with the most boring name in Bitcoin. Hey, Sjors.

00:00:16.560 --> 00:00:17.040
<v Sjors Provoost>What's up?

00:00:17.500 --> 00:00:18.540
<v Aaron van Wirdum>Where are you? In Utrecht?

00:00:18.920 --> 00:00:19.580
<v Sjors Provoost>That's right.

00:00:19.960 --> 00:00:23.960
<v Aaron van Wirdum>All right. I'm still in San Salvador, El Salvador. This is my last week here.

00:00:24.280 --> 00:00:26.500
<v Sjors Provoost>Oh, you're coming back? Or are you going somewhere else?

00:00:26.620 --> 00:00:31.340
<v Aaron van Wirdum>It's going to be a little bit of a detour, but I'm basically heading back to the

00:00:31.340 --> 00:00:34.920
<v Aaron van Wirdum>Netherlands. Yeah, through Miami, Nashville, then the Netherlands.

00:00:35.480 --> 00:00:37.700
<v Sjors Provoost>Sounds fun. Fair warning, it's raining here.

00:00:38.180 --> 00:00:43.220
<v Aaron van Wirdum>Yeah, not looking forward to that. So in my last week here, I think we're going

00:00:43.220 --> 00:00:48.200
<v Aaron van Wirdum>to do another on-topic episode. We're going to discuss the Chivo wallet.

00:00:48.580 --> 00:00:50.360
<v Sjors Provoost>Yes. Tell me about it.

00:00:50.700 --> 00:00:54.580
<v Aaron van Wirdum>Yes, this episode will be a little bit different than others in a way. And that's

00:00:54.580 --> 00:00:59.100
<v Aaron van Wirdum>also something we discuss because essentially we're talking about something that

00:00:59.100 --> 00:01:01.200
<v Aaron van Wirdum>we have no idea how it actually works.

00:01:01.660 --> 00:01:05.860
<v Sjors Provoost>Yes, but we have you in the field. You're able to try things and you've talked to

00:01:05.860 --> 00:01:11.640
<v Sjors Provoost>people. So we can learn by observing a system. But we've talked previously

00:01:11.640 --> 00:01:16.200
<v Sjors Provoost>that it's nice when a system is open source and transparent. The Chivo system is

00:01:16.200 --> 00:01:17.100
<v Sjors Provoost>not really that.

00:01:17.510 --> 00:01:22.330
<v Aaron van Wirdum>Yeah, so we're just kind of based on my personal observations, we're sort of

00:01:22.330 --> 00:01:27.950
<v Aaron van Wirdum>going to try and explain how the wallet probably works and how it doesn't work

00:01:27.950 --> 00:01:33.910
<v Aaron van Wirdum>and the good things and the bad things. And then I'm going to inquire your expert

00:01:33.910 --> 00:01:35.750
<v Aaron van Wirdum>opinion on all of that, Sjors.

00:01:36.170 --> 00:01:36.470
<v Sjors Provoost>Okay.

00:01:36.870 --> 00:01:41.270
<v Aaron van Wirdum>So yeah, let's start at the beginning. First of all, everything about the Chivo

00:01:41.270 --> 00:01:44.910
<v Aaron van Wirdum>app. Let me first explain what the Chivo app is, in case people don't know this.

00:01:45.390 --> 00:01:50.290
<v Aaron van Wirdum>So Bitcoin became a legal tender in El Salvador a couple weeks ago. In fact, it

00:01:50.290 --> 00:01:56.210
<v Aaron van Wirdum>became a mandatory tender, which means that merchants are obligated to accept it.

00:01:57.070 --> 00:02:01.710
<v Sjors Provoost>I think that's what legal tender means, by the way. I know you could implement it

00:02:01.710 --> 00:02:02.730
<v Sjors Provoost>differently, but...

00:02:02.710 --> 00:02:06.950
<v Aaron van Wirdum>Maybe that's a whole different debate. Well, but I want to address that because

00:02:06.950 --> 00:02:11.770
<v Aaron van Wirdum>it's not what legal tender means. What legal tender means is that if the legal

00:02:11.770 --> 00:02:17.350
<v Aaron van Wirdum>system comes into play, essentially, then any debts incurred can be repaid in

00:02:17.350 --> 00:02:21.930
<v Aaron van Wirdum>legal tender. So whether that's a credit card debt or any other, like if the

00:02:21.930 --> 00:02:27.370
<v Aaron van Wirdum>judge says you need to repay this person, then that's where legal tender comes

00:02:27.370 --> 00:02:27.950
<v Aaron van Wirdum>in, essentially.

00:02:28.390 --> 00:02:31.740
<v Sjors Provoost>Okay, so it doesn't come in for every payment. It only comes in for like... if

00:02:31.740 --> 00:02:32.460
<v Sjors Provoost>there's a dispute.

00:02:32.880 --> 00:02:37.780
<v Aaron van Wirdum>Exactly. Usually, well, I mean, you can extend that a little bit and then the

00:02:37.780 --> 00:02:42.340
<v Aaron van Wirdum>logic becomes any debt essentially can be repaid in legal tender because

00:02:42.340 --> 00:02:46.380
<v Aaron van Wirdum>otherwise you just ask the judge and then the judge says, yep, you can repay in

00:02:46.380 --> 00:02:52.160
<v Aaron van Wirdum>legal tender. But the point is that at first, before we even establish a contract

00:02:52.160 --> 00:02:57.930
<v Aaron van Wirdum>or before you walk into my store, I'm not obligated to accept. a particular type

00:02:57.930 --> 00:03:02.930
<v Aaron van Wirdum>of money from you it's only after the fact so to say that debts can be repaid in

00:03:02.930 --> 00:03:07.340
<v Aaron van Wirdum>legal tender that's what legal tender means However, there are a few countries,

00:03:07.500 --> 00:03:11.760
<v Aaron van Wirdum>and now El Salvador is one of them, where they go further than that and where

00:03:11.760 --> 00:03:16.120
<v Aaron van Wirdum>they say legal tender also means that you are obligated to actually accept

00:03:16.120 --> 00:03:19.020
<v Aaron van Wirdum>payments in this currency in the first place.

00:03:19.240 --> 00:03:23.600
<v Sjors Provoost>Yeah, in other words, if you offer a product at all, then whoever pays it has to

00:03:23.600 --> 00:03:27.120
<v Sjors Provoost>be able to do that using either Bitcoin or the US dollars.

00:03:27.600 --> 00:03:33.560
<v Aaron van Wirdum>No, it doesn't even apply to US dollars. It's only applying to Bitcoin in El Salvador.

00:03:34.210 --> 00:03:37.570
<v Sjors Provoost>That's fascinating. So you're not obligated to accept dollars.

00:03:37.970 --> 00:03:38.350
<v Aaron van Wirdum>Exactly.

00:03:38.590 --> 00:03:38.690
<v Sjors Provoost>Yeah.

00:03:39.150 --> 00:03:44.290
<v Aaron van Wirdum>Interesting, right? Now I can go on a whole detour explaining all the pros and

00:03:44.290 --> 00:03:47.370
<v Aaron van Wirdum>cons, but I'm not going to do that because we're going to focus on the more

00:03:47.370 --> 00:03:51.490
<v Aaron van Wirdum>technical aspects of it. However, I will say that because of this mandatory

00:03:51.490 --> 00:03:57.210
<v Aaron van Wirdum>aspect of the law, the government also apparently felt that they needed to

00:03:57.210 --> 00:04:03.160
<v Aaron van Wirdum>apply a wallet that will allow merchants to accept payments in Bitcoin. but then

00:04:03.160 --> 00:04:07.780
<v Aaron van Wirdum>have them automatically convert into US dollars. So that way no one is obligated

00:04:07.780 --> 00:04:12.140
<v Aaron van Wirdum>to really accept Bitcoin or at least not to hold Bitcoin because the government

00:04:12.140 --> 00:04:15.700
<v Aaron van Wirdum>says you just need to accept it, but then it's automatically transferred to

00:04:15.700 --> 00:04:18.800
<v Aaron van Wirdum>dollars if that's what you prefer. Does that make sense?

00:04:19.200 --> 00:04:23.280
<v Sjors Provoost>Yeah, you're avoiding as a merchant, you're not getting the exchange rate risk

00:04:23.280 --> 00:04:28.040
<v Sjors Provoost>because the government is taking that away from you and they're even giving you

00:04:28.040 --> 00:04:32.500
<v Sjors Provoost>at least some practical way to actually accept it. Like a tool, like a wallet.

00:04:32.920 --> 00:04:38.420
<v Aaron van Wirdum>Yeah. So to summarize it, because it's made a mandatory tender, the government

00:04:38.420 --> 00:04:43.180
<v Aaron van Wirdum>also deployed this app to tell people, look, it's mandated to accept it, but you

00:04:43.180 --> 00:04:46.300
<v Aaron van Wirdum>don't have to hold it. And we're going to make sure you don't have to hold it

00:04:46.300 --> 00:04:49.600
<v Aaron van Wirdum>because you can just use this app and have it converted to dollars automatically.

00:04:50.000 --> 00:04:54.400
<v Aaron van Wirdum>So that's sort of, if I would have to say why this app is even a thing, why there

00:04:54.400 --> 00:04:59.840
<v Aaron van Wirdum>even is this app, it's because there was this aspect of the lawmaking. Bitcoin

00:04:59.840 --> 00:05:00.700
<v Aaron van Wirdum>mandatory tender.

00:05:00.980 --> 00:05:05.800
<v Sjors Provoost>And that is also a way to say that this app probably originally was more of a

00:05:05.800 --> 00:05:10.220
<v Sjors Provoost>merchant app. Like that was the focus of it. But then due to some other pivots,

00:05:10.440 --> 00:05:12.780
<v Sjors Provoost>it's now also very much a consumer app.

00:05:13.360 --> 00:05:13.800
<v Aaron van Wirdum>Possibly.

00:05:14.100 --> 00:05:17.540
<v Sjors Provoost>Or was that already the... Maybe not. But anyway, in any case, what we're talking

00:05:17.540 --> 00:05:21.060
<v Sjors Provoost>about is essentially two apps, even though they might physically be one app. We

00:05:21.060 --> 00:05:23.780
<v Sjors Provoost>have a merchant app that allows stores to accept Bitcoin.

00:05:24.310 --> 00:05:25.070
<v Aaron van Wirdum>Or dollars.

00:05:25.390 --> 00:05:30.390
<v Sjors Provoost>Well, I guess just Bitcoin. And we have a consumer app that lets people pay with Bitcoin.

00:05:30.750 --> 00:05:31.970
<v Aaron van Wirdum>Dollars as well, actually.

00:05:32.330 --> 00:05:33.510
<v Sjors Provoost>And dollars. You mentioned that.

00:05:34.150 --> 00:05:40.010
<v Aaron van Wirdum>You can also pay dollar to dollar with Chivo to a merchant Chivo. That's also

00:05:40.010 --> 00:05:45.840
<v Aaron van Wirdum>possible. First, let me finish some of the basics. So this law was announced

00:05:45.840 --> 00:05:50.920
<v Aaron van Wirdum>about three months before it went into effect. And that meant apparently or

00:05:50.920 --> 00:05:55.900
<v Aaron van Wirdum>seemingly that the app also had to be developed within three months, which is not

00:05:55.900 --> 00:05:59.900
<v Aaron van Wirdum>a lot of time to develop a wallet or a merchant app or anything like this is a

00:05:59.900 --> 00:06:04.940
<v Aaron van Wirdum>short amount of time. I think you would agree. Who or what's developed it is a

00:06:04.940 --> 00:06:10.240
<v Aaron van Wirdum>bit of a mystery. The government is not really giving any info. So the only info

00:06:10.240 --> 00:06:16.020
<v Aaron van Wirdum>we have is sort of indirect or, you know, leaks or journalists that

00:06:16.020 --> 00:06:21.140
<v Aaron van Wirdum>discovered things. It seems like the political lead, both the political lead and

00:06:21.140 --> 00:06:26.940
<v Aaron van Wirdum>the technical lead are actually Venezuelans. And the technical lead has some

00:06:26.940 --> 00:06:32.910
<v Aaron van Wirdum>background as a founder of like a Dash help desk company that's one of

00:06:32.910 --> 00:06:37.190
<v Aaron van Wirdum>the things that has been reported on what i just mentioned was El Faro and then

00:06:37.190 --> 00:06:41.630
<v Aaron van Wirdum>there's a forbes article that suggests that bitgo has had a big part of it

00:06:41.630 --> 00:06:47.450
<v Aaron van Wirdum>there's also been leaked documents that suggested Athena the atm company had a

00:06:47.450 --> 00:06:53.310
<v Aaron van Wirdum>big part of it i had Sergey from Bitrefill on the podcast a while ago no

00:06:53.310 --> 00:06:58.610
<v Aaron van Wirdum>on the twitter spaces stream he said that there was probably several companies

00:06:58.610 --> 00:07:03.840
<v Aaron van Wirdum>involved three, four, maybe five. So that all seems to sort of add up. There's

00:07:03.840 --> 00:07:07.640
<v Aaron van Wirdum>different aspects of the wallet developed by different companies. And it's all

00:07:07.640 --> 00:07:11.920
<v Aaron van Wirdum>sort of been glued together. And now we have the Chivo app. That's sort of what

00:07:11.920 --> 00:07:17.700
<v Aaron van Wirdum>it looks like to me and what I'm hearing indirectly. Yeah. So

00:07:17.700 --> 00:07:19.520
<v Aaron van Wirdum>that's what the Chivo app is.

00:07:19.760 --> 00:07:24.020
<v Sjors Provoost>And maybe another piece of context that's useful to point out before we go deeper

00:07:24.020 --> 00:07:28.530
<v Sjors Provoost>into the app is that people don't have to use this app. You know, especially for

00:07:28.530 --> 00:07:32.670
<v Sjors Provoost>the Bitcoin things, of course, it is actually Bitcoin that people are using or

00:07:32.670 --> 00:07:38.570
<v Sjors Provoost>can use. So as a customer, in principle, you can use your own Bitcoin wallet. And

00:07:38.570 --> 00:07:42.690
<v Sjors Provoost>as a merchant, in principle, you can use your own Bitcoin wallet. And in fact,

00:07:42.790 --> 00:07:46.970
<v Sjors Provoost>you've demonstrated this at McDonald's where you used, I think, your own or you

00:07:46.970 --> 00:07:50.470
<v Sjors Provoost>used the Bitcoin Beach wallet and you paid McDonald's, which was using OpenNode.

00:07:50.730 --> 00:07:55.450
<v Sjors Provoost>So you were not using Chivo on any side of that McDonald's transaction you did,

00:07:55.610 --> 00:07:56.950
<v Sjors Provoost>which became very famous.

00:07:57.150 --> 00:08:01.930
<v Aaron van Wirdum>That is correct. I will say two things. There are two things to incentivize the

00:08:01.930 --> 00:08:06.070
<v Aaron van Wirdum>use of the Chivo app. So you're right that it's not obligated to use Chivo app.

00:08:06.110 --> 00:08:10.430
<v Aaron van Wirdum>You can use any Bitcoin wallet you want. There are two things that incentivize

00:08:10.430 --> 00:08:15.270
<v Aaron van Wirdum>use of the Chivo app. First is that any Salvadoran who downloads and starts using

00:08:15.270 --> 00:08:20.480
<v Aaron van Wirdum>the Chivo app gets... $30 worth of Bitcoin for free. So there's a monetary

00:08:20.480 --> 00:08:25.240
<v Aaron van Wirdum>incentive directly to use the Chivo app, to download it, to register an account.

00:08:25.520 --> 00:08:29.600
<v Aaron van Wirdum>And then the second one is that the conversion that I mentioned from dollars to

00:08:29.600 --> 00:08:34.300
<v Aaron van Wirdum>Bitcoin or Bitcoin to dollars, I think it works both way, is free if you use the

00:08:34.300 --> 00:08:37.700
<v Aaron van Wirdum>Chivo app. While, you know, if you use any other merchant service, then usually

00:08:37.700 --> 00:08:41.720
<v Aaron van Wirdum>there's a cost involved, there's fees for conversion. And with the Chivo, that's

00:08:41.720 --> 00:08:45.940
<v Aaron van Wirdum>free. So merchants are incentivized to use Chivo as well. I would say.

00:08:46.140 --> 00:08:50.000
<v Sjors Provoost>Yeah. And there may also be some slightly different counterparty risk when you're

00:08:50.000 --> 00:08:53.400
<v Sjors Provoost>dealing with a sovereign government versus a private enterprise.

00:08:53.620 --> 00:08:59.080
<v Aaron van Wirdum>Of course, I will say that. So the Chivo app is actually... So there's a Chivo

00:08:59.080 --> 00:09:03.620
<v Aaron van Wirdum>company and it's like a subsidiary of the government that's maintaining the

00:09:03.620 --> 00:09:08.660
<v Aaron van Wirdum>wallet. It's called Chivo. I think the company is just called Chivo, but it's not

00:09:08.660 --> 00:09:14.080
<v Aaron van Wirdum>clear who actually owns the company or operates it. Again, there is a lot of... I

00:09:14.080 --> 00:09:18.340
<v Aaron van Wirdum>mean, I consider it a lack of transparency. Maybe that's a colored way of putting

00:09:18.340 --> 00:09:24.220
<v Aaron van Wirdum>it, objective, more facts. Let's just say there's a lot we don't know.

00:09:25.060 --> 00:09:26.800
<v Aaron van Wirdum>There's a lot we don't know.

00:09:27.280 --> 00:09:30.640
<v Sjors Provoost>Yeah, so even the counterparty risk is literally unknown, right? Because we're

00:09:30.640 --> 00:09:33.160
<v Sjors Provoost>assuming that this is a government thing and that the government is your

00:09:33.160 --> 00:09:36.940
<v Sjors Provoost>counterparty, but it may actually turn out that, no, the government is not your

00:09:36.940 --> 00:09:41.460
<v Sjors Provoost>counterparty. But at least, you know, you get the vote a little bit about this

00:09:41.460 --> 00:09:41.940
<v Sjors Provoost>sort of stuff.

00:09:42.260 --> 00:09:47.120
<v Aaron van Wirdum>Okay, so I think I've now said four times that these were the basics and now get

00:09:47.120 --> 00:09:50.580
<v Aaron van Wirdum>into the technicals, but I lied all four times because there's one more basic

00:09:50.580 --> 00:09:55.840
<v Aaron van Wirdum>thing I want to mention. There's also the Chivo ATM, which, you know, it's

00:09:55.840 --> 00:10:01.560
<v Aaron van Wirdum>branded similarly. What we know for a fact is that these are being deployed by

00:10:01.560 --> 00:10:07.460
<v Aaron van Wirdum>Athena, Athena, the ATM producer. And I understand there are two types of this.

00:10:07.700 --> 00:10:11.190
<v Aaron van Wirdum>We're not going to get into this in detail in this episode, I think. But there

00:10:11.190 --> 00:10:15.250
<v Aaron van Wirdum>are two types, essentially, or two types of backends or two types of software

00:10:15.250 --> 00:10:19.390
<v Aaron van Wirdum>developed by two different companies. But it's basically Athena that got the

00:10:19.390 --> 00:10:23.410
<v Aaron van Wirdum>contract for the ATMs and there are 200 ATMs in the country now.

00:10:23.590 --> 00:10:28.810
<v Sjors Provoost>But it does mean that rather than the 10% or whatever or 5% that you used to pay

00:10:28.810 --> 00:10:33.550
<v Sjors Provoost>for a commercially run Bitcoin ATM to buy and sell, now you're suddenly getting

00:10:33.550 --> 00:10:35.730
<v Sjors Provoost>it for free or at least subsidized by the government.

00:10:36.030 --> 00:10:41.400
<v Aaron van Wirdum>Correct. You can use the ATMs for free. There's no conversion fee. And yes, of

00:10:41.400 --> 00:10:45.980
<v Aaron van Wirdum>course, that means that it's still not free to ship cash to and from these

00:10:45.980 --> 00:10:49.780
<v Aaron van Wirdum>machines and operate them and blah, blah, blah. So that's essentially subsidized

00:10:49.780 --> 00:10:54.990
<v Aaron van Wirdum>by the government. In other words, it's subsidized by the taxpayer. Another basic

00:10:54.990 --> 00:10:59.150
<v Aaron van Wirdum>thing, I guess I keep coming up with new basic things. Sjors, how do you like that?

00:10:59.430 --> 00:10:59.950
<v Sjors Provoost>That's good.

00:11:00.410 --> 00:11:04.550
<v Aaron van Wirdum>One more basic thing is that apparently the wallet has been downloaded. At the

00:11:04.550 --> 00:11:08.950
<v Aaron van Wirdum>time of recording, the wallet has been downloaded over 2 million times. Of

00:11:08.950 --> 00:11:12.750
<v Aaron van Wirdum>course, we have no way to verify that, but that's the numbers that have been published.

00:11:13.210 --> 00:11:15.250
<v Sjors Provoost>Doesn't the Android Play Store publish some of that?

00:11:15.430 --> 00:11:16.450
<v Aaron van Wirdum>Oh, I don't know. Does it?

00:11:16.670 --> 00:11:19.810
<v Sjors Provoost>That could still be like a million Chinese clones. But let's assume the numbers

00:11:19.810 --> 00:11:21.270
<v Sjors Provoost>true. How many people live in El Salvador?

00:11:21.800 --> 00:11:26.280
<v Aaron van Wirdum>Yes, somewhere between 6 and 7 million people. So it's like one third of the

00:11:26.280 --> 00:11:28.060
<v Aaron van Wirdum>country has downloaded this wallet.

00:11:28.540 --> 00:11:33.100
<v Sjors Provoost>Yeah, and obviously, at least I think a reasonable guess is to say that the $30

00:11:33.100 --> 00:11:35.580
<v Sjors Provoost>airdrop, you know, is an incentive to do that.

00:11:35.840 --> 00:11:41.560
<v Aaron van Wirdum>Oh, I mean, I can basically confirm that a lot of people, it's become a whole

00:11:41.560 --> 00:11:45.560
<v Aaron van Wirdum>thing where a lot of people... We're skipping ahead a little bit, but since I

00:11:45.560 --> 00:11:49.880
<v Aaron van Wirdum>started my sentence, I'll finish it. So a lot of people are downloading the

00:11:49.880 --> 00:11:55.640
<v Aaron van Wirdum>wallet and then essentially selling their $30 to some friend or

00:11:55.640 --> 00:12:01.500
<v Aaron van Wirdum>someone on Facebook or whatever for $25 in cash. And then they just

00:12:01.500 --> 00:12:07.400
<v Aaron van Wirdum>get $25 cash in hand and then they're happy. And then whoever bought the $30 of

00:12:07.400 --> 00:12:12.220
<v Aaron van Wirdum>Bitcoin for $25 of cash, he's going to collect it from like 10 people and then...

00:12:12.340 --> 00:12:16.780
<v Aaron van Wirdum>stand in line at one of the atms to get the money out and he made you know 50

00:12:16.780 --> 00:12:18.940
<v Aaron van Wirdum>bucks if he did that with 10 people

00:12:18.940 --> 00:12:21.560
<v Sjors Provoost>yeah or sell it to somebody else in the line and yeah

00:12:21.560 --> 00:12:24.880
<v Aaron van Wirdum>yeah so there's definitely a lot of people that are downloading the wallet is

00:12:24.880 --> 00:12:30.820
<v Aaron van Wirdum>basically just to cash out the funds for dollars bukele published some stats

00:12:30.820 --> 00:12:36.660
<v Aaron van Wirdum>the other days which suggests that there's quite a few transactions happening but

00:12:36.660 --> 00:12:41.000
<v Aaron van Wirdum>i i don't know what to think of that we definitely can't verify these stats I

00:12:41.000 --> 00:12:44.940
<v Aaron van Wirdum>also don't know, is this one guy playing around doing like a thousand

00:12:44.940 --> 00:12:48.940
<v Aaron van Wirdum>transactions back and forth from Bitcoin to dollar because it's free anyways? Or

00:12:48.940 --> 00:12:52.720
<v Aaron van Wirdum>are there really thousand people paying for something in a shop? I doubt the

00:12:52.720 --> 00:12:57.100
<v Aaron van Wirdum>latter because I just don't really see people using it a lot. I mean, my

00:12:57.100 --> 00:13:01.380
<v Aaron van Wirdum>perspective is limited, obviously. I'm one guy just sort of walking around and

00:13:01.380 --> 00:13:04.860
<v Aaron van Wirdum>half of the day I'm in my hotel room anyways. It's not like I'm doing research on

00:13:04.860 --> 00:13:10.120
<v Aaron van Wirdum>the street every day, all day. But just from sort of looking around and... Or

00:13:10.120 --> 00:13:14.460
<v Aaron van Wirdum>asking if I can pay with Bitcoin and then sort of based on the response, I can

00:13:14.460 --> 00:13:18.660
<v Aaron van Wirdum>tell that I'm the first person to ask that that day, or at least it doesn't

00:13:18.660 --> 00:13:22.480
<v Aaron van Wirdum>happen very often. So just based on my personal experience, I don't think people

00:13:22.480 --> 00:13:24.380
<v Aaron van Wirdum>are really using it a lot.

00:13:24.680 --> 00:13:27.880
<v Sjors Provoost>Yeah, if they still have to charge an iPad, then that's usually a sign they

00:13:27.880 --> 00:13:28.740
<v Sjors Provoost>haven't done it for a while.

00:13:29.180 --> 00:13:30.080
<v Aaron van Wirdum>Right, yeah.

00:13:30.220 --> 00:13:33.560
<v Sjors Provoost>That's my experience in other cities, in other countries. Okay, so maybe we

00:13:33.560 --> 00:13:36.140
<v Sjors Provoost>should start with the user-facing app.

00:13:36.340 --> 00:13:40.620
<v Aaron van Wirdum>and talk about that a bit let's start actually discussing the app as far as we

00:13:40.620 --> 00:13:45.820
<v Aaron van Wirdum>can actually do that so yeah there is the chivo application the wallet which i

00:13:45.820 --> 00:13:51.600
<v Aaron van Wirdum>have on my phone now actually some local was friendly enough to give me her

00:13:51.600 --> 00:13:55.940
<v Aaron van Wirdum>app essentially access to her app so i can sort of play around with it and see

00:13:55.940 --> 00:14:01.580
<v Aaron van Wirdum>how it works and see what can be done with it so Let me open it right now while

00:14:01.580 --> 00:14:06.760
<v Aaron van Wirdum>we are recording this podcast so I can sort of give a very short overview of it.

00:14:07.580 --> 00:14:11.400
<v Aaron van Wirdum>It's loading, Sjors. I should have opened this before we started [unclear]

00:14:11.880 --> 00:14:13.240
<v Sjors Provoost>Well, here's the magic of editors.

00:14:14.460 --> 00:14:20.000
<v Aaron van Wirdum>Yeah, good point. All right. So it's a pretty basic app. There's nothing too

00:14:20.000 --> 00:14:23.600
<v Aaron van Wirdum>interesting, I would say. But it has a home screen where you can see the history

00:14:23.600 --> 00:14:28.740
<v Aaron van Wirdum>of transactions. It has a conversion screen, like I mentioned, where it converts

00:14:28.740 --> 00:14:34.680
<v Aaron van Wirdum>USD to BTC and back. And then it has an options screen with

00:14:34.680 --> 00:14:39.480
<v Aaron van Wirdum>options. All right. The first thing to note is that there are two ways of

00:14:39.480 --> 00:14:44.980
<v Aaron van Wirdum>receiving money. So one is in dollars, one is in Bitcoin, and the dollar option

00:14:44.980 --> 00:14:49.960
<v Aaron van Wirdum>is basically for other Chivo apps. So that is, if I have a dollar account and

00:14:49.960 --> 00:14:53.360
<v Aaron van Wirdum>someone else has a dollar account, then you use the dollar option and then the

00:14:53.360 --> 00:14:55.080
<v Aaron van Wirdum>dollars go from my wallet to your wallet.

00:14:55.600 --> 00:14:57.080
<v Sjors Provoost>Right, so that's essentially PayPal.

00:14:57.420 --> 00:15:02.980
<v Aaron van Wirdum>That's essentially PayPal, yeah, or Venmo or one of these. And we can safely

00:15:02.980 --> 00:15:07.210
<v Aaron van Wirdum>assume that... Hopefully the money is in a bank account somewhere and there's

00:15:07.210 --> 00:15:10.690
<v Aaron van Wirdum>just a ledger entry. This obviously has nothing to do with Bitcoin or Lightning.

00:15:10.930 --> 00:15:13.790
<v Aaron van Wirdum>There's no Lightning transaction. I think that's safe to assume.

00:15:13.870 --> 00:15:17.030
<v Sjors Provoost>We can know for sure that these dollars do not exist in the app itself. They

00:15:17.030 --> 00:15:22.850
<v Sjors Provoost>exist in a database on a server and they may or may not be backed by US

00:15:22.850 --> 00:15:26.670
<v Sjors Provoost>dollars in a bank account to the full extent or some partial extent.

00:15:27.050 --> 00:15:27.290
<v Aaron van Wirdum>Right.

00:15:32.930 --> 00:15:37.390
<v Aaron van Wirdum>Now, then there's a Bitcoin option. And if you open that, you get just a Bitcoin

00:15:37.390 --> 00:15:42.950
<v Aaron van Wirdum>address, just an on-chain address. Now, there is also, it's really hidden in the

00:15:42.950 --> 00:15:48.310
<v Aaron van Wirdum>app. You need to go to like other payments methods, other wallets, actually. And

00:15:48.310 --> 00:15:52.890
<v Aaron van Wirdum>then if you go there, so you sort of dig in the receive page, then you actually

00:15:52.890 --> 00:15:54.810
<v Aaron van Wirdum>find a Lightning option.

00:15:55.310 --> 00:15:56.070
<v Sjors Provoost>Very cool.

00:15:56.570 --> 00:16:00.790
<v Aaron van Wirdum>So it works with Lightning as well. And then you can send sort of same idea.

00:16:01.230 --> 00:16:06.730
<v Aaron van Wirdum>dollars of bitcoin and if you choose bitcoin then you can scan a qr code which

00:16:06.730 --> 00:16:11.830
<v Aaron van Wirdum>can be either bitcoin qr code or lightning qr code now the first thing i'll say

00:16:11.830 --> 00:16:16.690
<v Aaron van Wirdum>so far so good right i will say however that every time i've tried to accept

00:16:16.690 --> 00:16:22.330
<v Aaron van Wirdum>funds receive funds that works every time i've tried to send funds it did not work

00:16:22.330 --> 00:16:23.010
<v Sjors Provoost>okay

00:16:23.540 --> 00:16:29.160
<v Aaron van Wirdum>Is that because this wallet now exists on two phones and that's causing

00:16:29.160 --> 00:16:35.100
<v Aaron van Wirdum>some kind of error? Is it because the wallet itself is buggy? Is it because some

00:16:35.100 --> 00:16:39.920
<v Aaron van Wirdum>other reason? I don't know. All I know is I have literally not been able to send

00:16:39.920 --> 00:16:45.000
<v Aaron van Wirdum>any funds either on-chain Bitcoin or over Lightning. The only thing that has

00:16:45.000 --> 00:16:50.160
<v Aaron van Wirdum>worked for me is sending funds to other Chivo wallets. That actually worked when

00:16:50.160 --> 00:16:54.200
<v Aaron van Wirdum>we were at the merchant and we wanted to send funds. That works, but sending

00:16:54.200 --> 00:16:58.420
<v Aaron van Wirdum>Bitcoin either on Chain or on Lightning, literally every time I tried it, it just

00:16:58.420 --> 00:16:58.880
<v Aaron van Wirdum>didn't work.

00:16:59.380 --> 00:17:00.380
<v Sjors Provoost>Okay, so that's interesting.

00:17:00.580 --> 00:17:04.020
<v Aaron van Wirdum>I would personally argue, but this is a personal opinion, that for a Bitcoin

00:17:04.020 --> 00:17:08.600
<v Aaron van Wirdum>wallet, that's sub-ideal. If you can't make any transactions...

00:17:08.600 --> 00:17:09.840
<v Sjors Provoost>Well, you can, you can receive.

00:17:10.160 --> 00:17:10.560
<v Aaron van Wirdum>Right.

00:17:10.880 --> 00:17:14.120
<v Sjors Provoost>And we'll get back to that for why that's interesting. So when you installed this

00:17:14.120 --> 00:17:17.660
<v Sjors Provoost>app, did you get a 24-word or 12-word mnemonic that you had to write down?

00:17:18.360 --> 00:17:20.960
<v Aaron van Wirdum>Excellent question, Sjors. I did not. No.

00:17:21.120 --> 00:17:25.460
<v Sjors Provoost>Okay, so then my guess is going to be that these coins are not really on your

00:17:25.460 --> 00:17:27.240
<v Sjors Provoost>phone either, just like the dollars.

00:17:27.790 --> 00:17:33.690
<v Aaron van Wirdum>I am basically 100% sure that you are right. And this, I mean,

00:17:33.830 --> 00:17:37.670
<v Aaron van Wirdum>we don't even have to guess. Like, yes, this is obviously a custodial.

00:17:37.850 --> 00:17:40.810
<v Sjors Provoost>For the lightning node, you can find out very easily. If you make a lightning

00:17:40.810 --> 00:17:46.150
<v Sjors Provoost>invoice and your phone does not get screaming hot, then it's probably not running

00:17:46.150 --> 00:17:49.350
<v Sjors Provoost>on your phone. But yeah, so it sounds like just like the dollars, there is a

00:17:49.350 --> 00:17:54.010
<v Sjors Provoost>database somewhere in El Salvador or some other place in the world that is

00:17:54.010 --> 00:17:58.970
<v Sjors Provoost>creating Bitcoin addresses and telling the app. Show this address or show the QR

00:17:58.970 --> 00:18:03.130
<v Sjors Provoost>code. And then whenever somebody sends Bitcoin to that place, those Bitcoins go

00:18:03.130 --> 00:18:08.350
<v Sjors Provoost>to some wallet somewhere in the world. And the number on your account goes up.

00:18:08.430 --> 00:18:12.570
<v Sjors Provoost>And that's just the number in the database. But that means that somebody's

00:18:12.570 --> 00:18:16.650
<v Sjors Provoost>hopefully taking care of these coins. But of course, you don't know. Again, you

00:18:16.650 --> 00:18:20.030
<v Sjors Provoost>have no idea whether that's fractional or not.

00:18:20.460 --> 00:18:25.900
<v Aaron van Wirdum>Yes, exactly. So the Bitcoin in your wallet are, I would argue, better

00:18:25.900 --> 00:18:31.740
<v Aaron van Wirdum>described as Bitcoin IOUs in your wallet. You're essentially getting a promise

00:18:31.740 --> 00:18:37.380
<v Aaron van Wirdum>of Bitcoin. You should be able to withdraw them to your own wallet eventually, if

00:18:37.380 --> 00:18:42.720
<v Aaron van Wirdum>it works at all. But you're not controlling your own keys. You're not controlling

00:18:42.720 --> 00:18:46.720
<v Aaron van Wirdum>your own coins. In that sense, it has very little to do with Bitcoin.

00:18:46.900 --> 00:18:51.320
<v Sjors Provoost>Yeah, it's like Coinbase. But with Lightning, some Lightning support and you

00:18:51.320 --> 00:18:52.240
<v Sjors Provoost>can't pay anyone.

00:18:52.360 --> 00:18:53.420
<v Aaron van Wirdum>You can't pay anyone.

00:18:53.580 --> 00:18:57.000
<v Sjors Provoost>But I assume you've talked to at least some people who have been able to use the

00:18:57.000 --> 00:18:58.700
<v Sjors Provoost>Chivo wallet to send money out.

00:18:59.160 --> 00:19:02.860
<v Aaron van Wirdum>Yes, I have heard of examples where it actually did work. Correct.

00:19:03.440 --> 00:19:06.760
<v Sjors Provoost>Right. Because a general pattern that would have me very worried would be where

00:19:06.760 --> 00:19:12.520
<v Sjors Provoost>lots of people are able to send Bitcoin to this wherever Chivo is. And nobody's

00:19:12.520 --> 00:19:16.480
<v Sjors Provoost>able to send Bitcoin away from whatever this Chivo is. That would suggest that,

00:19:16.480 --> 00:19:20.680
<v Sjors Provoost>you know, Bitcoins are accumulating somewhere. No, I mean, it's more like a

00:19:20.680 --> 00:19:24.060
<v Sjors Provoost>usability problem. Your wallet doesn't work well, but other people's wallets work

00:19:24.060 --> 00:19:25.360
<v Sjors Provoost>better or it's just luck.

00:19:25.860 --> 00:19:30.740
<v Aaron van Wirdum>Yeah, I mean, I think it's just buggy. And because it's closed source, which you

00:19:30.740 --> 00:19:35.180
<v Aaron van Wirdum>mentioned, we can't figure out what the bug is. And people like you can't help

00:19:35.180 --> 00:19:39.420
<v Aaron van Wirdum>solve it either. It's just a black box. And all I know is that it doesn't work

00:19:39.420 --> 00:19:45.240
<v Aaron van Wirdum>for me. Yeah. What I'm also pretty sure of, but again, who knows, but I

00:19:45.240 --> 00:19:49.640
<v Aaron van Wirdum>think it's probably safe to assume that Bitcoin transactions from Chivo to Chivo

00:19:49.640 --> 00:19:55.420
<v Aaron van Wirdum>are also just custodial ledger entries. It's not like, because why would you make it?

00:19:55.660 --> 00:19:59.760
<v Sjors Provoost>Well, that is something you can find out, right? So you can send, say, $10 of

00:19:59.760 --> 00:20:02.920
<v Sjors Provoost>Bitcoin to this address that the app is showing, and then you look at a block

00:20:02.920 --> 00:20:07.680
<v Sjors Provoost>explorer. And you start just toggling it between dollars and Bitcoin or sending

00:20:07.680 --> 00:20:12.360
<v Sjors Provoost>it to somebody else. And if that doesn't correlate with actual transactions on

00:20:12.360 --> 00:20:15.680
<v Sjors Provoost>the chain, then you know something is in the database. My guess would be that the

00:20:15.680 --> 00:20:19.540
<v Sjors Provoost>money stays in that address until some point their server is sweeping a bunch of

00:20:19.540 --> 00:20:23.420
<v Sjors Provoost>addresses at the same time, unrelated to when you're making payments. Because

00:20:23.420 --> 00:20:27.590
<v Sjors Provoost>they'll probably treat it as one big account. Although that depends, and this

00:20:27.590 --> 00:20:31.690
<v Sjors Provoost>ties into your news article, I think there was mention of BitGo being involved.

00:20:31.870 --> 00:20:36.250
<v Sjors Provoost>And I think BitGo at least offers services where every customer has a unique,

00:20:36.530 --> 00:20:41.090
<v Sjors Provoost>like has a segregated account, but they may not be using that. I think the

00:20:41.090 --> 00:20:44.690
<v Sjors Provoost>technical term is omnibus account versus individual accounts.

00:20:45.170 --> 00:20:49.670
<v Aaron van Wirdum>Right. So insofar that I've been able to test this, I have made one Bitcoin

00:20:49.670 --> 00:20:54.930
<v Aaron van Wirdum>transaction to a merchant that used Chivo. Now, if I go into my transaction

00:20:54.930 --> 00:20:59.390
<v Aaron van Wirdum>history and if I click at it, I don't see any Bitcoin address that it has been

00:20:59.390 --> 00:21:05.070
<v Aaron van Wirdum>sent to. It just says an amount. For other transactions, I am seeing Bitcoin addresses.

00:21:05.570 --> 00:21:07.230
<v Sjors Provoost>But that's inside your wallet, right?

00:21:07.290 --> 00:21:08.830
<v Aaron van Wirdum>Inside my own wallet, yes, correct.

00:21:09.250 --> 00:21:12.290
<v Sjors Provoost>But if you look at that address on a Wallet Explorer, Bitcoin Explorer, you might

00:21:12.290 --> 00:21:14.230
<v Sjors Provoost>see something moving, but probably you will not.

00:21:14.650 --> 00:21:18.530
<v Aaron van Wirdum>Yes, well, I might. But at this point, I don't know what address it originally

00:21:18.530 --> 00:21:22.530
<v Aaron van Wirdum>was or how that originally... There's no way for me to figure it out. Now, my

00:21:22.530 --> 00:21:26.870
<v Aaron van Wirdum>history does not show an address that it would have been sent to. It just shows

00:21:26.870 --> 00:21:30.050
<v Aaron van Wirdum>there was a payment made to a Chivo app. So my...

00:21:30.050 --> 00:21:33.510
<v Sjors Provoost>Yeah, but then on the blockchain, you would see a transaction around the same

00:21:33.510 --> 00:21:34.960
<v Sjors Provoost>time. Or you don't.

00:21:35.280 --> 00:21:39.240
<v Aaron van Wirdum>No, I get that. It's just, we have no way of verifying that right now.

00:21:39.580 --> 00:21:40.040
<v Sjors Provoost>That's true.

00:21:40.620 --> 00:21:46.300
<v Aaron van Wirdum>One thing I'll note is that, so I mentioned the free $30 that people got when

00:21:46.300 --> 00:21:51.700
<v Aaron van Wirdum>they registered their wallet for the first time. First of all, this does require

00:21:51.700 --> 00:21:56.960
<v Aaron van Wirdum>that you include all your personal info. So obviously there's no privacy involved

00:21:56.960 --> 00:22:01.160
<v Aaron van Wirdum>at all. The government knows, or at least whoever is operating a Chivo wallet

00:22:01.160 --> 00:22:05.800
<v Aaron van Wirdum>knows who's paying who, when, how much. The second thing is that these first $30

00:22:05.800 --> 00:22:11.720
<v Aaron van Wirdum>were actually locked. They had a restriction on it. These first $30 could only

00:22:11.720 --> 00:22:17.000
<v Aaron van Wirdum>be spent to other Chivo wallets. So the idea here is to incentivize that people

00:22:17.000 --> 00:22:22.860
<v Aaron van Wirdum>would actually use these $30 to buy something, to walk in a store and to buy.

00:22:23.530 --> 00:22:25.530
<v Aaron van Wirdum>whatever it is people are buying here.

00:22:25.830 --> 00:22:29.850
<v Sjors Provoost>And this was $30 in dollars or $30 in Bitcoin?

00:22:30.190 --> 00:22:31.410
<v Aaron van Wirdum>$30 in Bitcoin.

00:22:31.710 --> 00:22:36.950
<v Sjors Provoost>So if they kept it, then the price would start fluctuating. So it becomes Bitcoin

00:22:36.950 --> 00:22:39.370
<v Sjors Provoost>the second you register the app, I guess.

00:22:39.650 --> 00:22:44.910
<v Aaron van Wirdum>Yes, I think that's right. At the time you register, that's when you get $30 and

00:22:44.910 --> 00:22:50.270
<v Aaron van Wirdum>it becomes Bitcoin essentially. So these first $30 were restricted,

00:22:50.270 --> 00:22:54.760
<v Aaron van Wirdum>like I explained. I personally think that was a big mistake. I think it goes

00:22:54.760 --> 00:22:59.140
<v Aaron van Wirdum>against the whole philosophy of Bitcoin where you can send your money anywhere

00:22:59.140 --> 00:23:03.700
<v Aaron van Wirdum>you want. Second of all, it gave a lot of people bad experience because anyone

00:23:03.700 --> 00:23:07.980
<v Aaron van Wirdum>who walked into a McDonald's found out that they couldn't actually pay for the

00:23:07.980 --> 00:23:10.840
<v Aaron van Wirdum>Big Mac that they thought they were going to be able to pay for with a free $30.

00:23:11.640 --> 00:23:16.700
<v Aaron van Wirdum>Plus, a company like a McDonald's and a bunch of others, they actually went the

00:23:16.700 --> 00:23:21.300
<v Aaron van Wirdum>extra mile to make sure that they could accept Bitcoin on day one. They didn't

00:23:21.300 --> 00:23:25.720
<v Aaron van Wirdum>wait for the Chivo app. They made sure like they want to be ready. They want to

00:23:25.720 --> 00:23:28.860
<v Aaron van Wirdum>make sure that all these people can walk into the McDonald's and spend their

00:23:28.860 --> 00:23:33.360
<v Aaron van Wirdum>coins. And then they didn't. So the companies that went the extra mile actually

00:23:33.360 --> 00:23:37.000
<v Aaron van Wirdum>were punished for that. So that was another bad thing. And third of all, I

00:23:37.000 --> 00:23:40.480
<v Aaron van Wirdum>already mentioned this. It didn't even work because most people just figured out

00:23:40.480 --> 00:23:45.040
<v Aaron van Wirdum>how to cash it out after all. And they did cash it out. So the $30 restriction

00:23:45.040 --> 00:23:47.180
<v Aaron van Wirdum>was a big mistake if you ask me.

00:23:47.570 --> 00:23:51.950
<v Sjors Provoost>So the $30, you could send it to another Chivo wallet, but not to an external

00:23:51.950 --> 00:23:56.330
<v Sjors Provoost>wallet, right? So any merchant using Chivo would be able to accept it, but any

00:23:56.330 --> 00:24:00.110
<v Sjors Provoost>merchant not using Chivo would not be able to accept it, which is exactly the

00:24:00.110 --> 00:24:02.630
<v Sjors Provoost>opposite of the point of being interoperable.

00:24:03.070 --> 00:24:08.210
<v Aaron van Wirdum>Yeah, that's not ideal. After it was spent, so once these $30 were spent once to

00:24:08.210 --> 00:24:13.650
<v Aaron van Wirdum>another Chivo app, Then they became freely spendable anywhere. But it was this

00:24:13.650 --> 00:24:15.990
<v Aaron van Wirdum>first hop that was restricted to other Chivo apps.

00:24:16.490 --> 00:24:19.870
<v Sjors Provoost>Yeah, I guess we're going to have to do another episode about Covenants, which

00:24:19.870 --> 00:24:21.310
<v Sjors Provoost>covers this phenomena.

00:24:21.730 --> 00:24:25.430
<v Aaron van Wirdum>Right, right. Yeah, so what else about the app? I mean...

00:24:25.430 --> 00:24:28.230
<v Sjors Provoost>We've talked about it. It's closed source. It's custodial.

00:24:28.430 --> 00:24:28.830
<v Aaron van Wirdum>Yes.

00:24:28.930 --> 00:24:33.170
<v Sjors Provoost>So the money is not in the thing itself. There appear to be some bugs. I think

00:24:33.170 --> 00:24:38.310
<v Sjors Provoost>you've mentioned a few. that you're unable to pay and we talked about the airdrop

00:24:38.310 --> 00:24:40.490
<v Sjors Provoost>so maybe we can talk about the merchant app

00:24:40.850 --> 00:24:45.670
<v Aaron van Wirdum>Yeah. Okay. So let's move to the merchant app. I want to clarify one thing. I've

00:24:45.670 --> 00:24:50.690
<v Aaron van Wirdum>so far sounded very negative about the wallet. That's because I am. I think it's

00:24:50.690 --> 00:24:54.070
<v Aaron van Wirdum>a piece of shit. I think they shouldn't have released something that's clearly

00:24:54.070 --> 00:24:59.550
<v Aaron van Wirdum>not finished. And I don't feel like defending this at all. I've seen some people

00:24:59.550 --> 00:25:03.630
<v Aaron van Wirdum>defend it with arguments like, well, they're trying something new and they rolled

00:25:03.630 --> 00:25:08.460
<v Aaron van Wirdum>it out in. you know, record time and give them a slack. I think, no, you're

00:25:08.460 --> 00:25:12.240
<v Aaron van Wirdum>dealing with financial software. This is other people's money. There was no real

00:25:12.240 --> 00:25:17.040
<v Aaron van Wirdum>reason to necessarily release it on September 7th. They could have just said,

00:25:17.180 --> 00:25:20.880
<v Aaron van Wirdum>okay, look, Bitcoin is legal tender now, but the wallet is not finished. We're

00:25:20.880 --> 00:25:23.580
<v Aaron van Wirdum>not going to enforce the mandatory part of the law. We're going to keep

00:25:23.580 --> 00:25:27.410
<v Aaron van Wirdum>developing the wallet; we're going to roll it out as a pilot. We're going to

00:25:27.410 --> 00:25:30.690
<v Aaron van Wirdum>first roll it out to a thousand people, let them experiment. Blah, blah, blah.

00:25:30.770 --> 00:25:34.970
<v Aaron van Wirdum>They could have done so many things, but instead they felt the need to, for

00:25:34.970 --> 00:25:38.810
<v Aaron van Wirdum>whatever reason, roll it out to millions of people at the same time. And millions

00:25:38.810 --> 00:25:42.150
<v Aaron van Wirdum>of people had a bad experience. I think it was a bad mistake. And I don't really

00:25:42.150 --> 00:25:45.970
<v Aaron van Wirdum>see why we shouldn't be allowed to criticize that. I'm definitely not going to

00:25:45.970 --> 00:25:49.650
<v Aaron van Wirdum>bite my tongue because I like the project or anything like that.

00:25:49.930 --> 00:25:51.930
<v Sjors Provoost>Well, you're still in El Salvador. I'm not.

00:25:52.210 --> 00:25:53.350
<v Aaron van Wirdum>Yes, as well.

00:25:53.590 --> 00:25:57.930
<v Sjors Provoost>But yeah, no, I agree with, this sounds like a reasonable assessment. This, I

00:25:57.930 --> 00:26:01.550
<v Sjors Provoost>think, could have been predicted in advance that when you tried something this

00:26:01.550 --> 00:26:05.330
<v Sjors Provoost>ambitious, because I do think it's very ambitious, it's better to roll it out

00:26:05.330 --> 00:26:06.410
<v Sjors Provoost>more carefully.

00:26:06.710 --> 00:26:10.790
<v Aaron van Wirdum>It was predicted in advance. That's the other thing. It was predicted in advance.

00:26:10.990 --> 00:26:15.990
<v Aaron van Wirdum>I know for a fact that several people and several companies literally told the

00:26:15.990 --> 00:26:19.790
<v Aaron van Wirdum>El Salvadoran government that three months is a crazy timeline for something like

00:26:19.790 --> 00:26:25.470
<v Aaron van Wirdum>this. They decided to push through with it anyways. It backfired, or at least it

00:26:25.470 --> 00:26:31.110
<v Aaron van Wirdum>didn't go well, as predicted. I think at this point, it's completely fair to

00:26:31.110 --> 00:26:34.530
<v Aaron van Wirdum>criticize the failure that this launch has been.

00:26:35.090 --> 00:26:41.030
<v Sjors Provoost>Essentially, you're launching PayPal plus Coinbase, the whole

00:26:41.030 --> 00:26:44.910
<v Sjors Provoost>exchange mechanism, and you're doing Lightning, which is all the work that Jack

00:26:44.910 --> 00:26:49.010
<v Sjors Provoost>Mallers and other people have done, and you're trying to explain that to a whole

00:26:49.010 --> 00:26:53.390
<v Sjors Provoost>population. Then you're doing an airdrop, which itself is very complicated. Yeah,

00:26:53.490 --> 00:26:57.770
<v Sjors Provoost>this is very ambitious and not something you can do in three months. Maybe

00:26:57.770 --> 00:27:02.170
<v Sjors Provoost>Singapore could have done it, but... I don't think it was a realistic plan.

00:27:02.430 --> 00:27:05.310
<v Sjors Provoost>Anyhow, we'll see how that evolves. Moving on to the merchant app.

00:27:05.410 --> 00:27:09.790
<v Aaron van Wirdum>Oh yeah, I will. Okay, so if I do want to end on a positive note on the wallet

00:27:09.790 --> 00:27:14.890
<v Aaron van Wirdum>part, I do think it is being improved. It is getting better from what I

00:27:14.890 --> 00:27:18.810
<v Aaron van Wirdum>understand. Even though my transactions are still not coming through, I am

00:27:18.810 --> 00:27:23.530
<v Aaron van Wirdum>hearing from just other people online and elsewhere that the wallet is slowly but

00:27:23.530 --> 00:27:27.310
<v Aaron van Wirdum>surely improving. So I guess that would be the positive note. Anyone who's

00:27:27.310 --> 00:27:30.750
<v Aaron van Wirdum>looking for a positive note now has a positive note. There you go.

00:27:31.210 --> 00:27:32.390
<v Sjors Provoost>Cool. The merchant app.

00:27:32.610 --> 00:27:38.310
<v Aaron van Wirdum>Okay, so obviously I'm not a merchant. And so my experience with it has

00:27:38.310 --> 00:27:44.090
<v Aaron van Wirdum>only been sort of from the other end. Although at one point when a merchant was

00:27:44.090 --> 00:27:48.330
<v Aaron van Wirdum>having trouble, they did allow me to actually sort of click around a little bit

00:27:48.330 --> 00:27:53.520
<v Aaron van Wirdum>and see what it looked like and see what was happening sort of with that app. I

00:27:53.520 --> 00:27:58.160
<v Aaron van Wirdum>can say for sure, or at least, first of all, I thought the app looked a bit

00:27:58.160 --> 00:28:01.520
<v Aaron van Wirdum>confusing when I was playing around with it. Because there were sort of two

00:28:01.520 --> 00:28:06.120
<v Aaron van Wirdum>options. It was like either accept payment with US dollar or accept payment with

00:28:06.120 --> 00:28:10.340
<v Aaron van Wirdum>Bitcoin. But it was not clear to me that if you accept a payment with Bitcoin,

00:28:10.560 --> 00:28:15.240
<v Aaron van Wirdum>that it was actually converted behind the screens into dollars. And it was clear

00:28:15.240 --> 00:28:19.760
<v Aaron van Wirdum>to me that payments to the US dollar version was not compatible with Bitcoin

00:28:19.760 --> 00:28:25.190
<v Aaron van Wirdum>payments. If a merchant wanted to accept a Bitcoin payment, but have it converted

00:28:25.190 --> 00:28:30.090
<v Aaron van Wirdum>into US dollars, maybe that was the Bitcoin option. But I'm making a mess of this

00:28:30.090 --> 00:28:30.490
<v Aaron van Wirdum>explanation.

00:28:30.870 --> 00:28:33.230
<v Sjors Provoost>Yeah, I think I see what you're trying to get to. So it looks like you have to

00:28:33.230 --> 00:28:37.730
<v Sjors Provoost>make a payment, an invoice in dollars or in Bitcoin, because if you made one in

00:28:37.730 --> 00:28:42.930
<v Sjors Provoost>dollars, then you can't pay it when you have a dollar balance. but if you made it

00:28:42.930 --> 00:28:46.750
<v Sjors Provoost>in bitcoin then the amount would be fixed in bitcoin but you're thinking maybe it

00:28:46.750 --> 00:28:50.450
<v Sjors Provoost>wasn't fixed in bitcoin it would be changing all the time or if you go to a

00:28:50.450 --> 00:28:51.310
<v Sjors Provoost>normal like

00:28:51.310 --> 00:28:55.610
<v Aaron van Wirdum>no let me let me explain very clearly what i mean so as far as i could tell there

00:28:55.610 --> 00:29:00.430
<v Aaron van Wirdum>were two options either paying dollars or paying bitcoin if i chose paying

00:29:00.430 --> 00:29:04.750
<v Aaron van Wirdum>dollars then i literally had to pay in dollars with the chivo app essentially as

00:29:04.750 --> 00:29:09.070
<v Aaron van Wirdum>far as i could tell if i chose paying bitcoin then i could pay in bitcoin but

00:29:09.070 --> 00:29:13.210
<v Aaron van Wirdum>then it wasn't clear to me if the merchant would have that amount converted in

00:29:13.210 --> 00:29:17.990
<v Aaron van Wirdum>dollars if they wanted to the reason i'm unsure about this is because i wanted to

00:29:17.990 --> 00:29:21.070
<v Aaron van Wirdum>do this and then the merchant said no no we don't accept bitcoin payments only

00:29:21.070 --> 00:29:25.830
<v Aaron van Wirdum>dollar payments so that was odd to me because i want to pay with bitcoin and they

00:29:25.830 --> 00:29:29.800
<v Aaron van Wirdum>have a Chivo app so they should be able to have it converted to dollars now maybe

00:29:29.800 --> 00:29:33.040
<v Aaron van Wirdum>that was something that happened behind the screens and maybe that was something

00:29:33.040 --> 00:29:36.860
<v Aaron van Wirdum>they had in their options menu and the girl i was speaking to didn't notice

00:29:36.860 --> 00:29:41.460
<v Aaron van Wirdum>that's all very plausible but i will say it was not very natural like it was not

00:29:41.460 --> 00:29:45.060
<v Aaron van Wirdum>obvious from just sort of scrolling through the app it was not super clear what

00:29:45.060 --> 00:29:45.620
<v Aaron van Wirdum>was going on

00:29:45.940 --> 00:29:49.220
<v Sjors Provoost>No, and this is, of course, something that the merchant has to know and

00:29:49.220 --> 00:29:52.140
<v Sjors Provoost>understand because they probably have to select something. Like, do you want to

00:29:52.140 --> 00:29:56.540
<v Sjors Provoost>keep everything in dollars or do you want to keep half of it in Bitcoin? Or, you

00:29:56.540 --> 00:29:58.800
<v Sjors Provoost>know, there's got to be some slider somewhere to do that.

00:29:59.280 --> 00:29:59.600
<v Aaron van Wirdum>Exactly.

00:29:59.820 --> 00:30:02.380
<v Sjors Provoost>And if there's no slider, then I wouldn't know what the behavior is.

00:30:02.640 --> 00:30:06.720
<v Aaron van Wirdum>Right. So in the wallet app, the slider is very clear. The slider is right there.

00:30:06.860 --> 00:30:10.920
<v Aaron van Wirdum>If you're accepting a Bitcoin, it lets you decide right there. Do you want to

00:30:10.920 --> 00:30:14.040
<v Aaron van Wirdum>have it in Bitcoin or do you want to have it in Lightning? I did not see this

00:30:14.040 --> 00:30:18.200
<v Aaron van Wirdum>slider in the merchant app, which is why I wasn't sure what was actually going

00:30:18.200 --> 00:30:23.160
<v Aaron van Wirdum>on. Now, about the things that I'm a little bit more sure about is the merchant

00:30:23.160 --> 00:30:28.220
<v Aaron van Wirdum>app does not appear to accept Lightning transactions, only on-chain, as far as I

00:30:28.220 --> 00:30:32.600
<v Aaron van Wirdum>could tell. On-chain or maybe it was a custodial kind of thing. That's also

00:30:32.600 --> 00:30:37.620
<v Aaron van Wirdum>possible. But Lightning did not appear to be an option in the merchant app. I

00:30:37.620 --> 00:30:41.800
<v Aaron van Wirdum>made several payments at Chivo apps. One of them was Chivo.Chivo, like I

00:30:41.800 --> 00:30:46.560
<v Aaron van Wirdum>mentioned. That one was actually quick and easy. presumably because it was a

00:30:46.560 --> 00:30:48.660
<v Aaron van Wirdum>custodial ledger entry, I think.

00:30:48.860 --> 00:30:51.040
<v Sjors Provoost>But that was a dollar transaction, I'm guessing.

00:30:51.440 --> 00:30:52.980
<v Aaron van Wirdum>No, that was a Bitcoin transaction.

00:30:53.400 --> 00:30:56.120
<v Sjors Provoost>So how does it know that then? Because you're seeing an invoice.

00:30:56.580 --> 00:30:57.980
<v Aaron van Wirdum>I'm seeing a Bitcoin address.

00:30:58.590 --> 00:31:01.950
<v Sjors Provoost>How then does it know that it's an internal thing? Does it have some sort of

00:31:01.950 --> 00:31:02.670
<v Sjors Provoost>master list?

00:31:02.850 --> 00:31:05.670
<v Aaron van Wirdum>I mean, we can only guess, but that would be my guess, yes.

00:31:06.090 --> 00:31:06.810
<v Sjors Provoost>That's interesting.

00:31:07.230 --> 00:31:11.310
<v Aaron van Wirdum>I mean, or it was an on-chain transaction and it's just not visible as such in my

00:31:11.310 --> 00:31:15.770
<v Aaron van Wirdum>wallet. That's also possible. To our listeners, like we mentioned, this is a bit

00:31:15.770 --> 00:31:18.950
<v Aaron van Wirdum>of an odd episode because we're guessing so much. And the reason we're guessing

00:31:18.950 --> 00:31:22.970
<v Aaron van Wirdum>so much is because it is closed source and it's sort of the only thing we can do

00:31:22.970 --> 00:31:23.430
<v Aaron van Wirdum>is guess.

00:31:23.860 --> 00:31:27.200
<v Sjors Provoost>Yeah, well, there's some things you can actually observe in the app, right? So

00:31:27.200 --> 00:31:30.140
<v Sjors Provoost>you mentioned that if it's a real on-chain payment, it's not going to go through.

00:31:30.500 --> 00:31:35.000
<v Sjors Provoost>But if it's not, then it does. And you can use another Bitcoin app to scan the

00:31:35.000 --> 00:31:38.900
<v Sjors Provoost>same thing and see what you're getting. To see when you scan the invoice at the

00:31:38.900 --> 00:31:44.060
<v Sjors Provoost>shop, is it just a regular Bitcoin address with an amount? Or is there some extra

00:31:44.060 --> 00:31:48.140
<v Sjors Provoost>information in it? Or is it not even a Bitcoin address, but some sort of website

00:31:48.140 --> 00:31:49.160
<v Sjors Provoost>that you go to and then...

00:31:49.540 --> 00:31:55.400
<v Aaron van Wirdum>Okay. So if I go to one of the transactions that I made on chain back

00:31:55.400 --> 00:32:01.400
<v Aaron van Wirdum>when I was working, I guess, I am seeing a receiving Bitcoin address. I see a 3

00:32:01.400 --> 00:32:06.040
<v Aaron van Wirdum>L blah, blah, blah, blah. I see an address. When I go to the one that I made at

00:32:06.040 --> 00:32:10.640
<v Aaron van Wirdum>another Chivo app, I do not see an address. I just see the name of whoever. But

00:32:10.640 --> 00:32:14.740
<v Aaron van Wirdum>I'm pretty sure that when I was there, I made the payments to a Bitcoin address.

00:32:14.960 --> 00:32:18.600
<v Aaron van Wirdum>I think what flashed on the screen was, I think was a Bitcoin address.

00:32:19.090 --> 00:32:23.450
<v Sjors Provoost>So I guess next time when you go to the shop, you should bring two phones or try

00:32:23.450 --> 00:32:26.730
<v Sjors Provoost>two apps on the same phone where you scan the address with the regular Bitcoin

00:32:26.730 --> 00:32:31.290
<v Sjors Provoost>app and then scan it with the Chivo app. And then if you pay it with the Chivo

00:32:31.290 --> 00:32:36.350
<v Sjors Provoost>app, and again, it shows the destination on it, that's very interesting indeed,

00:32:36.370 --> 00:32:41.890
<v Sjors Provoost>because then they probably map the addresses to the identities in the backend and

00:32:41.890 --> 00:32:46.440
<v Sjors Provoost>then figure it out and actually not make an on-chain transaction. That could be

00:32:46.440 --> 00:32:49.200
<v Sjors Provoost>true. So it could be that the Chivo app, when you're trying to make a payment

00:32:49.200 --> 00:32:52.540
<v Sjors Provoost>first says, do I know this person? If I know it, I'm just going to make a

00:32:52.540 --> 00:32:55.940
<v Sjors Provoost>database entry. If I don't know it, I'm actually going to make a payment. Yeah.

00:32:56.480 --> 00:32:59.440
<v Sjors Provoost>Those things you can reverse engineer it. It's just that somebody would have to

00:32:59.440 --> 00:33:04.260
<v Sjors Provoost>do it and make a giant wiki that precisely explains what this app is doing. Or

00:33:04.260 --> 00:33:06.380
<v Sjors Provoost>they could open source it and everybody would understand it.

00:33:06.740 --> 00:33:11.800
<v Aaron van Wirdum>Yeah, we are going on my personal experience and more specifically my memory of

00:33:11.800 --> 00:33:17.740
<v Aaron van Wirdum>my personal experiences, which is obviously pretty far from scientific. But, you

00:33:17.740 --> 00:33:22.560
<v Aaron van Wirdum>know, we're doing the best we can here, I guess. Okay, so the Merchant app does

00:33:22.560 --> 00:33:27.710
<v Aaron van Wirdum>not have lightning. We mentioned that. One thing I tried is paying with a RBF

00:33:27.710 --> 00:33:32.300
<v Aaron van Wirdum>transaction replace by fee transaction. Did I mention this? So one of the normal

00:33:32.300 --> 00:33:37.240
<v Aaron van Wirdum>transactions without RBF that I did, that went through immediately. So it seems

00:33:37.240 --> 00:33:41.720
<v Aaron van Wirdum>that they are accepting zero-conf transactions if it's not an RBF transaction.

00:33:42.180 --> 00:33:47.740
<v Aaron van Wirdum>However, if it is an RBF transaction, then the merchant app doesn't

00:33:47.740 --> 00:33:52.060
<v Aaron van Wirdum>register the transaction at all until it's confirmed, probably.

00:33:52.380 --> 00:33:53.600
<v Sjors Provoost>That's a lot of fun.

00:33:53.800 --> 00:33:57.860
<v Aaron van Wirdum>That was a lot of fun when I was standing in line trying to pay for my groceries.

00:33:58.300 --> 00:34:03.300
<v Aaron van Wirdum>where I made the payments. I mean, I knew I was messing around. I knew I

00:34:03.300 --> 00:34:06.820
<v Aaron van Wirdum>intentionally put RBF on to see what would happen. So I knew-

00:34:06.820 --> 00:34:08.800
<v Sjors Provoost>Yeah, but there's plenty of wallets that have it on by default, so.

00:34:08.940 --> 00:34:13.000
<v Aaron van Wirdum>Yeah, exactly. So I had RBF on just to see what would happen. Well, what happened

00:34:13.000 --> 00:34:18.540
<v Aaron van Wirdum>was basically nothing. The merchant app did not register the payments at all. And

00:34:18.540 --> 00:34:22.560
<v Aaron van Wirdum>of course, the people that were working in the store, they just thought I didn't

00:34:22.560 --> 00:34:26.710
<v Aaron van Wirdum>pay. They just told me you didn't pay, even though. i mean i could explain a

00:34:26.710 --> 00:34:28.870
<v Aaron van Wirdum>little bit that i was showing them my wallet and then

00:34:28.870 --> 00:34:29.750
<v Sjors Provoost>computer says no

00:34:29.750 --> 00:34:34.090
<v Aaron van Wirdum>computer says no i showed them my wallet and then they didn't understand it and i

00:34:34.090 --> 00:34:39.310
<v Aaron van Wirdum>tried to explain and then more people had to come to our cash register and take a

00:34:39.310 --> 00:34:43.470
<v Aaron van Wirdum>look at it and then someone else had to come to that spoke better english and

00:34:43.470 --> 00:34:47.990
<v Aaron van Wirdum>then the line kept forming it got longer and longer and then someone started

00:34:47.990 --> 00:34:53.180
<v Aaron van Wirdum>making phone calls and then they told me to wait you know on a bench and I think

00:34:53.180 --> 00:34:57.580
<v Aaron van Wirdum>about 20 minutes later, the transaction actually confirmed. Then they started to

00:34:57.580 --> 00:35:01.980
<v Aaron van Wirdum>make more phone calls and eventually they said, okay, everything is good. You can

00:35:01.980 --> 00:35:07.220
<v Aaron van Wirdum>go. But we can definitely conclude that the merchant app does not show the

00:35:07.220 --> 00:35:11.440
<v Aaron van Wirdum>transaction at all. So it does not show the transaction in a way like a

00:35:11.440 --> 00:35:16.420
<v Aaron van Wirdum>transaction has been paid, but there's a problem because RBF or it just... it's

00:35:16.420 --> 00:35:21.320
<v Aaron van Wirdum>as if no payment has been made so i would say that's clearly sub-ideal because

00:35:21.320 --> 00:35:24.300
<v Aaron van Wirdum>like you said there are a lot of wallets that have rbf on by default

00:35:24.300 --> 00:35:29.460
<v Sjors Provoost>yeah and the problem of course with without rbf is you can't take it back

00:35:29.980 --> 00:35:33.640
<v Sjors Provoost>Or I guess you could cancel it, but it means that if you then decide, oh, let me

00:35:33.640 --> 00:35:37.720
<v Sjors Provoost>just pay in cash, you can't do that either because now you're paying twice. So

00:35:37.720 --> 00:35:41.940
<v Sjors Provoost>that's why on-chain payments, we've already decided many years ago, are just not

00:35:41.940 --> 00:35:45.660
<v Sjors Provoost>the way forward. And Lightning is much better for this type of in-person merchant

00:35:45.660 --> 00:35:50.120
<v Sjors Provoost>experience. So let's hope that they'll add that later. My guess is they would

00:35:50.120 --> 00:35:54.040
<v Sjors Provoost>because it's already in the user app somewhere. And I think everybody realizes

00:35:54.040 --> 00:35:55.160
<v Sjors Provoost>that Lightning is the way to go.

00:35:55.570 --> 00:35:58.990
<v Aaron van Wirdum>I'm assuming they're going to roll it out eventually. All I know is that right

00:35:58.990 --> 00:36:04.270
<v Aaron van Wirdum>now it seems like it's only on chain. It's possible, I guess, that it's some sort

00:36:04.270 --> 00:36:08.990
<v Aaron van Wirdum>of hidden feature again. You know, if you dig deep through the options menu or

00:36:08.990 --> 00:36:13.640
<v Aaron van Wirdum>whatever, maybe there's like a lightning option somewhere. But for sure, it's not

00:36:13.640 --> 00:36:17.880
<v Aaron van Wirdum>obvious. And for sure, merchants that I've encountered wouldn't have known that

00:36:17.880 --> 00:36:18.960
<v Aaron van Wirdum>if it was the case.

00:36:19.460 --> 00:36:24.120
<v Sjors Provoost>No. So basically, it's just on chain at this point in time and not very

00:36:24.120 --> 00:36:26.780
<v Sjors Provoost>compatible with RBF either. Yeah.

00:36:32.720 --> 00:36:36.920
<v Aaron van Wirdum>I just recalled something. So this is another bug I ran into is that you have

00:36:36.920 --> 00:36:40.860
<v Aaron van Wirdum>these QR codes, of course, if you need to make a payment. And usually you need to

00:36:40.860 --> 00:36:46.190
<v Aaron van Wirdum>make a very exact payment, right? Like it's a Satoshi precise amount. And then if

00:36:46.190 --> 00:36:51.410
<v Aaron van Wirdum>you don't pay the Satoshi precise amount, then it's going to be an error and the

00:36:51.410 --> 00:36:54.370
<v Aaron van Wirdum>payment is going to show us failed or something, you know.

00:36:54.550 --> 00:36:58.070
<v Sjors Provoost>Yeah, it depends on how picky the backend is, right? Some merchants have gone

00:36:58.070 --> 00:37:03.090
<v Sjors Provoost>pretty far in sort of dealing with user error because, for example, you might

00:37:03.090 --> 00:37:07.810
<v Sjors Provoost>have an item that's $1 and then they show you an invoice, you scan it with your

00:37:07.810 --> 00:37:13.030
<v Sjors Provoost>little wallet. And it says, oh, this is $1.01 because your wallet has a slightly

00:37:13.030 --> 00:37:17.030
<v Sjors Provoost>different exchange rate. And then you as a user might say, no, I want to send $1.

00:37:17.030 --> 00:37:22.370
<v Sjors Provoost>So you manually type $1. And then the server is smart enough to have some sort of

00:37:22.370 --> 00:37:26.670
<v Sjors Provoost>tolerance there. But not too much because then everybody starts to game it. So it

00:37:26.670 --> 00:37:29.590
<v Sjors Provoost>depends on how smart it is. But if it's not smart, then yeah, if there's one

00:37:29.590 --> 00:37:33.150
<v Sjors Provoost>Satoshi too much or too little, it's going to say, please send one extra Satoshi.

00:37:33.610 --> 00:37:37.670
<v Sjors Provoost>Or it's going to say, oh, you sent one Satoshi too much. You know, what do you want to do?

00:37:38.270 --> 00:37:42.490
<v Aaron van Wirdum>Right, right. Well, I mean, the reason I bring it up is because I've definitely

00:37:42.490 --> 00:37:47.280
<v Aaron van Wirdum>had this come up with the wallet. where the amount that was shown on the QR was

00:37:47.280 --> 00:37:51.360
<v Aaron van Wirdum>not the exact amount that was paid eventually. I should clarify maybe that

00:37:51.360 --> 00:37:55.900
<v Aaron van Wirdum>because I mentioned that I've not been able to make any payments. So to clarify,

00:37:55.900 --> 00:38:00.840
<v Aaron van Wirdum>I've not been able to make any payments since I copied the wallet to my own

00:38:00.840 --> 00:38:05.600
<v Aaron van Wirdum>phone. Before that, we were using the same wallet, essentially the same person.

00:38:05.860 --> 00:38:09.880
<v Aaron van Wirdum>And back then we made some payments that worked, like I mentioned, the Chivo to

00:38:09.880 --> 00:38:14.320
<v Aaron van Wirdum>Chivo. And also this one that I'm describing right now, that payment went

00:38:14.320 --> 00:38:18.760
<v Aaron van Wirdum>through, but the amount wasn't correct. After I copied it to my own wallet, it

00:38:18.760 --> 00:38:20.920
<v Aaron van Wirdum>hasn't been able, I've only been able to receive.

00:38:21.220 --> 00:38:23.080
<v Sjors Provoost>But you're saying there's some sort of rounding error?

00:38:23.540 --> 00:38:28.100
<v Aaron van Wirdum>Possibly some rounding errors. Who knows? Who knows? We can't look at the source

00:38:28.100 --> 00:38:32.300
<v Aaron van Wirdum>code. So who knows what the exact problem is? All we know is that the exact

00:38:32.300 --> 00:38:36.840
<v Aaron van Wirdum>amount that I was supposed to send was not the amount that was sent. And that was

00:38:36.840 --> 00:38:39.320
<v Aaron van Wirdum>causing problems with one of the ATMs, actually.

00:38:39.880 --> 00:38:43.720
<v Sjors Provoost>Yeah, that could cause some headache. Okay, so we've covered the user and the

00:38:43.720 --> 00:38:47.680
<v Sjors Provoost>merchant app. Maybe we can briefly still talk about the backend because we don't

00:38:47.680 --> 00:38:52.260
<v Sjors Provoost>know anything about it. But it's good to remind the listener that everything is

00:38:52.260 --> 00:38:58.220
<v Sjors Provoost>using a server or multiple servers. And we do not know who runs those servers.

00:38:58.560 --> 00:39:04.540
<v Sjors Provoost>We don't know how their hot wallet works, how their cold storage works, how

00:39:04.540 --> 00:39:09.840
<v Sjors Provoost>much is in it, etc. And this is a general problem with custodial services. And

00:39:09.840 --> 00:39:14.060
<v Sjors Provoost>even if they were to do a proof of reserves, we also know from the industry that

00:39:14.060 --> 00:39:19.360
<v Sjors Provoost>nobody checks it, or at least very few people check it. So I don't want to

00:39:19.360 --> 00:39:22.740
<v Sjors Provoost>necessarily blame them. I mean, the best way, of course, is to not use a

00:39:22.740 --> 00:39:26.420
<v Sjors Provoost>custodial service. But one of the things a custodial service does give you is

00:39:26.420 --> 00:39:31.360
<v Sjors Provoost>this super smooth exchange between fiat and Bitcoin. You know, especially

00:39:31.360 --> 00:39:35.280
<v Sjors Provoost>frictionless because it's just a number to database and you want a number to be

00:39:35.280 --> 00:39:39.860
<v Sjors Provoost>dollars or Bitcoin. It's one click of the button and it's changed. Which then

00:39:39.860 --> 00:39:43.040
<v Sjors Provoost>brings the question of whether that's really happening. If they're really

00:39:43.040 --> 00:39:46.220
<v Sjors Provoost>actually doing an exchange there, which means they're, you know, whether their

00:39:46.220 --> 00:39:51.620
<v Sjors Provoost>asset ratios are being updated. And if they really are, whether that creates some

00:39:51.620 --> 00:39:55.560
<v Sjors Provoost>sort of arbitrage where somebody could come in with millions of dollars and sniff

00:39:55.560 --> 00:40:00.670
<v Sjors Provoost>little bits out of the exchange rate because of the way it's subsidized. We'll find out.

00:40:01.350 --> 00:40:05.190
<v Aaron van Wirdum>Yeah. Okay. We're discussing the backend now. The obvious thing is we don't know

00:40:05.190 --> 00:40:10.190
<v Aaron van Wirdum>a lot about the backend at all. Like that's pretty far. What do we know? Not much.

00:40:10.590 --> 00:40:13.390
<v Sjors Provoost>No, again, there are things you can learn from reverse engineering. If you wanted

00:40:13.390 --> 00:40:18.950
<v Sjors Provoost>to, you can at least see what domains the app is communicating with. And then you

00:40:18.950 --> 00:40:23.290
<v Sjors Provoost>can look at domain registrars and see who owns these domains and who signed the

00:40:23.290 --> 00:40:28.230
<v Sjors Provoost>HTTPS certificate. Is that directly owned by some legal entity? Then you can look

00:40:28.230 --> 00:40:32.670
<v Sjors Provoost>up the legal entity and see if it's somewhat reasonably owned by the government.

00:40:33.520 --> 00:40:38.260
<v Sjors Provoost>You know, if it points to some entity in the Cayman Islands, then maybe you're

00:40:38.260 --> 00:40:39.020
<v Sjors Provoost>slightly more worried.

00:40:39.440 --> 00:40:40.480
<v Aaron van Wirdum>Right. Yeah, that's interesting.

00:40:40.700 --> 00:40:44.180
<v Sjors Provoost>But, you know, I would not put my life savings in an app like that unless I had

00:40:44.180 --> 00:40:48.380
<v Sjors Provoost>the answers to stuff like that. Like, okay, what happens if this entity has a

00:40:48.380 --> 00:40:53.280
<v Sjors Provoost>breach? You know, are they insured or not? That sort of stuff. Same with the

00:40:53.280 --> 00:40:56.500
<v Sjors Provoost>dollar balance, right? Because you don't know what's backing it.

00:40:57.060 --> 00:41:01.480
<v Aaron van Wirdum>Yes. I actually wanted to go to the ATMs real quick as well. The Chivo ATMs.

00:41:01.640 --> 00:41:01.690
<v Sjors Provoost>Sure.

00:41:01.700 --> 00:41:07.060
<v Aaron van Wirdum>Yeah. So the Chivo ATMs I've personally used a couple of times now. Sometimes

00:41:07.060 --> 00:41:12.980
<v Aaron van Wirdum>they work quite well. There are some confusing user interface things

00:41:12.980 --> 00:41:17.360
<v Aaron van Wirdum>going on, confusing user experience issues. Okay. First of all, it's not

00:41:17.360 --> 00:41:22.880
<v Aaron van Wirdum>Lightning compatible. There are no Lightning invoices on the atm it's just on chain

00:41:22.880 --> 00:41:27.380
<v Sjors Provoost>but there is Chivo to atm right because i think i saw people make a lightning

00:41:27.380 --> 00:41:32.280
<v Sjors Provoost>payment to a Chivo user wallet and then the user making a dollar payment to the

00:41:32.280 --> 00:41:36.880
<v Sjors Provoost>atm i guess and getting physical dollars out is that how it worked because there

00:41:36.880 --> 00:41:38.300
<v Sjors Provoost>were people showing on the twitter

00:41:38.300 --> 00:41:43.500
<v Aaron van Wirdum>i think so yes i think there's chivo to chivo atm payments that are basically

00:41:43.500 --> 00:41:49.210
<v Aaron van Wirdum>custodial payments custodial ledger entries i think I've mostly used the on-chain

00:41:49.210 --> 00:41:53.550
<v Aaron van Wirdum>payments and they have sort of a two-step process because they're going to wait

00:41:53.550 --> 00:41:58.830
<v Aaron van Wirdum>for confirmations. So you send the money, most of the cases at least, you send

00:41:58.830 --> 00:42:04.080
<v Aaron van Wirdum>the money. And then receipt is printed out with the code. And it says, once your

00:42:04.080 --> 00:42:09.480
<v Aaron van Wirdum>transaction has one confirmation, you can use this code to get the money out. The

00:42:09.480 --> 00:42:13.800
<v Aaron van Wirdum>most confusing thing about that is that it definitely waited for more

00:42:13.800 --> 00:42:16.200
<v Aaron van Wirdum>confirmations sometimes that I used it.

00:42:16.860 --> 00:42:19.720
<v Sjors Provoost>Okay, but that sounds like any other Bitcoin ATM.

00:42:20.100 --> 00:42:24.680
<v Aaron van Wirdum>Yes, I mean, it is. The ATM is pretty regular as far as, I mean, it's an ATM and

00:42:24.680 --> 00:42:28.220
<v Aaron van Wirdum>I think they work like other ATMs. They're just branded as Chivo mostly.

00:42:28.750 --> 00:42:32.790
<v Aaron van Wirdum>Although, like I said, I do think there's some Chivo to Chivo custodial thing in

00:42:32.790 --> 00:42:33.710
<v Aaron van Wirdum>the background as well.

00:42:33.950 --> 00:42:38.850
<v Sjors Provoost>And some noticeable bugs that suggest that it's not just that company because

00:42:38.850 --> 00:42:41.150
<v Sjors Provoost>they wouldn't make those mistakes if they've been around long enough.

00:42:41.430 --> 00:42:45.670
<v Aaron van Wirdum>Right. Yeah. About the bugs. Yeah, exactly. I've encountered some bugs myself

00:42:45.670 --> 00:42:51.330
<v Aaron van Wirdum>where I try to send Bitcoin and get some dollars out and it just wouldn't give me

00:42:51.330 --> 00:42:55.950
<v Aaron van Wirdum>the dollars. I've had that happen twice now for two different reasons. But I

00:42:55.950 --> 00:43:00.050
<v Aaron van Wirdum>think one of them was... essentially a hardware reason like the receipts the

00:43:00.050 --> 00:43:04.830
<v Aaron van Wirdum>printer was out of receipts or something like that however i also didn't get an

00:43:04.830 --> 00:43:08.470
<v Aaron van Wirdum>sms message even though i was supposed to get an sms message so several things

00:43:08.470 --> 00:43:13.450
<v Aaron van Wirdum>went wrong at once and then another time i already mentioned was because the

00:43:13.450 --> 00:43:18.230
<v Aaron van Wirdum>amount wasn't satoshi to satoshi compatible and then it didn't give the money out

00:43:18.230 --> 00:43:23.950
<v Aaron van Wirdum>either we've also heard the opposite example where someone i think bought

00:43:23.950 --> 00:43:29.200
<v Aaron van Wirdum>bitcoin essentially And then kept getting more and more money for a couple of

00:43:29.200 --> 00:43:30.660
<v Aaron van Wirdum>hours. Did you hear this?

00:43:31.060 --> 00:43:34.940
<v Sjors Provoost>Yeah, the story I heard was a famous Dutch podcaster. Let's not mention his name.

00:43:35.160 --> 00:43:35.520
<v Aaron van Wirdum>Right.

00:43:35.700 --> 00:43:41.540
<v Sjors Provoost>He put in some amount of dollars in the ATM. got on a plane, saw the

00:43:41.540 --> 00:43:45.260
<v Sjors Provoost>transaction come in on his Bitcoin wallet. It's like, this is great. Then landed

00:43:45.260 --> 00:43:50.060
<v Sjors Provoost>and saw the same transaction five times and then got on another international

00:43:50.060 --> 00:43:55.920
<v Sjors Provoost>flight and eventually got 36 transactions and tried to contact the president to

00:43:55.920 --> 00:44:00.160
<v Sjors Provoost>say, hey, let me know if you want this money back because we're not trying to rob

00:44:00.160 --> 00:44:02.400
<v Sjors Provoost>you. But yeah, that happened.

00:44:03.000 --> 00:44:03.740
<v Aaron van Wirdum>Yeah, that happened.

00:44:04.000 --> 00:44:07.900
<v Sjors Provoost>And that sounds like the kind of bug that any ATM operator that's been around

00:44:07.900 --> 00:44:13.020
<v Sjors Provoost>long enough. would not have because they would not be around. So that sounds like

00:44:13.020 --> 00:44:17.860
<v Sjors Provoost>there's some sort of integration between the Chivo app, perhaps, and the ATM

00:44:17.860 --> 00:44:21.760
<v Sjors Provoost>operators and something like Haywire in that integration.

00:44:21.980 --> 00:44:22.360
<v Aaron van Wirdum>Right.

00:44:22.640 --> 00:44:25.300
<v Sjors Provoost>Which is the kind of thing that can happen when you're doing a super ambitious

00:44:25.300 --> 00:44:29.260
<v Sjors Provoost>project and you've got five companies working together. And it's quite easy to

00:44:29.260 --> 00:44:33.580
<v Sjors Provoost>make a mistake where one program updates a database and says, you know, I've

00:44:33.580 --> 00:44:38.590
<v Sjors Provoost>paid. And then... For some reason, that database change doesn't get saved. And

00:44:38.590 --> 00:44:41.470
<v Sjors Provoost>the other side is like, oh, I should make this payment because it hasn't been

00:44:41.470 --> 00:44:45.250
<v Sjors Provoost>made yet. And it just keeps making the same payment. And conversely, money could

00:44:45.250 --> 00:44:50.070
<v Sjors Provoost>disappear if it's not recorded that, hey, I need to send out on this amount. But

00:44:50.070 --> 00:44:51.110
<v Sjors Provoost>those are very painful bugs.

00:44:51.710 --> 00:44:56.450
<v Aaron van Wirdum>Yeah. Okay. So I think we're coming up to the end of our episode. Is there

00:44:56.450 --> 00:44:58.210
<v Aaron van Wirdum>anything else you want to mention?

00:44:58.650 --> 00:45:02.730
<v Sjors Provoost>No, I think we've kind of gone through it. I would like to see people doing a

00:45:02.730 --> 00:45:07.450
<v Sjors Provoost>more systematic reverse engineering of what this app is doing. Because I think by

00:45:07.450 --> 00:45:11.410
<v Sjors Provoost>trial and error and looking at the blockchain and looking at more subtle

00:45:11.410 --> 00:45:15.610
<v Sjors Provoost>behavior, you can probably find out a lot more than what we were just guessing in

00:45:15.610 --> 00:45:18.470
<v Sjors Provoost>the podcast. I already proposed some experiments in our conversation.

00:45:18.990 --> 00:45:24.210
<v Aaron van Wirdum>Yeah, so I agree with that. I think this is sort of a first look kind of episode.

00:45:24.450 --> 00:45:28.450
<v Aaron van Wirdum>That's the best way to look at it. I did, for the listeners, just so you know, I

00:45:28.450 --> 00:45:33.350
<v Aaron van Wirdum>did try to reach out to at least one local hacker that I know has been doing more

00:45:33.350 --> 00:45:38.070
<v Aaron van Wirdum>experiments with the wallet. He did not respond in time for this episode. So we

00:45:38.070 --> 00:45:42.890
<v Aaron van Wirdum>are going a bit on my personal experience and memories and anecdotes. There's

00:45:42.890 --> 00:45:45.490
<v Aaron van Wirdum>definitely room for more thorough analysis.

00:45:45.950 --> 00:45:49.370
<v Sjors Provoost>Yeah, and maybe a fair warning to people who are doing that. Keep in mind,

00:45:49.410 --> 00:45:54.010
<v Sjors Provoost>there's such a thing as responsible disclosure. So if you find some behavior in a

00:45:54.010 --> 00:45:57.270
<v Sjors Provoost>wallet and you suddenly realize that you can make millions of dollars with it,

00:45:57.730 --> 00:46:01.910
<v Sjors Provoost>don't just go out on Twitter and demonstrate that because you shouldn't be doing

00:46:01.910 --> 00:46:06.280
<v Sjors Provoost>that. for moral reasons, and you shouldn't be doing that for staying out of jail

00:46:06.280 --> 00:46:10.860
<v Sjors Provoost>reasons. So, you know, just be a little bit careful with that. But again, I don't

00:46:10.860 --> 00:46:15.610
<v Sjors Provoost>even know if they have a responsible disclosure. email address that you can say,

00:46:15.930 --> 00:46:21.330
<v Sjors Provoost>dear Mr. Bukele or assistant, I found this issue that's making me infinite money.

00:46:21.510 --> 00:46:22.670
<v Sjors Provoost>Maybe you want to fix this.

00:46:23.250 --> 00:46:27.030
<v Aaron van Wirdum>Yeah. Well, final words, I guess I have already mentioned this halfway the

00:46:27.030 --> 00:46:31.490
<v Aaron van Wirdum>episode, but I'm just going to repeat it. I'm seeing a lot of excitement around

00:46:31.490 --> 00:46:36.430
<v Aaron van Wirdum>this project and a lot of Bitcoiners who really like this move by the government

00:46:36.430 --> 00:46:40.230
<v Aaron van Wirdum>and what they're doing and making Bitcoin legal tender. And I totally understand

00:46:40.230 --> 00:46:45.860
<v Aaron van Wirdum>that. At the same time, we are talking about the Chivo wallet, which is literally

00:46:45.860 --> 00:46:51.740
<v Aaron van Wirdum>a closed source, custodial, intransparent application that's pushed

00:46:51.740 --> 00:46:56.560
<v Aaron van Wirdum>by a government that's not really telling anyone where the money is or anything

00:46:56.560 --> 00:47:01.540
<v Aaron van Wirdum>like that. They're using taxpayer money to develop it. Like if we as Bitcoiners

00:47:01.540 --> 00:47:05.320
<v Aaron van Wirdum>cannot be critical of this, then I don't know what we can be critical of anymore.

00:47:05.600 --> 00:47:09.780
<v Aaron van Wirdum>The wallet is just not working very well. Unfortunately that's the only

00:47:09.780 --> 00:47:15.300
<v Aaron van Wirdum>conclusion I can draw at this point. I guess I can mention once again there does

00:47:15.300 --> 00:47:18.820
<v Aaron van Wirdum>seem to be a little bit of improvement if you're looking for a more positive

00:47:18.820 --> 00:47:22.660
<v Aaron van Wirdum>angle. I do think it's improving a little bit even though the transactions on my

00:47:22.660 --> 00:47:27.420
<v Aaron van Wirdum>own wallet are still not working. So that was sort of the first look at the Chivo

00:47:27.420 --> 00:47:28.260
<v Aaron van Wirdum>app. Sjors?

00:47:28.600 --> 00:47:30.160
<v Sjors Provoost>Yeah, I think that's all we've got, right?

00:47:30.380 --> 00:47:34.680
<v Aaron van Wirdum>That's all we've got. I think our next episode might be in person again. I think

00:47:34.680 --> 00:47:37.920
<v Aaron van Wirdum>we might be able to record our next episode in the Netherlands.

00:47:38.380 --> 00:47:38.820
<v Sjors Provoost>Exciting.

00:47:39.180 --> 00:47:43.080
<v Aaron van Wirdum>Although, I don't know what the restrictions are nowadays. Am I supposed to still

00:47:43.080 --> 00:47:46.620
<v Aaron van Wirdum>self-quarantine and these kinds of things?

00:47:46.940 --> 00:47:51.720
<v Sjors Provoost>Yeah, I believe the latest rule is because El Salvador, both El Salvador and the

00:47:51.720 --> 00:47:57.320
<v Sjors Provoost>United States are on the orange list, as we call it. So that means you probably

00:47:57.320 --> 00:47:59.300
<v Sjors Provoost>need to take a test before you get on the plane.

00:47:59.520 --> 00:48:00.660
<v Aaron van Wirdum>Well, that's for sure.

00:48:00.900 --> 00:48:06.620
<v Sjors Provoost>And then you, I believe you still have to quarantine. No, I don't think you have

00:48:06.620 --> 00:48:08.520
<v Sjors Provoost>to quarantine anymore. I think they changed that.

00:48:08.920 --> 00:48:09.160
<v Aaron van Wirdum>Great.

00:48:09.460 --> 00:48:13.060
<v Sjors Provoost>This depends on vaccination status. So maybe you don't want to disclose any of

00:48:13.060 --> 00:48:16.890
<v Sjors Provoost>those details. But you should look it up. There's lots of websites that will tell

00:48:16.890 --> 00:48:17.710
<v Sjors Provoost>you the latest rules.

00:48:18.190 --> 00:48:21.910
<v Aaron van Wirdum>All right. Well, Sjors, then I'll see you in the Netherlands soon.

00:48:22.290 --> 00:48:26.790
<v Sjors Provoost>Cool. See you soon. Thank you for listening to Bitcoin Explained, formerly known

00:48:26.790 --> 00:48:28.110
<v Sjors Provoost>as the Van Wirdum Sjorsnado.

00:48:28.410 --> 00:48:28.930
<v Aaron van Wirdum>There you go.

