Oct. 22, 2025

CD181: FRANCIS POULIOT - BULL BITCOIN SELF CUSTODY BULL WALLET

The player is loading ...
CD181: FRANCIS POULIOT - BULL BITCOIN SELF CUSTODY BULL WALLET

Francis is the Founder of Bull Bitcoin, one of the best bitcoin brokerage services. They recently launched a self custody mobile wallet on ios and android: Bull Wallet. This rip was earlier today, in person, in Lugano. We are both here for the PlanB Forum.

Francis on Nostr: https://primal.net/francis
Francis on X: https://x.com/francispouliot_
Bull Wallet:
https://wallet.bullbitcoin.com
PlanB Forum: https://planb.lugano.ch/planb-forum/

EPISODE: 181
BLOCK: 920238
PRICE: 929 sats per dollar

(00:00:00) Catching up from Lugano: old rips, 2019 memories, and lore

(00:01:07) Introducing Bull Wallet: goals, BDK under the hood, and UX vision

(00:02:21) Lightning lessons: LDK attempts, liquidity pain, and Phoenix tradeoffs

(00:04:38) Fee shocks and “just-in-time” channels: why Liquid entered the plan

(00:06:24) Liquid + Boltz atomic swaps: architecture, Rootstock notes, and standards push

(00:07:37) Designing for privacy and power users: Sparrow on mobile, Payjoin journey

(00:12:21) Data minimization in practice: no push, no cloud leaks, strict dependencies

(00:13:56) Shipping realities: iOS approval grind and cross‑platform necessity

(00:15:11) Secure versus Instant: Liquid framing, hype cycles, and collaborative custody

(00:19:13) The UX–compromise matrix: placing Liquid among trust models

(00:21:24) Auto‑swap safety rails: keeping Liquid balances modest by default

(00:24:26) Confidential transactions and buying flows: privacy wins via Liquid

(00:27:24) Swap providers and resilience: Boltz today, multi‑provider tomorrow

(00:31:05) Builders who ship: moving fast, potentially Ark or Spark in the future

(00:32:11) Why Ark: unilateral exits, pre‑confirmed states, and costs

(00:50:00) Ark tradeoffs without soft forks: watchtowers, refresh, and liveness

(00:57:15) Ark vs Liquid in Bull Wallet: timelines, reckless testing, and user defaults

(01:04:12) Payjoin, heuristics, and passive consolidation

(01:11:01) Consolidation strategies: Liquid swaps, CT, and fee‑aware UTXO management

(01:15:48) Lightning address UX with Liquid: directories, costs, and tiny payments

(01:17:10) Nostr as a wallet backend: zaps, contact book, and secure comms

(01:18:01) Multisig in practice: BitPay’s UX, Miniscript future, and mobile approvals

(01:20:19) Operator messaging and alerts: following npubs inside the app

(01:20:49) Core v30, OP_RETURN, and policy vs consensus

(01:31:09) Funding open source: OpenSats, private companies, and shipping culture

(01:35:15) Why open source keeps us sane: creativity, legacy, and closing notes



more info on the show: https://citadeldispatch.com
learn more about me: https://odell.xyz

00:00 - Catching up from Lugano: old rips, 2019 memories, and lore

01:07 - Introducing Bull Wallet: goals, BDK under the hood, and UX vision

02:21 - Lightning lessons: LDK attempts, liquidity pain, and Phoenix tradeoffs

04:38 - Fee shocks and “just-in-time” channels: why Liquid entered the plan

06:24 - Liquid + Boltz atomic swaps: architecture, Rootstock notes, and standards push

07:37 - Designing for privacy and power users: Sparrow on mobile, Payjoin journey

12:21 - Data minimization in practice: no push, no cloud leaks, strict dependencies

13:56 - Shipping realities: iOS approval grind and cross‑platform necessity

15:11 - Secure versus Instant: Liquid framing, hype cycles, and collaborative custody

19:13 - The UX–compromise matrix: placing Liquid among trust models

21:24 - Auto‑swap safety rails: keeping Liquid balances modest by default

24:26 - Confidential transactions and buying flows: privacy wins via Liquid

27:24 - Swap providers and resilience: Boltz today, multi‑provider tomorrow

31:05 - Builders who ship: moving fast, potentially Ark or Spark in the future

32:11 - Why Ark: unilateral exits, pre‑confirmed states, and costs

50:00 - Ark tradeoffs without soft forks: watchtowers, refresh, and liveness

57:15 - Ark vs Liquid in Bull Wallet: timelines, reckless testing, and user defaults

01:04:12 - Payjoin, heuristics, and passive consolidation

01:11:01 - Consolidation strategies: Liquid swaps, CT, and fee‑aware UTXO management

01:15:48 - Lightning address UX with Liquid: directories, costs, and tiny payments

01:17:10 - Nostr as a wallet backend: zaps, contact book, and secure comms

01:18:01 - Multisig in practice: BitPay’s UX, Miniscript future, and mobile approvals

01:20:19 - Operator messaging and alerts: following npubs inside the app

01:20:49 - Core v30, OP_RETURN, and policy vs consensus

01:31:09 - Funding open source: OpenSats, private companies, and shipping culture

01:35:15 - Why open source keeps us sane: creativity, legacy, and closing notes

WEBVTT

NOTE
Transcription provided by Podhome.fm
Created: 10/22/2025 20:34:17
Duration: 5792.767
Channels: 1

1
00:00:00.160 --> 00:00:05.299
What is up, freaks? It's Odell here. I got another in person rep this time from Lugano.

2
00:00:05.680 --> 00:00:06.580
Audio only.

3
00:00:06.960 --> 00:00:09.620
We got a good friend here, absolute legend,

4
00:00:09.920 --> 00:00:15.325
Francis. How's it going, Francis? I'm doing great, man. Thanks for having me. It's It's a pleasure. I've we haven't,

5
00:00:16.025 --> 00:00:19.005
have you ever been on Dispatch, dude? I've been I've been on

6
00:00:19.625 --> 00:00:21.485
the the Dispatch with Marty,

7
00:00:22.105 --> 00:00:25.485
I think, like, I don't know, like, six years ago or seven years. Oh, Marty's show. Right?

8
00:00:25.880 --> 00:00:29.020
I don't I don't remember. Oh, no. We did it together in 2019.

9
00:00:29.320 --> 00:00:36.140
At the Bitcoin conference The first week going on. San Francisco. Yeah. Oh my god. Okay. So we've gotten a lot done since then. Oh, yeah.

10
00:00:37.079 --> 00:00:50.085
That day was the day Marty found out he was having his first kid. I remember and then we got trashed on the roof. Yeah. I think we got trashed before the rip also. We were there. Yeah. During the rip too. And Bitcoin topped at 13 k that day. Yeah.

11
00:00:50.385 --> 00:00:52.590
And I told everyone to smash buy.

12
00:00:53.070 --> 00:01:02.850
And for two years, we were under 13 k, and everyone said I was a fucking idiot. Oh, well, who's the who's the idiot now? Now we're just a humble 10 x guy since then.

13
00:01:03.470 --> 00:01:06.690
Okay. So I got a couple topics for us. Let's just dive right in.

14
00:01:07.229 --> 00:01:08.050
First topic,

15
00:01:09.215 --> 00:01:13.395
you guys released the new self custody bull Bitcoin wallet. Yep.

16
00:01:14.415 --> 00:01:16.355
Fucking awesome. I've been playing with it.

17
00:01:17.135 --> 00:01:17.635
So,

18
00:01:18.175 --> 00:01:26.590
I mean, to the freaks that haven't used it yet, first of all, you can just you can download it in your favorite app store, Bull Wallet. Just search Bull Wallet, or you can go to wallet.bitcoin

19
00:01:26.990 --> 00:01:28.930
@wallet.bullbitcoin.com.

20
00:01:30.430 --> 00:01:32.690
But, what is the wallet? Why should people care?

21
00:01:33.310 --> 00:01:34.909
Yeah. So the wallet is,

22
00:01:37.095 --> 00:01:42.855
typical classic Bitcoin wallets is, is, is the core of it. So we're using BDK under the hood, the Bitcoin dev kit.

23
00:01:43.655 --> 00:01:47.515
I've been involved with the Bitcoin dev kit project for like almost like three years.

24
00:01:47.815 --> 00:01:49.815
Yeah, they're awesome. They're really awesome.

25
00:01:51.780 --> 00:01:59.480
What makes the bolt wallet I guess special or different or part of like a new wave of bitcoin wallet,

26
00:02:00.340 --> 00:02:05.880
which is by the way like one of the hot topics of this conference it's like that we call them like the next generation wallets

27
00:02:06.275 --> 00:02:11.735
is that actually originally I wanted to do an LDK wallet. Originally my goal was to have a full blown

28
00:02:12.115 --> 00:02:12.615
like

29
00:02:12.995 --> 00:02:13.495
Phoenix

30
00:02:13.875 --> 00:02:14.375
style,

31
00:02:15.075 --> 00:02:16.215
fully self custodial,

32
00:02:16.515 --> 00:02:19.655
like lightning note on your phone wallet. So that's actually

33
00:02:20.210 --> 00:02:20.870
how we

34
00:02:21.250 --> 00:02:24.150
started. Right. And I built we started to build on on LDK

35
00:02:24.850 --> 00:02:29.190
and then I got kind of like I got a little bit black build on lightning because of that because,

36
00:02:29.890 --> 00:02:39.125
like, lightning does a lot of things, like, really well. Like lightning is is really phenomenal, but there are things that you simply cannot abstract away with lightning.

37
00:02:39.825 --> 00:02:43.605
And you know, I don't have to go into the details, but it's, it's, it's got to do with,

38
00:02:44.145 --> 00:02:49.819
the liquidity management, right? Like the backup stuff, that's fine. Like running a node on your phone is fine. It's doable. It's just the light,

39
00:02:50.220 --> 00:02:54.640
the liquidity management. And, and, and also there's like, it's not just technical, there's like economic

40
00:02:55.020 --> 00:03:03.655
components to it. Like, let's say, all right, I'm a developer. I want to launch a wallet and to find an LSP, of course. Right? And imagine, like, you have a thousand users with a thousand,

41
00:03:05.875 --> 00:03:12.614
dollars worth of of channels. You have, a million dollars of liquidity that needs to be locked up by an LSP doable.

42
00:03:12.915 --> 00:03:47.970
But once you get to a 100,000 users or a million users, you're talking about a fuck ton of money. Anyway The cap the capital management's Yeah. So, you know, I'm like, alright. So the LDK wallet's not happening. So what if Really, Phoenix has been the only one who's too close to pulling it up. Fucking legends, man. Because what they're doing is, like, really, really, really hard. And also, I I I honestly didn't think that we were gonna be able to do what Phoenix did. Like, they're they're exceptionally good. And they're I mean, their nose, I I don't know how many millions of dollars is on their node right now. I'm pretty sure it's the biggest node on the network. I think Async is probably the biggest node. But I just feel like that's an important thing to just,

43
00:03:48.829 --> 00:03:51.225
iron in here because if the freaks are like me,

44
00:03:52.025 --> 00:03:55.485
I've run a ton of lightning notes, twenty four seven lightning notes in my life.

45
00:03:55.785 --> 00:03:58.205
I still run a couple mostly because,

46
00:03:58.985 --> 00:04:02.605
I need, like, twenty four seven uptime or whatever for certain tasks including,

47
00:04:03.065 --> 00:04:05.405
getting SATS. They support the show with SATS.

48
00:04:06.099 --> 00:04:11.080
But my go to wallet on a day to day basis has been Phoenix. Right? I take a single coinjoin UTXO,

49
00:04:11.700 --> 00:04:20.520
drop it a big a big UTXO. It works better with bigger UTXOs, drop it into Phoenix, and then I just make my payments as I need to. And now that the bull wallet's out,

50
00:04:21.104 --> 00:04:24.965
I find myself sitting there, I'm like, which one do I use going forward? Mhmm.

51
00:04:25.985 --> 00:04:38.520
Well, there because there's different it's a different trade off balance, but it it's filling the similar need for me, right, which is just I wanna top up my eSIM or I wanna send a quick lightning payment, and I could easily just open the bulldog and make the payment. So

52
00:04:39.400 --> 00:04:46.940
So Phoenix works now. The reason why I got black billed is actually because I was at the El Salvador conference in 2023 exactly during the first ordinal,

53
00:04:47.480 --> 00:04:50.325
fee wave and I'm onboarding a guy to Phoenix

54
00:04:50.725 --> 00:05:01.465
in El Salvador. And I'm like, I'm gonna send you your first payment. Right. Right? And then what Phoenix does is called the just in time channel. They will open a channel at the same time as the guy's receiving money. So I'm sending the guy $5.

55
00:05:01.525 --> 00:05:05.605
Instead of an unpaid transaction. Yes. But the fees were like a 175,

56
00:05:05.605 --> 00:05:16.479
I don't know, SaaS provider or something. So the fee to open the channel It was like $4 or something. No. Way more. Yeah. Way more. Like like $30 or something like that. Right? So so

57
00:05:17.099 --> 00:05:21.120
like the the pure Phoenix model works well economically,

58
00:05:22.055 --> 00:05:25.514
when the fees are low. I guess even right now where fees are basically zero

59
00:05:26.055 --> 00:05:29.034
it's still like 60¢ or something. Yeah yeah

60
00:05:29.335 --> 00:05:37.470
yeah so I'm like you know in my bed in the middle of the night and I'm just like oh my god like are we gonna have to do a custodial wallet? I'm, like, freaking out because,

61
00:05:38.010 --> 00:05:50.974
you know, for for people who, like, don't know me, I'm, like, you know, mister self custody. Right? So, like, you know No no custodial lever. No no custodial lever, and that's always been, like, my my North Star. It's, like, self custody at all costs. Like, everything I do is to support

62
00:05:51.275 --> 00:05:54.414
or facilitate self custody. And I'm like, how the fuck we're gonna do that?

63
00:05:54.715 --> 00:05:58.974
So that's when the idea of using the liquid network came in. Right? So,

64
00:05:59.675 --> 00:06:09.919
and and this and I think a lot of people have the same idea are pretty much around the same time. And that same time is literally, like, the ordinals span wave. So it's it's not a coincidence,

65
00:06:10.860 --> 00:06:12.400
because we all kind of, like,

66
00:06:14.300 --> 00:06:15.099
felt the same,

67
00:06:15.500 --> 00:06:21.995
felt the same kind of, like, problem that I was having with with the just in time, like, LDK, like, full lightning node model.

68
00:06:22.855 --> 00:06:23.255
And,

69
00:06:23.815 --> 00:06:28.955
yeah. So the idea was alright. So let's build a Bitcoin wallet that has a,

70
00:06:29.895 --> 00:06:35.370
Bitcoin wallet inside and a liquid network wallet inside. The thing with the Liquid Network is that,

71
00:06:36.410 --> 00:06:37.630
there there's no

72
00:06:38.090 --> 00:06:45.710
there's nobody else using it. Right? So there's no merchants using the Liquid Network. They're all using the Lightning Network. So somehow we needed to find a way

73
00:06:46.255 --> 00:06:52.735
to move value between the liquid network and whatever other wallet the person was using. And that's where this company came in called,

74
00:06:53.135 --> 00:06:54.195
Bolts. So Bolts,

75
00:06:54.735 --> 00:07:02.090
my fucking favorite company in Bitcoin, they're absolute legends. They're absolutely amazing. So what these guys did is they built an API

76
00:07:02.870 --> 00:07:26.235
that creates a non custodial atomic swap between various networks Yep. And Lightning. Between Bitcoin and Lightning, between Liquid and and Lightning, between Rootstock and Lightning, and now between arc and lightning. Yeah. Alright. So so liquid was the first iteration. So People don't realize rootstock is actually decently used by degen's in Latin America. Like They found that out when we went to Brazil. Rootstock has some

77
00:07:32.090 --> 00:07:36.750
think that was, like, something that I heard of, like, six years ago. It's a thing. It's yeah. Yeah. It's a thing. It's real.

78
00:07:37.289 --> 00:07:42.574
So yeah. So bull Bitcoin, it's a a bitcoin wallet and a liquid wallet. And then when you send and receive,

79
00:07:43.435 --> 00:07:59.030
there's a non custodial atomic lightning swap. And that's really It's like the moon, but with liquid. That's exactly that's exactly it's like it's like moon, but with liquid and without the retarded backup that, you know, system that Moon invented. Right. Just as a seed backup. Yeah. Yeah. And,

80
00:08:00.150 --> 00:08:01.050
like, for us,

81
00:08:01.590 --> 00:08:03.210
we are obsessed with standardization

82
00:08:03.590 --> 00:08:18.194
also, in the wallet. So even here, one of the reasons I'm here is to help kind of, like, figure out stuff with ARC to make sure that all the ARC wallets that are popping up, like, really quickly are are on the same standard. So we have we're here specifically to also partly build standards for ARC.

83
00:08:18.655 --> 00:08:22.490
We'll talk about ARC in a second. Let's continue on this wallet. Yeah. Yeah. Yeah. So,

84
00:08:23.289 --> 00:08:29.150
and then my goal you know, so, like, people know, man. I'm an OG. I'm like a cypherpunk. So

85
00:08:30.169 --> 00:08:47.024
the the the wallet that I I I build a product that I wanna use. Right? So I'm I'm at this point in my Bitcoin journey where I've done a lot of stuff and now I want to do something for me. Like, the wallet is a very ego it's a it's a fully ego driven project. Right? So first of all, I want to build something for me that I really want to use personally.

86
00:08:47.565 --> 00:08:49.964
I also kind of consider it to be almost like,

87
00:08:51.180 --> 00:08:53.500
performance art or something like that or like,

88
00:08:54.140 --> 00:08:57.680
I I want that to be like what people remember before. Like, like, I want that

89
00:08:58.060 --> 00:09:08.025
to be my legacy because the Bullbick One exchange will close one day, you know. It's it's a fiat business. It's literally an exchange is a fucking it's the most fiat business ever. All they do is deal with that. Hyperbitcoinization.

90
00:09:09.125 --> 00:09:14.425
We're not touching fiat. Yeah. Of course. And, like, an open, an open source bitcoin wallet will

91
00:09:14.965 --> 00:09:15.465
hopefully,

92
00:09:16.280 --> 00:09:26.860
like, outlast me and at the very least the code will always exist and people in a in a thousand years are probably gonna, you know, I'm gonna probably inscribe a copy of the source code on my tomb or something, you know, it's gonna be my legacy.

93
00:09:27.480 --> 00:09:29.820
So I wanted it to be kind of like

94
00:09:30.675 --> 00:09:41.335
very easy to use, but also super cyberpunk. So some of so like the concept of the wallet is to is to make it sexy and and UX friendly, but also have cyberpunk features inside it. Right? So,

95
00:09:41.955 --> 00:09:50.020
from, you know, my goal with the wallet, for example, is to is for it to be kind of like a Sparrow substitutes for mobile. Right? So imagine

96
00:09:50.640 --> 00:10:07.375
Sparrow is kind of like a gold standard of the desktop wallet because it gives you control. Yeah. We like Sparrow. Right? So so Sparrow is amazing because you can control everything. You have very good coin selection and labeling. You obvious of course you can connect your own nodes and of course with Sparrow you can connect your hardware

97
00:10:07.755 --> 00:10:14.970
wallet. Yeah. Right. So it's got the coin selection, it's got the hardware wallet, it's got your own nodes, they They have privacy features. They had Whirlpool in there.

98
00:10:15.670 --> 00:10:17.770
You can do operations with descriptors.

99
00:10:18.310 --> 00:10:22.090
You can update your port card for so it's like it's like a massive

100
00:10:22.470 --> 00:10:43.680
it's like a software individual toolbox. That's what Sparrow says. Piece of software that is my my all my projects and companies Yep. And my family relies on. Yeah. Yeah. Absolutely. Additional piece of desktop software. Uh-huh. Just like the best. It doesn't come No. No. No. Exactly. You know, and, like like, you have, like, Electrum, which is kind of there too, you know, but I personally use Sparrow just just because it's it's

101
00:10:44.640 --> 00:10:48.160
I've it showed Sparrow to my mom, by the way, and,

102
00:10:49.040 --> 00:11:02.625
she she finds she finds it very intuitive. Like Well, that's what's cool about it. It's like for a power user, it has literally everything you'd ever need. Yeah. But for the average person, they can figure it out and use it. And that's what I wanna do for mobile. That's what I wanna do for mobile. And that's the goal of the bull bitcoin wallet.

103
00:11:03.245 --> 00:11:15.170
And, you know, so some of the things that kind of, made us stand out, like, we were the first wallets to integrate, PayJoin v two. We were kind of like the reckless version of PayJoin. It's gonna get way better. Like, Pay PayJoin

104
00:11:15.710 --> 00:11:24.755
the the new version of the last, like, stable version of pay join, like, is is coming out. It it was pretty reckless to do that on mobile, to be honest. But it worked. Like, pay join actually did work.

105
00:11:25.855 --> 00:11:32.675
We have, like The pay join piece is still a little bit rough around the edges. Right? It it is. I mean trouble making It is. Yeah. Even in, like, test environments.

106
00:11:33.190 --> 00:11:34.490
And it's also incompatible

107
00:11:35.110 --> 00:11:39.770
with, like there's, like, breaking changes to the page on protocol, but we've literally just,

108
00:11:40.150 --> 00:11:46.490
they launched the version one point zero point zero of page on, like, last week. So page on is is is basically going to become

109
00:11:47.665 --> 00:11:50.405
stable and standardized starting basically now.

110
00:11:50.865 --> 00:12:23.435
So for example, the other companies that, like, Cake, for example, and Bull, Cake is the other wallet that makes us PayJoin. Yeah. Right? We were, like, on incompatible versions of page joins, so you we can actually Oh, so is that what you're working? Yeah. Yeah. Yeah. Because page join kept making these changes as well. The wall would detect that it was a page join compatible wallet. Yeah. It wouldn't make the transaction. Yeah. Yeah. Okay. And and and page join also has, like, a server component to it. And same with Wasabi. I was Wasabi is the other one that supports it, I think. Right? Yeah. But Wasabi I couldn't get it to work with Wasabi. Incompatible versions. Okay. Fair enough. So it was it was it was a little it was a little reckless.

111
00:12:24.214 --> 00:12:32.780
But yeah. So But it doesn't matter. It's not like any funds are lost. It just the transaction doesn't work. Right. Right. And, like, of course, I also wanted to have a privacy

112
00:12:33.160 --> 00:12:41.435
first wallet. And it's, like, people when people think about privacy wallets, they think, like, oh, so you don't have coin join? No. No. There's, like, there's other aspects to it. Like, so no push notifications,

113
00:12:41.895 --> 00:12:43.755
like zero data collection whatsoever.

114
00:12:44.695 --> 00:12:54.260
There's, like, all sorts of That's where Phoenix really falls flat. They do a lot of, like, the Yeah. So so we Edge Dev, iOS, Android checks where they're doing, like, push notifications,

115
00:12:54.640 --> 00:13:01.940
cloud backups. Yeah. No. And and the the mobile front dev team, specifically the ones that work on the wallet are are very strict. Very, very,

116
00:13:02.240 --> 00:13:03.840
very severe in terms of,

117
00:13:05.200 --> 00:13:08.740
like, dependency on on, like, servers and stuff like that.

118
00:13:09.335 --> 00:13:10.715
So, of course, like, now,

119
00:13:11.095 --> 00:13:16.615
well, now what we have. Okay. So what we have, so I have I've actually been using it for, like, two and a half years. Okay.

120
00:13:17.815 --> 00:13:19.575
We're on version 6.2

121
00:13:19.575 --> 00:13:20.075
now,

122
00:13:20.695 --> 00:13:21.435
but we,

123
00:13:21.895 --> 00:13:22.395
we

124
00:13:23.279 --> 00:13:25.779
came to a point where I was, like, comfortable

125
00:13:28.160 --> 00:13:33.620
promoting it. Right? I mean Right? I mean, we we actually got, like, 10,000 users just through,

126
00:13:34.080 --> 00:13:37.940
over the last two years literally not try like, literally not trying

127
00:13:38.535 --> 00:13:44.475
to to to push it because it was you know, there's bugs. Right? There's there's, like, no there's no, like,

128
00:13:45.575 --> 00:13:49.435
catastrophic lose your money bugs, but, you know, there's, like, shitty shitty UX bugs. Right?

129
00:13:49.975 --> 00:13:58.450
But now we reached a point where we're like, okay. We're we're ready to to start to start, like, commercializing it. So, yeah, what we recently announced was the

130
00:13:58.830 --> 00:14:00.350
the iOS launch.

131
00:14:00.670 --> 00:14:01.730
IOS was actually,

132
00:14:02.430 --> 00:14:04.930
very hard. Like, very hard,

133
00:14:06.110 --> 00:14:16.204
spiritually even. It took us a long time a long, long time to get iOS Apple to approve it. I have, like, 250 emails back and forth. Experience.

134
00:14:17.464 --> 00:14:20.444
Yeah. I almost gave up. Yeah. I almost gave up. Yeah. Yeah.

135
00:14:21.329 --> 00:14:27.510
So what else is there there to say about this? I think look. It's pain in the ass working with, Apple on the App Store.

136
00:14:28.370 --> 00:14:30.709
But if you want, like, an actual

137
00:14:33.185 --> 00:15:03.065
mass massively used wallet Oh, you gotta meet people where they are. And it needs to be on both because Yeah. From, like, a from a recommendation point of view, I mean, you've been doing this as long as me. Yeah. As soon as I have to ask, like, oh, we're using Android or iPhone and then recommend a different wallet for them, it breaks apart. Yeah. Yeah. For sure. Being able to say, like, download primal For sure. It just doesn't matter where it is or download bull wallet Mhmm. Is is absolutely key. Okay. So what I wanna talk about real quick is, so you're using liquid, it's like moon, the freaks know moon because I was showing moon like crazy,

138
00:15:04.085 --> 00:15:11.065
where I rest and but instead of with moon, I I rest, it sits on the liquid network. Mhmm. And then you're doing on demand swaps.

139
00:15:11.685 --> 00:15:12.745
First, a comment.

140
00:15:13.125 --> 00:15:14.825
I really like how in the wallet

141
00:15:15.399 --> 00:15:25.180
you say you have the on chain wallet which is secure you call it secure bitcoin and then instant payments which I think is just immediately intuitive it's like okay I'm not keeping my life savings in instant payments,

142
00:15:25.800 --> 00:15:27.660
I'm keeping that in the secure wallet

143
00:15:28.574 --> 00:15:42.240
and so I really like that framing. I think that you don't have to explain it to the user. A lot of people have passed it, like, called it, like, checking versus savings account. Mhmm. But where we're going, most people don't know what checking and savings accounts are. Right? So I think that's a really good frame. So good job on that.

144
00:15:43.040 --> 00:15:47.779
Liquid is something that for probably, like, ten years now, I've been

145
00:15:49.040 --> 00:15:50.339
I've I've I've,

146
00:15:51.520 --> 00:15:57.220
fallen into the hype cycle of liquid maybe four or five times. We're like, this is the moment that liquid is actually gonna be used.

147
00:15:57.845 --> 00:16:01.385
I feel like this might be it. Yeah. But I've been there before.

148
00:16:02.485 --> 00:16:09.225
The the big issue that people have with liquid, we've talked about this in the past, and I just wanna be clear with it, is it is

149
00:16:10.040 --> 00:16:15.500
a collaborative custody model. So it's a multisig federation. You can't you can't leave on demand.

150
00:16:17.079 --> 00:16:20.220
You you need permission to leave. You need if the bolt is down,

151
00:16:21.160 --> 00:16:27.355
you can't get out of liquid. How do you how do you think about that as like, you said, you know, you wanna reduce dependencies? Yeah.

152
00:16:28.135 --> 00:16:35.195
Does that keep you up at night? Like, do you have a bunch of users that are in liquid? Maybe they're not able to get out. How do you, like what are the mitigations there?

153
00:16:35.620 --> 00:16:41.000
This is this is probably my my favorite topic to discuss in in the entire world, and, I'm just gonna

154
00:16:41.620 --> 00:16:47.480
do a quick shout out to Roy from Greece, which which also is is is a is a

155
00:16:47.935 --> 00:16:51.394
very forward thinking person in terms of rethinking

156
00:16:52.014 --> 00:16:54.115
custody versus trustlessness. Right?

157
00:16:56.014 --> 00:16:56.595
So, technically,

158
00:16:57.694 --> 00:17:10.070
liquid is self custodial. Like, on a technical level, like, you own the LVTC assets. Right? But of course it's not you're self cussing the irony. It's like it's not trustless you know it's kind of like you know if you have if you have a tether

159
00:17:10.530 --> 00:17:13.830
on your I don't know whatever fuck like if you're in wallet

160
00:17:14.210 --> 00:17:16.550
right yeah and trust wallet you are self cussing

161
00:17:17.010 --> 00:17:22.085
tether but of course tether, the organization is the one at the end of the day, which is guaranteeing

162
00:17:22.465 --> 00:17:27.525
the peg. Right. Right. And the peg is guaranteed because tether will send you a fiat wire transfer

163
00:17:27.904 --> 00:17:29.284
in exchange for your USDT.

164
00:17:29.585 --> 00:17:36.620
Yeah. At some point, there is there is a a a redeemer of last resort. Right? I would go so far as to say, like, it's impossible to self custody,

165
00:17:37.559 --> 00:18:03.710
like, Tron or something. It's it's it's Because or or because it's just a centralized network. So at the end of the day, there's trust in Justin Sun. Right? Yeah. Yeah. And and there there's there's certainly not trustless. So the way that I see, liquid, I see it as a Bitcoin stable coin. Right. Kind of. Right? So so it's a stable coin. It's another coin which is backed one to one by Bitcoin and the job the job of the liquid federation is to guarantee the peg. Right. It's not and they guarantee the peg by custodying

166
00:18:04.410 --> 00:18:09.310
an amount of bitcoin which is equivalent to the amount of liquid bitcoin, right, in a multisig.

167
00:18:09.690 --> 00:18:14.030
So from a strict technical perspective, they're not custodying your bitcoin.

168
00:18:14.475 --> 00:18:17.934
They're guaranteeing a one to one peg between your liquid Bitcoin

169
00:18:18.395 --> 00:18:24.575
and and that is And uptime. They're guaranteeing peg and uptime. Right? And there actually is a legal distinction also here,

170
00:18:24.875 --> 00:18:32.070
where I don't think legally that liquid is a custodian. I think legally the the liquid network for and and that has to do with,

171
00:18:32.690 --> 00:18:33.350
you know,

172
00:18:34.770 --> 00:18:35.910
KYC regulation

173
00:18:36.370 --> 00:18:41.110
and how to, like, avoid that. So liquid actually, like, somehow has a has a very clever way

174
00:18:41.505 --> 00:18:42.465
to avoid being,

175
00:18:42.945 --> 00:18:46.805
there's no k y c a m l on liquid. Like it's, it's a blockchain, right? Quote unquote.

176
00:18:47.665 --> 00:18:52.565
But, the thing that I really liked about liquid is that it exists.

177
00:18:53.185 --> 00:18:56.385
Right. And that it works. Right. So,

178
00:18:57.450 --> 00:18:59.230
it's it's really easy to

179
00:19:00.970 --> 00:19:01.710
to criticize

180
00:19:02.330 --> 00:19:02.830
something

181
00:19:03.450 --> 00:19:11.529
and say that another model could be better, but the other model doesn't exist whereas the existing model works. And the way that I see it, there's

182
00:19:11.914 --> 00:19:12.654
so okay.

183
00:19:13.195 --> 00:19:18.414
So there is a scale here. Right? There's two axis. There's the y axis and the x axis.

184
00:19:19.034 --> 00:19:21.375
And the way I see it, there's a UX

185
00:19:22.154 --> 00:19:22.654
and

186
00:19:23.914 --> 00:19:24.414
compromise

187
00:19:25.860 --> 00:19:32.440
matrix. Right? And by compromise, I mean compromising on on core cyclical values of self custody, of privacy,

188
00:19:32.820 --> 00:19:39.080
of trustlessness, and permissionlessness. Right? So typically what a company will do is that they will compromise on the

189
00:19:39.554 --> 00:19:41.014
ethos in order to gain

190
00:19:41.315 --> 00:19:55.174
UX points. Yes. Right? That's and it's it's almost like and think think of, like, the the coin bases and the big pays and all of these, you know, people, they they they very quickly compromise to gain, marginal UX points. They're the UX. Yeah. Right? Whereas

191
00:19:55.850 --> 00:20:00.270
I I have and there's, like, these dots on on the matrix where

192
00:20:00.650 --> 00:20:24.780
I think what what what I wanna do is I have a certain level of compromise over which I will not walk the line, and I need to stay under this compromise level, but I wanna increase my UX points under this compromise level. It's hard for the freaks to see that because I'm literally waiting with my hands right now and I'm like trying to like trying to make you imagine a chart. But, but liquid is, for me, orders of magnitudes

193
00:20:25.720 --> 00:20:29.500
more secure than, like, was it Satoshi? Right. And,

194
00:20:29.880 --> 00:20:30.540
you know,

195
00:20:31.400 --> 00:20:34.540
orders of magnitude more secure than cash in,

196
00:20:35.245 --> 00:20:37.424
orders of magnitude more secure than FEDI,

197
00:20:37.725 --> 00:20:38.225
and

198
00:20:38.924 --> 00:20:39.424
now

199
00:20:40.365 --> 00:20:44.304
and it exists and it works. Okay? So, I'm not Maybe not FEDI.

200
00:20:44.765 --> 00:20:55.650
I mean, technically technically what the what the FEDI rate. This product How it's implemented the federate. Right? So the thing is how it's implemented actually makes a difference. Right? So technically, you could have you could have, like, a FETI

201
00:20:56.110 --> 00:20:57.250
that has 15

202
00:20:57.790 --> 00:21:03.090
very professionally run Right. We just don't have that yet. We just don't have that yet. Right? So again, like, liquid exists.

203
00:21:03.625 --> 00:21:04.125
But,

204
00:21:06.664 --> 00:21:07.485
I obviously

205
00:21:08.105 --> 00:21:15.645
my fear with using the wallet was that people were accidentally gonna confuse liquid with Bitcoin. Yeah. It's it's really hard to to

206
00:21:16.345 --> 00:21:16.845
not

207
00:21:18.290 --> 00:21:20.390
cognitively overwhelm a person,

208
00:21:20.770 --> 00:21:45.965
but also not mislead them at the same time. It's very, very difficult. Yep. Right? It requires a lot of finesse in in UX. And thank you for saying, I actually spent a lot of time trying to figure that one out. It was good. Instant payments versus secured Bitcoin. And, you know, like, a common balance, but also two separate balances that I have to look at. It's it's it's tough. So one of the things that I did, is the auto swap. Yeah. I think the auto swap is is the fucking greatest feature of the bull bitcoin wallet. As soon as the auto swap is a million sats,

209
00:21:46.420 --> 00:22:15.740
by default, and then as soon as you reach a million sass on liquid, the next time you open the wallet, it will auto swap into the secret into bitcoin on chain. So that there's, like, a mechanism to prevent people from accidentally Interesting. Because you're not you're not really supposed to have more than $500 in a liquid wallet or like a thousand or maybe like a couple thousand. If you're I don't know. Depends on what you're spending, you know? Yeah. Depends. What it it should real the hard part is is it's like a percentage of your stack. Yeah. Of course. Of course. So it's on a case case by case basis. Right? And, like, you know,

210
00:22:16.140 --> 00:22:22.160
if if you're like a rich guy, you know, and you're spending Bitcoin, you know, I I spend, thousands of dollars of Bitcoin a month,

211
00:22:22.700 --> 00:22:27.520
you know. So you have 10 k in the liquid wallet. No big deal. You Yeah. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. Big deal. Like

212
00:22:28.595 --> 00:22:38.055
it's it's it's it's my my monthly budget for, like, groceries and my rent. But I like that auto swap concept. Yeah. I mean, in general, this is also what I've been pushing for in the Casio space. Yeah. It's like,

213
00:22:38.435 --> 00:22:41.015
you use Casio for convenience Yeah. But then

214
00:22:41.555 --> 00:22:44.280
move the user into a more secure setup automatically.

215
00:22:44.600 --> 00:22:47.180
Yeah. So we need to make choices for the user,

216
00:22:47.640 --> 00:22:52.940
and I know it's kinda confusing but defaults matter and, like, these things matter because one of the reasons why

217
00:22:54.360 --> 00:22:57.340
I one of the reasons why both Bitcoin is noncustodial

218
00:22:57.720 --> 00:23:02.345
in the first place is is because, you know, companies that are like custodial Bitcoin exchanges, they're gonna say,

219
00:23:02.645 --> 00:23:12.985
yeah, but we're encouraging people to withdraw to a self custody wallet, but they don't. They don't. They just don't. They just leave it in the self in the custodial wallet. So that's I I didn't want that to happen with liquid even though I think liquid

220
00:23:13.460 --> 00:23:25.560
is secure enough for me to be able to sleep at night. The auto swap thing, it's like, okay. Now I'm now I feel really comfortable because, like, I know that the worst that can happen to a user is that they lose, like, a million sats,

221
00:23:26.375 --> 00:23:33.975
which is, like, not a trivial amount of money, but also, like, you know, you'll you know, it's It's not the end of the world. It's not the end of the world. You can call your way out of that. Yeah.

222
00:23:34.375 --> 00:23:34.875
So

223
00:23:35.495 --> 00:23:47.250
and Liquid has, And they probably won't anyway. Like, Liquid one of the biggest things Liquid has going for is just what, like, ten years, twelve years of uptime and reputation. It's relatively well organized also. Like like, Liquid is not it's not

224
00:23:47.630 --> 00:24:02.165
and there's nothing wrong with, like, a bunch of dudes doing that in their basement. There's nothing wrong with that. That that's cool. That's great. But but Liquid actually has you know, we have committees, we have boards, we have It's institutionalized. It's institutionalized and it's it's a little bureaucratic. It's a little annoying, actually,

225
00:24:02.485 --> 00:24:05.945
because it's it's kind of bureaucratic. And then you have Blockstream as a company

226
00:24:06.405 --> 00:24:12.250
which doesn't control Liquid, but Blockstream, I would say, is kind of like the secretary of of Liquid. So Blockchain,

227
00:24:13.510 --> 00:24:25.690
they will, like, you know, send you, you know, calendar invites to, like, the meetings and stuff like that, you know, and, like, they make sure, like, the functionaries and everything Yeah. Are are talking to each other when it's time to update the software and that kind of stuff.

228
00:24:26.285 --> 00:24:32.625
But I'm not satisfied with liquid of course. Like liquid, I don't want bitcoin. I don't want liquid to be the model of bitcoin, of course. So,

229
00:24:33.485 --> 00:24:35.585
there is one thing interesting with liquid,

230
00:24:35.885 --> 00:24:42.690
which which I kind of like discovered is that when you're buying bitcoin Yeah. You should always, regardless of the amount,

231
00:24:43.150 --> 00:24:45.330
I think you should you should buy them on Liquid.

232
00:24:45.870 --> 00:24:56.385
Liquid has a very nice feature called confidential transactions. The reason we don't have that on Bitcoin is that it doesn't scale at all. It's it's a very large transaction in size, like, 6,000 bytes per transaction.

233
00:24:56.765 --> 00:25:06.625
But, of course, the benefit of centralization with liquid is also that, you get scale, you get low fees, which you obviously, that's the the the the reason why Bitcoin is is so amazing.

234
00:25:07.860 --> 00:25:14.200
It's that it it's decentralized and that's why Bitcoin doesn't scale because if you scale Bitcoin by, like, increasing the block sizes,

235
00:25:15.140 --> 00:25:18.600
you centralize Bitcoin. Liquid doesn't have that Liquid is centralized

236
00:25:18.900 --> 00:25:28.085
by default so you can do stuff on Liquid that makes it scale. And a lot of people start using liquid and blocks are We'll just fucking increase the block size. You know, it's fine. It's it's it's a 15 functionaries.

237
00:25:28.465 --> 00:25:35.284
Will send an event invite and then you guys We'll just we'll just run this off fork. You know, whatever. We'll run the hard fork or whatever. It's fine.

238
00:25:36.059 --> 00:25:38.320
But it has confidential transactions. So imagine,

239
00:25:38.700 --> 00:25:54.705
what you wanna prevent when you're buying Bitcoin is you wanna you wanna you wanna minimize your your on chain traceability and it's it's not it's not like, you know, a fuck the state thing. It's also like I don't wanna get the kidnap thing and I don't want people to know how much money I have thing and I when I go to the store and

240
00:25:55.085 --> 00:25:56.225
I'm paying for coffee,

241
00:25:57.005 --> 00:26:05.460
you know which doesn't happen on lightning but like I don't want the coffee shop owner to like know how much bitcoin I have or if I buy like I don't know a used motorcycle at the store like

242
00:26:07.940 --> 00:26:13.159
like, I don't wanna spend from my stash and the guy seeing that I have, like, you know, 10 bitcoins in my wallet. Yeah. The example I always use is, like, your boss shouldn't know

243
00:26:13.700 --> 00:26:23.805
what you're spending your salary on Of course. And and and the guy you're buying a sandwich from shouldn't know your salary. Exactly. These are basic financial privacy primitives that you understand.

244
00:26:24.105 --> 00:26:27.325
So if you receive if you get paid with,

245
00:26:28.105 --> 00:26:31.645
either liquid directly or the bolt swap like lightning to liquid,

246
00:26:32.220 --> 00:26:34.559
you end up with funds in your liquid wallet, whatever.

247
00:26:34.860 --> 00:26:36.559
When you swap that to,

248
00:26:37.020 --> 00:26:59.665
your secure Bitcoin wallet like the on chain wallet, there is no more on chain trail Right. Between the funds that end up in your Bitcoin wallet and the funds that you got paid from. So it's kind of like the way that people would, like, swap to Monero or something. Right? You know, it's like, oh, yeah. I will. You swap to Monero and come back to Bitcoin. Well, that's kind of like what you can do with liquid. You can swap into liquid and swap it back. But in both situations, you have a like, it's not perfect. There's a timing analysis

249
00:26:59.970 --> 00:27:01.570
issue and stuff. Right? Like, they see

250
00:27:02.130 --> 00:27:15.190
Yeah. Maybe that changes as more people use it. But right now, as as there's less people using it. Well well, the thing with is with confidential transactions, you don't see the amounts on the liquid chain. So you can you can see that a transaction happens on liquid and Bitcoin

251
00:27:16.065 --> 00:27:34.980
within a Bitcoin block, kind of, but you can't match them because you can see the the amount of What I'm saying is Boltz does more volume, it's probably better. Right? Yeah. Yeah. Yeah. Yeah. And because if you're the only one doing it in Of course. Ten minute period or something, then it doesn't have they see a liquid transaction going to a bulk wallet and then you see because the addresses aren't blinded, only the amounts.

252
00:27:35.440 --> 00:27:45.525
The amounts and the asset type. Right? So if someone's you can't tell if it's USDT or if it's Bitcoin and you can't tell what the other is. Like Samsung's video. Whatever. Yeah. One of those shit coins on liquid.

253
00:27:45.905 --> 00:28:08.320
So liquid liquid is not perfect. The ecosystem is not perfect. There's, like, of of course, there's, like, points of failure, which is, like, you know, bolts is one of the two or three swap companies that are doing so. Bolt's open source. Can't you run this one provider too? I can definitely run the swap provider. Is there is that something you're considering? That's kinda I was I was a leading question when I said to you, like, like, your users would be not like, if Bolt goes down,

254
00:28:08.940 --> 00:28:17.685
then I'm stuck in liquid for I'm I'm I'm I'm confident there's gonna be a bunch of anonymous people running running. Yeah. And so do you imagine in the wallet you'll allow

255
00:28:18.065 --> 00:28:22.405
a switch provider? A 100%. I think that the reason why right now we are,

256
00:28:22.785 --> 00:28:27.125
just using Bolts. So right right now there's like one Bolts server by the phone which is the Bolts one.

257
00:28:27.820 --> 00:28:43.805
There well, there's two reasons. The first one is because, I love these guys, and they're making money from the swaps. Yeah. Right? And, like, Bold Bitcoin doesn't need to make money from swaps. And they've done a lot of proof of work. Right. Like, good operation. Yeah. Like, we make money from the exchange. So, like, I'm not I'm not trying to I'm not trying to, like, milk revenue from the wallets.

258
00:28:44.825 --> 00:29:15.625
I I make way, way, way more money on the exchange than anything I could do with the wallet. And the other reason is that it's not trivial to run a bolt server. Right? It's like it's it's it's just running a power lightning node is a full time job and and they're doing a great job. But definitely in the future kind of like And it's kind of the same LSP problem. Right? It's a capital constraint problem. It's a little bit easier. But it's Oh, yeah. You need you need you need you need you need you need liquidity to run, like, a bold server and you need to be able to move that liquidity automatically quickly. You need scripts. You need, like, engineers to, like, manage all that. So it's not trivial,

259
00:29:16.005 --> 00:29:24.540
but it's also not it's also not, like, magic, you know? It's not anybody that's motivated enough and that, like, is running a power lightning node, like,

260
00:29:25.160 --> 00:29:38.595
could could run like a bolt server. And in the future, of course, what you're gonna see is you're gonna see a bunch of different bolt servers and maybe even a bolt server discovery mechanism, kind of like that's one of the things that Wasabi did that I thought was,

261
00:29:39.535 --> 00:29:52.515
an ordinator discovery. And and by the way, just so you know, that was a bounty on Nasr that I paid for. Yeah. That was my that was my for your service. Yeah. Yeah. Yeah. That that was my my bounty that actually, Cooks ended up implementing in Nasr, which is a coordinator discovery service,

262
00:29:53.270 --> 00:29:55.210
where, you know, when you start up the wallets,

263
00:29:55.909 --> 00:30:13.815
if you have people that are running coordinators anonymously over Tor, the problem is, like, how do you market your anonymous service without dock doxing yourself? Well, you can just announce it on and your clients can just get all these announcements. And you have the UX problem just like this coordinator do I use? Yeah. Yeah. Yeah. From the user perspective. Yeah. Of course. And that's that's,

264
00:30:14.295 --> 00:30:19.590
because the coordinator can lie about whatever they're saying. You know? It's it's it's not what it's it's it's we're

265
00:30:20.370 --> 00:30:22.389
what we're doing is we are moving

266
00:30:22.850 --> 00:30:28.389
on the compromised scale to lower and lower and lower compromise while maintaining the UI. Lower trust,

267
00:30:28.769 --> 00:30:37.375
but pushing it as far as possible to the UX. Right. Yeah. Yeah. Yeah. Which is a problem we've had in space. It's either one extreme or the other. It's like either super trusted with good UX

268
00:30:37.855 --> 00:30:46.195
Yep. Or very sovereign cypherpunk and horrible UX. And we need a bunch of options in the middle. Yes. Yes. There is there is some there is some degree of compromise

269
00:30:46.655 --> 00:30:48.115
that you have to make, but

270
00:30:48.600 --> 00:30:55.340
what our job as so there's there's two types of cypherpunks. Okay? There's the there's the intellectual cypherpunks and there's the, like,

271
00:30:56.360 --> 00:30:56.860
commercializing

272
00:30:57.240 --> 00:31:12.235
cypherpunks. And that's why, for example, I love Grease, I love arcade, I love golds, is because, like, we we fucking we ship we fucking ship products. Shit toned crap out. We we ship products that people use and, you know, we change our products over time. We improve them over time.

273
00:31:13.175 --> 00:31:15.655
You wanna talk talk about ARC? Yeah. So,

274
00:31:17.160 --> 00:31:17.640
just,

275
00:31:18.040 --> 00:31:27.100
real quick, what did I have there? Bolts. Yeah. Let's let's talk about arc because so so we're talking about liquid. We're using liquid here, and two things have come

276
00:31:27.640 --> 00:31:29.900
two new projects have started shipping.

277
00:31:31.294 --> 00:31:33.315
And I'm right there with you that I

278
00:31:34.095 --> 00:31:37.075
from a from a product focus point of view, like,

279
00:31:37.615 --> 00:31:43.154
fuck hype. There's, like, there's so much bullshit hype in this space for, like, if for the last ten years,

280
00:31:43.600 --> 00:31:57.059
if I focus on every white paper that came out, I would have no time to actually get anything done. So I really only start paying attention to something when it's actually shipping, when it's actually usable. Right? And so the two things that have appeared is ARC and Spark.

281
00:31:57.705 --> 00:31:59.645
Yesterday, we had ARC Day here.

282
00:32:01.705 --> 00:32:07.245
How are you thinking about those two things, and then how do you how do you think about those two projects in relationship

283
00:32:07.784 --> 00:32:11.410
with Bold and Liquid and going forward and whatnot? Right. So,

284
00:32:12.210 --> 00:32:13.990
Arc is the technology

285
00:32:15.010 --> 00:32:17.110
that gets me the most excited

286
00:32:18.130 --> 00:32:20.150
of of anything I've seen in Bitcoin

287
00:32:20.530 --> 00:32:21.030
since,

288
00:32:23.105 --> 00:32:30.005
look, I'm gonna say probably since lightning. I mean, there's other stuff that gets me excited, like silent payments, not and not for example. Like, there's there's stuff

289
00:32:30.305 --> 00:32:31.685
that we've done in Bitcoin,

290
00:32:32.065 --> 00:32:39.570
like, that that got me really excited. Something that okay. Before I get into ARC, actually, because once I get into ARC, I'm I'm gonna go deep into ARC. But, like,

291
00:32:40.190 --> 00:32:41.809
there's stuff like silent payments,

292
00:32:42.269 --> 00:32:48.130
I think is is a phenomenal piece of technology. I think what we're gonna do at Bull with silent payments is gonna be fucking dope.

293
00:32:49.505 --> 00:32:51.445
Silent what's the problem with painting

294
00:32:52.065 --> 00:32:52.885
with samurai?

295
00:32:53.265 --> 00:33:02.405
The problem with painting is that they had a a there's there's two. The bit, I was gonna say. Yeah. The oh, fuck. I I forgot the name of the bit. The one that they were using was, like, on chain inefficient.

296
00:33:02.940 --> 00:33:14.960
And 47. Bit 47. And then the When there was a there was a transaction in and off return. Yeah. Timely. Right. In and off return that that set up the pairing between the two. So you had at least one extra transaction.

297
00:33:16.135 --> 00:33:30.155
And the Pay Name Server was a centralized server. The the naming so like you got a code Yes. Right? You had a one time use code which didn't require a server. Yep. But if you were gonna pay to, like, sleepy moose or something, that was actually centralized server that was connecting the code to the Yes. Oh,

298
00:33:30.470 --> 00:33:38.010
I remember. Just before we move on real quick, on the Bolt side, I think it's important for users to realize that the coolest part about Bolt is

299
00:33:38.390 --> 00:33:45.450
you're trusting them with uptime. So if they're down, then you can't make a transaction, but you're not actually trusting them with with funds.

300
00:33:45.915 --> 00:33:54.815
If if the transaction fails, you don't lose any money. They never actually take custody of the funds. So both on demand atomic swap, which is really, really cool and very different from, like,

301
00:33:56.315 --> 00:34:08.330
shape shift or side shift Oh. Different instant A 100%. Seen in the past. Past. Both is fucking good because you have you have what's called a lock up transaction, which is basically like if the an atomic swap is is something that's like

302
00:34:09.510 --> 00:34:30.970
that that does not exist before Bitcoin. Right? That is a very new financial technology which is, you know, when you're buying drugs from someone, you know, you hand over the weed and I hand over you the cash. Like, we can't atomically swap swap the weed from the cash. Someone has to send the money first. Whereas an atomic swap, if one of the payments fails, the entire transaction doesn't fail. Like, both payments need to be successful.

303
00:34:31.670 --> 00:34:33.290
So so that's, like, that's great.

304
00:34:33.910 --> 00:34:45.605
Okay. So silent payments, imagine if It's for back. Yeah. Imagine if we had a decentralized directory for silent payments. Right. Well, we have that with, you know, l n u r l. Yeah. It's Noster. Right. Noster is your directory. Yep. So,

305
00:34:46.325 --> 00:34:47.625
I'm not I'm not, like,

306
00:34:48.244 --> 00:35:15.685
I hope nobody does that before me because I won't be the first one to do that. But I did put it up on GitHub, of course, what you're gonna do. What we're gonna do is sign in payment directory on Master. Right. Right. Master enabled open contact book. What I wanna do is I wanna have the sexy fucking Cash App UX with Cypher for blank. And part of the sexy fucking Cash App UX is that I send money to at Odell. Right. Right? I'm not sending money to, like, SP 1212 or whatever. And I think specifically it's probably a combo of silent payments for on chain Yeah. And then bolt 12

307
00:35:15.985 --> 00:35:26.170
for lightning. Yeah. So, and you can even put, like, a native arc You can put a native arc address in there. You can put, The the the the one thing that I don't like about Master is that,

308
00:35:26.890 --> 00:35:33.805
it's it's too lightning focused where people still use on chain. I wanna do basically, I wanna do on chain zaps. Right? So Alex Gleeson,

309
00:35:34.345 --> 00:35:41.005
the guy who booked it social for chain, and now he's working on, like, AI and Master stuff, he released a spec for

310
00:35:41.464 --> 00:35:44.605
on chain zaps. Well, did I But it's a reused address.

311
00:35:44.920 --> 00:35:52.540
Oh, well It's not a silent payments. It's a reused address. That's the thing. Like, don't don't we're we're past that, you know. We're we're past the thing with silent payments,

312
00:35:53.400 --> 00:35:55.260
is that it's actually hard to execute.

313
00:35:55.560 --> 00:36:06.845
It's really difficult to to implement. Right? That's why nobody has done it. Well, that's why I kinda like that's that's why I kinda like this reuse status because it's very simple. And also, like, for public zaps, there are there's no privacy anyway.

314
00:36:07.705 --> 00:36:19.539
So it's, like, not that worst privacy to go. You you you can have you can have that in my post, it, like, says France has zapped, you know, 2,000 zaps or something. Sure. But we can we can have zaps that don't reveal the TXID.

315
00:36:19.920 --> 00:36:32.625
Of course. Yeah. Right. That's strictly better. Yeah. Yeah. Yeah. That's strictly better. So that's what I wanna I I don't wanna I I don't wanna go back, you know. So I I want I wanna try to push it forward, but, it's hard. And that that's why, for example, I gotta I gotta give a shout out to Cake.

316
00:36:33.405 --> 00:36:34.625
You know, Cake,

317
00:36:35.565 --> 00:37:05.335
Shitcoin wallet, it has it has Litecoin, it has Monero, it has all sorts of crap in it, but they have shipped. They ship, and they have shipped silent payments and Yeah. I have Seth on the show all the time, and I get so much shit for it. He's great. I love these guys. But I've I've historically given them a ton of shit for Bitcoin stuff. I think it's a distraction. They are kind of stuck in the tech tech tech tech tech debt world where it's like Yeah. They already have Nano users in shit, so it's hard to get them off the platform. But on the Bitcoin side, they ship like crazy. Yeah. Yeah. Yeah. Yeah. So, yeah, so silent payments. The other thing that I've,

318
00:37:07.029 --> 00:37:12.730
I don't wanna get too deep in that because that that's gonna be a hard pill for swallow for a lot of people. We did actually do a very,

319
00:37:14.230 --> 00:37:14.730
advanced

320
00:37:15.190 --> 00:37:16.890
Bitcoin wallet backup protocol,

321
00:37:17.349 --> 00:37:26.575
which is loosely based on the Photon SDK concept, which came out about five years ago. Hey. Let's talk about it real quick. Okay. Because I think cloud backups are actually

322
00:37:27.455 --> 00:37:29.714
once again, you're pushing the UX sovereignty

323
00:37:30.015 --> 00:37:34.115
trade off bounce. Did you try the encrypted backup in bulk? Have you had It doesn't work on iOS.

324
00:37:34.430 --> 00:37:43.250
Oh, it doesn't? Alright. Okay. You didn't hear that freaks. We're gonna fix that. Okay. So I've been I've been meaning to give you that feedback. Alright. Okay. So here's the here's here's the TLDR.

325
00:37:44.510 --> 00:37:53.994
We wanna make something that's easy to use, that's secure and that's very difficult. If you if you encrypt a Bitcoin wallet backup with a user generated password,

326
00:37:54.535 --> 00:38:09.089
you will get backed. Right? So you think you have a good password, you think your passphrase, you think your big 30 nine passphrase is good because it's fucking 12 characters? It's not. It's brute forcible. It it it really is. So some kind of like an Apple user, anyone who has access to iCloud Yes. Just

327
00:38:09.789 --> 00:38:15.250
try a budget and passwords to OneWorks, has a computer do it. Yeah. That's what it brute force. Because if I if I take

328
00:38:15.625 --> 00:38:34.859
the physical possession of your encrypted backup file, there's no rate limiting Yeah. On the encryption. Like, it's not like the pin on your phone, like, where there's rate limiting. There's a secure element stopping. Yeah. Yeah. Exactly. If I have the physical backup, I can brute force the shit out of it and I will. And there has been a research of of people brute forcing bit 39 and you think

329
00:38:35.880 --> 00:38:37.180
the the the amount

330
00:38:38.040 --> 00:38:49.655
of generating compute enough to to brute force a password is a trivial thing now. Yeah. Right? It's like And users it's known that users don't make secure passwords. They they they they most certainly absolutely do not. Yeah.

331
00:38:50.135 --> 00:39:06.410
So what we did is basically And then you also have the opposite side where then they make it too secure and then they forget it. Good. You have to lose access to it. Right? Because you have to remember that most people I mean, I'm not reminding you. I'm reminding you freaks. Most people lose bitcoin. They don't get it stolen. So you're always trying to find this balance. And, you know,

332
00:39:07.190 --> 00:39:09.915
okay. So all of this is on recoverable.com.

333
00:39:09.915 --> 00:39:18.655
Okay. I literally have a video explaining all of these. I spent a lot of time and, you know, that's the background that I came from is from the big one embassy where I dealt with

334
00:39:19.355 --> 00:39:25.535
both the really high IQ and the low IQ users. So I think I know the big corner and I know, like, the big one person really well. And, of course,

335
00:39:25.940 --> 00:39:28.920
that's the big problem is if your passphrase is secure enough,

336
00:39:29.620 --> 00:39:38.360
you're gonna lose it and if it's insecure you're gonna get a brute force. So how do you fix that? Well, what we did is and I didn't invent that but I think we did it way better is basically

337
00:39:39.075 --> 00:39:39.815
we derive

338
00:39:40.115 --> 00:39:41.974
a very large encryption key

339
00:39:42.275 --> 00:39:42.775
from

340
00:39:43.075 --> 00:39:47.895
the bitcoin wallet private key itself using bip 85 right so you start with the mnemonic

341
00:39:48.195 --> 00:40:02.620
and we derive the child key essentially another mnemonic from your mnemonic right it's you know, it's just red random entropy, and we encrypt the mnemonic with the key that we derived from the mnemonic. Right. Okay?

342
00:40:03.040 --> 00:40:11.265
So you can upload your encrypted mnemonic to the cloud because that to to to brute force that encrypted file

343
00:40:11.565 --> 00:40:12.785
is the same energy

344
00:40:13.165 --> 00:40:22.385
required to guess your private key. So but, of course, the problem is, alright. So now your encryption key is another mnemonic. What do you do with that? Hey. So I lost my phone. Right. How am I responding?

345
00:40:22.685 --> 00:40:43.125
Okay. So that encryption key that allows you well, the fir first of all, it to restore your your your backup file, you just go in your drive, in your Google Drive, and, like, you download it. It's fine. Right? But how do you, decrypt it? Well, we created something. It's called a key server. It's it's it's called a recoverable server, and think of that as being like a password like a password manager.

346
00:40:43.585 --> 00:40:49.205
It's fully anonymous. There's no accounts. There's no email. There's no phone number. It it works only on Tor.

347
00:40:49.585 --> 00:40:51.285
And when you are doing a backup,

348
00:40:51.910 --> 00:40:52.570
you give

349
00:40:52.870 --> 00:40:54.890
the encryption key to the key server

350
00:40:55.350 --> 00:40:56.170
and you

351
00:40:56.710 --> 00:41:07.165
authenticate yourself with, like, a very easy password. Right? And So the user is still picking a password, but it's the easier password because it's it's not The the password can be a six digit PIN. Okay. Right? Because,

352
00:41:07.625 --> 00:41:09.245
the recoverable server enforces

353
00:41:09.785 --> 00:41:33.885
So it's backwards the user basically is just pressing cloud backups Yes. And then just remembering a six digit PIN. Yes. They lose their phone, they reload the app on the new phone, they put in their six digit PIN Yeah. And the wallet's there. It's it's minimum six digit PIN, and we we prevent the most retarded six like, you can't One one one one. You can't do that. Like, we we we, actually, we have the thousand most common PINs Okay. And you can't use the thousand most common pins. Wow. Anything other than one two three four five six, 111111,

354
00:41:33.885 --> 00:41:34.945
888888,

355
00:41:35.005 --> 00:41:36.385
like, you can do that. So,

356
00:41:37.244 --> 00:41:53.080
the key server and, like, the way we've we've I'm not gonna go too deep into the details, but the way that we've implemented it is really good. It's fully anonymous. There's no way that the key server knows who you are. There's no option to connect to it other other than Tor. If there doesn't work, then you can't use the recoverable server. The key here is the key here is

357
00:41:54.020 --> 00:41:56.520
if we're gonna actually talk about trade off model,

358
00:41:57.595 --> 00:41:58.495
you could technically,

359
00:42:00.555 --> 00:42:01.535
you can technically,

360
00:42:03.595 --> 00:42:05.055
work with Apple and

361
00:42:05.595 --> 00:42:06.095
and

362
00:42:06.475 --> 00:42:10.799
steal the backup. Right? So so so so we're talking about that that that recoverable

363
00:42:11.099 --> 00:42:24.160
and Apple recoverable and Google aren't working together, which is a strictly better than just trusting Apple or just just Google. Right? If if I was somehow able to convince Larry Page to give me access to the other Google Drive Or vice versa. Or or vice versa.

364
00:42:24.460 --> 00:42:26.775
The the thing is Google doesn't know,

365
00:42:27.175 --> 00:43:09.825
which recoverable server is being used or if a recoverable server is being used because you can use you don't have to use the recoverable server. You can export that private key and just do a regular backup without using the server. Yeah. I mean, to be clear, I think this is a great trade off. Yeah. It's not cold storage, but it's not supposed to solve cold storage. It's it's it's the first thing on the website is, like, this is not cold storage. Let me right. Yeah. Yeah. You do the framing really well. And I think I mean, look at the opposite not the opposite, but another trade off balance here is what Phoenix does. Where on Phoenix, they have, like, a quick and easy upload to iCloud button. Yeah. And what they say is, like, they make you check a box that's, like, the NSA and Apple can steal your money. Are you cool with it? Yeah. And, also, that threat model is probably good for the majority of people. Like, I think most people don't have Apple

366
00:43:10.310 --> 00:43:26.055
and and the NSA in their threat model, and this is significantly better than that. And and, you know, I I wanted to do something that's also a little bit better than Envoy's, like, magic backup, but they they had the right idea. They had, like, the right UX. I just think ours is, like, a little bit more, like, consider I think it's considerably more,

367
00:43:26.915 --> 00:43:27.655
more secure.

368
00:43:28.195 --> 00:43:41.319
And the thing is, like, what people act and you have to think about, like, okay, what do people actually do? Right? And the same thing with Liquid. It's like, what do people actually use? Well, they use one of Satoshi. Yeah. And what do they do with the backup? They fucking put the entire mnemonic. Dude, people put their mnemonic

369
00:43:41.940 --> 00:43:46.680
in LastPass. Or like Apple Notes is even worse than that. They put it in Apple Notes. They put it in Google Drive.

370
00:43:46.980 --> 00:44:04.369
What they do is they put the mnemonic on on a piece of paper and they leave it in their office. What they do is they scribble it on a fucking post it and they lose the post it. Like, that's what they actually do. Right? People don't get hacked. Take a screenshot, keep it in their photos or whatever. And, like, what they do is they they leave it on Coinbase. That's what they do. Right? With a password.

371
00:44:04.670 --> 00:44:25.065
Alright. So let's talk about art. Alright. So why am I fucking sold? Real quick. Yeah. Sorry. Go ahead. And last but not least, if none of that suits you, you can just write down a classic seed phrase Yeah. Of course. Stored securely and do that as your full Bitcoin backup. You lose if you lose your phone, you just put in your mnemonic. Boom. Done. You got it. And that's why thanks for the issue actually. Like, that's I I wanted

372
00:44:25.605 --> 00:44:37.650
the, turn off the exchange. Right? So so if you don't wanna use exchange, actually someone actually did a PR. I saw that. Yeah. It was in hot Really quick. It was like one day or something. It was a random person from the Internet that did the PR. I've zapped him for it. Yeah. Sweet.

373
00:44:39.550 --> 00:44:56.875
So I want, you know, I actually do use recoverable for my hot wallets because I don't know. I got like $800 on it, and it's still convenient. And I uninstall wallets all the time, so it's, like, super convenient. I like cloud backups. But but but, you know, the thing is I I'm obviously not gonna fucking put my stash on cloud backup because because my stash is, you know, I don't know where it is.

374
00:44:57.255 --> 00:45:00.150
I don't have a stash. Just just so it worked out. I lost all my Bitcoins,

375
00:45:00.710 --> 00:45:26.599
except the ones in my recoverable backup, just $600. That's all all the Bitcoins I have. But, yeah, of course. So so you can see the general theme here. The general theme is, like, I wanna make I wanna make sure that's easy, for my mom. My mom's a Bitcoiner, actually. She's fucking awesome. I wanna make, something that's easy for my mom, but also that I can use. And I know it sounds cliche, but, man, you would be shocked at the amount of people that told me, like, you cannot do that. Even I remember, like like like,

376
00:45:26.900 --> 00:45:58.480
I got feedback from, like, the Bitcoin design guy, the people in design club, and they're like, you know, you're you're trying too hard to, like, you're trying too hard to cater to both the cyclocon server and normies. Like, you you have to pick one. You know, like, you have to just either you have to be Sparrow or you have to be Aqua. Yeah. I'm like, no. I don't wanna be either Sparrow or Aqua. I want I want to be both. There's a happy middle. Right. There there is a happy middle and it's called advanced options. You know? And it's like you had you pick a default path. If you don't know what you're doing, you click the buttons. Next. Next. Next. And if you know what you're doing, then you click the advanced option and then you go into the advanced,

377
00:45:59.339 --> 00:46:00.940
the advanced settings, you know? And,

378
00:46:01.900 --> 00:46:04.720
right. So At the realtor, let's talk about our Okay. So,

379
00:46:05.339 --> 00:46:06.240
so ARC,

380
00:46:06.780 --> 00:46:07.895
is a

381
00:46:08.595 --> 00:46:10.695
completely different set of trade offs

382
00:46:11.075 --> 00:46:17.255
than liquid or any kind of custodial or semi custodial or trust minimized model,

383
00:46:18.115 --> 00:46:23.339
because ARC has this very specific feature where you have unilateral exits from arc. So

384
00:46:23.720 --> 00:46:25.579
arc is a concept where you will,

385
00:46:25.960 --> 00:46:27.660
the arc server virtualizes

386
00:46:28.440 --> 00:46:31.180
UTXOs into virtual UTXOs. So it's like

387
00:46:31.640 --> 00:46:37.020
converting your Bitcoin into virtual Bitcoin, which only exists into the in in an arc ecosystem. So

388
00:46:37.585 --> 00:46:38.085
not

389
00:46:38.545 --> 00:46:47.365
unlike, you know, Cashew or Liquid or that kind of stuff. It's a you have a token of a virtual UTXO which is worth one to one is worth a Bitcoin UTXO.

390
00:46:47.745 --> 00:46:49.505
But what ARC does is that,

391
00:46:49.905 --> 00:46:54.070
there is a pre signed transaction which allows you to claim

392
00:46:54.450 --> 00:46:56.230
the Bitcoins on chain

393
00:46:56.930 --> 00:46:57.670
non cooperatively

394
00:46:58.050 --> 00:47:08.595
with the the server in case the server goes down. You can exit whenever you want with that one. Yes. You can exit whenever you want. And, like, the server can't rub you if you exit and if they get,

395
00:47:09.135 --> 00:47:34.050
you know, arrested or seized. And what's the trade off is that it costs a lot of non chain fees? Yeah. So so so the the trade off is that you that, like, let's say that you have $5 on Arc and you do a new viral exit, like, you're gonna get robbed. And there there's another kind of, like, weird trade off in ARC where ARC has a pre confirmed transaction model, which is, like, you can have a in order to get the on chain guarantee on ARC, you need to include

396
00:47:34.385 --> 00:47:35.684
your virtual UTXO

397
00:47:36.305 --> 00:47:41.125
in an actual music Taproot output on chain. Yeah. And that's not

398
00:47:41.505 --> 00:47:43.045
free. Right? The ARC

399
00:47:43.585 --> 00:47:44.885
ASP needs to publish

400
00:47:45.425 --> 00:47:46.565
a Bitcoin transaction

401
00:47:46.865 --> 00:47:50.110
in order to update, I guess, the state's

402
00:47:50.810 --> 00:47:52.510
So how often are they doing this?

403
00:47:53.210 --> 00:48:00.165
Man, if I dude, Alex is gonna kill me if I explain ARC wrong, but, they they will do that, whenever they want.

404
00:48:00.565 --> 00:48:04.665
Well, then I'll have Alex on at some point. You know, I'm I'm I'm assuming

405
00:48:04.965 --> 00:48:05.865
something like,

406
00:48:06.245 --> 00:48:17.070
like my assumption Like, once a day or something? Like, a couple times a day or something like that. Right? And you don't end but you don't have to have on chain guarantee because if you you you can choose to not have the on chain guarantee.

407
00:48:17.450 --> 00:48:18.430
And in that case,

408
00:48:18.810 --> 00:48:20.190
the ARC server,

409
00:48:20.730 --> 00:48:28.270
if it colludes with the sender, can double spend you. Right? So so if you have the on chain guarantee, you can't you can't be rugged.

410
00:48:28.994 --> 00:48:30.694
If you don't have the unchain guarantee,

411
00:48:31.555 --> 00:48:35.575
you trust that the ARC server is not colluding It's not malicious.

412
00:48:35.875 --> 00:48:40.775
It has to be actively malicious. It's it's like a zero con transaction. Yeah. But,

413
00:48:41.795 --> 00:48:43.234
the thing with the zero con,

414
00:48:44.410 --> 00:48:50.510
but the ASP needs to, like, actively collude against you. Right? So for anything that's like alright. So let's say I'm a merchant

415
00:48:50.810 --> 00:48:54.430
and I'm getting paid, like, I don't know, a $150 for for for a dinner. Mhmm.

416
00:48:56.330 --> 00:48:56.830
Is

417
00:48:57.290 --> 00:48:58.350
the ARC organization

418
00:48:58.810 --> 00:49:04.295
going to double spend me? Are they colluding with the person buying dinner? Right? Yes. I mean,

419
00:49:04.675 --> 00:49:13.975
again, like, no. You know, there's like there's like The probability of that happening is very low. It's it's very low. So so do do I really need that $150

420
00:49:14.150 --> 00:49:19.610
to be on chain claimable in a Taproot music output? Like, no. But, you know, if I'm a large organization

421
00:49:19.910 --> 00:49:24.810
or if I'm a or a large merchant, that's fine. Like and, you know, I'm getting to the point when where,

422
00:49:26.835 --> 00:49:44.760
I might also be afraid that the art server goes down, you know. Like So but that's right. Yeah. Correct me if I'm wrong. So that's why, like, there's a balancing act there where you do it once a day or something. Yeah. Right? So it's like, okay. There's a settlement. Right? Like, once a day is it kinda settles and then it can happen. Look, as the as the end user, I'm I'm I'm gonna pay for the settlement. Right? So so the ARC,

423
00:49:45.140 --> 00:50:03.055
I mean, I don't know what the pricing model, but you you can imagine that if ARC is paying the on chain fees, they're eventually gonna pass that on to the end user. They're not gonna it's it's it's expensive, especially if fees go up. If we're actually bullish on Bitcoin, fees should probably go up. I don't know about that. But And the there's another problem with ARC, which is that,

424
00:50:03.535 --> 00:50:08.230
the ARC server needs to lock up liquidity to kinda, like, front the,

425
00:50:08.770 --> 00:50:10.150
the Arc network. So,

426
00:50:10.849 --> 00:50:26.795
the your virtual UTXO will expire. It actually expires. And, like, right now, I think it's, like, fifty days or something or, like, sixty days or something. So you need to refresh your UTXO, and there is a liveness requirement to that. And that's why people say that you need confidence

427
00:50:27.175 --> 00:50:29.595
to make Arc better. Right. Because,

428
00:50:30.055 --> 00:50:30.955
It makes it cheaper.

429
00:50:31.575 --> 00:50:35.035
Well, okay. And I I I I'm going above my pay rate here,

430
00:50:35.415 --> 00:50:36.955
because, you know, I'm

431
00:50:37.350 --> 00:50:39.530
I'm not I'm not a Bitcoin script

432
00:50:39.910 --> 00:50:40.410
guy,

433
00:50:40.870 --> 00:50:42.090
but my understanding

434
00:50:42.390 --> 00:50:42.890
is

435
00:50:43.190 --> 00:50:43.850
that Convenance

436
00:50:44.150 --> 00:50:45.850
would allow people to,

437
00:50:47.110 --> 00:50:48.970
refresh their v t x o's,

438
00:50:49.925 --> 00:50:53.545
without a liveness requirement, like, without your wallet being online.

439
00:50:53.845 --> 00:50:54.345
But

440
00:50:54.645 --> 00:50:57.305
the thing is that we can solve these problems with

441
00:50:57.845 --> 00:51:24.244
software that's not protocol changes. Right? So for example is, like, getting CTV as a software, while it might be ideal for ARC, it seems very unlikely that we're We have to assume we have to assume that it's not gonna happen. The the same way to be a Bitcoin is to assume no soft forks will happen. Yes. Exactly. If you base your business model on a soft fork, you're gonna get wrecked. You're gonna get wrecked. So the same thing happened with, Lightning. Right? So what happens if your node is offline where when there is a But Lightning, we got the software.

442
00:51:25.345 --> 00:51:28.785
Yeah. But but but it we did get the software for Lightning, but,

443
00:51:29.105 --> 00:51:33.650
we still have to have a watch tower. Right? So so if your lightning node goes offline

444
00:51:34.270 --> 00:51:37.650
and there is, what's it called? Anyway, there's, an exit transaction

445
00:51:37.950 --> 00:51:55.164
Yeah. Like, your your no Penalty transaction. Yeah. Punct like, your no needs to wake up. Right? And that's why Otherwise, your counterpart against take all your money. Yes. So that's why we have the concept of watchtower. So, like, one of the reasons why I am here specifically right now And also, like, you have to be offline for, like, two weeks or something. Yeah. Yeah. Yeah. Yeah. But I mean In practice,

446
00:51:55.464 --> 00:52:28.130
most people aren't using watchtowers, and we rarely ever see that attack app. That that's that's that's right. It's it's the same thing for ARC. Like, if you are if you're online, then you can refresh. But if you're not if you're not online when your v you say so expires, like, there is a likeness requirement. So, you know, stuff that that that we are going to work on is a a kind of like a watchtower model, but a a delegate refresh model. Right? Where maybe the wallet operator like bull, we can run a delegate server so that the user tell it's like conceptually, the user is telling us, like, hey. Like, these are my VUTXOs.

447
00:52:29.150 --> 00:52:30.369
This is when they expire.

448
00:52:30.829 --> 00:52:42.289
Like, refresh them for me when it's time to refresh for me. Well, they are taking custody or anything. Yeah. Yeah. Exactly. Exactly. So it's just like a service to help. So that's there's, like, some of these trade offs that are somewhat

449
00:52:42.805 --> 00:53:07.550
fixed or mitigated by a soft fork. We're gonna try our very best to fix them with with light. It sounds like they're workable without. It's it's it's it's it's workable without and, like, the the so so liquid is kinda like in liquid, you can't really be double spent. It's like there's, like, more finality, but there's no exit transaction. Right? Which is really bad that there's no exit transaction. Of course, it's bad. And that's the that's the That's the beauty of lightning. Like, lightning has a bunch of trade offs

450
00:53:07.925 --> 00:53:18.185
that make it kinda shitty UX wise, self custody wise. But at the end of the day, I can always escape off chain on chain myself without any permission or Well, look, like, lightning is

451
00:53:18.885 --> 00:53:22.244
a miracle. It's it's it's amazing. Right? It it it's amazing. And then,

452
00:53:23.700 --> 00:53:29.720
so there is another one called Spark. I and I'm gonna be honest. I didn't I didn't look into Spark because of the vibes.

453
00:53:30.020 --> 00:53:36.520
Yeah. It's purely vibes. It's purely aesthetics. Clients grow vibes. Yeah. It's purely aesthetics and also, like,

454
00:53:37.434 --> 00:53:38.654
Spark and Arcade.

455
00:53:39.194 --> 00:53:42.095
So Arc is the name of the protocol. Arcade is the one implementation

456
00:53:42.555 --> 00:53:45.535
that, you know, people who are familiar with Alex b and,

457
00:53:46.395 --> 00:53:48.075
Tierro and Cooks, you know,

458
00:53:48.714 --> 00:53:50.654
these are Legends in their own right.

459
00:53:50.954 --> 00:53:52.494
Fucking my my favorites.

460
00:53:53.650 --> 00:54:06.045
One one of the reasons why I'm so into ARK is because there's people I respect in this space. There's, Roy from Breeze. Yeah. There's, Tierro, which I knew from the liquid days. Yeah. And there's Cooks.

461
00:54:06.845 --> 00:54:19.984
Right? And, and there's both. Yeah. And And Frizz. Just Cooks, like, has a very low profile, but he's most well known for BTC pay server. He was heavily involved in BTC pay server, and he's actually one of the co creators of Nostr,

462
00:54:21.110 --> 00:54:32.330
alongside Fiat Jeff. And what these guys have in common is they ship. Yeah. They fucking deliver. Like, Thiero delivers. Cooks delivers. Roy delivers. Bolts delivers.

463
00:54:33.684 --> 00:54:34.345
And coincidentally,

464
00:54:34.964 --> 00:54:55.900
we were all at Arcade Day. We're very excited about Arc. Right? So so so the the the the there is there is a let's fucking ship mentality with with Arc. To be fair, Spark also did ship. They Smart Smart They've been a a lot of people have underestimated. They've shipped like crazy. Yeah. And and and Spark is shipping in a kind of a corporate way where they are,

465
00:54:56.440 --> 00:54:58.060
like, going after exchanges

466
00:54:58.520 --> 00:55:10.225
and, like, they're It's more it's more polished. It's easier to build on right now. Spark bought a payment processor in order to get inside, like, the the kind of, like, fintech payment space. Oh, it helps when you get a $165,000,000

467
00:55:10.225 --> 00:55:15.045
with a 16 seed investment. That, yeah, that that doesn't hurt, to to to be perfectly honest.

468
00:55:15.609 --> 00:55:16.109
However,

469
00:55:16.650 --> 00:55:19.050
I and I don't wanna say anything negative about Spark.

470
00:55:19.450 --> 00:55:19.930
It's just,

471
00:55:21.130 --> 00:55:25.950
you know Well, I'll go out there. Like, the biggest negative right now is on the privacy side. They basically

472
00:55:26.410 --> 00:55:28.250
modeled Spark off of,

473
00:55:28.650 --> 00:55:29.630
Mercury layer,

474
00:55:30.255 --> 00:55:58.240
which is a state chain implementation, and then they stripped the privacy stuff out, and then they made it even less private. So, like, right now as it currently stands, you can kind of think it like of it like the Tron trust model, which ironically, a lot of people use Tron. More people Mhmm. Use Tron, quote, self custody than Bitcoin. But it's just with a single reusable address. So if you have someone's Spark address, if you pay them once on Lightning and you have their Spark address, you can see every transaction they've ever made Yeah. Including their current balance. Yeah. But

475
00:55:58.715 --> 00:55:59.535
on the alternate side, it's

476
00:55:59.915 --> 00:56:03.515
really easy to build. Yeah. Yeah. Yeah. For sure. And,

477
00:56:04.075 --> 00:56:06.655
one of the things that, ARC, I think,

478
00:56:07.755 --> 00:56:12.255
we will have to work on is, the privacy as well because, of course, the ASP,

479
00:56:13.190 --> 00:56:17.589
you can you can think of you can think think of ARC as, like, a private mental, which is the ASP's,

480
00:56:17.990 --> 00:56:19.849
private mental. So obviously the ASP,

481
00:56:20.710 --> 00:56:21.529
can see

482
00:56:21.829 --> 00:56:22.809
all of the VITXOs.

483
00:56:23.109 --> 00:56:31.265
You as a user, you can't see, like, the mental as ARC's private mental. Presumably, they couldn't make it public. So it's not, I don't think it's an improvement

484
00:56:31.725 --> 00:56:33.105
necessarily of privacy

485
00:56:33.565 --> 00:56:34.065
over

486
00:56:34.605 --> 00:56:35.105
Bitcoin

487
00:56:35.565 --> 00:56:57.635
in the same way that, like, liquid, it has a privacy improvement over Bitcoin even though Liquid also has a utility It's not a perfect analogy, but I call it like a custodial privacy model. You're trusting you're trusting a third party with your privacy. Yeah. I mean, people already trust electric surfers, like, random electric surfers and Internet. So but, you know, the the thing about ARC transaction is that they're essentially free inside the ARC network. Yeah.

488
00:56:58.255 --> 00:57:02.015
And, if they're free, I don't know. Maybe we can do CoinJones and ARC. I don't know. Like,

489
00:57:02.415 --> 00:57:03.955
it's it's still early. I'm

490
00:57:04.335 --> 00:57:04.835
I'm

491
00:57:05.215 --> 00:57:09.635
I'm confident that the guys involved in ARC and Arcade specifically are,

492
00:57:10.850 --> 00:57:21.030
are people that have worked on privacy technologies, I think I think we're gonna be able to solve that. So, like, the thing about the thing about ARC is that it has different trade offs, but it has some really, really neat features.

493
00:57:21.890 --> 00:57:46.480
So is it going to replace liquid? Yeah. That's my next question. Is there a future where liquid gets removed from the bull wallet and arc gets replaced with it? There there payments? There's a 100% of future. There's a 100% of future where, the instant payments wallet, which is, like, the default one that the the user that that doesn't know what he's doing is the one that he's receiving funds into. Yeah. There is a future where that's in our wallet. Okay. And that and that future,

494
00:57:46.940 --> 00:57:51.840
might be close, might be far. Do you think the middle future is, like, you have both in there or

495
00:57:52.140 --> 00:58:01.755
is is there gonna be a world because that gets confusing too. I mean so there's, like Did I see a screenshot that you posted online that was, like, bull using ARC? Yeah. So What's going on there? Is that just testing? Or

496
00:58:02.395 --> 00:58:08.555
I mean, it's testing on on mainnet with real money. So it it it is I I I have ARC on the mainnet right now.

497
00:58:09.035 --> 00:58:10.015
So, of course,

498
00:58:10.370 --> 00:58:11.270
there are things

499
00:58:11.570 --> 00:58:12.070
that

500
00:58:12.450 --> 00:58:17.910
when you say, like, sleep at night, like, what makes me sleep at night. Right? There are I'm not comfortable,

501
00:58:19.410 --> 00:58:24.070
with with, like, onboarding you to ARC right now. I I I would feel bad because,

502
00:58:25.425 --> 00:58:29.765
the the UTXO expiry stuff is not is not really solved.

503
00:58:30.145 --> 00:58:31.985
There's no UX around the,

504
00:58:32.465 --> 00:58:33.605
unilateral exit.

505
00:58:34.305 --> 00:58:36.645
There's no UX around, the the delegation,

506
00:58:37.585 --> 00:58:41.099
delegated the refresh of the UTXO. So there's, like, stuff that's missing.

507
00:58:42.359 --> 00:58:59.945
Whereas on liquid, I mean, it's it's pretty Paul. I mean, liquid is this for for, like, ten years, so it's like, you know, give it some time. But I I think that future is, like, a lot closer than than than we think. And, like, okay, so there's, like, a wallet. It's called layers. Right? And layers is kind of like, we have all the layer twos and, like, you can choose your layer two, like but that's that's

508
00:59:00.645 --> 00:59:01.705
it's like,

509
00:59:02.005 --> 00:59:02.505
man,

510
00:59:04.085 --> 00:59:08.905
there's, like, this this, like, info thing in the wallet where I, like, explain the art, the liquid

511
00:59:09.930 --> 00:59:38.430
security. Imagine me explain, like Yeah. Choose your network. Like, here's the trade off. Lost the user when you're doing that. I I have to make that choice for them. And I have to make that choice for them. And I have to make that choice for them. And I have to make that choice for them. And I do see the default. Like, I love them, but, like, if if a user needs to watch it to our BTC sessions video, like, we've already lost the plot. Yeah. Of course. They should never have to do that. It's just very simple. So Volvik one is gonna have to decide whether the default is arc or liquid or spark or state chain or mercury or whatever it is. And I'm gonna make that decision based on what I think is right.

512
00:59:39.069 --> 00:59:46.530
And I think right now, of course, liquid is the obvious choice. It's it's liquid is the now. Arc is the future. Yeah. And Arc also has

513
00:59:47.069 --> 00:59:47.569
other

514
00:59:48.030 --> 00:59:49.170
kind of, like, defy,

515
00:59:49.630 --> 00:59:58.825
implications to it, which get people really excited. Not me, really. Like, I'm more of a I'm more of a dumb dumb. Like, I like I just wanna pay for pay for my fruits with Bitcoin. I don't I don't need, fucking,

516
01:00:00.005 --> 01:00:01.385
sushi swap exchange.

517
01:00:01.765 --> 01:00:02.665
Right. Coins.

518
01:00:02.965 --> 01:00:26.665
So yeah. I'm, I want people to pay with Bitcoin and earn Bitcoin. That's that's what I want. And then I guess, like, the one thing that might be valuable, quote unquote, in the defies place is, like, lending stuff. Exactly. But then the question to me is always, like, at the end of the day, like, if I take a loan out of my Bitcoin, first of all, you should be very careful with it because that's how people get wrecked. But then second of all, like, I need dollars in my bank account. So there's gonna be centralized elements regardless.

519
01:00:27.205 --> 01:00:40.220
Well, there's so why are we pretending why are we doing this huge Rube Goldberg machine when you have tether in there, so you're trusting tether, and then you have your bank account in there somewhere, so you're trusting your bank account. I'm not gonna go too much into the questionable. I'm I'm not gonna go too much in details,

520
01:00:41.080 --> 01:00:42.380
but you can have

521
01:00:44.200 --> 01:00:45.020
very trustless,

522
01:00:45.480 --> 01:00:45.980
almost

523
01:00:46.280 --> 01:00:47.955
trustless stable coins on mark.

524
01:00:48.755 --> 01:00:56.215
You you can have that. You you you we we can we can make But is it what is that, like, is it, like, die or something? Like, it's, like, Bitcoin collateralized

525
01:00:56.755 --> 01:01:01.500
algorithmic stable coin? Kind of. It's like have a tendency to blow up too. Right?

526
01:01:01.800 --> 01:01:05.580
So think of the the fact that on ARC you have the unilateral exit

527
01:01:05.960 --> 01:01:09.260
from the ARC v UTXO. You can have a unilateral

528
01:01:09.640 --> 01:01:18.785
exit on Bitcoin from a stable coin. Right? That's that that that's something that ARC makes possible. That's cool. It is it is cool, and it's it's probably

529
01:01:19.085 --> 01:01:24.705
the only thing about ARC that's not Bitcoin that interests me. The other thing that that we can do on on ARC

530
01:01:25.085 --> 01:01:26.945
is, like, these kind of, like,

531
01:01:28.599 --> 01:01:29.099
trustless

532
01:01:29.560 --> 01:01:30.859
swaps between,

533
01:01:31.800 --> 01:01:37.900
like, you know, if you're if you're if you're trading Bitcoin for stablecoins right now Right. There's a centralized counterparty,

534
01:01:38.680 --> 01:01:45.475
but kind of like the bolts model where you can have a ton atomic swap. You can have an atomic swap between, a Bitcoin and a stable coin. Okay. That's not a.

535
01:01:47.055 --> 01:01:55.075
But really, this is like it's like it's like icing on the cake. It's DeFi stuff. I'm not interested in it personally. You like the payments use case. I like I like the payments use case, and,

536
01:01:55.455 --> 01:01:58.355
I I I think ARC is the only thing

537
01:01:58.839 --> 01:01:59.579
that has

538
01:01:59.960 --> 01:02:04.859
come up other than Spark, which is, like, a fully new model. Right? Like, because

539
01:02:05.240 --> 01:02:06.859
cashew, fetti, liquid,

540
01:02:07.160 --> 01:02:10.140
it's the same kind of thing. Right? It's like you have a

541
01:02:10.680 --> 01:02:11.180
custodian

542
01:02:11.640 --> 01:02:22.685
or you have an entity which is guaranteeing a peg, whatever. It's like cash, liquidity, and liquid are like different shades of the same thing, whereas ARK is a completely new thing. I think a good comparison is like lightning. It's like fundamentally

543
01:02:23.305 --> 01:02:23.745
Yeah.

544
01:02:24.185 --> 01:02:24.765
A fundamentally

545
01:02:25.385 --> 01:02:28.100
innovative Yeah. New way for Bitcoin payments.

546
01:02:28.560 --> 01:02:29.940
Absolutely. And, like,

547
01:02:30.880 --> 01:02:36.640
as a as a fanboy of, you know, like, we Bolt Bolt was we integrated lightning in 2019

548
01:02:36.800 --> 01:02:44.484
Right. But we launched it on May 2022. It took us three years to do that just because it wasn't ready. But, like, I I was, like, first to jump on lightning,

549
01:02:44.865 --> 01:02:56.060
first to jump on liquid, and, like, just out of, I guess, just out of ego, I wanna be the first one to to run on Arc. So so Arc actually does work in the bull wallet. Like, you can send from, like, the Bull Wallet,

550
01:02:56.680 --> 01:03:12.055
if you have access to the super user mode. And I I don't think I'm gonna give it to the I'm a little scared. There is a super user mode. If if you don't ask me nicely, I'll I'll give you the the codes. You have to tap certain things in the wallet and then access the Arc ARC wallet, but it it is reckless.

551
01:03:12.434 --> 01:03:13.974
ARC, it's it's reckless right now.

552
01:03:14.355 --> 01:03:18.055
So so do it really is. So, like, do that with, like, pocket money.

553
01:03:19.395 --> 01:03:19.875
But,

554
01:03:20.355 --> 01:03:23.734
but yeah. So so it it does work, and, like, we have

555
01:03:24.710 --> 01:03:26.490
the best best engineers

556
01:03:26.869 --> 01:03:28.089
ever and, like,

557
01:03:29.349 --> 01:03:30.549
really excited to

558
01:03:31.349 --> 01:03:33.609
and, of course, like, not only do I want,

559
01:03:35.349 --> 01:03:43.355
Arc in the wallet, I want Arc in the exchange. Same thing with PageJoin. PageJoin is in the wallet right now. It's not in the exchange, and it's not for legal reasons at all.

560
01:03:43.655 --> 01:03:51.420
It's literally just because what we're talking about earlier, like, PageJoin v two is, like, reckless, and it just Yeah. It just kinda breaks. So it's it's it's fine if

561
01:03:51.720 --> 01:04:05.740
it's, you know, you and me testing a page line at a conference. But, like, if someone's buying, like, a $100 worth of Bitcoin, I don't want the page to fail. Yeah. Of course. But still, I don't think money would be a lot there's no risk of money. No. Money money wouldn't be lost. It was just kinda like No transaction.

562
01:04:06.065 --> 01:04:12.005
Yeah. The the page one would like to get stuck and then there would be a fallback transaction. It was just, you know, kind of like piss people off, really.

563
01:04:12.545 --> 01:04:25.180
But, yeah, I I do wanna have, arc arc I wanna play with arc and and the bullet exchange and, like, make make that like, I want bullet point to be always, like, the the most technologically advanced exchange at the at the at the forefront.

564
01:04:25.560 --> 01:04:35.260
And, like, our goal really has always been, like, just just looking like the the be the model. Like, I wanna be the I wanna be I wanna be the model that, like, people emulate.

565
01:04:36.015 --> 01:04:36.915
Okay. I got

566
01:04:38.174 --> 01:04:40.035
a couple more topics real quick.

567
01:04:40.655 --> 01:04:42.194
Just real quick back to Liquid.

568
01:04:43.055 --> 01:04:44.035
It feels like

569
01:04:45.295 --> 01:04:48.994
Liquid could do a little bit more on the privacy side. You've been very,

570
01:04:50.289 --> 01:04:50.789
involved,

571
01:04:51.170 --> 01:04:54.630
like, in liquid network management and whatnot. Do you is there any

572
01:04:56.849 --> 01:04:57.349
interesting

573
01:04:57.970 --> 01:05:05.075
updates happening there on that side, or is it kinda stagnant and it is what it is? And we have confidential transactions and we should just be

574
01:05:05.454 --> 01:05:08.275
I mean, at with what we have. At the protocol level,

575
01:05:08.895 --> 01:05:10.994
I don't think there's much more

576
01:05:11.454 --> 01:05:17.090
that can be done, but there's Or not even the protocol of a I mean, there's there's nothing stopping a visabi Of

577
01:05:18.350 --> 01:05:32.565
course. There there's nothing stopping anyone right now from from doing coin zones and liquid. Like, they Well, there's no app. No one wants to do it. Right? I mean, I think no one wants to because liquid has a really funny thing, which is that, chain analysis doesn't work on liquid because chain analysis

578
01:05:32.964 --> 01:05:34.025
uses I

579
01:05:34.645 --> 01:05:35.385
mean, it could,

580
01:05:35.845 --> 01:05:39.224
but one of the main heuristics of chain analysis is,

581
01:05:39.605 --> 01:05:52.160
change detection. Yeah. And Specifically, like, around the mouse. Yeah. And if you don't see it because and the freaks know this, but but the way chain analysis works and chain surveillance works is all probability analysis, and they're trying to figure out when ownership changes. Yes.

582
01:05:52.780 --> 01:06:24.290
So when you don't have the amounts, it makes it much more difficult. It it makes us really, really, really hard. But if you're, like, sending max amounts, then you can still there's no change. It gets becomes a little bit obvious stuff like that. There's there's no there's no no. You're right. Yeah. So if you're doing max amounts and and also there's a new thing. It's like there are a lot of page ones on liquid. Yeah. There's a tons of page ones. Yes. So page join does do. It even better improvement on liquid than it does on chain because the amounts are blind. And the reason why there's so many page ones on liquid is that all the USDT to Bitcoin swaps happening on liquids are used,

583
01:06:24.830 --> 01:06:25.730
using a,

584
01:06:26.990 --> 01:06:38.345
like, somewhat non disclosure model called site swap, and every swap is a page on a liquid. Right? So a lot of transactions are liquid or actually page on. So the common input ownership heuristic,

585
01:06:38.885 --> 01:06:41.545
which is the core of gen analysis

586
01:06:41.845 --> 01:06:55.410
Do you think Boltz will do that as well? Do page joins by default? Because maybe that's all we need. Maybe that makes a huge upgrade. It's up to both. Okay. It's up to both. What I will say what I will say is that with the advent of page join one point zero point zero,

587
01:06:57.150 --> 01:06:58.130
many things become

588
01:06:58.590 --> 01:07:10.695
more more possible than than were before like page one was was definitely a little reckless and then there's also page one d three which is an exaggeration of page one which is multi party page one which is you know effectively a coin join in a way,

589
01:07:10.995 --> 01:07:25.330
and we could drop in that on to liquid too, Right? Yeah. Yeah. Of course. Of course. That's one of the cool parts about liquid is it's very similar to bitcoin. It's it's it's like it's like a it's like a fork of bitcoin where you can just play around with it, you know, and since it's centralized, we can update it without without too many worries.

590
01:07:26.714 --> 01:07:32.255
But no. Like like, the thing about page one that really so I have a I have a specific,

591
01:07:33.994 --> 01:07:34.494
very,

592
01:07:35.515 --> 01:07:38.414
personal and very visceral hatred of chain analysis,

593
01:07:38.930 --> 01:07:40.470
of some chain analysis companies

594
01:07:40.930 --> 01:07:44.710
for it's a long story I'll I'll I'll share one day. I I really dislike chain analysis.

595
01:07:45.170 --> 01:07:47.350
And one of their motivations for me,

596
01:07:48.610 --> 01:07:56.335
to to to make Page one a reality is that I actually believe that the chain analysis companies are are bullshit. They're they're they're phonies, they're fake, they're voodoo.

597
01:07:56.714 --> 01:08:06.255
They're doing a lot of bad things, but that's the worst part. Right. They're they're astrologers. And what they end what they end up doing is they do a lot of false positive where where Bitcoiners who are innocent

598
01:08:06.900 --> 01:08:07.380
are,

599
01:08:07.780 --> 01:08:17.640
have evidence against them on shame that they did something wrong where they they did it. They they didn't do anything wrong. And the change It's probability analysis. And, like, when it's 60% probability,

600
01:08:18.340 --> 01:08:21.225
the chain of the analyst firms, they, like, pretend it's a 100.

601
01:08:21.465 --> 01:08:39.139
They pretend it's definitive. They say it's 60% probable. Right? But that number is fucking pulled out of their buttholes completely. Right. They're, like, 10%. Right. And I you know, it's like you either you either did it or didn't do it. Right? It's like crime is bling. You know what I mean? You're not 60% guilty, but the problem is the justice system is taking Cheninossa's

602
01:08:39.440 --> 01:08:40.260
word for it

603
01:08:40.639 --> 01:08:41.699
because it has

604
01:08:42.639 --> 01:08:45.300
partly because based on the common ownership,

605
01:08:45.840 --> 01:08:49.185
common input ownership heuristic. So if we destroy that heuristic,

606
01:08:49.565 --> 01:08:50.065
then

607
01:08:51.405 --> 01:09:05.670
is any chain analysis evidence ever admissible in court after that? Because if the if chain analysis is there's an argument it shouldn't be admissible already. Right. But but even more so. Right. Because, you know, chances can say, like, we have we have some solid

608
01:09:06.130 --> 01:09:08.070
reasoning behind our report,

609
01:09:08.450 --> 01:09:27.925
and I can be like, well, your solid reasoning is based on this realistic, which is no longer correct. So all of your fucking analysis falls apart. So page one is really cool really cool in that in that regards. Also, a really neat thing about page one is that it allows for anyway, I'm such a fan of page one. It's so great. It allows for passive consolidation of Bitcoin. So when you consolidate

610
01:09:28.225 --> 01:09:41.430
when you have a lot of small UTXOs in your wallet, that's not a good thing because in the future, if the the fees go up, you will be paying transaction fees for every little UTXO you have in your wallet. So you wanna consolidate. Right? But people don't know

611
01:09:41.785 --> 01:09:48.845
that they should consolidate, and they don't know how to consolidate. Less UTXOs are better fee wise, but worse privacy wise. Exactly.

612
01:09:49.385 --> 01:09:54.445
Exactly. So that's why, by the way, with the auto swap, like, the I think that a million sat UTXO

613
01:09:55.065 --> 01:10:07.830
is, like, the right trade off between privacy and and I I think the million SAT UTXO is, like, it's it's, like, should be the default right now. But if you are You're saying push it, but I like it. Yeah. Yeah. It's it's

614
01:10:08.385 --> 01:10:10.945
it's it's sounds nice. A 100 a 100,000

615
01:10:10.945 --> 01:10:25.199
will probably always be economically spendable. Yeah. Like, at least the next next ten years or so. Yeah. That's true. But, like, a a a million UTXOs is a is a thousand bucks. Like, if the coffee shop owner knows that you had a thousand bucks, like, everybody has a thousand bucks. You know what I mean? I agree. It's a good check.

616
01:10:25.659 --> 01:10:31.360
So if you have UTXOs in your wallet, the way that you would consolidate is by sending those UTXOs

617
01:10:31.739 --> 01:10:33.040
to yourself. Yeah.

618
01:10:33.420 --> 01:10:39.040
Send all to myself. Yes. But if you have Pejoint in your wallet and I am sending you

619
01:10:39.525 --> 01:10:40.025
Bitcoins,

620
01:10:40.725 --> 01:10:41.785
you are consolidating

621
01:10:42.485 --> 01:11:08.079
passively without realizing it as a receiver. Yeah. Which is fucking awesome. Because as a receiver, I'm contributing an input Yeah. And then you're contributing an input Yeah. And then I get one bigger input of it. Yes. Yes. So that's that's the love page on. But I guess you contribute two inputs. I contribute two inputs. I contribute one input. Right? And then we do We we we we can program page on to do whatever we want. Like, the bull Bitcoin wallets could have consolidation mode. Right? Where

622
01:11:09.175 --> 01:11:14.955
you you know what I mean? Like like, okay, let's say you have 10 inputs. You have 10 UTXOs, but you only need to contribute two.

623
01:11:15.495 --> 01:11:29.600
You can choose to contribute all of them in that page on it. Right? And we can have the consolidation mode as a social based on the network fees at the time. You can say, hey. If the fees are less than this amount Well, that's why I think it may be particularly helpful on the liquid side because fees are so fucking cheap. It's like 33¢

624
01:11:29.600 --> 01:11:30.659
or something. Yeah.

625
01:11:31.120 --> 01:11:32.820
And if you're consolidating Bitcoin,

626
01:11:33.245 --> 01:11:39.265
maybe, you know, you can consolidate it inside a swap. Right? So you have tons of small UTXOs you wanna consolidate.

627
01:11:40.045 --> 01:11:59.500
You're not gonna gain backwards privacy because those once the coins are consolidated on chain, like, we can all see that they're linked to the same person. Yeah. Unless it's a big one. Unless it's a big one. But, if you consolidate into a swap, you know, you you consolidate into liquid and then you swap it back to Bitcoin, like, that new Bitcoin that you got is completely unlinked.

628
01:12:02.085 --> 01:12:08.105
Very unlinked, let's say, to to the original to the original Bitcoin that you got. So, like, so, you know, like like,

629
01:12:08.725 --> 01:12:35.935
coin drawing is not coin drawing is not the only game in town. Yeah. Right. No. I agree. As and especially with confidential transactions, I think it could be there's a lot of cool things you can do on the liquid side without protocol change. Yep. That my mind is really racing now that there's actually a very usable liquid wallet. Because that was the one of the main things Yeah. Stopping liquid usability was there was just no good user facing stuff and now we have It's a never effect, man. And the thing is, like, it's it's kind of exponential because what happened is

630
01:12:36.395 --> 01:12:47.400
Bolt's Breeze, Bull, and, to some degree also the Aqua team and some other teams kind of, like, all gravitated towards the same conclusion at the same time, which was around the time, by the way, of the Bitcoin at Planis,

631
01:12:47.800 --> 01:12:52.280
the the conference in in Madera where we all kind of, like, got together and we were like

632
01:12:53.955 --> 01:13:00.855
a lot of the builders were like, this is this is what we're gonna do. This this is the model that so so there's, like, the network effect of of liquid is growing,

633
01:13:01.474 --> 01:13:01.974
but

634
01:13:02.514 --> 01:13:04.215
the network effect of arcades,

635
01:13:05.635 --> 01:13:07.554
is is also growing really quick, man. I

636
01:13:08.270 --> 01:13:11.090
Yeah. You'll have a look at that there's there's at least,

637
01:13:11.630 --> 01:13:21.495
at least six Bitcoin companies right now that are building an arc. And I think the fact that you're the a lot of a lot of wallets, including yourself, are using lightning as, like, kind of the

638
01:13:21.895 --> 01:13:33.415
interoperable layer. It is. You said that you didn't it doesn't you don't have to fight the network effect as much because you can drop an arc where liquid is, and at the end of the day, they're still paying and receiving from lightning. So that I have I have a question for you.

639
01:13:34.055 --> 01:13:37.035
The so the biggest trade off with using a liquid enabled

640
01:13:37.420 --> 01:13:39.599
lightning wallet is is

641
01:13:40.380 --> 01:13:48.719
small we haven't really talked about it. It's small transactions because you do have to make that on you have to make the liquid the liquid transaction. So, like, sending, like,

642
01:13:49.099 --> 01:13:54.765
I think a lot of bots, maybe yours even included, like, you you can receive a payment under a thousand sats,

643
01:13:55.545 --> 01:13:59.325
which, you know, people for whatever reason love sending, like, 3 sats payments,

644
01:13:59.945 --> 01:14:20.745
so you have that, but the second piece is you don't have lightning address support, how do you think about that, like, I will email support? We will. I'm gonna I'm gonna make it happen. I'm just gonna ship it. I'm gonna fucking ship it. I'm gonna Is there is there a concern that, like, how does that work? Are you gonna be running basically a server that is, like, holding liquid addresses or something? Like, how does that work? Yeah. It's gonna be directory server. Right? So so,

645
01:14:21.225 --> 01:14:21.965
and that

646
01:14:22.665 --> 01:14:24.685
is not as trustless,

647
01:14:25.305 --> 01:14:29.965
is there there there's there's more trust assumption involved there, but what we can do as, like,

648
01:14:31.460 --> 01:14:34.679
a company is we can run a lightning server and basically,

649
01:14:35.620 --> 01:14:37.000
you give us, like,

650
01:14:37.540 --> 01:14:38.280
a liquid,

651
01:14:39.540 --> 01:14:42.440
you know, I guess, an ad Either either an

652
01:14:43.780 --> 01:14:52.995
x club or one address. It's probably better if it's just one address. I think address reuse is probably better than x public to be perfectly honest. So Couldn't couldn't I was thinking, like,

653
01:14:53.535 --> 01:14:55.075
every time I open the wallet

654
01:14:55.775 --> 01:15:08.380
You can send it out. Or send you, like, a 100 addresses or something. Yeah. Yeah. We we can we can lock 100 addresses. Yeah. But basically, what would happen is, like, I would create a swap between the sender and your address Yeah. As the receiver,

655
01:15:08.680 --> 01:15:14.140
and we would be hosting, like You give it to Bolt's And yeah. Yeah. Exactly. And instead of creating a lightning

656
01:15:14.600 --> 01:15:18.295
network invoice with my node as the server operator, I get a a

657
01:15:18.935 --> 01:15:29.915
I create a swap with the bolt server. It's not it's not as fully trustless as a proper bolt swap. There's, like, a tiny amount of time in in between that swap where a rug can technically happen.

658
01:15:30.300 --> 01:15:42.780
Not fully You could probably man in the middle. You could give a liquid address that you control so that I control. Yeah. There there's, like, I need to Which I think is fine. I I need to get a little deeper into that. I just want people to be able to pay me at a odel@bullbitcoin.com,

659
01:15:42.780 --> 01:16:01.220
you know. Know? Like, it's just a convenience thing. And if I need if I need more security, then I'll give them an actual invoice. Well, the thing the thing on Liquid is, like, we actually dropped the fees on Liquid. Like, is Yeah. We can just do things on a centralized network, which is great. So the fees on on Liquid is $0.01.0.01

660
01:16:01.360 --> 01:16:01.860
sat

661
01:16:02.480 --> 01:16:03.540
per v byte

662
01:16:04.160 --> 01:16:06.820
and a It's like 33 sat of transactions.

663
01:16:08.800 --> 01:16:09.940
For a confidential

664
01:16:10.240 --> 01:16:17.175
transaction, which is, like, 20 times bigger than than a than a than a regular transaction, I think we're talking about

665
01:16:17.955 --> 01:16:18.695
3,000

666
01:16:18.994 --> 01:16:19.494
vBytes.

667
01:16:19.875 --> 01:16:26.295
Therefore, yes, 33 SaaS. For a regular transaction, it's zero. Right? So so a regular transaction on liquid that's not confidential,

668
01:16:27.280 --> 01:16:30.900
is basically free. And the reason why we don't do swaps,

669
01:16:31.920 --> 01:16:34.980
under a thousand sets is because a swap transaction

670
01:16:35.360 --> 01:16:36.820
involves two on chain transactions

671
01:16:37.360 --> 01:16:40.020
and two on chain confidential transactions. So, like,

672
01:16:41.115 --> 01:16:43.295
bold Bitcoin swaps using bolts,

673
01:16:44.475 --> 01:16:49.755
which we could, like, not use confidential transactions if you wanted to, but I think it's worth it. It's not using very,

674
01:16:50.715 --> 01:16:53.055
that will be 6,000 bytes. Therefore,

675
01:16:53.435 --> 01:17:12.265
60 sets. Right? 66 Sats around that, which is, like, I don't know, man. Like, we could yeah. I mean, it's it's, like, 6% of a thousand Sats transactions. So it's, like, not great. But there's nothing stopping us from doing, for example, silent payments on Liquid. We could do that. Yeah. We could we could we could do a bunch of things. Right? We can just do that if we want to.

676
01:17:13.705 --> 01:17:14.025
So,

677
01:17:14.585 --> 01:17:18.265
definitely, like, at least on chain, I wanna have the the on chain zaps with,

678
01:17:18.905 --> 01:17:33.710
because the the UIpes that we want is, like, yeah. I I pay at Badel and then at Badel is a Master handle. So my Bold Bitcoin wallet, which I very obviously, we're gonna have Monster in the Bold Bitcoin wallet Yeah. For for many reasons. I first of all,

679
01:17:34.170 --> 01:17:35.070
I wanna have,

680
01:17:36.054 --> 01:17:39.014
private group chats Yeah. In in both Bitcoin Yeah.

681
01:17:39.895 --> 01:18:02.715
Because when you are paying someone, you are also talking with that person. Right. Whether because let's say I wanna pay you, I mean, you're gonna be like I may be like sending address. Right? It's a human condition. It's like what? It's like 80% of p two p trays are happening on, like, WhatsApp or something. Yeah. Of course. People just want to chat. Yeah. Of course. So so you want that to be confidential. There's also cool things. Obviously, the next frontier is multisig. Right? So I've never been

682
01:18:03.114 --> 01:18:04.895
a individual multis multisig,

683
01:18:06.474 --> 01:18:06.974
fan,

684
01:18:07.355 --> 01:18:09.375
like like multisig yourself.

685
01:18:09.994 --> 01:18:18.139
Never been a fan. But I think now with the technologies that that are arriving with mini scripts, now is the time to, like, have a refresh at the MultiSync experience.

686
01:18:18.519 --> 01:18:22.539
And what I really wanna do is something that I use personally. My my greatest shame

687
01:18:23.079 --> 01:18:25.099
is that I use the BitPay wallet.

688
01:18:25.719 --> 01:18:40.555
Copay. Right? It used to be called Copay, now it's just called BitPay Yeah. For multisig because The original multisig wallet. The original multisig wallet because both Bitcoin, we have some of our budget is in Bitcoin. Right? So, you know, like, when when made x does these crazy,

689
01:18:41.015 --> 01:18:44.955
like, stunts, you know, that that that for both Bitcoin, you know,

690
01:18:45.860 --> 01:19:05.775
we have a we have a a budget for we we call it that we can just do things budget, and it's it's a it's a multisig wallet. And and in order to make sure that nobody does anything too retarded with that budget, we have a multisig. And why don't you Sparrow for those? Because you want mobile? It's because we we spend a lot of we we do it all the time. Right? So you want the convenience of mobile? Yeah. Exactly. I get I get, like, a notification

691
01:19:06.155 --> 01:19:19.600
on BitPay app, which is, like, Natex wants to spend this amount of money to, I don't know, rent a tank. Oh, and it just gives you an it gives you an in app notification. Yeah. With a message. With, like, literally, like press, like, approve. Yeah. Exactly. Like, Francis, I want $5,000,

692
01:19:19.820 --> 01:19:25.280
I'm gonna rent a tank Right. For for a video shoot or something. And I'm, like, approve or deny. So I want that

693
01:19:25.995 --> 01:19:35.534
over white noise. Yeah. I want that over in Austria. 100%. Right? I wanna do other things in in in Austria. I want White noise will be perfect for that. I want it's still early, but it'll Like, I wanna be able to communicate

694
01:19:35.835 --> 01:19:37.855
with the the bull users. Yeah.

695
01:19:38.170 --> 01:19:53.835
I can't right now. As as the bull bitcoin operator be because I've said this push notification, basically. Well, probably push notification. Well, basically, what I can do is I can create a nostril as a very small I don't I don't wanna compete with with social media stuff. I wanna use nostril as a back

696
01:19:54.215 --> 01:20:06.590
end. A contact foot. Yeah. Yeah. Yeah. Yeah. It's just like as a back end communications network for contacts and for stuff like that. But there's nothing stopping you or us, which obviously we will do, to generate a master key pair and you're connected to,

697
01:20:07.050 --> 01:20:15.870
you're automatically following whole Bitcoin or you're automatically collected to to my relay or something like that. And I'm saying, like, guys, we have an update or something like that. And and you,

698
01:20:16.435 --> 01:20:32.240
I'm not pushing anything to you. You're following me, I'm not sure. Right. Automatically And you're opening the app and you don't even check your And and and in the app, we can just say, like, hey. Any message that's coming from this end pub Just say displayed on the displayed on the homepage. Right? Because we this end pub is the, like, emergency

699
01:20:32.780 --> 01:20:47.905
bulb equipment and, like, there's a bug. We need to update stuff transact whatever it is. Or, like, you know, Indians have arrived, whatever it is. It's important. It's important to be able to communicate with the users in a secure way. Yeah. So so not not not not not their art, silent payments, all that kind of shit. I love it. Like yeah.

700
01:20:48.525 --> 01:20:53.244
Yeah. Okay. I don't, like, kept you too long already, and you have some obligations, but,

701
01:20:54.045 --> 01:20:55.324
you're not allowed to leave without

702
01:20:56.204 --> 01:21:00.730
what's your opinion on, core thirties opera turn? Oh, well,

703
01:21:03.750 --> 01:21:11.510
it's such a I have the only correct opinion, by the way. So I have I have the I've noticed that about most of your opinions is how you feel about them. And and,

704
01:21:11.830 --> 01:21:17.285
it's it's it's it's it's so nuanced. In order to be correct, you need to have a lot of nuance.

705
01:21:19.585 --> 01:21:19.825
I,

706
01:21:21.105 --> 01:21:23.685
I don't wanna burst anybody's bubble, but running knots,

707
01:21:24.465 --> 01:21:25.185
will not

708
01:21:25.745 --> 01:21:27.845
it's it's it's there there's

709
01:21:28.225 --> 01:21:29.205
there's there's a certain

710
01:21:29.640 --> 01:21:30.140
fatality,

711
01:21:30.760 --> 01:21:35.020
fatalistic aspect to my opinion, which is there's nothing we can do really to prevent

712
01:21:35.560 --> 01:21:36.060
spam,

713
01:21:36.440 --> 01:21:38.140
and that was proven by,

714
01:21:39.720 --> 01:21:46.105
you know, the kind of like the joker of Bitcoin, like Peter Todd, you know, who, like, created Liber Relay and he was like, like

715
01:21:46.485 --> 01:21:52.105
We'll relay all the things. Oh, we'll relay all the things. And then before before that, there was a kind of gentleman's

716
01:21:52.485 --> 01:21:52.985
agreement

717
01:21:53.684 --> 01:21:56.905
in Bitcoin that, you know, we have two mechanisms.

718
01:21:57.350 --> 01:22:03.190
We have the policy one and we have the consensus one. And the policy one, you can call it a gentleman's agreement, like,

719
01:22:03.990 --> 01:22:13.785
and if someone decides to not be a gentleman, you can't force the agreement on them. Whereas the consensus layer, of course, is the hard rules. That's the hard rules of government. It's the hard the hard rules, of course.

720
01:22:15.705 --> 01:22:17.325
And, you know, I,

721
01:22:18.185 --> 01:22:24.125
I have mixed feelings about Bitcoin Core, and I I kinda feel it's kinda weird because I've been in the early camp

722
01:22:24.739 --> 01:22:26.360
of, like, you know,

723
01:22:26.820 --> 01:22:29.000
there's some things about Bitcoin core,

724
01:22:29.780 --> 01:22:35.239
the the process, because bit like, there's something about the Bitcoin core process and, of the Bitcoin core

725
01:22:35.620 --> 01:22:37.719
inner circle that I don't like. Yeah.

726
01:22:38.685 --> 01:22:47.585
There's definitely, like, a a click a little clicky 100%. Yeah. Aspect to it and, you know, not everybody's PRs get merged and it it helps the difference.

727
01:22:47.965 --> 01:23:18.795
Yeah. If you want to get sh things shipped in Bitcoin core and you're part of the inner circle, you kind of, like, get you know, you're not automatically white listed, but, you know, your your stuff is So there's a fast track. Yeah. You're fast track. There's, like, things that that I don't like. Specifically about Bitcoin core 30, by the way, which really sucks is they removed that was the thing that I that pissed me off the most. Really niche thing. They removed support for legacy wallets. They removed support for importing Bitcoin. Bitcoin addresses and private keys into a Bitcoin core wallet, which means that we will not be updating to Bitcoin core 30,

728
01:23:19.415 --> 01:23:19.915
because,

729
01:23:20.215 --> 01:23:23.195
part of Cipher Note, like our open source Bitcoin back end relies

730
01:23:23.869 --> 01:23:27.650
on that to work, relies on legacy wallets, so that kinda sucks.

731
01:23:28.510 --> 01:23:31.650
But Bitcoin's fine. Bitcoin's What was their argument for that?

732
01:23:34.429 --> 01:23:47.022
I I'm assuming it's because They built cleanup or something? Yeah. Something is that they don't they don't wanna work. They don't wanna maintain it. Yeah. And, it's fine. Like, I don't need them to make I can run, you know, 29.2,

733
01:23:47.271 --> 01:23:49.016
forever. Yeah. 29.2

734
01:23:49.016 --> 01:23:51.510
introduces the 0.1 stats per, or the

735
01:23:52.389 --> 01:24:10.304
the lower side bite limit. You like that change. I fucking love it, man. I fucking love it. Like, if the miner is, there's you know, I don't wanna have an artificial price for for Yeah. That's that's communism. You know? That's what we have in Canada with the price of fucking maple syrup. You know what I mean? There's a an artificial price for on it or something like that. So I'm I'm happy that the fees are fees are getting low.

736
01:24:10.925 --> 01:24:13.105
But the thing is, like, if I had never

737
01:24:13.725 --> 01:24:16.304
heard of the Bitcoin core upturn,

738
01:24:17.244 --> 01:24:17.744
debate,

739
01:24:18.525 --> 01:24:20.784
it would still have not affected my life. Right?

740
01:24:21.165 --> 01:24:28.040
So and, of course, like, I don't I don't like spam. Of course. I don't want it to be on Bitcoin.

741
01:24:29.380 --> 01:24:39.515
I don't like shit coins. I don't like I don't I don't want some people want the shit coins to be on Bitcoin. Like, they specifically want that. Like, I don't want that at all. Same. I'm a monetary Bitcoiner. You know, I think the Bitcoin,

742
01:24:40.055 --> 01:24:47.275
blockchain is not a general purpose database. It's it's a financial it's a monetary transaction database. It's like what I want it to be. It's money. It is money,

743
01:24:47.735 --> 01:24:48.475
but unfortunately,

744
01:24:49.495 --> 01:24:53.960
it's not up to me to decide what it is. It's up to the the the the consensus,

745
01:24:54.500 --> 01:25:07.165
to decide. And short of a soft fork or a hard fork even maybe, there's nothing we can do. And Is there even a really a fork that could stop it? I mean, you could obviously move off return, but you still have shit coins in Bitcoin. I mean,

746
01:25:07.965 --> 01:25:11.585
there would certainly be a whack a mole game where, you know,

747
01:25:12.445 --> 01:25:50.065
after we do let's say we do some You can't but you can't really do whack a mole soft forks. So the soft forks are super difficult to pull off. Correct. And and I think people have gotten a little bit spoiled. We haven't had that many soft works, but people have gotten spoiled with the soft works that we have. Yeah. They don't realize that, first of all, there's no really way to know if there's consensus ahead of time. Yeah. You're kinda winging it. You feel like there's consensus. Yeah. And if a significant portion if there isn't consensus, you could have an inverted chain split after the fact. Yeah. Of course. Of course. Which would just be chaotic. It'd be fine. Everyone would be, like, you could Yeah. Go to sleep and be fine if you have have your funds in self custody. But if you're running businesses and stuff, it'd be a fucking pain in the ass. Yeah. Yeah. So, like,

748
01:25:50.389 --> 01:25:55.369
aesthetically, I'm kind of like, I wish there was no spam. Yeah. I wish there was no nothing. And then,

749
01:25:55.670 --> 01:26:01.770
you know, I I also I also feel like there's something wrong with the Bitcoin core process. But at the same time, like,

750
01:26:02.165 --> 01:26:05.785
Bitcoin core does ship really nice things, and a lot of the technologies

751
01:26:06.165 --> 01:26:08.905
that, we're going to need I mean,

752
01:26:09.445 --> 01:26:10.265
I'm not

753
01:26:10.645 --> 01:26:16.025
I I I I'm I'm getting closer to the belief that that some form of confidence

754
01:26:16.325 --> 01:26:16.825
is

755
01:26:17.840 --> 01:26:19.760
is something that I would like to see on Bitcoin.

756
01:26:20.559 --> 01:26:22.260
And the thing is, like,

757
01:26:22.880 --> 01:26:23.380
I

758
01:26:23.920 --> 01:26:30.615
I've never been, like, fully closed minded against covenants. I just I was just, like, you know, like, kind of like with Taproot, it's, like,

759
01:26:31.575 --> 01:26:32.315
with Arc,

760
01:26:32.695 --> 01:26:52.170
now it's like, oh, you can actually use Taproot to be so so so Arc is a Taproot thing. Right? Yeah. Taproot is and I was like very skeptical of Taproot because like, no nobody is fucking using Taproot. Like, only the shareholders are using Taproot. It's fucking retired. Why did we even need Taproot? Yeah. The thing is Bolt actually uses Taproot for the the refund path, which is great. So Bolt,

761
01:26:52.710 --> 01:26:57.765
actually implemented Taproot in a really nice way. So I was, like, actually, Bull Bitcoin is now a Taproot

762
01:26:58.065 --> 01:27:02.405
user. Right. And with ARC, ARC is just full Taproot. Right? So I'm like, okay.

763
01:27:03.185 --> 01:27:06.965
What the guys on ARC have done, it it's kinda like, okay. Right. So

764
01:27:07.505 --> 01:27:08.885
despite opening up

765
01:27:10.340 --> 01:27:11.320
some attack vector,

766
01:27:11.700 --> 01:27:13.320
we did gain arc with Taproot.

767
01:27:13.940 --> 01:27:22.455
Right? And then, with And with the attack vector, it's, like, cheaper spend. Right? Yeah. Yeah. There was the Inscriptions exploit, which was always possible, quote, quote, but obviously made

768
01:27:23.015 --> 01:27:25.575
Significantly cheaper. Right? Yeah. Yeah. It made made,

769
01:27:27.095 --> 01:27:28.715
the the barrier to spam,

770
01:27:29.575 --> 01:27:34.075
difficult or the barrier to spam was, like, reduced, let's call it, with with Taproot,

771
01:27:34.695 --> 01:27:36.375
somewhat, not not fully, but somewhat.

772
01:27:37.150 --> 01:27:40.290
They could they could have spanned anyway on just segway without that route. But,

773
01:27:41.230 --> 01:27:42.370
so I think, like,

774
01:27:43.150 --> 01:27:43.650
we

775
01:27:44.110 --> 01:27:48.610
core core can and this is the kind of thing that that core can ship that

776
01:27:48.990 --> 01:27:51.775
that very few other people can ship. Like, let's say,

777
01:27:52.395 --> 01:27:56.335
to ship Convenience onto Bitcoin is something that's very,

778
01:27:57.275 --> 01:27:58.175
very tricky,

779
01:27:58.635 --> 01:27:59.135
and

780
01:27:59.675 --> 01:28:00.815
even the core devs

781
01:28:01.675 --> 01:28:13.680
and and the Bitcoin devs in general, like, don't agree. And And when we implement it, it's it's hardcore shit, man. It's like it's and so having having, like, hardcore protocol crypto experts

782
01:28:14.060 --> 01:28:16.080
able to deliver that thing is

783
01:28:17.020 --> 01:28:17.760
is is nice.

784
01:28:18.265 --> 01:28:18.765
So

785
01:28:19.625 --> 01:28:21.885
that could be upgrading to Bitcoin $4.30

786
01:28:22.185 --> 01:28:22.685
until

787
01:28:23.225 --> 01:28:24.205
we've fixed.

788
01:28:24.505 --> 01:28:32.125
And what's funny you gotta do work on the cipher node side to remove the legacy wall. It depends on Yeah. And you know what's gonna do? Some time to do that. I mean, I was gonna do that anyway.

789
01:28:32.745 --> 01:28:35.540
Eventually, I was gonna we were gonna switch server stuff eventually,

790
01:28:36.560 --> 01:28:37.440
but, you know,

791
01:28:37.920 --> 01:28:38.420
yeah.

792
01:28:39.119 --> 01:28:41.699
That's that's the essence of my opinion is that,

793
01:28:42.320 --> 01:28:43.860
it's, it's over. The the the the

794
01:28:45.840 --> 01:28:49.545
the the gentleman's agreement was broken, and that's what it is. Yeah. We,

795
01:28:50.185 --> 01:28:53.085
I think I'm pretty much completely aligned on your opinion,

796
01:28:54.185 --> 01:28:55.485
and I've talked about this

797
01:28:56.505 --> 01:28:57.485
just at length,

798
01:28:58.344 --> 01:29:00.185
for almost over a year now.

799
01:29:00.585 --> 01:29:10.530
Just been a massive DDoS in my time, but, look, it's good that people care about Bitcoin so much. Yeah. I think we died based on apathy. Apathy is probably the single biggest risk to Bitcoin.

800
01:29:11.310 --> 01:29:14.610
Just real quick, so when we launched Open Sats,

801
01:29:15.615 --> 01:29:18.675
this was the main concern we had was

802
01:29:19.055 --> 01:29:20.675
the there was a very,

803
01:29:23.455 --> 01:29:26.835
I had maybe it's too strong of a word, but it felt kind of like incestuous

804
01:29:27.375 --> 01:29:29.075
funding path and

805
01:29:29.590 --> 01:29:30.810
core group. Mhmm.

806
01:29:31.110 --> 01:29:36.730
And we thought Open SaaS could do something different and be more independent and be more transparent

807
01:29:37.270 --> 01:29:53.875
and be more open. Yeah. And and I think we've really accomplished that goal, we've provided over 300 grants, like really just try to broaden the pie. Yeah. And a lot of that the overall majority of that isn't for protocol. Yeah. It's for us, you know, we're the largest supporter of BTC pay server now. Mhmm. We've done a lot of cashier support,

808
01:29:54.414 --> 01:30:04.570
tons of different mobile wallets, pay join. Yeah. We help them start up their their in their non profit. They have their own non profit now, and that's one of the things we wanna see, like, a thousand flowers bloom.

809
01:30:05.270 --> 01:30:15.375
But for better or for worse, we found basically massive success, and now we're the heavyweight in the room. Yeah. And so I'm getting a lot of flack, which is fine, like I understand, you know, people

810
01:30:16.155 --> 01:30:24.175
and and to be clear, the way we designed OpenSats is that I'm just one vote of nine votes. Yeah. Yeah. So, like, I can't unilaterally push things through. But do you have any

811
01:30:24.555 --> 01:30:27.215
there's a new narrative of just, like, funding any developers

812
01:30:27.910 --> 01:30:40.010
this way is bad. Do you have any, like, recommendations or opinions on how we proceed with OpenSats? Like, what's the best path for Bitcoin going forward on that front? I think OpenSats failed a very much needed

813
01:30:42.324 --> 01:30:47.864
narrative and an operational space, which is that the protocol devs were, like,

814
01:30:49.685 --> 01:30:50.005
they're

815
01:30:50.804 --> 01:30:52.985
to improve Bitcoin, you you

816
01:30:53.364 --> 01:31:08.565
you you can do other types of software which is not protocol development, like like the ones that you named. And before OpenSats, I think, like, the the the Bitcoin cord if you wanted to to fund the Bitcoin, you would just fund Bitcoin cord devs and what OpenSats is is fund the application layer, which is the one that is that I'm that that I'm most interested in.

817
01:31:09.285 --> 01:31:09.945
You know,

818
01:31:11.045 --> 01:31:13.545
I wish there was more private companies

819
01:31:14.324 --> 01:31:16.405
Same. Doing that. Right? And, like,

820
01:31:16.965 --> 01:31:20.425
I I will say that that's one of my biggest,

821
01:31:22.320 --> 01:31:24.179
my pride is that, like,

822
01:31:25.600 --> 01:31:27.440
all of the software that we do,

823
01:31:27.840 --> 01:31:33.219
is is funded by us. Right? So, like, the Bolt the Bolt Rust library, which is used by a bunch of,

824
01:31:33.985 --> 01:31:38.285
these, these these new wallets, that's us. Like, we maintain a bunch of open source software.

825
01:31:39.145 --> 01:31:39.965
You know, PayJoin,

826
01:31:40.505 --> 01:31:43.805
I I paid my debts to work on PayJoin. I paid,

827
01:31:44.265 --> 01:31:44.925
I financed,

828
01:31:45.385 --> 01:31:54.410
you know, I I did, like, little private grants, so, like, joinster and, like, a bunch of shit like that. I wish a lot of more people would do it, but, apparently, they don't.

829
01:31:55.350 --> 01:31:58.095
I am actually, like, kinda, like, a little concerned that,

830
01:31:58.735 --> 01:32:01.395
that I'm competing with OpenSats for, like, employees.

831
01:32:02.495 --> 01:32:24.860
So so but, you know, it is what it is. Like pay them less than people realize, though. Yeah. Yeah. We we intentionally don't publicly say what our highest grant amount is because people would just apply for the highest, but it's not that high. Yeah. I mean, it's not it's not that high, but, you know, Bull Bitcoin is also not like a VC funded company. So we, like, you know Yeah. But that's a that's an ethical I like the choice. Yeah. I think a lot of the a lot of Bull Bitcoin devs,

832
01:32:25.685 --> 01:32:31.545
take a pick at working on Bold Bitcoin. They take a look. Also say, like, look. My dream is similar to your dream because

833
01:32:31.925 --> 01:32:53.060
I actually have to go out there as a volunteer and try and raise donations Yeah. Which is not sustainable. Yeah. And I think it's much more sustainable, and I'm a capitalist to have private companies doing this. And that's where the ten thirty one side comes in. Right? Because we're one of the few Yeah. VCs that actually fund full open source stack companies like StartNine Yeah. Yeah. Or mempool mempool that space Yeah. Primal. Mhmm.

834
01:32:53.460 --> 01:32:59.465
And the dream there is, like, actually sustainable, profitable businesses that contribute to open source. Yeah. And I would just say on that front too,

835
01:33:00.245 --> 01:33:03.225
while I really respect that you are completely bootstrapped operation,

836
01:33:04.325 --> 01:33:12.610
as a Bitcoin focus open source VC, there's also not that much money there. No. No. Right. Yeah. Yeah. Yeah. No. For sure for sure. It's not a light spark. It's a 165,000,000

837
01:33:12.690 --> 01:33:21.030
Yeah. Yeah. Yeah. No. Scene around. And and to be very clear, like, I love what you guys are doing. And, you know, fuck the haters. Go they they could go fuck themselves. It's, you know, if you're not if you're not

838
01:33:21.330 --> 01:33:22.310
building anything,

839
01:33:23.250 --> 01:33:23.989
your opinion

840
01:33:24.370 --> 01:33:39.335
matters very little to me. Right? And, like, you know, you guys are not specifically building shit, but you're you're you're you're enabling builders. Yeah. And, like, you know, there's a really good example, for example, is page on. Like, page on is a great example where, like, we contributed,

841
01:33:39.795 --> 01:33:41.255
a little bit to it, but

842
01:33:41.840 --> 01:33:48.260
for pay joins to go from v zero to v one to v two to the release of v two to go to v three,

843
01:33:48.800 --> 01:33:51.300
that's a four to five year effort,

844
01:33:51.600 --> 01:33:52.340
in total

845
01:33:52.720 --> 01:33:53.220
that,

846
01:33:54.560 --> 01:33:55.060
required,

847
01:33:56.585 --> 01:34:05.885
I don't know how many people. And to go to v three is gonna also take, like, you know, two to three to four, like, almost like full time people to, like, to get there.

848
01:34:06.825 --> 01:34:07.325
And

849
01:34:07.880 --> 01:34:22.940
even for a company like Bullbick, it's like it's above my budgets to fund the entire page on the thing. Like, I can't, I can't, you know, I have other employees, you know, that I have to take care of. So a lot of these things like, like kind of like wouldn't happen and even stuff like, like arcade and like,

850
01:34:23.335 --> 01:34:27.034
you know, who knows how they're going to make money. It's, it's, it's, it's very, very experimental.

851
01:34:27.895 --> 01:34:28.395
But

852
01:34:28.775 --> 01:34:32.695
I, I, I think that, you know, there is money to be made in open source software.

853
01:34:34.614 --> 01:34:52.715
We're very fortunate at Bold Bitcoin that we have, you know, the only profitable business model in the space Yeah. Which is like Bitcoin brokerage. Buy, sell Bitcoin. Yeah. Buy or sell Bitcoin. Charge a reasonable fee. Yeah. Exactly. And like, there there's there's others but like, you know, there's others but, you know, mostly that's that's the one and then so,

854
01:34:53.415 --> 01:34:54.155
and then

855
01:34:54.455 --> 01:35:02.315
we we use I use open source as a marketing tool. Yeah. Right? So and it's not just for that, obviously. Like, I do it because

856
01:35:02.935 --> 01:35:04.635
I I do it because, like,

857
01:35:05.820 --> 01:35:07.040
out of

858
01:35:07.980 --> 01:35:13.199
out of ego, out of pride, and out of, since there is a sincere there is a sincere desire,

859
01:35:13.900 --> 01:35:27.805
to to help Bitcoin and and and to do something. And it's where we hold the line. Right? Sort of software is where we hold the line. Yeah. Yeah. Exactly. It's foundational. It's it's the it's the core of the freedom movement. Yeah. Yeah. Of course. And it it's also it's also really fun, to be perfectly honest. Like,

860
01:35:28.425 --> 01:35:33.085
as someone who's dealt with governments and banks and, you know, running a Bitcoin exchange is just an endless

861
01:35:33.410 --> 01:35:44.070
and endless stream of problems. Like, every day I wake up, I open my phone and it's just like problem, problem, problem, problem. But, like, what I've I have found with open source is this really satisfying,

862
01:35:45.250 --> 01:35:46.310
purely creative,

863
01:35:46.770 --> 01:35:47.270
unrestrained

864
01:35:48.050 --> 01:35:57.775
like, Like, you can do anything in open source development, and you don't have to you don't need to ask anybody's permission. And, like, the sky is the fucking limit. Like, software is magic. You know? The more I the more I discover open source software,

865
01:35:58.155 --> 01:36:02.575
the more I'm just, like, like, happy. You know? So working for me, working in open source software

866
01:36:03.115 --> 01:36:03.695
is what

867
01:36:04.100 --> 01:36:21.265
allows me to swallow the shit of, like, the fiat world of running exchange is, like, knowing that at least half of my day is gonna be interesting, which is the half of my day where I'm working with the open source desk. I love it. Francis, this is great. Let's do this more often? Yeah. Totally, man. Okay. Yeah. Get some upstairs. Thanks so much, man. Alright.

868
01:36:22.205 --> 01:36:29.344
Freaks. I hope you enjoyed that. Hopefully, I'll get some more in person rips while I'm here in Lugano. Maybe I won't. Not sure. But,

869
01:36:30.205 --> 01:36:31.824
stay on the stack sets. Peace.