1
00:00:00,000 --> 00:00:08,480
sup reeks yeah nine years after the first four years since our last uh 614 15 episodes uh add

2
00:00:08,480 --> 00:00:14,320
100 to it this will be uh you'll be 7 13 or 14 depending on when we put this out good to see you

3
00:00:14,320 --> 00:00:18,240
again marty it's good to see you too we have a lot to catch up on all right let's just jump in

4
00:00:18,240 --> 00:00:22,720
uh all right so uh there's this guy jeffrey epstein he's uh got a lot of people caught

5
00:00:22,720 --> 00:00:27,200
up in some stuff there's some emails out there jeff epstein the bitcoin maxi yeah yeah that guy

6
00:00:27,200 --> 00:00:38,400
uh i am astounded at how many people are showing up in those files yeah it's crazy to me it i think

7
00:00:38,400 --> 00:00:44,460
it's not surprising that the guy who owned the biggest house in new york city who had hundreds

8
00:00:44,460 --> 00:00:49,580
of millions of dollars was interested in a speculative financial opportunity in 2014 2017

9
00:00:49,580 --> 00:00:56,280
that's not particularly surprising to me i think the fud that he had anything more to

10
00:00:56,280 --> 00:01:02,520
do with it than that that it was being used for who knows what i don't think there's any evidence

11
00:01:02,520 --> 00:01:06,840
for that but that's not the most damn thing the most damn thing is how many people were

12
00:01:06,840 --> 00:01:13,080
communicating with this guy well after it was known he was a creep convicted creep convicted

13
00:01:13,080 --> 00:01:18,760
creep uh openly not even by the end to you signal or saying let's take this to a phone call or

14
00:01:18,760 --> 00:01:22,440
anything just gmailing back and forth casually about can we meet up can we talk about this

15
00:01:22,440 --> 00:01:29,080
opportunity it's crazy to me how many people were comfortable with that yeah and like just reading

16
00:01:29,080 --> 00:01:32,600
through some of the emails haven't done a deep dive on all three million emails but the ones

17
00:01:32,600 --> 00:01:37,320
that i've seen floating up on twitter it does seem like uh i want to suck off the teat even though i

18
00:01:37,320 --> 00:01:41,640
don't think there's anything particularly damning or criminal but a tremendous amount of poor

19
00:01:41,640 --> 00:01:47,800
judgment on a lot of people's parts yeah lack of moral character yeah that's uh you know there's

20
00:01:47,800 --> 00:01:51,800
always been what was this saying i think we mentioned this in 2017 when we did the first

21
00:01:51,800 --> 00:01:57,320
episode it's the way the smartest of people in the dumbest of money meet yeah yeah well wow talk

22
00:01:57,320 --> 00:02:02,120
about the dumbest of money i mean he had hundreds of millions of dollars at his disposal but also a

23
00:02:02,120 --> 00:02:07,560
twice convicted sex offender most notorious in the world there are certainly other places you could go

24
00:02:07,560 --> 00:02:13,240
if you need an extra buck yeah i'm not quite sure why people felt the need to continue a relationship

25
00:02:13,240 --> 00:02:16,680
with him there are plenty of examples in the files of people rejecting his company

26
00:02:16,680 --> 00:02:22,780
I wish more of the people that showed up that were in the Bitcoin adjacent ecosystem would have done the same.

27
00:02:23,260 --> 00:02:23,620
Agreed.

28
00:02:24,540 --> 00:02:28,240
No, it is, I'm just talking to people behind the scenes.

29
00:02:28,400 --> 00:02:34,080
It is spooking people like, oh, it's just going to be an existential narrative crisis for Bitcoin.

30
00:02:35,140 --> 00:02:40,480
You know, if you hint and wink and nudge at it, you can say this person and this person and this person.

31
00:02:40,560 --> 00:02:45,080
Play six degrees and say, oh, you can point to Jeff Epstein and eventually get to someone you might have met.

32
00:02:45,080 --> 00:02:45,280
Get to me.

33
00:02:45,660 --> 00:02:46,260
Yeah, right.

34
00:02:46,260 --> 00:02:52,900
get to you yeah but to what end okay so this person sent this person an email and then that

35
00:02:52,900 --> 00:02:58,740
person did what it looks like a lot of it was sent some money for a speculative investment okay yeah

36
00:02:58,740 --> 00:03:05,780
and what happened i think the uh the media labs thing is the the most most interesting because i

37
00:03:05,780 --> 00:03:13,620
think there's a lot of bitcoiners that have come into the space uh more recently and weren't around

38
00:03:13,620 --> 00:03:21,460
back in that era when uh joy ito in the media lab uh the mit media lab really began sort of backing

39
00:03:21,460 --> 00:03:26,100
core developers and gavin anderson people have been talking about i think there's a lot of

40
00:03:26,100 --> 00:03:31,300
misunderstood context by newer bitcoiners where if you were around back in the day

41
00:03:31,940 --> 00:03:35,700
mit media lab like in the beginning people were like oh this is pretty cool but then they started

42
00:03:35,700 --> 00:03:42,180
doing weird stuff and i think gavin anderson obviously 2015 when he started pushing what was

43
00:03:42,180 --> 00:03:47,140
a bitcoin classic bitcoin ultimate bitcoin xt right it's hard to keep track of all the fours

44
00:03:47,940 --> 00:03:53,460
and then um i don't even like joy ito and like what was it nira what was her name um

45
00:03:54,660 --> 00:03:59,460
name just gave me but i remember yeah they started putting out like proposals that i remember being

46
00:03:59,460 --> 00:04:04,420
like that i don't like this and publicly being like this is not the way bitcoin should go well

47
00:04:04,420 --> 00:04:08,020
you know instead of dismissing let's look at it adversarially and there's two ways you can go right

48
00:04:08,020 --> 00:04:13,540
the adversarial way is okay so there's this shady i'm just sex offender that's the easy

49
00:04:13,540 --> 00:04:18,260
that's the scivia stuff he's also obviously involved with intelligence agencies and all sorts

50
00:04:18,260 --> 00:04:25,460
of oligarchies and autocracies and bad actors all around and he's throwing money at uh early stage

51
00:04:25,460 --> 00:04:31,140
bitcoin developers to some nefarious end he wants to get some proposal implemented in bitcoin for

52
00:04:31,140 --> 00:04:37,460
reasons unknown it doesn't look like any of the things that were proposed were particularly

53
00:04:39,140 --> 00:04:47,460
successful uh if i think of can you name some uh media lab we were talking about downstairs like

54
00:04:47,460 --> 00:04:52,420
again if we're kimono open we're gonna think of something as like tad try to he was at media lab

55
00:04:52,420 --> 00:04:56,820
for he was funded by the street log contracts and then there's the beginning of the lightning network

56
00:04:56,820 --> 00:05:02,660
yeah uh so if you really wanted to be tinfoil had you could say jeff epstein wanted payment

57
00:05:02,660 --> 00:05:08,180
channels for some reason enlightening was just an iteration on a payment channel idea that had

58
00:05:08,180 --> 00:05:14,100
been around for a while yeah to what end again yeah um well let's keep going with that adversarial

59
00:05:14,100 --> 00:05:18,020
thought maybe he wanted maybe he's the man who wanted to make sure that bitcoin was wired as

60
00:05:18,020 --> 00:05:23,140
a settlement network and it would become digital gold and not actually bitcoin cash he's thwarted

61
00:05:23,140 --> 00:05:27,860
satoshi's true vision that seems wildly unlikely there are so many different things that have to

62
00:05:27,860 --> 00:05:34,980
line up to make that true it's much more the it's fun to play conspiracy theorist conspiracy fact is

63
00:05:34,980 --> 00:05:39,140
much creepier which is this guy had a ton of money and was putting it every which way and there were

64
00:05:39,140 --> 00:05:43,380
plenty of people who should have said no who were well within their rights to say no but didn't feel

65
00:05:43,380 --> 00:05:50,180
like saying no because money is fun joy certainly certainly should have known better there's no mit

66
00:05:50,180 --> 00:05:54,980
is procedures university there was no shortage of potential funding oh that's where we get into

67
00:05:54,980 --> 00:06:01,860
like conspiratorial nature yeah so why lay down with this guy i incredibly poor judgment yeah

68
00:06:02,980 --> 00:06:08,260
no it is um it has been a crazy week yeah this coming out you get the price dumping

69
00:06:09,140 --> 00:06:14,660
uh it's just a weird time do you think the price is jumping related to the news or is it shocked

70
00:06:14,660 --> 00:06:20,420
i think there's more i've actually been trying to do more research on the october 10th last year

71
00:06:20,420 --> 00:06:24,420
the whole binance thing yeah binance thing like i've been talking to some people that are

72
00:06:26,100 --> 00:06:29,940
well within the know like the market makers that were affected by that and they're like these people

73
00:06:29,940 --> 00:06:34,260
don't feel comfortable coming back to like make markets and a liquidity profile for big i could be

74
00:06:34,260 --> 00:06:38,580
wrong but that's much more interesting to me not that i mean we can talk about the epstein stuff

75
00:06:38,580 --> 00:06:42,980
all day if you want yeah but that's much more interesting to me uh if you see one thing that

76
00:06:42,980 --> 00:06:50,500
a friend of mine pointed out to me is that bitcoin has been dropping steadily on the weekends uh

77
00:06:50,500 --> 00:06:56,580
which is something we've seen in the past when a major market maker in exchange blows up and

78
00:06:56,580 --> 00:07:00,980
they're unable to cover it during the normal intraday trading sessions and that's obviously

79
00:07:00,980 --> 00:07:05,060
conspiracy there might be a million reasons why bitcoin is dropping over the reasons that was his

80
00:07:05,060 --> 00:07:11,460
theory uh i'd sort of pushed back on that but the idea that they're instead of somebody blowing up

81
00:07:11,460 --> 00:07:15,620
that there were market makers and liquidity providers who were just spooked by what happened

82
00:07:15,620 --> 00:07:19,940
on 10 10 and now the price just bottomed out from none of them and they're staying on the sidelines

83
00:07:21,380 --> 00:07:26,100
yeah that's worth investigating i think that i think there are external factors just broader

84
00:07:26,740 --> 00:07:35,220
liquidity in the in the uh economy if you look at um what's happening uh at the stock market i think

85
00:07:36,100 --> 00:07:40,420
there are many people looking at what's happening in ai and being like all right there's 400 billion

86
00:07:40,420 --> 00:07:45,940
dollars of capital that's been outlaid into these hyperscalers specifically working on the models

87
00:07:45,940 --> 00:07:50,020
and they're only bringing in 20 billion dollars of revenue or something like that and so they're

88
00:07:50,020 --> 00:07:54,180
positioning for a crash and everyone's slowly taking their chips off the table that's another

89
00:07:54,180 --> 00:08:00,980
good one yeah uh let's see what else is there there's potential changes to the federal reserve

90
00:08:02,500 --> 00:08:07,300
hawkish fed chair coming in what could that mean likes bitcoin but he's hawkish bad for bitcoin

91
00:08:07,300 --> 00:08:16,060
quantum fud or not fud that's it's it's almost gonna say fud and not fud quantum joke there

92
00:08:16,060 --> 00:08:23,140
i took you a second took me a second but now i got it yeah no there's a there's a ton of like

93
00:08:23,140 --> 00:08:28,420
i think 13 years in that's the one thing i've learned is like who the fuck knows exactly why

94
00:08:28,420 --> 00:08:36,180
more buyers than sellers right that's the line yeah and uh but i certainly do think there's more

95
00:08:36,180 --> 00:08:45,360
more doubt around bitcoin that i've seen in quite some time um maybe since 2022 but even 2022 there

96
00:08:45,360 --> 00:08:50,540
was this you could point at sam bank from freed and be like oh it was definitely him like everybody's

97
00:08:50,540 --> 00:08:56,140
a bad actor and you could slowly rebuild that um that's sort of reputational trust with bitcoin

98
00:08:56,140 --> 00:09:00,560
specifically but right now like as we're discussing it's like what is the exact cause there's no ftx

99
00:09:00,560 --> 00:09:04,980
to point at maybe you can put it binance on october 10th but it doesn't seem like many people are

100
00:09:04,980 --> 00:09:10,680
doing that i think people are getting spooked one thing that we didn't mention was at the

101
00:09:10,680 --> 00:09:16,920
when donald trump was first elected there was all the talk of the strategic bitcoin reserve day one

102
00:09:16,920 --> 00:09:22,100
that was literally what we were talking about and now it's what a year and change into this

103
00:09:22,100 --> 00:09:26,340
administration and there's nothing on the horizon maybe it's that narrative dying out and the idea

104
00:09:26,340 --> 00:09:31,100
that the government is going to be there to buy your bags so well it's even worse than that uh

105
00:09:31,100 --> 00:09:34,840
because we do have the executive order strategic reserve where it's anything we've seen we get the

106
00:09:34,840 --> 00:09:39,600
keep and then you had the guy who's supposed to be looking over uh the seized bitcoin fund his son

107
00:09:39,600 --> 00:09:45,240
just took the keys and ran is that so hang on is that the guy who's supposed to watch over or is

108
00:09:45,240 --> 00:09:51,820
that treasury versus doj is there i think they hired a third party custodian i don't know i

109
00:09:51,820 --> 00:09:56,540
didn't dive deep into this story i mean i've seen the headlines and i think the last thing i saw a

110
00:09:56,540 --> 00:10:00,960
few days ago is like the kid took 40 million dollars of seized how hard is it to set up a

111
00:10:00,960 --> 00:10:05,700
multi-sig come on guys this is a humiliation ritual I mean it's why we're still so early this

112
00:10:05,700 --> 00:10:10,200
is why yeah this is okay we're gonna go bullish now we're so early don't even know how to secure

113
00:10:10,200 --> 00:10:13,860
Bitcoin properly at the government level which should not be shocking the government can't really

114
00:10:13,860 --> 00:10:21,600
do much competently so um yeah all of this is to say weird times in Bitcoin weird how would you

115
00:10:21,600 --> 00:10:29,220
compare this environment right now to you know it was definitely strange back when we did the first

116
00:10:29,220 --> 00:10:35,700
one 2016 2017 because there was the whole ICO phenomenon and some the first ICO was a one-off

117
00:10:35,700 --> 00:10:39,000
right you just say well that's weird that's a bizarre thing that happened and then the next

118
00:10:39,000 --> 00:10:45,900
one comes and then suddenly was file coin raised 250 million for a colored coin Tezos yeah yeah

119
00:10:45,900 --> 00:10:52,980
around that time too and then we're off to the races and you watch everyone sort of lose their

120
00:10:52,980 --> 00:11:01,380
lines collectively, and then they all come back to their senses all one by one.

121
00:11:01,380 --> 00:11:06,300
It was bizarre then watching that initial realization that, okay, whatever this is,

122
00:11:06,300 --> 00:11:07,300
this isn't going away.

123
00:11:07,300 --> 00:11:12,620
This is this new era that we've entered where people will talk about tokens and they might

124
00:11:12,620 --> 00:11:14,040
not accrue in value.

125
00:11:14,040 --> 00:11:17,980
They might not be worth anything, but they're not a thing that's being outlawed or forgotten.

126
00:11:17,980 --> 00:11:20,140
They exist.

127
00:11:20,140 --> 00:11:27,800
I remember the insane feeling of watching everyone around me suddenly gain interest in this stuff and then lose interest in it.

128
00:11:27,800 --> 00:11:36,740
And having to sort of pretend like, wait a minute, 12, 18 months ago, you were shilling me on the idea of a currency specifically for dentists, all their own.

129
00:11:37,900 --> 00:11:38,060
Yeah.

130
00:11:39,300 --> 00:11:39,740
Yes.

131
00:11:40,000 --> 00:11:42,200
Dentists need to have their own particular currency.

132
00:11:42,880 --> 00:11:44,200
The dollars just are not good enough.

133
00:11:44,240 --> 00:11:44,960
You need debt to coin.

134
00:11:45,780 --> 00:11:50,040
And then a year later, the same person will just have pretended to have forgotten.

135
00:11:50,140 --> 00:11:54,940
having had that conversation that was bizarre for me now we're in this new world where okay great

136
00:11:54,940 --> 00:12:00,220
we're i guess we're doing i don't know what's the thing that comes after nfts is there anything after

137
00:12:00,220 --> 00:12:06,940
bitcoin uh i mean uh meme coins meme coins right uh pumped off on but that's even died out yeah

138
00:12:06,940 --> 00:12:12,220
you know let's actually we should talk about this the thing that was big over the last year that uh

139
00:12:13,260 --> 00:12:16,940
caught on like wildfire and then abruptly ran out of gas was bitcoin treasury companies

140
00:12:16,940 --> 00:12:23,660
is yeah is it out of gas yet or are we just hey we're just i i mean we're definitely past the

141
00:12:23,660 --> 00:12:27,340
peak that's for sure i think there's a collective understanding that if whatever we're whatever you

142
00:12:27,340 --> 00:12:30,620
and i are about to do when we step out of here after the rip we are definitely not going to

143
00:12:30,620 --> 00:12:37,340
launch our own bitcoin treasury company no well that's the that's the um that's the most frustrating

144
00:12:37,340 --> 00:12:43,180
part about this treasury company meme is they they took bitcoin treasury as a meme away from

145
00:12:43,180 --> 00:12:47,280
I don't want to say the people that wanted to do it correctly, but like two years ago,

146
00:12:48,440 --> 00:12:54,740
I don't think MicroStrategy even got the sort of label Bitcoin treasury strategy company until

147
00:12:54,740 --> 00:12:59,360
like two or three years ago. But our thesis at 1031 is that every company is going to be a Bitcoin

148
00:12:59,360 --> 00:13:03,220
treasury company. They're just going to have positive cash flows. They're going to sweep

149
00:13:03,220 --> 00:13:07,480
flows into Bitcoin on their balance sheet. They're going to be a productive member of the economy,

150
00:13:07,480 --> 00:13:14,520
part of the economy and a bitcoin treasury in my mind when i was running at tftc what we try to run

151
00:13:14,520 --> 00:13:20,360
at 1031 was okay let's go out run a profitable business and save the fruits of that labor in

152
00:13:20,360 --> 00:13:24,200
bitcoin that was the concept of bitcoin treasury company it's just been completely ripped away from

153
00:13:24,200 --> 00:13:29,160
that sensible um sort of approach to it and the companies that were doing that are reaping the

154
00:13:29,160 --> 00:13:33,400
benefits and quite happy about it and ship posting with their heart consent there's a steak and shake

155
00:13:33,400 --> 00:13:39,880
uh my favorite is bull bitcoin francis can right talk better than anybody and i think he's got

156
00:13:39,880 --> 00:13:44,600
the strongest legs to stand on in this regard because i completely bootstrap that company and

157
00:13:45,320 --> 00:13:50,680
they pay all their employees in bitcoin they run on a bitcoin standard bull bitcoin yeah yeah uh

158
00:13:51,320 --> 00:13:55,560
i think there's absolutely that's a great strategy just buy and hold bitcoin and hang on to it it's

159
00:13:55,560 --> 00:13:59,320
the whole trying to when a lot of these bitcoin tradition companies tried to pretend that they

160
00:13:59,320 --> 00:14:03,040
that they were MicroStrategy 2.0 without realizing the MicroStrategy had a few decades

161
00:14:03,040 --> 00:14:07,660
of cash flow and a viable business that they were sitting on top of.

162
00:14:07,660 --> 00:14:10,760
You can't just issue paper and then hope it'll all work out.

163
00:14:10,760 --> 00:14:11,760
You have to have more than that.

164
00:14:11,760 --> 00:14:13,240
There actually is financial engineering there.

165
00:14:13,240 --> 00:14:15,380
I'm not a holder of MicroStrategy.

166
00:14:15,380 --> 00:14:18,200
I'm not involved with them in any way, but I can understand the logic of what they're

167
00:14:18,200 --> 00:14:19,200
doing.

168
00:14:19,200 --> 00:14:26,760
Just trying to take that meme and be a Seller 2.0, it's probably a winner takes most situation.

169
00:14:26,760 --> 00:14:30,540
lost count of how many bitcoin bitcoin treasury companies that were at the end they were trying

170
00:14:30,540 --> 00:14:36,240
to replicate the whole micro strategy lightning in a bottle and just what have they gotten what

171
00:14:36,240 --> 00:14:39,300
do they have to show for it at this point everyone's underwater how do you think this

172
00:14:39,300 --> 00:14:48,060
winds down uh what happens to all this bitcoin locked in these uh treasuries good question

173
00:14:48,060 --> 00:14:53,580
we see a wave of m a is it just they're forced to sell yeah probably financial engineering there

174
00:14:53,580 --> 00:14:59,340
be it depends on the lockup terms and what's encumbered some things will die slowly some

175
00:14:59,340 --> 00:15:02,940
things will die quickly some things might survive until the next bull market and then they just blow

176
00:15:02,940 --> 00:15:07,420
up in price that's sort of i mean isn't that what happened with coins there are a lot of them that

177
00:15:07,420 --> 00:15:11,740
should have died but you just hang on and if you're listed on coinbase you wait till the next cycle

178
00:15:11,740 --> 00:15:17,180
and then enough liquidity comes in that your value is pumped up again you get to live in another day

179
00:15:17,180 --> 00:15:21,820
yeah i've i've been sidelines for the last year and it feels uh it feels like i'm missing something

180
00:15:21,820 --> 00:15:30,460
zcash pumping dude it's back oh god did you ever catch that meme on uh on x the last six months uh

181
00:15:30,460 --> 00:15:36,700
on zcash all the zcash i watched the whole meta that was very coordinated to me it was old

182
00:15:37,580 --> 00:15:44,780
yeah but you say like ah this is like i think matt tweeted or excuse me our intern tweeted from 1031

183
00:15:44,780 --> 00:15:49,740
account uh zcash is a shit coin all the replies were like you're zied lined like of course you're

184
00:15:49,740 --> 00:15:55,360
you're going to say that so how how long between that tweet and when it started dumping probably

185
00:15:55,360 --> 00:16:01,120
like six weeks if that it's all the timing yeah yeah you know matt's good at that your intern

186
00:16:01,120 --> 00:16:10,060
yes yeah yeah the intern yes his name's also matt matt showedell yeah shit we've been talking

187
00:16:10,060 --> 00:16:15,660
i'm cussing i gotta watch my language can we edit that on or no we don't edit things here i there's

188
00:16:15,660 --> 00:16:19,340
a three-hour rip of me being inebriated during covid that proves to me that we don't edit things

189
00:16:19,340 --> 00:16:27,340
in defense of matt odell i mean he was snoring yeah and edit that out yeah god i'll never forget

190
00:16:27,340 --> 00:16:34,540
that uh what we haven't talked about is how gold and silver trading like ship coins that is crazy

191
00:16:34,540 --> 00:16:43,500
to me that's another like that's i mean not that i have a uh a storied career in financial markets i'm

192
00:16:44,460 --> 00:16:48,860
still in my mid-30s so i don't have like a 20-year career to look back on but i was alive

193
00:16:48,860 --> 00:16:55,900
door of the dot-com bubble vaguely remember it um this is like i've never seen anything like this

194
00:16:55,900 --> 00:17:01,740
yeah like precious metals should not be giving you memories of the dot-com crash you you know enough

195
00:17:01,740 --> 00:17:06,460
this is insane what's happening now the only thing that can explain it is something else breaking in

196
00:17:06,460 --> 00:17:12,220
the financial system and that's why i wonder um if that's what's going on now like is there a

197
00:17:12,220 --> 00:17:17,740
liquidity crisis people are just falling back to gold makes a lot of sense silver i mean i guess you

198
00:17:17,740 --> 00:17:23,800
you can try to justify that there's so much industrial use and obviously this expansion

199
00:17:23,800 --> 00:17:28,300
of the energy infrastructure and compute is going to drive industrial demand for silver and supply

200
00:17:28,300 --> 00:17:33,500
is not as big but to that degree i mean i sure there's an industrial use but it shouldn't be

201
00:17:33,500 --> 00:17:38,140
you shouldn't be seeing these insane monetary premiums attached to it right yeah well maybe

202
00:17:38,140 --> 00:17:42,820
the i mean maybe the gold and silver bugs have been right they've been suppressed by uh paper

203
00:17:42,820 --> 00:17:47,640
markets for so long and it was and something was bound to break a beach ball underwater as they

204
00:17:47,640 --> 00:17:54,340
say something broke somebody's getting squeezed possibly there's that around to what like 120

205
00:17:54,340 --> 00:18:02,260
i think i checked this morning it was like 175 so down 40 in like three days can't talk bitcoin

206
00:18:02,260 --> 00:18:09,940
was down like 10 today but it has a point being wild time in markets unlike anything i've ever

207
00:18:09,940 --> 00:18:16,240
seen in my relatively short short career but that's not what i like to talk that's not what

208
00:18:16,240 --> 00:18:20,560
like to talk with you about what would you like to talk about so far we've covered epstein and his

209
00:18:20,560 --> 00:18:24,880
weirdness we've talked about the bitcoin treasury stuff all right jump in what do you want to talk

210
00:18:24,880 --> 00:18:31,680
about i mean uh let's start with i mean i love to talk bitcoin protocol with you all right sure

211
00:18:31,680 --> 00:18:37,440
what do you want to talk uh obviously we're gonna get the sig bash uh which you're working on but

212
00:18:37,440 --> 00:18:45,920
before we get there i think last two years specifically uh bitcoin protocol development

213
00:18:46,480 --> 00:18:53,440
it's i think post taproot people are looking back and the originals wave came inscriptions came

214
00:18:54,640 --> 00:19:02,320
uh the people sort of close to protocol development and um close enough to understand

215
00:19:02,320 --> 00:19:07,280
the ramifications of protocol development look at segwit taproot ordinals inscriptions and they

216
00:19:07,280 --> 00:19:15,520
say uh a lot of unintended consequences with some of the things that that we sort of saw forked into

217
00:19:15,520 --> 00:19:23,680
bitcoin and enabled and i think i'll just speak for myself i know somebody was a cheerleader of

218
00:19:23,680 --> 00:19:30,560
seguit cheerleader taproot could not foresee uh the ramifications of the combination of those two

219
00:19:30,560 --> 00:19:36,880
things and watch the ordinals inscriptions thing um come to market and i'm not even taking a

220
00:19:38,000 --> 00:19:43,760
a stance on whether they're good or bad i would prefer them not to happen or i would prefer bitcoin

221
00:19:43,760 --> 00:19:51,040
be used for monetary asset only but i do recognize we did things and they're enabled and you can't

222
00:19:51,040 --> 00:19:59,200
stop people from accessing a permissionless uh protocol to do those things um and i think the

223
00:19:59,200 --> 00:20:05,220
the last two years around protocol development there's been a bit of like a uneasy is it i don't

224
00:20:05,220 --> 00:20:10,460
want to say it's aimless but it's it's very much like what like how do we actually do this moving

225
00:20:10,460 --> 00:20:15,380
forward so i can see why it feels that way but let's and i'm not going to talk you back from that

226
00:20:15,380 --> 00:20:20,820
view but i think it's important to remember that protocol development is not what the one thing

227
00:20:20,820 --> 00:20:24,760
that everyone seems to love to focus on which is what's the next software going to be we have we

228
00:20:24,760 --> 00:20:29,240
have this sort of built-in instinct to ask ourselves what's next how do we where do we go

229
00:20:29,240 --> 00:20:33,000
from here what's the next thing to turn on what's the next knob that we can turn there's been plenty

230
00:20:33,000 --> 00:20:39,400
of work on the bitcoin protocol in the past two years it's just not manifesting in software

231
00:20:39,400 --> 00:20:43,480
proposals that gather steam there have been plenty of software pros even friendly bips that have

232
00:20:43,480 --> 00:20:57,958
proposed modification of the bitcoin protocol but none of them seem to have gathered much traction a lot of them have centered around covenant proposals there are i aware of at least four different proposals

233
00:20:58,758 --> 00:21:04,358
for specific covenant implementations and then if you want to be more accurate about that more than

234
00:21:04,358 --> 00:21:10,118
one of those is featured in or more than one software proposal features a different covenant

235
00:21:10,118 --> 00:21:15,878
proposal so there's op ctv which is the old school covenant even before that there was an

236
00:21:15,878 --> 00:21:21,158
old school covenant proposal that i'm not remembering for 2016 uh johnson allows but

237
00:21:21,158 --> 00:21:28,678
we'll put that aside there's op ctv there's object contract verify there's op template hash

238
00:21:29,798 --> 00:21:36,038
uh let's see that's three or four come on a cat oh okay if you want to talk about cat being a

239
00:21:36,038 --> 00:21:39,798
covenant yeah that was out of left field the tap your wizards guys actually were pushing for that

240
00:21:39,798 --> 00:21:47,718
soft work everyone's got their own idea of what a potential covenant soft work might be and because

241
00:21:47,718 --> 00:21:51,158
there are so many different proposals and none of them can gather consensus because now we've got

242
00:21:51,158 --> 00:21:55,158
all sorts of different ways to fight about how we implement covenants and what are actually

243
00:21:55,158 --> 00:21:58,838
covenants good for what are we trying to accomplish covenants what scares us about covenants

244
00:21:59,638 --> 00:22:04,918
i think there's been a tremendous amount of effort put in there's not much work that's manifested as

245
00:22:04,918 --> 00:22:10,678
result of that because we can't all get behind one of these proposals and the reason why is not

246
00:22:10,678 --> 00:22:15,158
necessarily not invented hero syndrome i don't think it's lack of agreement on what we're trying

247
00:22:15,158 --> 00:22:20,758
to accomplish with covenants we know generally what a covenant is we want to be able to commit to

248
00:22:21,318 --> 00:22:26,278
a certain transaction structure and be able to say this transaction can only spend coins in this way

249
00:22:26,278 --> 00:22:29,478
but how we accomplish that and what trade-offs we're making everyone seems to have a different

250
00:22:29,478 --> 00:22:35,558
opinion and none of us really agrees on what we're trying to accomplish by making these commitments

251
00:22:35,558 --> 00:22:40,998
do we want to enable new scaling constructions different layer two mechanisms better layer two

252
00:22:40,998 --> 00:22:46,918
mechanisms let layer two mechanisms that require less coordination or work without with less user

253
00:22:46,918 --> 00:22:52,838
feedback do we want to be able to enable vaults constructions that allow us to claw back funds

254
00:22:52,838 --> 00:22:57,318
in the event that a malicious actor tries to spend a transaction without her permission do we want

255
00:22:57,318 --> 00:23:01,398
both is there some secret third thing that we're trying to accomplish with covenants or do we just

256
00:23:01,398 --> 00:23:05,318
want to have the next software to be able to say we did the next soft work that's where i think

257
00:23:05,318 --> 00:23:11,638
we're stuck right now if we don't understand where we're trying to go it's useless to argue about

258
00:23:11,638 --> 00:23:16,998
which car we're going to try to take to get there yeah would you consider a vault covenant

259
00:23:16,998 --> 00:23:22,678
proposal or a vaulting proposal a vault is a type of covenant proposal yeah it's the covenant

260
00:23:22,678 --> 00:23:29,238
broadly speaking is any method for restricting the outputs of a transaction so op vault definitely

261
00:23:29,238 --> 00:23:35,638
meets that bar it's a restricted form of covenant and i think even the author james oberon has said

262
00:23:35,638 --> 00:23:41,878
that you can implement op vault using op ctv and if he had the preference between the two he would

263
00:23:41,878 --> 00:23:51,238
he would prefer to have op ctv activated um so let's see that's op vault op ctv cat

264
00:23:51,958 --> 00:23:58,438
object contract verify op template hash optx hash that was yeah so we're at six covenant proposals

265
00:23:58,438 --> 00:24:02,358
and all of them are excellent proposals they're well written they're well thought out the people

266
00:24:02,358 --> 00:24:07,398
who have come up with them have thought about the trade-offs we can't seem to agree this is

267
00:24:07,398 --> 00:24:12,038
what the process of coming consensus looks like i think when you see six proposals the only other

268
00:24:12,038 --> 00:24:18,598
proposal i'm aware of for the next soft fork is uh bif360 which is still being developed but the

269
00:24:18,598 --> 00:24:22,758
post-quantum quantum yeah so that's the one that makes it like tap leaf

270
00:24:23,398 --> 00:24:26,038
quantum resistant address i think it's still in progress it was just

271
00:24:26,758 --> 00:24:31,638
rewritten a couple weeks ago but yeah that's the general idea yeah well

272
00:24:33,798 --> 00:24:39,478
before we even get into the conversation around the six different covenant proposals and how you

273
00:24:39,478 --> 00:24:43,478
choose one i think this is something going back to what i was saying earlier and to your point i

274
00:24:43,478 --> 00:24:48,438
think you um really narrowed down what i was trying to say which is like soft fork fatigue and

275
00:24:48,598 --> 00:24:54,818
ptsd from like okay we just did two major soft forks segway was a massive overhaul tapper was

276
00:24:54,818 --> 00:24:59,658
a massive overhaul i think that's another problem that should be entered in the conversation i think

277
00:24:59,658 --> 00:25:06,238
people equate the any future soft fork um they equate the magnitude of a future soft fork with

278
00:25:06,238 --> 00:25:10,598
segway and taproot which isn't going to be the case and i don't i think segway was more of like

279
00:25:10,598 --> 00:25:16,178
an engine segway and tapper together like an engine restructure in a way where the soft forks

280
00:25:16,178 --> 00:25:23,618
mentioned are lighter touch from what i understand hopefully but i suspect that any software that

281
00:25:23,618 --> 00:25:30,258
implements new opcode is going to mean a new segwit version or taproot version it's going to mean a

282
00:25:30,258 --> 00:25:36,098
new address type for it might not be from the point of view of someone who's actually merging

283
00:25:36,098 --> 00:25:40,098
the code into bitcoin core it might not be as heavy lift as segwit or taproot sure but from the

284
00:25:40,098 --> 00:25:44,658
point of view of wallet integrators and exchanges it might be the same roughly the same amount of

285
00:25:44,658 --> 00:25:49,778
work for them would you just go to the next beck32 version for sure but let's say if you've if you

286
00:25:49,778 --> 00:25:55,698
haven't built your software stack to make that just a a trivial operation and it's coding a whole new

287
00:25:55,698 --> 00:26:01,618
address uh whatever from scratch that might be pretty difficult some there are a lot of software

288
00:26:01,618 --> 00:26:05,858
stacks that just sort of assume seg would implicitly would be the be all end all that's not the same

289
00:26:05,858 --> 00:26:09,218
thing to think but you're not planning for the next software you're like i just have to worry

290
00:26:09,218 --> 00:26:12,738
about this one address type yeah because then you have app layer standardization and just be

291
00:26:12,738 --> 00:26:16,978
interoperable with each other where you get a big ux hurdle but again going back to

292
00:26:19,458 --> 00:26:24,818
what i was saying earlier i think the big question in my mind and looking at all these and um on

293
00:26:25,858 --> 00:26:31,378
just looking at them and talking to the developers been working on the these covenant proposals for

294
00:26:31,378 --> 00:26:36,018
years it's like yeah it sounds like it would be a nice to have but i always had that lingering

295
00:26:36,018 --> 00:26:40,578
thought in the back of my head is like have we tried everything we can do yeah not only at the

296
00:26:40,578 --> 00:26:45,058
protocol level but combining things that are currently possible at the protocol level with

297
00:26:45,698 --> 00:26:51,378
second layer solutions as well like have we tested and pushed the limits of scaling with

298
00:26:52,098 --> 00:26:58,898
everything that's been implemented to date sufficiently enough to warrant a sort of

299
00:27:01,138 --> 00:27:08,418
a very opinionated uh vision on the next soft work if that makes sense yeah it does and it's

300
00:27:08,418 --> 00:27:13,778
the thing is to me it feels like every six to 12 months we manage to push things a little farther

301
00:27:13,778 --> 00:27:18,578
in terms of what we're able to do on layer two systems things like arc where arc was two years

302
00:27:18,578 --> 00:27:26,658
ago versus last year versus this year with our arcade os and arc script when we look at what

303
00:27:26,658 --> 00:27:30,978
spark is doing with where state chains were two years ago with i think mercury mercury

304
00:27:30,978 --> 00:27:34,578
there would have been the state of the art versus now spark state chain what we're able to do there

305
00:27:34,578 --> 00:27:40,138
it seems like we're still being we're still figuring out new things that we can do at the

306
00:27:40,138 --> 00:27:47,738
layer two level obviously if you're trusting a layer two operator be it spark as the state

307
00:27:47,738 --> 00:27:53,478
chain operator or the arc service provider or a bit vm bridge that's a different thing than

308
00:27:53,478 --> 00:27:58,578
trusting consensus than placing your faith in the bitcoin network to validate and force the

309
00:27:58,578 --> 00:28:05,618
the rules that your transaction must follow. But for every time we make one of these advances with

310
00:28:05,618 --> 00:28:10,458
ARK with any of these R-layer 2 systems, it begs the question, well, if we can do this here,

311
00:28:10,578 --> 00:28:13,698
even though you have this trust assumption, if the trust assumption is middle enough,

312
00:28:13,838 --> 00:28:18,018
is that enough to accomplish what you were hoping to accomplish? Why did you actually need to change

313
00:28:18,018 --> 00:28:22,498
consensus? There might be a good reason. We might have good reasons for having to change consensus.

314
00:28:22,498 --> 00:28:29,858
We might, there might be things that we can't do or are undesirable to put that level of trust on an ARC service provider.

315
00:28:30,498 --> 00:28:36,218
But we're having collectively a difficult time articulating exactly what those limitations are.

316
00:28:37,058 --> 00:28:40,178
And to your point, I've always thought, I've always been excited about ARC.

317
00:28:41,138 --> 00:28:47,058
Happy to have been, I think, with the second protocol guys who have their own ARC implementation.

318
00:28:47,298 --> 00:28:49,398
I think I was one of the first mainnet ARC transactions.

319
00:28:50,218 --> 00:28:50,538
Oh, yeah.

320
00:28:50,638 --> 00:28:51,498
I think I saw you in the video.

321
00:28:51,498 --> 00:28:51,818
Yeah.

322
00:28:51,918 --> 00:28:52,038
Yeah.

323
00:28:52,038 --> 00:28:53,998
And it was like magic.

324
00:28:54,158 --> 00:28:57,518
It was the ability to basically turn a UTXO into a VTXO

325
00:28:57,518 --> 00:29:04,438
and instantly send to the other people leveraging their ASP in the same rounds.

326
00:29:05,158 --> 00:29:09,158
And I've always thought I've had ARK just as a concept,

327
00:29:09,398 --> 00:29:12,738
and obviously we have competing ARK protocols with ARK and Second.

328
00:29:13,638 --> 00:29:16,438
But I've always liked the idea of like, okay,

329
00:29:16,518 --> 00:29:20,398
if these ARK protocols can provide enough utility to the market

330
00:29:20,398 --> 00:29:25,198
they can reach a certain scale and they reach the upper limits of that scale that could be pushed

331
00:29:25,198 --> 00:29:30,238
even further with a covenant proposal being implemented like that seems like a good

332
00:29:30,238 --> 00:29:38,878
justification yeah for implementing uh covenants specifically and i think like i've fallen back on

333
00:29:38,878 --> 00:29:44,398
like i think that's what needs to happen if you want to get covenants like i i have i love james

334
00:29:44,398 --> 00:29:52,718
oberton good friend of mine love op vault and his passion for making it so you can create covenant

335
00:29:52,718 --> 00:29:57,758
structures and which makes it impossible for exchanges to get hacked and it's easy or harder

336
00:29:57,758 --> 00:30:05,678
for individual bitcoiners to lose their bitcoin but um i feel like that's like i don't want to say

337
00:30:05,678 --> 00:30:13,678
esoteric but it's like a nebulous uh sort of intent almost intangible reason to do this where

338
00:30:13,678 --> 00:30:19,918
like i feel like asp if arc protocol if one of the protocols were to re like provide utility you could

339
00:30:19,918 --> 00:30:26,478
do the extensible expressive smart contracts you have this payments layer that exists and

340
00:30:27,038 --> 00:30:31,278
reaches a critical mass of people that really love the service and then it hits the top of

341
00:30:31,278 --> 00:30:37,438
its scaling limits and could be um those scaling limits could be alleviated with a covenant it

342
00:30:37,438 --> 00:30:42,238
would make more sense to do it that way it's interesting to me you know the first one of these

343
00:30:42,238 --> 00:30:46,318
that we did you and i episode 100 we were talking about i think we talked through the definition of

344
00:30:46,318 --> 00:30:51,918
what network effects are they're the director indirect benefits that participants gain by

345
00:30:51,918 --> 00:30:57,438
joining a network uh i'm gonna drop that now because i think this is touching on network

346
00:30:57,438 --> 00:31:03,918
effects the reason if you think about it uh vault construction should theoretically be more appealing

347
00:31:03,918 --> 00:31:09,118
because who wants to lose their bitcoin but the people who would want a vault construction who

348
00:31:09,118 --> 00:31:13,758
would argue for it who would champion it are the people who are either prone to losing their bitcoin

349
00:31:13,758 --> 00:31:19,038
or have lost their bitcoin so they're sort of they've already exited the network by uh unwillingly

350
00:31:19,678 --> 00:31:25,438
so they have sort of less pull in the software the next software conversation it's even though

351
00:31:25,438 --> 00:31:29,918
nobody i mean there's you're not gonna anyone who says actually i would like to use lose my bitcoin

352
00:31:29,918 --> 00:31:35,438
everybody would theoretically benefit from a vault in reality there's probably more excitement and

353
00:31:35,438 --> 00:31:40,318
more mind share around the next scaling solution bring more people onto the network than helping

354
00:31:40,318 --> 00:31:45,198
people who are prone to falling off the network yeah and that's i mean that's something else we

355
00:31:45,198 --> 00:31:51,678
were talking about downstairs is this emergence of a clear product market fit for lightning

356
00:31:51,678 --> 00:31:58,398
specifically as a connector between these disparate but interoperable second layer protocols

357
00:31:58,398 --> 00:32:05,198
you mentioned spark arc liquid chauley and mints yeah and lightning payment channels as rails between

358
00:32:05,198 --> 00:32:14,558
all of them yes and again i think we're just beginning to recognize the potential of this

359
00:32:14,558 --> 00:32:19,038
interoperability that lightning provides all these different networks and and i think the

360
00:32:19,918 --> 00:32:27,358
sort of scaling potential of the that the interaction of all these protocols is

361
00:32:27,358 --> 00:32:33,438
relatively unexplored as well it's like what's the argument for exploring that as much as possible how

362
00:32:33,438 --> 00:32:39,918
do you do it so it's actually nothing that can be done with the soft work i don't think to start it

363
00:32:39,918 --> 00:32:44,798
has to be the second layer systems have to first grow enough and scale to be worth connecting to

364
00:32:44,798 --> 00:32:49,678
and then operators have to say okay well you know it makes sense for you and i to be connected because

365
00:32:50,238 --> 00:32:54,478
we've got a lot of liquidity that's hitting the main chain that we're paying fees for instead

366
00:32:54,478 --> 00:32:58,318
of doing that i know that most of my sats are going out to you and most of your sats are going

367
00:32:58,318 --> 00:33:03,278
out to me or your users are going back and forth so why don't we instead of paying the miners just

368
00:33:03,278 --> 00:33:06,038
just open up a channel with each other.

369
00:33:06,038 --> 00:33:09,598
That takes a decent amount of critical mass to acquire.

370
00:33:09,598 --> 00:33:11,118
And all of these systems right now

371
00:33:11,118 --> 00:33:13,158
are still very much in the experimental stage.

372
00:33:13,158 --> 00:33:16,738
ARC launched just a few months ago.

373
00:33:16,738 --> 00:33:18,718
Second, a few months before that.

374
00:33:18,718 --> 00:33:22,338
Spark, I'm not sure if they're even live on mainnet yet.

375
00:33:23,278 --> 00:33:24,118
Are they sure?

376
00:33:24,118 --> 00:33:24,958
Are they?

377
00:33:26,518 --> 00:33:27,538
I'm not 100% sure.

378
00:33:27,538 --> 00:33:29,598
I gotta be honest, their trusted operator model

379
00:33:29,598 --> 00:33:30,418
sort of understood it to me,

380
00:33:30,418 --> 00:33:32,338
so I'm not as up to date on them as I should be.

381
00:33:32,338 --> 00:33:36,898
think that i think they're on mainnet now but yeah because they had the the address snafu yeah they

382
00:33:36,898 --> 00:33:42,338
must be live on main i think the breeze sdk i think yeah i think in breeze sdk you can yeah

383
00:33:42,338 --> 00:33:49,858
some spark capabilities all right so that's three and then uh let's see we covered arc second spark

384
00:33:49,858 --> 00:33:56,018
and what are we talking about chami and mints call me liquid liquid the dark horse liquid's been

385
00:33:56,018 --> 00:33:59,618
sitting there for a decade it's been waiting for a while actually liquid's actually starting to

386
00:33:59,618 --> 00:34:06,498
pick up steam you know but it takes time for a second layer uh to become palatable to people

387
00:34:06,498 --> 00:34:10,018
the reason why is well what forces you onto a second layer if the force layer if the first

388
00:34:10,018 --> 00:34:14,178
layer is too expensive transaction fees are so low that there's no real incentive for people to

389
00:34:14,178 --> 00:34:19,138
adopt secondary solutions you need something more than just low transaction fees i think that's what

390
00:34:19,138 --> 00:34:24,578
we found out with the rate of lightning adoption arc in particular offers that opportunity because

391
00:34:24,578 --> 00:34:27,938
there's these all these new interesting things you can do with arcade script that you can't do on

392
00:34:27,938 --> 00:34:34,338
mainnet i think i i'm the worst at reading tea leaves in terms of software adoption but i think

393
00:34:34,978 --> 00:34:38,418
it's a lot more likely that people build cool things on arc that you couldn't build on the

394
00:34:38,418 --> 00:34:42,978
main chain and then that attracts liquidity and then the liquidity shows up there and then it

395
00:34:42,978 --> 00:34:48,818
wants to exit to some other secondary solution and then those two l2s have to set up a payment

396
00:34:48,818 --> 00:34:55,298
channel between them that seems like a likely path forward to me yeah well i will say um even though

397
00:34:55,298 --> 00:35:02,258
no fees uh on the main chain are disgustingly low shout out mad unfairly cheap shout out

398
00:35:02,258 --> 00:35:07,778
mad odell mempools will never clear again that was a meme for about a year mempools

399
00:35:07,778 --> 00:35:15,218
been clear for about uh two years almost now and uh the um i think to push back on like

400
00:35:15,938 --> 00:35:20,498
the fees on the main chain being the only forcing function up to layer two i think instant settlement

401
00:35:20,498 --> 00:35:28,178
um with lightning specifically like i see it in the business uh just paying invoices um and

402
00:35:28,178 --> 00:35:34,498
receiving sats over podcasting 2.0 and zapping people like i absolutely see that being the uk

403
00:35:34,498 --> 00:35:41,138
is the problem is now you're asking people to adopt a new unit of account so if people weren't

404
00:35:41,138 --> 00:35:46,258
paying with bitcoin before that's not going to be what pulls them to do it but if you want to pay

405
00:35:46,258 --> 00:35:49,218
with bitcoin lightning is the way to do it otherwise what are you going to do zero conf

406
00:35:49,218 --> 00:35:55,618
of course yeah so it's that adoption curve just takes significantly longer than

407
00:35:57,298 --> 00:36:01,538
than i would like at least uh but you know maybe that's just me being impatient how

408
00:36:01,538 --> 00:36:08,738
often do you pay lightning invoices uh for probably at least between

409
00:36:12,098 --> 00:36:16,818
for retail payments i mean probably like between like retail payments

410
00:36:16,818 --> 00:36:24,078
probably like once or twice a week for like paying contractors and zapping like yeah are

411
00:36:24,078 --> 00:36:29,958
you zap right or literally zapping is in nostril zaps or nostril zaps like zap like I get that's

412
00:36:29,958 --> 00:36:37,818
been my um zap right invoices has been one of my sort of low level indicators like Bitcoin adoption

413
00:36:37,818 --> 00:36:42,738
like if I'm getting more of those in a month-to-month basis like I'm highly confident that Bitcoin

414
00:36:42,738 --> 00:36:48,418
adoption is increasing and i'm happy to report that that has been happening um obviously i'm

415
00:36:48,418 --> 00:36:53,458
unique in the sense that a lot of the companies i interact with are bitcoin companies but um it is

416
00:36:53,458 --> 00:36:58,178
there and the ability to pay in lightning given the choice i will pay in lightning it typically

417
00:36:58,178 --> 00:37:02,338
works i think we were talking about this as well downstairs but by the way when we keep saying

418
00:37:02,338 --> 00:37:06,898
downstairs we're shooting at pubkey right now i'm not gonna tell about yeah by the background when

419
00:37:06,898 --> 00:37:14,738
we were at the bar uh the idea that you were using your is it clodbot or maltbot or is it

420
00:37:14,738 --> 00:37:20,098
clodbot then it went to maltbot and then two days later it's changed to openclaw so uh in

421
00:37:21,298 --> 00:37:29,138
out of respect to the project maintainers i will abide by the uh most recent name change of openclaw

422
00:37:29,138 --> 00:37:34,578
so that's what i'm running but uh i fall back on claw pot because uh it's nostalgic to me i was

423
00:37:34,578 --> 00:37:38,258
there in the first week before they had to change the name all right then i'll use cloudbot i don't

424
00:37:38,258 --> 00:37:46,178
want to dead name it um i i think you we actually won't be worrying about these details in the very

425
00:37:46,178 --> 00:37:50,338
near future whether what how are you going to be paying you'll just tell your llm agent hey

426
00:37:50,338 --> 00:37:54,018
make sure these stats get there and the llm agent will say okay well i know you need this much

427
00:37:54,018 --> 00:37:57,858
liquidity and i know you need this sort of settlement and they'll worry about the details

428
00:37:57,858 --> 00:38:01,858
and it'll be abstracted away from us from the point of view of the ux yeah and so i was telling

429
00:38:01,858 --> 00:38:10,258
armed out downstairs i've been playing with this for eight nine days now and i set it up to do

430
00:38:10,258 --> 00:38:17,058
research for me for tftc for 1031 to pull data it's made decks for me it's helped me

431
00:38:17,778 --> 00:38:27,218
uh find clips in the podcast so like when this podcast goes to our dropbox um it'll trigger

432
00:38:27,218 --> 00:38:32,258
a transcription to get made so we get the transcription and once the transcripts and

433
00:38:32,258 --> 00:38:39,058
the txt file is in dropbox somewhere we have claude bot um basically scanning our dropbox

434
00:38:39,058 --> 00:38:46,818
via a read-only api for txt files it'll find that txt file assume that is a transcript of a podcast

435
00:38:46,818 --> 00:38:54,498
um 99 out of 100 txt files we put in our dropbox are so it's it's a safe assumption on behalf of

436
00:38:54,498 --> 00:39:01,218
our claude bot um and then it'll automatically read the transcript and we've sort of trained it

437
00:39:01,218 --> 00:39:08,258
with enough data of transcripts and twitter performance that'll be able to go in and find

438
00:39:08,258 --> 00:39:13,538
the time stamps of sections of the episode that are most likely to go viral on twitter and then

439
00:39:13,538 --> 00:39:17,778
that'll get sent to my producer in a discord chat that's connected to the club bot as well and say hey

440
00:39:18,418 --> 00:39:23,538
here are what i believe will are the sections of the podcast and if you clip out will go most viral

441
00:39:23,538 --> 00:39:26,818
so i'm gonna have an llm going through this transcript with you and me figuring out what's

442
00:39:26,818 --> 00:39:30,738
going to pop on twitter is that what you're telling me i'm highly uh confident it's going

443
00:39:30,738 --> 00:39:38,098
to be about the first part of the conversation baba buoy baba buoy was that it the uh

444
00:39:40,178 --> 00:39:42,658
actually we do have an older audience they probably get the reference

445
00:39:43,618 --> 00:39:50,418
the stern reference so old um oh wait okay one for the kids six seven oh god oh man

446
00:39:51,138 --> 00:39:55,458
my uh almost six-year-old did that for the first time in the other month i was like no please no

447
00:39:56,498 --> 00:40:01,218
but that was like we started doing that like i built those processes out first and then

448
00:40:01,858 --> 00:40:05,058
once those were up and running and it was like working i was like holy that's cool what else

449
00:40:05,058 --> 00:40:10,738
can this and that's the beauty of um what claude bot open claw whatever we're calling it has brought

450
00:40:10,738 --> 00:40:17,298
so you have these wider context windows and the harness i guess is what you call it is set up in

451
00:40:17,298 --> 00:40:24,418
way where it can really uh after compacts context after a large token run it's not just starting from

452
00:40:24,418 --> 00:40:30,098
scratch we have to upload everything it's able to go back and go into skill files markdown files

453
00:40:30,098 --> 00:40:33,378
basically say all right here's the context that's been built up over time like i sort of

454
00:40:34,098 --> 00:40:41,138
know what we're doing in the conversation moving forward and it's been massive for tftc research

455
00:40:41,138 --> 00:40:48,578
i've got a cron jobbing bank research papers like pulling them in and dissecting those get a summary

456
00:40:48,578 --> 00:40:52,498
a banking summary once a day of what all the bank research desks are writing about

457
00:40:53,378 --> 00:40:56,338
but then it got to the point i was like all right can this thing like do bitcoin stuff and i was

458
00:40:56,338 --> 00:41:03,218
like all right i like i was telling you downstairs i i give it pull only read only access to apis

459
00:41:03,218 --> 00:41:08,338
um so it has our youtube api as our dropbox api it has a third-party twitter api that we use

460
00:41:08,338 --> 00:41:10,798
to gather Twitter data.

461
00:41:11,578 --> 00:41:16,598
And I wanted to check out like a Gentic payments on the web.

462
00:41:16,638 --> 00:41:21,078
And I was like, I'm not giving you access to debit, credit card information, a Stripe account.

463
00:41:22,178 --> 00:41:26,298
Let's see if you can spin up a Bitcoin node and accept the Lightning payment.

464
00:41:26,858 --> 00:41:27,718
So we did some research.

465
00:41:27,818 --> 00:41:30,238
I was like, all right, this is what I want you to do.

466
00:41:30,238 --> 00:41:48,916
Like do some research and let have a conversation about what you think is the most efficient way to do this At first actually I put an LDK I was like look at LDK let spin up at LDK now And I was like did it And then like payments were failing And I was like oh yeah duh LDK is not as widely adopted as L or Sea Lightning or Eclair even

467
00:41:49,676 --> 00:41:51,136
So it's not going to be viable.

468
00:41:51,256 --> 00:41:53,356
I was like, okay, round zero, you do research.

469
00:41:53,536 --> 00:41:54,116
Then it came back.

470
00:41:54,136 --> 00:41:55,816
It's like this Phoenix D server looks cool.

471
00:41:56,596 --> 00:41:57,736
I was like, okay, let's go with that.

472
00:41:57,836 --> 00:41:58,476
Spun it up.

473
00:41:59,496 --> 00:42:03,216
And it's like, okay, I need to get Bitcoin.

474
00:42:03,216 --> 00:42:08,336
uh you can't send me an on-chain payment but there's this bolt technology where if you could

475
00:42:08,336 --> 00:42:15,136
send on-chain payment there it was splits and it'll open up a lightning channel um with you via phoenix

476
00:42:15,136 --> 00:42:19,296
and you'll be able to spend over the lightning network did that and this happened over the

477
00:42:19,296 --> 00:42:24,496
course of like 10 minutes so just figured out autonomously how to do a submarine swap yes

478
00:42:25,376 --> 00:42:30,336
did a submarine swap had bitcoin and a lightning channel within 10 minutes

479
00:42:31,216 --> 00:42:36,416
and i was like okay you've got a phoenix d server that means you can ln url off into um compatible

480
00:42:36,416 --> 00:42:39,856
website so it's like all right go to ellen markets and see if you can sign in there and it did

481
00:42:40,736 --> 00:42:46,496
and i was like all right send some sats and make a small trade and it did point being is like what

482
00:42:46,496 --> 00:42:54,256
you said and it's completely to you wouldn't have any idea if it was if they if your agent and ellen

483
00:42:54,256 --> 00:42:57,616
markets well it's in the name but if they were to adopt arc you wouldn't know anything about it you

484
00:42:57,616 --> 00:42:58,236
You wouldn't care.

485
00:42:58,576 --> 00:43:00,836
They'd be sorting out the liquidity founders themselves.

486
00:43:00,956 --> 00:43:01,956
It's not for you to worry about.

487
00:43:02,756 --> 00:43:06,616
No, and it is funny because a bunch of Bitcoiners have been experimenting with this.

488
00:43:07,256 --> 00:43:10,116
I've seen Bram Cramstein from the Bitcoin Millennials podcast.

489
00:43:10,116 --> 00:43:21,576
He created this skill, which basically gets your agent access to your Lightning Wallet via Nostra Wallet Connect, which is, I guess, a cool hack.

490
00:43:21,656 --> 00:43:23,096
But then they have access to that wallet.

491
00:43:24,256 --> 00:43:25,616
And I found this out after the fact.

492
00:43:25,616 --> 00:43:33,216
breeze came out with a skill that you can have your uh claw bot download to build a wall via

493
00:43:33,216 --> 00:43:38,896
breezes development kit but i thought it was just cool like it just did its research found phoenix

494
00:43:38,896 --> 00:43:46,576
d it worked and it's still working right now man i feel like i've had my head buried in the sand

495
00:43:46,576 --> 00:43:51,296
for the past few months and i've come up and everyone is we're not quite at agi but you guys

496
00:43:51,296 --> 00:43:54,576
are on another level i got to spend a week actually digging into the stuff and getting my

497
00:43:54,576 --> 00:44:00,576
getting an lm to start buying things from you yeah but to your point i think uh many people

498
00:44:00,576 --> 00:44:05,536
especially if you haven't touched this stuff yet are under appreciating like ux hurdles that this

499
00:44:05,536 --> 00:44:10,256
is going to dissolve yeah um like really i think the whole form factor of how we interact

500
00:44:11,536 --> 00:44:15,536
with i guess the internet i don't even know we're going to call it anymore it's just voice to text

501
00:44:15,536 --> 00:44:21,296
or text to like i was talking to a couple of bitcoiners uh yeah last week and the way they

502
00:44:21,296 --> 00:44:24,596
they were describing it as like, you're just going to be a projectionist, like anything you want.

503
00:44:25,056 --> 00:44:28,676
That's a great way to look at it. I think if, if we and I were having this conversation a year,

504
00:44:28,756 --> 00:44:32,876
two years ago, we'd be talking about QR codes and how you unify on chain versus on off chain

505
00:44:32,876 --> 00:44:37,036
QR codes. Now it's just let, okay, write a skill for it. Let someone else figure that out. Let

506
00:44:37,036 --> 00:44:43,976
something else figure that out. Yeah. Do they have souls? I don't think so. But, um, to your point,

507
00:44:44,456 --> 00:44:50,376
um, no, not to your point, but that's cool. I think that's going to be massive for adoption and

508
00:44:50,376 --> 00:44:57,256
use user um like ease of use user experience uh but bringing this back to like protocol development

509
00:44:57,256 --> 00:45:03,336
pushing the limits before we decide on the next soft fork if it ever happens maybe we've ossified

510
00:45:03,336 --> 00:45:11,096
already part of it i think is well ossification isn't any one person's choice to make but on the

511
00:45:11,096 --> 00:45:16,696
part of developers all of the drama around softworks in general is a gigantic turnoff

512
00:45:16,696 --> 00:45:21,256
nobody wants to be the one who's stuck working on the next soft fork just to absorb a tremendous

513
00:45:21,256 --> 00:45:30,136
amount of discontent of hatred of uh jibes and the slings and arrows of outrageous fortune from

514
00:45:30,136 --> 00:45:34,856
people online you know why not just work on something else like ephemeral anchors or cluster

515
00:45:34,856 --> 00:45:40,216
mempool or something there's plenty of interesting things that can be done on bitcoin it's easy to

516
00:45:40,216 --> 00:45:48,296
forget that we're still 17 years out from some guy doing a weird scientist experiment in vs code

517
00:45:48,296 --> 00:45:53,736
in windows that just barely worked on his one machine and now we're at a multi-trillion dollar

518
00:45:53,736 --> 00:45:59,576
economy there's a tremendous amount of work to be done getting this thing actually to the point where

519
00:45:59,576 --> 00:46:04,456
we're trusting it where we can trust it to the level that we are already trusting it right now

520
00:46:05,176 --> 00:46:09,336
uh a lot of that stuff doesn't have to be a soft fork a lot of it is more gratifying

521
00:46:09,336 --> 00:46:17,336
or less stressful or less drama prone it's difficult to justify working on a soft fork

522
00:46:17,336 --> 00:46:21,816
proposal if you don't know what fruits that software proposal is going to reap

523
00:46:22,936 --> 00:46:28,856
i think maybe segwit taproot and script you stuff has a small part to do with that but a large part

524
00:46:28,856 --> 00:46:33,256
is okay if it's covenants for example what are you trying to accomplish with covenants if it's

525
00:46:34,376 --> 00:46:37,816
the post-quantum stuff is probably the only thing where we can say definitively what's the goal of

526
00:46:37,816 --> 00:46:42,776
soft proposal well it's to not get hacked by a graphically relevant quantum computer everything

527
00:46:42,776 --> 00:46:48,696
else is well we want to scale we want to think make things more secure what does scaling actually

528
00:46:48,696 --> 00:46:53,816
mean what does more secure actually mean for who and i think it's a problem you've been thinking

529
00:46:53,816 --> 00:47:02,216
about oh wow nice segue what uh what does it mean to you how do we saw oh man uh okay for background

530
00:47:02,216 --> 00:47:07,096
odell already scooped you on this he he uh ambushed me like nine months ago i think he wanted to talk

531
00:47:07,096 --> 00:47:14,936
about the book um and what we ended up talking about is the project i was working on called sigbash

532
00:47:15,576 --> 00:47:20,696
which is a programmatic signer just you know think of it this way there's two ways that bitcoin can

533
00:47:20,696 --> 00:47:25,096
move right there's proof of work and there's signing transactions proof of work is mining

534
00:47:25,096 --> 00:47:30,216
obviously and signing transactions is what we normally do it's broadcasting yeah with our wallets

535
00:47:30,216 --> 00:47:39,296
a programmatic signer is what you would use if you wanted to have someone else in your multi-sig

536
00:47:39,296 --> 00:47:44,376
that wasn't someone else that instead of a person like uncle jim or a company like coinbase you

537
00:47:44,376 --> 00:47:48,876
wanted to have just an anonymous service that would give you a signature if something happened

538
00:47:48,876 --> 00:47:53,856
i thought that was a neat project to work on and i wanted to get my hands dirty with it so

539
00:47:53,856 --> 00:47:59,716
i spun it up about two years ago and i got it up and running and testing and started banging on it

540
00:47:59,716 --> 00:48:06,796
with users. The original model I had used something called blinded Xpubs. And the idea

541
00:48:06,796 --> 00:48:13,396
behind blind Xpubs is the server has the master Xpub. We send you that master Xpub. You derive a

542
00:48:13,396 --> 00:48:18,716
child key from it that the server doesn't know anything about. And what you get out of that is a

543
00:48:18,716 --> 00:48:22,016
level of privacy that you don't get out of traditional multisig. Traditional multisig,

544
00:48:22,276 --> 00:48:28,756
when you share Xpubs with people, they see your entire transaction balance and your transaction

545
00:48:28,756 --> 00:48:35,716
history just by joining a multi-sig with you which is not great if you're if you want any sort of

546
00:48:36,356 --> 00:48:41,076
relationship with your multi-sig sign or beyond being best friends it's weird to start it off with

547
00:48:41,076 --> 00:48:47,236
hey here's everything about me here's everything i own everything i've ever done um i wanted to

548
00:48:47,236 --> 00:48:55,636
explore if there were if there was more to be done on the privacy layer than that uh and blinded xpubs

549
00:48:55,636 --> 00:49:02,676
is what i landed on and planting blind xpubs in a web server was interesting to me and so that was

550
00:49:02,676 --> 00:49:10,276
the first iteration and um just so i have around understanding of this and the audience as well

551
00:49:10,276 --> 00:49:18,676
with the you get a master key you create a child leave from that is it a situation in which like

552
00:49:18,676 --> 00:49:25,236
if it's a two or three multi-sig as long as you have the two keys you can sign and the blinded

553
00:49:25,236 --> 00:49:29,076
signer service will have no idea that you're moving bitcoin if you're using right keys but

554
00:49:29,076 --> 00:49:33,796
in the case that you lose one key in the backup and you need somebody there to be the second

555
00:49:33,796 --> 00:49:40,036
in the two is requorum you then bring your um your transaction to the blinded signer and say hey

556
00:49:40,596 --> 00:49:46,196
i actually need your help i know you have access to yeah that's the idea so break glass and you

557
00:49:46,196 --> 00:49:50,676
can use the signer which sounds great when we're talking about across the table right now but if

558
00:49:50,676 --> 00:49:54,836
you think about it for a few minutes and this is what i found talking to users and it took me a while

559
00:49:54,836 --> 00:49:59,716
to come around to this but it's the sad truth if you have a signer that only gives you privacy

560
00:49:59,716 --> 00:50:06,996
until you actually ask to use them that's not very useful you know uh the fatal flaw in it is you

561
00:50:06,996 --> 00:50:10,996
whenever you actually need the signer you have to show them your entire transaction details

562
00:50:10,996 --> 00:50:17,536
And it might be true that you don't have the same XPUB flaw as traditional ECDSA multi-sig,

563
00:50:17,536 --> 00:50:22,816
but you still don't have anything that can be called real privacy.

564
00:50:22,816 --> 00:50:29,016
The problem with that to me is that it's not just sort of that you're misleading the users

565
00:50:29,016 --> 00:50:30,496
by offering them well.

566
00:50:30,496 --> 00:50:32,516
You have privacy kind of as long as you don't use it.

567
00:50:32,516 --> 00:50:37,356
It's also the really interesting thing with assigner would be if you had total privacy

568
00:50:37,356 --> 00:50:38,356
from them.

569
00:50:38,356 --> 00:50:44,756
to ask them for any sort of permission besides just give me a signature basically like blind

570
00:50:44,756 --> 00:50:49,796
signing almost except without the flaws of blind signing if you were somehow able to do that that

571
00:50:49,796 --> 00:50:54,676
would be way more interesting you'd be in this whole new different realm of what it means to

572
00:50:54,676 --> 00:50:58,756
use a signer instead of having them as like judge during executioner for your transactions they could

573
00:50:58,756 --> 00:51:04,756
just be a notary you know someone just give me a stamp and go you're i need you if i've lost my

574
00:51:04,756 --> 00:51:08,596
keys or my friend isn't able to sign or any one of the million reasons but i don't want you to be

575
00:51:08,596 --> 00:51:15,156
involved anyway in this transaction and v1 just wasn't able to do that and so you've been iterating

576
00:51:15,156 --> 00:51:21,156
yeah well you guys were all you know i wish i wish you'd let me know there were coding agents while i

577
00:51:21,156 --> 00:51:26,516
was working on this it would have been helpful uh so i guess i will announce it now by the time this

578
00:51:26,516 --> 00:51:31,476
goes on wonder is it gonna air monday it's up to you let's say monday i don't want to do this too

579
00:51:31,476 --> 00:51:38,676
long once uh v2 of sigbash will be live i built a zero knowledge signer for arbitrary bitcoin

580
00:51:38,676 --> 00:51:44,756
predicates okay okay that's a lot to say should we explain what that is yeah yeah all right so

581
00:51:44,756 --> 00:51:48,916
the first thing with the signer was i talked to for v1 i talked to a lot of traders and they had

582
00:51:48,916 --> 00:51:54,516
all sorts of ideas like oh you should sign if the price of bitcoin is above or below a certain amount

583
00:51:54,516 --> 00:51:59,636
or the price of this or that is above or below something and that was interesting to me but

584
00:51:59,636 --> 00:52:02,756
but it sort of forces you to be an Oracle.

585
00:52:02,756 --> 00:52:04,916
That's what I was going to say is it's like a DLC Oracle,

586
00:52:04,916 --> 00:52:05,416
it sounds like.

587
00:52:05,416 --> 00:52:06,236
Yeah, we have the DLCs.

588
00:52:06,236 --> 00:52:09,356
The Oracle just provides the information hash.

589
00:52:09,356 --> 00:52:10,976
And on the one hand, that was interesting to me

590
00:52:10,976 --> 00:52:13,796
because I think one of the reasons DLCs haven't seen much

591
00:52:13,796 --> 00:52:17,756
adoption is while they're great in theory and practice,

592
00:52:17,756 --> 00:52:20,096
choosing to use DLCs, every DLC Oracle

593
00:52:20,096 --> 00:52:21,956
is sort of married to its own wallet.

594
00:52:21,956 --> 00:52:23,996
There's no standard DLC format.

595
00:52:23,996 --> 00:52:25,976
So if you want to enter a DLC contract,

596
00:52:25,976 --> 00:52:29,096
you're disposing into some app that is tied to a DLC.

597
00:52:29,096 --> 00:52:33,896
there's no like psbt for yeah there's no standard there's no sort of interoperability and beyond

598
00:52:33,896 --> 00:52:37,416
that there's the whole oracle problem you're trusting someone's idea of like what the price

599
00:52:37,416 --> 00:52:43,336
should be and you have to make sure they get it right it's a whole i i solved one problem by letting

600
00:52:43,336 --> 00:52:49,976
the signer do that and just there were five other problems with it um what i learned is that people

601
00:52:49,976 --> 00:52:55,496
are interested in talking about dlcs in theory and practice what motivates people who engage in those

602
00:52:55,496 --> 00:52:59,656
trades is liquidity above all else and they will sacrifice everything for liquidity if they have

603
00:52:59,656 --> 00:53:04,696
to choose between privacy and decentralization versus one extra iot of liquidity they will rush

604
00:53:04,696 --> 00:53:10,216
to fidelity or charles schwab or coinbase and they will get the liquidity they need which can't

605
00:53:10,216 --> 00:53:15,416
really blame them for yeah but everything so this would be like a margin top up yeah in their the

606
00:53:15,416 --> 00:53:21,496
use case with sigbash v1 yeah thinking like hey if the price goes below this level i have an

607
00:53:21,496 --> 00:53:26,296
understanding my mind exactly to send it to bitmex to meet margin requirements yeah so so i don't have

608
00:53:26,296 --> 00:53:31,256
to rush to find my wallet and do that i want you to just do it automatically and if you're going to

609
00:53:31,256 --> 00:53:35,496
do that why wouldn't you just have bitmex implement that scheme themselves why wouldn't you be close

610
00:53:35,496 --> 00:53:41,096
to the actual person who's executing the trade or the loan top up with a margin call or whoever yeah

611
00:53:41,976 --> 00:53:46,456
what i found talking through months and months of user reports was the one thing that people

612
00:53:46,456 --> 00:53:52,296
were interested in was uh the condition for i'll only sign after a certain date and that was

613
00:53:52,296 --> 00:53:55,496
confusing to me because you can do that with bitcoin now you can do that in mini scripts

614
00:53:55,496 --> 00:54:03,336
you know we have uh check lock time verify we have uh a rich manuscript language allowing you

615
00:54:03,336 --> 00:54:09,736
to specify i'll only sign after this date but what it took me a while to understand was that there's

616
00:54:09,736 --> 00:54:14,616
a difference between and it's obvious in retrospect it's wallet policies versus signing policies while

617
00:54:14,616 --> 00:54:19,256
policies are when can i spend from this wallet signing policies are when will i provide a

618
00:54:19,256 --> 00:54:23,656
signature that allows you to spend from this wallet they're they're sort of orthogonal

619
00:54:25,576 --> 00:54:31,416
and i took that understanding and i flipped around with v2 so v2 has no external conditions it's all

620
00:54:31,416 --> 00:54:38,216
the psbt is the source of truth so any condition that you can define in a psbt is what you could

621
00:54:38,216 --> 00:54:45,896
theoretically sign on so throw out a condition to me and i'll describe something um a thousand blocks

622
00:54:45,896 --> 00:54:50,856
guess oh yeah sure that's easy man i wanted something hard how about can i throw some out

623
00:54:50,856 --> 00:55:00,456
yeah um only sign to one set of addresses if the amount is over 100 000 sats and it's business

624
00:55:00,456 --> 00:55:08,136
hours otherwise only assigned to another set of addresses if it's below 100 000 sats but only

625
00:55:08,136 --> 00:55:13,576
once a week otherwise i can keep going with this i had to build a whole custom data structure to

626
00:55:13,576 --> 00:55:17,736
handle all this branching so when i say arbitrary predicates just think of as many conditions as

627
00:55:17,736 --> 00:55:22,216
you can put together and when i say conditions think of all the things you can see in a psbt

628
00:55:22,216 --> 00:55:28,616
sounds a lot like a covenant it's sort of like a covenant kind of it's what's a covenant

629
00:55:29,256 --> 00:55:35,096
it's a restriction so cosigners can emulate covenants in general and a zero knowledge cosigner

630
00:55:35,096 --> 00:55:39,896
can emulate certain forts of comets pretty well there's sort of a tension between okay you're

631
00:55:39,896 --> 00:55:44,296
trusting the cosigner it's zero knowledge so you're not trusting it to see your transaction

632
00:55:44,296 --> 00:55:50,456
details but you are trusting to be online to get a signature in exchange for that nobody else gets

633
00:55:50,456 --> 00:55:56,056
to see your transaction details so it's not enforced on chain which can be good which can

634
00:55:56,056 --> 00:55:59,496
be bad maybe you don't want to share the details of your transaction on chain maybe you just want

635
00:55:59,496 --> 00:56:04,616
it to look like a spinner a standard taproot spend and only have the signer involved not the signer

636
00:56:04,616 --> 00:56:11,016
doesn't mean no because it's zero knowledge but only the other signers involved so i think

637
00:56:12,216 --> 00:56:16,536
you're getting to uh an important detail having mentioned it three times last minute like zero

638
00:56:16,536 --> 00:56:23,576
knowledge how does that how does ck proof come into it so okay uh instead of showing a the signer

639
00:56:23,576 --> 00:56:28,696
a partially signed bitcoin transaction psbt that you want signed you present a zero knowledge proof

640
00:56:28,696 --> 00:56:34,136
proving that the psbt that you want signed meets the properties of the transaction that you initially

641
00:56:34,136 --> 00:56:44,856
asked us to sign okay so that zk proof logic lives it's not on bitcoin obviously no it's in

642
00:56:44,856 --> 00:56:49,016
it's written web assembly it's in the browser so you have like a browser relationship with your

643
00:56:49,016 --> 00:56:53,336
server yeah it's running these yeah so instead of i because i don't want to ask anyone to even

644
00:56:53,336 --> 00:56:57,816
download a program and run it so theoretically if i had you download a program that would be

645
00:56:58,456 --> 00:57:02,696
reading your transaction and sharing the zk proofs in reality it's all happening in your browser

646
00:57:02,696 --> 00:57:07,976
it's you just upload a psbt and you can you can verify yourself the psbt actually doesn't hit our

647
00:57:07,976 --> 00:57:14,136
servers which are hits our servers instead is the zk proof generated from the psbt and uh you know me

648
00:57:14,136 --> 00:57:21,896
uh not as highly technical as many other bitcoiners out there but i assume they don't have to like

649
00:57:22,696 --> 00:57:27,576
you're going to be okay if you set this up and then six months goes by you've cleared the cash

650
00:57:27,576 --> 00:57:32,856
of your browser and yeah yeah it's fine it's it's in the p it's in the ck proof that says hey you

651
00:57:32,856 --> 00:57:38,536
set up this psb or i recognize this psbt from having been set up before so what we store on

652
00:57:38,536 --> 00:57:43,576
our servers is an encrypted blob that only you can unlock so whenever you log in we'll see your

653
00:57:43,576 --> 00:57:48,616
we'll send you the encrypted blog blob uh that will have all of your transaction details and

654
00:57:48,616 --> 00:57:52,136
all the details of the proof that you need to satisfy and everything what we the only other

655
00:57:52,136 --> 00:57:56,536
thing we store is one hash one opaque hash that i can't tell anything about just a random string of

656
00:57:56,536 --> 00:58:01,256
numbers it's a the root of a merkle tree what you're submitting to me is a miracle inclusion

657
00:58:01,256 --> 00:58:06,536
proof and then a zero knowledge proof showing that you are able to provide inputs that satisfy

658
00:58:07,096 --> 00:58:12,216
that miracle inclusion proof how did you come to this it took about two years of banging my head

659
00:58:12,216 --> 00:58:19,176
against it uh it is very creative it is it was problem after problem after problem i drew some

660
00:58:19,176 --> 00:58:27,016
inspiration from uh bit 443 salvatorian gala's merkelize all the things idea uh i took a little

661
00:58:27,016 --> 00:58:29,976
bit from taproot and a little bit from what lightning did with tarot assets i was sort of

662
00:58:29,976 --> 00:58:35,096
obsessed with like i knew like a merkle tree in there somewhere would be good there's a paper that

663
00:58:35,096 --> 00:58:41,016
came out right after i launched v1 about zero knowledge predicates for snore transactions that i

664
00:58:41,016 --> 00:58:46,456
tried to get working and had to start from scratch because their thing was built like a battleship

665
00:58:46,456 --> 00:58:51,976
it was they they're using some insane groth 16 zero knowledge proof system that is great for like

666
00:58:51,976 --> 00:58:58,536
blind coin swaps and it was just they built a battleship i needed a drone and i realized like i

667
00:58:58,536 --> 00:59:02,936
after reading the paper reading paper i just realized their idea was right but their approach

668
00:59:02,936 --> 00:59:06,136
was just too much for me and i also needed something that i could understand and debug myself

669
00:59:07,096 --> 00:59:12,216
um and then i just spent about 18 months just banging banging banging banging and i finally got

670
00:59:12,216 --> 00:59:16,456
got the last bits of it working unlike everybody else because i had my head down you all were

671
00:59:16,456 --> 00:59:22,256
working on claude like a sucker i had chat gpt explaining my undergrad cs textbooks to me

672
00:59:22,256 --> 00:59:26,876
because i thought that was the way you used llms apparently i could have just said hey claude build

673
00:59:26,876 --> 00:59:30,696
me an awesome signer and that would have been it it's not there yet it's not there yet like

674
00:59:30,696 --> 00:59:37,316
give it two weeks by the time this airs i trust i trust uh claude code and codex to be able to

675
00:59:37,316 --> 00:59:45,136
build a flow for me that will take txt files and highlight uh potentially viral youtube clips but

676
00:59:45,136 --> 00:59:50,376
when it comes to bitcoin security um i'm not sure if i'm i'm comfortable with it there yet so i

677
00:59:50,376 --> 00:59:55,656
wouldn't uh deride yourself for banging your head and thinking about this from first principles and

678
00:59:55,656 --> 00:59:59,736
doing it the human way i should have just taken an extra year spending on the beach and then

679
00:59:59,736 --> 01:00:04,956
the next model will be able to do this we're all being replaced man how does that make you feel

680
01:00:04,956 --> 01:00:10,796
uh relieved if this is the last code that i've ever written then i'll feel good about that i feel

681
01:00:10,796 --> 01:00:15,176
like this is an interesting thing that i built and i hope the coiners enjoy it well it is

682
01:00:15,176 --> 01:00:21,456
incredibly interesting and again going back to what i was saying earlier like when you reached

683
01:00:21,456 --> 01:00:25,796
out to me the other week and i was going through the website and looking at all the use cases i

684
01:00:25,796 --> 01:00:28,496
mean it validated something we're discussing earlier it's like i don't think we've explored

685
01:00:28,496 --> 01:00:34,356
the design space that exists before us and i think what you're doing is just that i think there is a

686
01:00:34,356 --> 01:00:41,076
tremendous amount that we can do with multi-signature constructions in general, as long as we're

687
01:00:41,076 --> 01:00:46,676
honest with ourselves about what the trade-offs are. And I think if the signer in this case is

688
01:00:46,676 --> 01:00:52,176
fully zero knowledge, that trade-off space has been lessened significantly. There's no information

689
01:00:52,176 --> 01:00:55,696
leakage anymore. You don't have to worry about sharing your transaction details with me. You

690
01:00:55,696 --> 01:01:01,516
still have to worry about me being online or not. It's about liveliness. Yeah. So the Bitcoin's big

691
01:01:01,516 --> 01:01:06,316
draw is well as long as there's one honest minor one economically rational minor one person that's

692
01:01:06,316 --> 01:01:12,076
willing to mine my transactions for the appropriate free rate then we have censorship resistance

693
01:01:12,076 --> 01:01:17,196
if i'm only one signer well you have to worry about me being online all right

694
01:01:18,076 --> 01:01:21,596
that's i'm gonna do it because i can see odell on my shoulder right now all right

695
01:01:21,596 --> 01:01:26,396
could you run this in nostril relays you know i could you know what i'll do it just for odell

696
01:01:26,396 --> 01:01:31,116
they asked me nicely but like is that the way you could sort of even narrow that liveliness

697
01:01:31,996 --> 01:01:36,476
exploit down even further you know what theoretically that's possible yeah actually

698
01:01:36,476 --> 01:01:41,196
i don't see why not uh it might take a little bit of re-engineering based on what i have right now

699
01:01:41,196 --> 01:01:46,556
but what i have right now is malleable certainly yeah if odell asked me nicely if he makes me a cup

700
01:01:46,556 --> 01:01:50,636
of coffee from his excellent coffee machine as someone who thinks the world of him got him for

701
01:01:50,636 --> 01:01:56,796
his wedding not dropping any names then i might just do it but i mean again think like combining

702
01:01:56,796 --> 01:02:00,716
these things like i'm that you understand it's much better than i do like i don't know

703
01:02:00,716 --> 01:02:05,116
yeah you know what i when you say malleable you mean like you could port the zk sort of

704
01:02:06,236 --> 01:02:10,396
yeah you could probably well so the nostril would be the transport layer the zk stuff would

705
01:02:10,956 --> 01:02:14,636
you could have a separate binary somewhere that people downloaded and then they would

706
01:02:14,636 --> 01:02:18,556
send the proofs through nostril relays and then eventually they'd get to my end pub yeah you could

707
01:02:18,556 --> 01:02:19,396
You could do that.

708
01:02:19,396 --> 01:02:21,976
And in fact, that's certainly more,

709
01:02:21,976 --> 01:02:23,736
you've solved the censorship position access,

710
01:02:23,736 --> 01:02:38,274
I guess as long as there one odds relay Do we just solve something Are we scaling Bitcoin on this podcast the uh no but it like again like these design spaces have not been explored thoroughly enough

711
01:02:38,274 --> 01:02:43,794
and then yeah and so like the getting into like i know you gave the gimme our ball like you can

712
01:02:43,794 --> 01:02:47,714
only spend a hundred thousand sads storing business hours and staff for business hours less than 100

713
01:02:47,714 --> 01:02:54,834
like so practical use case uh let's run through three archetypes three different user archetypes

714
01:02:54,994 --> 01:02:59,554
yeah what are they in your mind like what are the day-to-day use cases for this so some people are

715
01:02:59,554 --> 01:03:04,274
going to want to do either white listing or blacklisting which i don't necessarily agree

716
01:03:04,274 --> 01:03:08,434
with conceptually but i understand that that's well you know there's some use cases that make

717
01:03:08,434 --> 01:03:13,314
sense and there's some use cases that doesn't the let's you have it on the website dpkr yeah sure um

718
01:03:14,754 --> 01:03:18,274
it was important to me to build something that could be used in ways that i don't approve of

719
01:03:18,274 --> 01:03:22,114
so i don't approve you setting up ovac blacklists with this but you certainly could and i wouldn't

720
01:03:22,114 --> 01:03:26,274
know about it and i wouldn't be able to stop you so you could do that more likely you'll probably

721
01:03:26,274 --> 01:03:30,674
want to do whitelisting and say i actually only want spends to go to my certain approved addresses

722
01:03:31,634 --> 01:03:38,674
uh there's the obvious you could mimic a vault of all construction of some sort you could do all

723
01:03:38,674 --> 01:03:42,834
sorts of treasury management stuff that's the thing that's most interesting to me uh you can

724
01:03:42,834 --> 01:03:48,354
go from beyond two or three multi-sync to really complicated if this key then do that if this key

725
01:03:48,354 --> 01:03:54,354
then do that uh which opens up a whole design space for bitcoin treasury companies oh no wait

726
01:03:54,354 --> 01:03:58,274
a minute did i just dump on them in the first half i'm thinking more um original bitcoin treasury

727
01:03:58,274 --> 01:04:04,674
companies yeah incentivizing early uh early employees who are helping you get to uh revenue

728
01:04:04,674 --> 01:04:11,314
profitability and scaling uh vesting right oh that'd be great you find it more guessing right

729
01:04:11,314 --> 01:04:15,314
like you hey if you help us get to a certain point i'll sign with this key and that'll give you

730
01:04:15,954 --> 01:04:19,554
50 million saps if we don't get to that point i sound with this kid you get 25 million you could

731
01:04:19,554 --> 01:04:24,354
absolutely do that yeah and then something that's near and dear to my heart because i found this out

732
01:04:25,554 --> 01:04:31,794
entirely by surprise when i was working at unchained i was working the booth one day at uh

733
01:04:31,794 --> 01:04:39,714
bitcoin 2021 i think okay yeah and i had the experience of having customer after customer

734
01:04:39,714 --> 01:04:44,354
walk up to us asking about inheritance bitcoiners are very concerned about their if you're hanging

735
01:04:44,354 --> 01:04:48,434
on to your sats and you've been doing so for a while you're concerned about where they're going

736
01:04:48,434 --> 01:04:54,194
after you pass how do you get them to your your errors so building a living trust would be something

737
01:04:54,194 --> 01:04:58,994
you could do with this building a trust or inheritance with more complicated rules than

738
01:04:58,994 --> 01:05:05,074
me my heir and my attorney so how would that work practically like would you have a time lock that

739
01:05:05,074 --> 01:05:09,954
you just assume all right if it runs this long i'm most likely dead and it releases or

740
01:05:09,954 --> 01:05:16,614
or give your well let's see you could have I'll give you an example how about three running time

741
01:05:16,614 --> 01:05:20,334
locks each one allowed to withdraw to a different address one will be

742
01:05:22,494 --> 01:05:27,474
you're still alive you still want control yeah yeah you need two for two and then the three will

743
01:05:27,474 --> 01:05:32,814
be we'll call one of them M one of them B and one of them K they all get them 18 years apart

744
01:05:32,814 --> 01:05:39,834
one five one three and one five months yeah uh or you provide your key so your errors you split

745
01:05:39,834 --> 01:05:45,674
funds three ways based on their 18th birthday okay i like that

746
01:05:45,674 --> 01:05:53,274
but the thing about it is you can literally build arbitrary policies so i don't want to

747
01:05:53,274 --> 01:05:58,394
imagine an ideal use case i want to know what you could do if you could build an arbitrary

748
01:05:58,394 --> 01:06:03,634
signing policy something that you can't express right now in bitcoin script is this um and it

749
01:06:03,634 --> 01:06:09,174
seems like actually you mentioned miniscript either i know miniscript has um sort of this

750
01:06:09,174 --> 01:06:15,014
foot gun uh exposure and that's why they're working on templates um right because if you

751
01:06:15,014 --> 01:06:20,774
just let anybody run wild with a mini script uh you can lock up bitcoin for a million blocks whatever

752
01:06:20,774 --> 01:06:25,734
it may be um accidentally so they're trying to come up with templates that say they have basically

753
01:06:25,734 --> 01:06:29,894
a rough framework of like we know this is outrageous and this is reasonable so we're

754
01:06:29,894 --> 01:06:35,174
going to try and keep you in the the realm of the reasonable where i imagine with sig bash it's much

755
01:06:35,174 --> 01:06:40,854
more controllable environment to an extent so i talked through this with the first round of beta

756
01:06:40,854 --> 01:06:44,694
testers if you hit the site you'll see it there's three different paths you can take the easy path

757
01:06:44,694 --> 01:06:49,814
is and i'm gonna can i plug maple ai yes you can the easy path is you don't actually see a ui builder

758
01:06:49,814 --> 01:06:56,054
or anything any details like that you type into a chat box that goes to maple and says hey here's

759
01:06:56,054 --> 01:07:01,654
the policy i want and it's automatically loaded into our ui builder the next step after that is

760
01:07:01,654 --> 01:07:06,454
click a template they're just like the manuscript foot guns yeah you probably just want to follow

761
01:07:06,454 --> 01:07:09,814
one of these pre-built templates just click it maybe you might have to enter an address but

762
01:07:09,814 --> 01:07:14,374
most of it will be filled out for you the third part is okay here's the policy builder

763
01:07:14,374 --> 01:07:18,214
canvas you can go from scratch go nuts if you know what you're doing i will give you

764
01:07:18,214 --> 01:07:25,734
all the foot guns you want yeah i love that optionality yeah what um and being again talking

765
01:07:25,734 --> 01:07:32,294
about form factor just explaining what you want gonna maple ai voice the text i've got three kids

766
01:07:33,574 --> 01:07:38,454
each one of them turns 18 on this this and that date i want this person to spend a bitcoin build

767
01:07:38,454 --> 01:07:43,814
it for me is that yeah build that logic yeah you could absolutely do that in fact i hope you try

768
01:07:43,814 --> 01:07:49,414
to build that and if there's a bug in it file a bug with me and we'll fix it yeah awesome what um

769
01:07:50,134 --> 01:07:58,134
what's your great hope after announcing this my great hope is that we push ourselves to more and more

770
01:08:01,254 --> 01:08:07,814
find what is possible at the frontier of bitcoin every time i start to feel discouraged that we're

771
01:08:07,814 --> 01:08:14,054
not making progress something comes around like cluster mempool or arc or something where that

772
01:08:14,054 --> 01:08:18,134
makes you think wait a minute this was possible this whole time why was i busy fighting about

773
01:08:19,014 --> 01:08:26,134
dick butts on the blockchain and not actually thinking about this if nobody uses this and it

774
01:08:26,134 --> 01:08:31,174
withers on the vine but it sparks one bitcoin or say hey this gave me an idea that would be my great

775
01:08:31,174 --> 01:08:37,254
hope just pushing things a little bit forward who do you expect the first users to be like do you

776
01:08:37,254 --> 01:08:41,574
think exchanges will uh you know what the first user is going to be the crazy mountain men that's

777
01:08:41,574 --> 01:08:47,254
going to be yeah the people who actually care about privacy i'm talking to a few wallets and

778
01:08:47,254 --> 01:08:52,214
custodians right now for ways to integrate with them and i can definitely see how it would be

779
01:08:52,214 --> 01:08:59,494
useful to them but my guess is because this happened with sigbatch v1 where i literally

780
01:08:59,494 --> 01:09:03,574
released it as a science experiment and before we were off to the races someone had locked up like

781
01:09:03,574 --> 01:09:08,534
the equivalent of it's much more than five thousand dollars now but five thousand dollars in a one of

782
01:09:08,534 --> 01:09:14,374
two with with some buggy logic that for a settlement that i don't think ever came to pass

783
01:09:14,374 --> 01:09:19,014
and i was flattered but also shocked i'm sure it will be one of the the crazy node runners that

784
01:09:19,014 --> 01:09:23,334
does it and whoever it is god bless you i love you and let me buy you a beer afterwards if you

785
01:09:23,334 --> 01:09:29,334
lose your funds will there be an api for this yeah yeah i think you have to build an api that's the

786
01:09:29,334 --> 01:09:32,854
hard lesson i learned from v1 everybody wanted to integrate because you know there's only so

787
01:09:32,854 --> 01:09:36,774
many people that are actually going to be uploading psbt's and interacting with the website that's

788
01:09:36,774 --> 01:09:41,814
sort of to gain mind share there's got to be the wallets and the custodians need nested kate

789
01:09:41,814 --> 01:09:46,374
integrate with thinking now about my my open claw bot yeah your open call but you're not going to use

790
01:09:46,374 --> 01:09:50,134
the sdk you're i realized this last week it's going to be your llm that's going to be integrating

791
01:09:50,134 --> 01:09:57,894
with the sdk yeah yeah how do you feel about the emergence of this uh agentic economy uh you know

792
01:09:57,894 --> 01:10:06,134
it's humbling in the sense that the agent is probably more often doing better work than i am

793
01:10:06,134 --> 01:10:10,614
it's probably you're thinking about this i think your clawbot will lose less sats over time than

794
01:10:10,614 --> 01:10:16,694
i have lost over time from like building foot guns and mistakes that's probably on balance best for

795
01:10:16,694 --> 01:10:20,374
everyone involved well i've been thinking about it in the last couple days since i spun up the

796
01:10:20,374 --> 01:10:27,254
phoenix d well like we need like a vps or bls bls a validated lightning signer yeah for for the

797
01:10:27,254 --> 01:10:30,614
agents where it's like hey i want you to have all the wallet logic but when it comes to signing the

798
01:10:30,614 --> 01:10:34,694
private key like i want something separate yeah from your server running in the cloud

799
01:10:35,334 --> 01:10:39,894
and maybe you communicate with maybe that's overdoing it maybe it's no i think that'd be

800
01:10:39,894 --> 01:10:44,214
great you could have your phone throw you a two-factor off just you know hey your asian wants

801
01:10:44,214 --> 01:10:48,614
to spend some sats okay i approve actually because there's a certain point where you want to be

802
01:10:48,614 --> 01:10:54,374
actually otherwise it's his life cloudbot's next thing at first clawbot buys the tickets for you

803
01:10:54,374 --> 01:10:58,294
then cloudbot goes on the vacation for you then suddenly your wife is taking pictures of the mac

804
01:10:58,294 --> 01:11:02,854
mini yeah well i'm very happy we're having this conversation because that like vls it's like that

805
01:11:02,854 --> 01:11:07,414
is liquid we were talking i mean we glossed over liquid but i think there's a ton of things

806
01:11:07,414 --> 01:11:14,214
that bit corners have been building number one number two not exploring the full design space

807
01:11:14,214 --> 01:11:18,894
uh sufficiently enough in my opinion and then number three timing has been off for a lot of

808
01:11:18,894 --> 01:11:26,574
these things we're like now with the agentic web um sort of emerging in front of us like something

809
01:11:26,574 --> 01:11:32,734
like vls makes a lot more sense now it uh especially if you're like vls up to this point

810
01:11:32,734 --> 01:11:39,054
like there is like a you're running a lightning node in the cloud and it's like yeah that's good

811
01:11:39,054 --> 01:11:45,854
enough like i would like to separate the private key um from the node logic and have physical

812
01:11:45,854 --> 01:11:50,414
access to the private key that's signing but like yeah it's good enough but now with like agents

813
01:11:50,414 --> 01:11:55,854
that can just run wild and sign on your behalf in the server it's like now maybe it actually makes

814
01:11:55,854 --> 01:12:02,014
like maybe that is the impetus we need to to separate the key from the um the node logic yeah

815
01:12:02,014 --> 01:12:07,774
you want to have a program you wouldn't have a reason to have any sort of access from internet

816
01:12:07,774 --> 01:12:12,014
technology machine before now you do have one but you still want a human in the loop right yeah yeah

817
01:12:13,214 --> 01:12:19,454
and then yeah it feels like the timing for a lot of things have been talked about for

818
01:12:20,094 --> 01:12:24,574
quite a while and bitcoin's been derived i think lightning is a great example that been around

819
01:12:24,574 --> 01:12:30,654
since 2018 uh hand up i was one of those people like this is going to be fantasy out of the box

820
01:12:30,654 --> 01:12:35,534
and now it takes like the better part of a decade to actually build yeah and interrupt uh a

821
01:12:35,534 --> 01:12:40,974
distributed interoperable protocol on top of another distributed protocol um i think we've

822
01:12:40,974 --> 01:12:45,614
gotten there and obviously the it's going to solve the payments use case it has to a certain degree

823
01:12:45,614 --> 01:12:50,094
but it's not as widespread as we'd like it to be but now here we are eight years later and it's like

824
01:12:50,094 --> 01:12:55,454
oh like it's beginning to take form and uh i don't think that's a lightning problem i see that as a

825
01:12:55,454 --> 01:12:59,934
bitcoin problem right i mean i don't know just me in the queue like bitcoin is like a bitcoin product

826
01:12:59,934 --> 01:13:04,014
uh it's a function of bitcoin adoption not necessarily lighting adoption right now

827
01:13:05,134 --> 01:13:11,294
weird thoughts on adoption how else yeah bitcoin is for anyone it's not for everyone um

828
01:13:12,814 --> 01:13:17,614
we've said that for a while i am concerned that it might have to be for everyone the way the dollar

829
01:13:17,614 --> 01:13:24,654
is going there you know just forget it just because it's not intended for everyone necessarily

830
01:13:24,654 --> 01:13:31,454
doesn't mean everyone's not going to need it at a certain point if gold is swinging 30 in 24 hours

831
01:13:31,454 --> 01:13:36,094
that starts to de-dollarization stops being a meme and starts being something you're actually

832
01:13:36,094 --> 01:13:41,374
concerned about and if you have exposure to gold it may feel nice to preserve your purchasing power

833
01:13:41,374 --> 01:13:46,574
when you need to go spend it it's not very yeah so i know it's easy to be bearish right now when

834
01:13:46,574 --> 01:13:50,494
we've i don't know what the price is when we walked in but i think we were just about to drop

835
01:13:50,494 --> 01:13:56,494
below the last cycle's all-time high we're pretty close we are at 75 or above where we were above

836
01:13:56,494 --> 01:14:01,774
where we were all right two rips ago when we did this i was dunked on for being a bear so i'm not

837
01:14:01,774 --> 01:14:06,174
making any price predictions but i will say it's easy to be bearish right now there's every reason

838
01:14:06,174 --> 01:14:14,494
to think that who cares about dollar sat parity the number of users is going to go up up up yeah

839
01:14:15,134 --> 01:14:20,254
i agree i think um again the user experience around this is getting better and better than

840
01:14:20,254 --> 01:14:26,414
ever the interoperability i mean you could say that at any moment right as time passes obviously

841
01:14:27,294 --> 01:14:33,694
user experience hurdles are going to be uh overcome but um yeah i don't know i i feel more

842
01:14:34,894 --> 01:14:42,014
funnily enough even at 75k 40 below the all-time high of uh three months four months ago i feel

843
01:14:42,014 --> 01:14:47,614
more confident than ever in bitcoin likewise you know what makes me feel and this is the weirdest

844
01:14:47,614 --> 01:14:52,654
thing to increase confidence but follow the thread if you can you know what gives you the

845
01:14:52,654 --> 01:14:58,974
most confidence watching you use and talk about whisper why do you say that well so there's this

846
01:14:58,974 --> 01:15:05,374
whole idea the biggest problem is getting people to switch their unit of account but why would that

847
01:15:05,374 --> 01:15:09,054
be a problem for you to worry about why don't you just tell your phone buy something and have your

848
01:15:09,054 --> 01:15:13,774
phone talk to the kiosk and decide what the unit of account is and what unit account are they going

849
01:15:13,774 --> 01:15:17,454
to settle on the thing that anyone can print out of thin air or the thing that both of them can

850
01:15:17,454 --> 01:15:22,734
agree has value yeah and even if they want to use two different things like the swappable nature of

851
01:15:22,734 --> 01:15:29,374
bitcoin and retailers is the rails in between is being automated via apis as we speak i mean it

852
01:15:29,374 --> 01:15:34,494
seems like you know brain fart thought leadership nonsense but really think about how many cycles

853
01:15:34,494 --> 01:15:38,414
we've talked we've spent talking about the actual symbol for the unit of account that we should use

854
01:15:38,414 --> 01:15:43,694
for bitcoin yeah your llm doesn't care i'm not happy with you block okay i see what you're doing

855
01:15:43,694 --> 01:15:48,414
the sats i see what you're trying to do you can put the b in front of the sats but it's still

856
01:15:48,414 --> 01:15:56,094
sats at the end of the day jack it's funny too because uh we helped make sats a standard with

857
01:15:56,094 --> 01:16:00,814
cash app back in the day if you don't remember are they doing i haven't it won't render on my

858
01:16:00,814 --> 01:16:03,694
laptop i know everyone's talking about them changing the icon but i don't know what the

859
01:16:03,694 --> 01:16:08,174
b looks like is it let me see let me see i'll put cash up see see what it looks like because

860
01:16:08,174 --> 01:16:16,254
i'm pretty sure if it's what i think it is that's the tie bot um i'll show you it looks like that

861
01:16:17,854 --> 01:16:21,374
okay yeah all right well hmm yeah

862
01:16:23,854 --> 01:16:27,614
it's sat still jack yeah i what um

863
01:16:30,414 --> 01:16:37,854
anything on well before we get your final thoughts on it i want to bring it back to zk

864
01:16:37,854 --> 01:16:44,094
proofs because i think this is something that's been talked about quite a bit just not in bitcoin

865
01:16:44,094 --> 01:16:49,614
but generally like obviously l2's bit vm roll ups everybody's using zero knowledge proofs it's this

866
01:16:50,334 --> 01:16:57,294
incredible sci-fi tech um that we should all be leveraging i agree like zero knowledge proofs is

867
01:16:57,294 --> 01:17:02,574
great but again going back to how do you actually implement it um instead of doing it with like

868
01:17:02,574 --> 01:17:10,894
innovate bit vm or some roll up on ethereum whatever it may be uh i think what you're

869
01:17:10,894 --> 01:17:14,734
building is an example like it doesn't need a blockchain to do this stuff like you can simply

870
01:17:14,734 --> 01:17:21,854
just use yeah the cryptographic logic to solve things and combine things was there a question

871
01:17:21,854 --> 01:17:27,374
in there that was just like in terms of implementation details of zero knowledge

872
01:17:27,374 --> 01:17:33,374
proof specifically like why did you settle on on this like it's not in a roll up it's not yeah well

873
01:17:34,094 --> 01:17:41,774
i was very lucky that i had with v1 a broken product and a broken feature set but a working

874
01:17:41,774 --> 01:17:46,654
user experience the general idea of like well you sign up and i'll give you an xpub and then you'll

875
01:17:46,654 --> 01:17:52,494
use that and you'll ask me to sign a psbt that makes sense so once i had that it was oh well

876
01:17:52,494 --> 01:17:57,614
instead of giving me the psbt rock can you give me a zero knowledge proof that is derived from

877
01:17:57,614 --> 01:18:02,174
the psbt and can i tie it to the psbt and convince myself that that's something that should return

878
01:18:02,174 --> 01:18:08,254
you a signature how do you how long did you test that like what made you comfortable for that

879
01:18:09,614 --> 01:18:10,094
it was

880
01:18:14,014 --> 01:18:19,694
i'm gonna say just shy of 18 months there because even i went the least see even to me

881
01:18:19,694 --> 01:18:24,734
zero knowledge proof so there's a lot of moon math there and i it was very important to me that i

882
01:18:24,734 --> 01:18:28,094
built something that i could understand and debug in the middle of the night so that god forbid if

883
01:18:28,094 --> 01:18:32,734
the worst happened i could say well this is what's going wrong because the thing with ckp is i can't

884
01:18:32,734 --> 01:18:37,774
tell anything about your transaction and asking you to debug it would say well step one i need you

885
01:18:37,774 --> 01:18:41,694
to sacrifice your privacy and share the transaction with me so i wanted to be absolutely sure that that

886
01:18:41,694 --> 01:18:51,534
uh that that didn't come to pass I v1 I actually made the mistake of testing on mainnet and I joked

887
01:18:51,534 --> 01:18:55,974
about like I'm testing on mainnet so I lost a couple hundred dollars in testing not viable

888
01:18:55,974 --> 01:19:00,114
this time it's all signet I wrote a couple of thousand test cases and banged on them banged

889
01:19:00,114 --> 01:19:03,954
on them banged on them I had I was very lucky I had a few alpha testers and a few beta testers

890
01:19:03,954 --> 01:19:10,254
that were rather relentless and provided me with feedback uh I'm gonna say 18 months

891
01:19:10,254 --> 01:19:13,334
What was like the weirdest edge case that you found that you weren't expecting?

892
01:19:14,254 --> 01:19:18,774
You know, the signing part of it, the ZK proof part of it, that was easy.

893
01:19:18,914 --> 01:19:23,454
The edge cases were things where a test would go through and I'd think about it and say,

894
01:19:23,594 --> 01:19:24,694
oh, wait, that leaks privacy.

895
01:19:24,934 --> 01:19:26,174
I just realized something about you.

896
01:19:26,214 --> 01:19:27,054
I can infer something.

897
01:19:27,514 --> 01:19:31,994
The model I tried to adopt was what happens if Chain Analysis or Lazus Group owns my server?

898
01:19:32,174 --> 01:19:33,074
What can they know about you?

899
01:19:33,154 --> 01:19:34,174
And I wanted to say nothing.

900
01:19:34,814 --> 01:19:36,054
It's really hard to get to nothing.

901
01:19:36,054 --> 01:19:41,514
um there were just all sorts of educations were like well okay I haven't seen your transaction

902
01:19:41,514 --> 01:19:45,714
but I can sort of infer your transaction structure if I think about it um

903
01:19:47,874 --> 01:19:54,834
things like well okay I don't know anything about your transaction but I know how long this transaction

904
01:19:54,834 --> 01:19:59,034
took for you to generate a proof and I know how long this simple transaction takes to generate a

905
01:19:59,034 --> 01:20:03,834
proof and if I look at the blockchain I can see well there's this heavy transaction that's settled

906
01:20:03,834 --> 01:20:10,474
must be you things like that okay it's amazing how privates can leak in a dozen different ways

907
01:20:10,474 --> 01:20:17,074
like timing broadcasts yeah all that stuff yeah there was no any one scary thing there were just

908
01:20:17,074 --> 01:20:21,914
a bunch of small little rabbit holes yeah so i'm gonna go back to dlcs that's one thing i remember

909
01:20:21,914 --> 01:20:28,254
testing out dlcs while it like shocked me again uh not the most technical but

910
01:20:28,254 --> 01:20:32,534
pick up things as i go like testing a dlc wall for the first time i was like it's taking a really

911
01:20:32,534 --> 01:20:36,694
long time to sign this yeah so like what you're saying is like on your side somebody brings you

912
01:20:36,694 --> 01:20:43,094
a transaction to sign and you observe like oh this is taking a minute yeah probably a bunch of

913
01:20:44,214 --> 01:20:49,574
other signatures in this transaction so i can go look at mempool.space look for a five seven or

914
01:20:49,574 --> 01:20:56,694
whatever and assume that that could have been the transaction out of your side yeah okay all right

915
01:20:56,694 --> 01:21:00,474
right well something what do you got for the freaks out there

916
01:21:02,394 --> 01:21:09,654
hmm how low are we going how low are we going how bearish are you you know what Odell's not

917
01:21:09,654 --> 01:21:14,994
here I would love it if we somehow managed to what was the high of the last cycle was

918
01:21:14,994 --> 01:21:20,994
a 69 420. did we something around there yeah I would love it if we broke the bottom of the

919
01:21:20,994 --> 01:21:26,154
of the last yeah that would be hilarious to me because I don't think we've ever done that

920
01:21:26,154 --> 01:21:32,454
for but I also think you and I might be recording this at the bottom of the bear market am I either

921
01:21:32,454 --> 01:21:36,414
way I'm screwed with the price prediction here I like I like hey just ride both sides of the

922
01:21:36,414 --> 01:21:40,614
fence like we're either going way lower or at the bottom already yeah I'll I'll be wrong either way

923
01:21:40,614 --> 01:21:46,914
won't I um and I don't want to be flipping about it but does it really matter in a year five years

924
01:21:46,914 --> 01:21:50,634
10 years are you going to look back on the price that's the thing I take from our last

925
01:21:50,634 --> 01:21:59,914
our first one was in 2017 next to 2021 2020 2020 all right yeah we met like around christmas time

926
01:21:59,914 --> 01:22:04,814
2020 god the cursed covid rip do you have any people how any idea how many people in a professional

927
01:22:04,814 --> 01:22:10,094
setting have rolled up to me and said i loved your podcast on tfdc and i say the one hour one

928
01:22:10,094 --> 01:22:14,854
where i sounded like a genius and like no the three hour one where you were drunk and mad

929
01:22:14,854 --> 01:22:24,374
odell dumped on you and took a nap on your rug so we got that yeah now we've got 2021 we did one

930
01:22:24,374 --> 01:22:30,294
year later when i was in austin and my back porch and the thing about all of them is i remember the

931
01:22:30,294 --> 01:22:34,774
bitcoin environment i remember the technology we talked about i remember the topics we touched on

932
01:22:34,774 --> 01:22:40,714
can't remember a thing about the price right same and that's why it stay humble stacks that's like

933
01:22:40,714 --> 01:22:47,914
doesn't like i it's funny because having done this for nine years and seen the waves of adoption via

934
01:22:47,914 --> 01:22:52,394
downloads and increased subscription numbers you could see like anytime the price goes up you get

935
01:22:53,434 --> 01:22:57,834
spikes up and it goes down but the plateau is higher than the last one and i just know there's

936
01:22:57,834 --> 01:23:03,754
a bunch of people who bought like 21 22 23 24 um 25 even and they're like what the

937
01:23:03,754 --> 01:23:07,994
fuck's going on it's like don't worry this is why we say stay humble stacks that's nothing's

938
01:23:07,994 --> 01:23:13,394
is going to change the fact that somebody like ArbedOut can build this blind signer

939
01:23:13,394 --> 01:23:19,934
using ZK proofs to give you more privacy on your Bitcoin without changing the protocol

940
01:23:19,992 --> 01:23:26,212
uh like the what you what you're building is like sci-fi technology that cannot be replicated not

941
01:23:26,212 --> 01:23:31,932
sci-fi but like it's very primitive cryptography not primitive but it's like you can understand the

942
01:23:31,932 --> 01:23:36,852
logic it's simple but it's powerful that's what i'm trying to get at not sci-fi but powerful

943
01:23:36,852 --> 01:23:42,972
sovereign technology and that hasn't changed at all in the seven years i've been talking

944
01:23:42,972 --> 01:23:47,512
it's only gotten better now i'm not just talking about the code i've written but the things

945
01:23:47,512 --> 01:23:53,872
we've managed to build collectively as a community in the past nine years when you started think of

946
01:23:53,872 --> 01:23:59,852
where lightning was think of where you were probably there when lightning lnd first launched

947
01:23:59,852 --> 01:24:04,232
its alpha you were there when nostril realized first went live and we all made the migration

948
01:24:04,232 --> 01:24:11,792
and we started spinning up end pubs yeah i think this podcast was probably the second or third

949
01:24:11,792 --> 01:24:17,272
podcast leveraging podcasting 2.0 i think we had one of the first lightning nodes on the network

950
01:24:17,272 --> 01:24:22,232
back in the day um it's great remember the lightning torch i remember participating in

951
01:24:22,232 --> 01:24:27,432
a lightning torch and not understanding channel liquidity and channel management oh god learning

952
01:24:27,432 --> 01:24:33,832
out the hard way yeah having a nasa excuse me a casa node um remember the casa yeah yeah box

953
01:24:33,832 --> 01:24:40,872
node i had that uh we've come a long way now i can just go into my open claw bot and say spin up a

954
01:24:40,872 --> 01:24:44,932
a Phoenix server and start trading on a L.A. markets for replace.

955
01:24:45,692 --> 01:24:46,352
I kind of this.

956
01:24:46,712 --> 01:25:02,872
The one thing this podcast is looking with is the taste for spinning up my own cloud bot just to counter trade against you I just going to try to poison you because I know you got three kids to deal with so this is easy all i have to do is time it with like their sleep schedules i want to be clear i not i not uh it was a test use case to see if we

957
01:25:02,872 --> 01:25:10,392
could ln url off into a website which you can which is like hey like that becomes a standard

958
01:25:10,392 --> 01:25:15,672
outside of bitcoin like just sign in with instead of google oauth like sign in with your lightning

959
01:25:15,672 --> 01:25:25,672
node like technically like i'm sure you see a moltbook the ai um the social networking like

960
01:25:25,672 --> 01:25:30,072
there's no reason i can't send my i don't think there is i'd have to check but i could probably

961
01:25:30,072 --> 01:25:35,352
definitely send them loose on uh stacker news or something like that with ellen url off it's just

962
01:25:35,352 --> 01:25:40,072
like hey sign up create account and begin posting on here and actually maybe i'll test that out

963
01:25:40,072 --> 01:25:44,152
tonight this is going to happen before we the podcast hits i'm going to see your post on stacker

964
01:25:44,152 --> 01:25:50,632
news from your cloud that it's crazy uh all right you were episode 100.

965
01:25:52,712 --> 01:25:58,952
2020 was probably like oh god 200 i think we actually did 100 200 we did every i think the

966
01:25:58,952 --> 01:26:06,392
second one was 200. really 2021 was probably like around 300 and here we are we took too much time

967
01:26:06,392 --> 01:26:15,832
between that one 7 13 7 14 depending on when you officially announce sig bash where can anybody

968
01:26:16,952 --> 01:26:36,652
who wants to learn more play around with that go i would love it if you tested it at www so by the time you hear this it going to be live on signet because i don want to make the same mistake we did with V1 and have people start playing with money immediately I pretty sure it battle tested and bulletproof at this point but I want to find out the hard way

969
01:26:36,932 --> 01:26:40,672
Who's the one like wallet developer out there that you want to be messing with this?

970
01:26:40,772 --> 01:26:41,752
I know you have a name in your mind.

971
01:26:42,572 --> 01:26:44,512
If he hasn't messed or she hasn't messed with it already.

972
01:26:44,872 --> 01:26:50,092
I'm going to do you a favor and not scream into the mic, but you're just tricking my Gary Oldman and I want to do everyone.

973
01:26:50,092 --> 01:26:57,192
Seriously, everybody, especially come at me if you have suggestions for the SDK.

974
01:26:57,432 --> 01:26:59,692
Right now, the web UI is what's up and live.

975
01:26:59,792 --> 01:27:03,932
So you can get a QR code to scan with your wallet and bang on that.

976
01:27:04,032 --> 01:27:06,392
But I need to figure out how people want to integrate with this.

977
01:27:06,432 --> 01:27:07,232
That's the hard part.

978
01:27:07,732 --> 01:27:11,332
There are so many different models for how you would integrate with a signer, how exchanges

979
01:27:11,332 --> 01:27:15,392
want to do one way, custodians another way, wallets another way, lending providers another

980
01:27:15,392 --> 01:27:15,712
way.

981
01:27:16,672 --> 01:27:17,332
Oh, sorry.

982
01:27:17,732 --> 01:27:17,992
Go ahead.

983
01:27:17,992 --> 01:27:20,432
and I just need to figure out a way to satisfy everyone's needs.

984
01:27:20,952 --> 01:27:21,552
All right.

985
01:27:21,552 --> 01:27:24,032
Use case here at TFTC.

986
01:27:24,032 --> 01:27:26,692
A lot of all boy, all men at the

987
01:27:27,632 --> 01:27:30,332
the company right now, not as diverse as many would like us to be.

988
01:27:30,332 --> 01:27:32,092
But the boys like to get paid in Bitcoin.

989
01:27:32,092 --> 01:27:34,652
They send me ZapRite invoices, obviously with the price moving

990
01:27:36,732 --> 01:27:37,452
different amounts

991
01:27:39,292 --> 01:27:42,192
in sats terms from invoice to invoice.

992
01:27:42,192 --> 01:27:44,952
Could I set up a lot like where I funded a wallet

993
01:27:44,952 --> 01:27:51,952
and was somehow able to get the ZapRite invoice,

994
01:27:53,952 --> 01:27:56,592
use the ZapRite API to get the dollar cost

995
01:27:56,592 --> 01:28:08,792
and the sats cost and then send it to you and say all right I have an idea in mind of a range of bitcoin i willing for you to blind sign like could i set that up so i don have to go in and physically

996
01:28:08,792 --> 01:28:14,392
sign yeah anytime an invoice comes yeah absolutely i wow okay so you just want to hand it all over

997
01:28:14,392 --> 01:28:18,872
to the cloud about to do the signing and they do the no no no the club one has no control over this

998
01:28:18,872 --> 01:28:22,552
i do this so you're gonna do the final i'm getting into the voice i'm like okay yeah sure you could

999
01:28:22,552 --> 01:28:27,352
do that pending when the sdk is released but yeah okay no that would help me massively all right

1000
01:28:27,352 --> 01:28:33,912
let's figure it out because there's times when i i get uh an invoice i'm busy i forget about i pay

1001
01:28:33,912 --> 01:28:39,272
it like i mean not late but i like to pay it as soon as i get it just to because that is the magic

1002
01:28:39,272 --> 01:28:43,272
of bitcoin yeah it's like somebody needs to get paid to send you an invoice like boom money's there

1003
01:28:44,072 --> 01:28:50,952
um but sometimes i lapse because i'm busy and it sounds like so you could have yeah and sign for

1004
01:28:50,952 --> 01:28:55,752
you if you were if you were busy doing other things yeah yeah absolutely okay sweet solve my

1005
01:28:55,752 --> 01:29:01,192
solving business logic problems here all right let's make it happen all right until uh let's

1006
01:29:01,192 --> 01:29:05,672
not wait if we wait another 400 episodes i won't see you until the other side of four figures so i

1007
01:29:05,672 --> 01:29:09,692
don't think we can do that i don't think i have the right to call dibs on episode a thousand you're

1008
01:29:09,692 --> 01:29:15,232
way too big league for me no you do you do you do anybody has dibs you do um but i will if not

1009
01:29:15,232 --> 01:29:16,072
1,999.

1010
01:29:16,792 --> 01:29:17,012
Okay.

1011
01:29:17,232 --> 01:29:17,412
Yeah.

1012
01:29:17,692 --> 01:29:17,932
Okay.

1013
01:29:18,292 --> 01:29:19,012
So we've got a.

1014
01:29:19,092 --> 01:29:23,332
My one condition is that Odell has to be present and even more inebriated than was during the

1015
01:29:23,332 --> 01:29:23,752
COVID rip.

1016
01:29:23,832 --> 01:29:24,892
I will have my revenge.

1017
01:29:25,012 --> 01:29:25,132
Okay.

1018
01:29:25,172 --> 01:29:28,412
We're getting, um, we're going to get a very good bottle of whiskey.

1019
01:29:28,472 --> 01:29:30,712
I don't drink whiskey that much anymore, but we're going to get a very good bottle of

1020
01:29:30,712 --> 01:29:31,292
whiskey for that one.

1021
01:29:31,472 --> 01:29:31,812
All right.

1022
01:29:31,812 --> 01:29:32,292
Sounds good.

1023
01:29:32,592 --> 01:29:32,872
All right.

1024
01:29:33,332 --> 01:29:33,772
Until then.

1025
01:29:33,932 --> 01:29:34,592
Peace and love freaks.

1026
01:29:35,012 --> 01:29:35,152
Okay.