1
00:00:00,000 --> 00:00:15,960
Welcome in to This Week in Bitcoin, episode 97.

2
00:00:16,340 --> 00:00:22,200
My name is Chris, ChrisLAS.com, JupiterBroadcasting.com.

3
00:00:22,520 --> 00:00:24,600
Well, today's episode is way off format.

4
00:00:24,720 --> 00:00:25,960
You got to have fun every now and then.

5
00:00:25,960 --> 00:00:28,440
I think this is really the episode 100 party.

6
00:00:28,440 --> 00:00:32,880
So that way episode 100 is all about business, you know, like the show is supposed to be.

7
00:00:32,900 --> 00:00:34,140
And this is where we have the fun.

8
00:00:34,440 --> 00:00:38,000
So today we're going to talk about node management in 2026.

9
00:00:38,360 --> 00:00:41,480
And to do that, I have a couple of my unplugged buddies with me.

10
00:00:41,600 --> 00:00:42,160
Hello, Wes.

11
00:00:42,300 --> 00:00:42,580
Hello.

12
00:00:43,160 --> 00:00:43,860
Hello, Brent.

13
00:00:44,020 --> 00:00:44,640
Hello there.

14
00:00:44,940 --> 00:00:45,640
Hello, you two.

15
00:00:45,760 --> 00:00:48,200
So all three of us are node operators.

16
00:00:48,620 --> 00:00:51,780
Wes, you probably have some of the most experience just because you play around for hours.

17
00:00:52,000 --> 00:00:54,100
And then I have probably the most amount of nodes.

18
00:00:54,300 --> 00:00:55,020
Yeah, definitely.

19
00:00:55,020 --> 00:00:59,300
And then, Brent, you probably have some of the most early experience.

20
00:00:59,460 --> 00:01:00,340
You have Ranonode.

21
00:01:00,460 --> 00:01:02,140
You also have AlbiHub.

22
00:01:02,620 --> 00:01:05,360
So you're kind of in that kind of maybe where some of the audience is at.

23
00:01:05,840 --> 00:01:07,280
It's a nice way of saying the least experience.

24
00:01:07,440 --> 00:01:10,020
We're trying to represent like the full spectrum on this episode.

25
00:01:10,160 --> 00:01:14,480
Yeah, you guys kind of got into it early over in office hours when my node was just a twinkle in my eye.

26
00:01:14,580 --> 00:01:16,280
I remember that fateful day.

27
00:01:16,360 --> 00:01:17,380
Early days of Umbral.

28
00:01:17,780 --> 00:01:22,900
In fact, that was one of our tasks that we'll talk about later is we had to rescue an old Umbral node.

29
00:01:22,900 --> 00:01:29,140
and I think we should start by acknowledging there's a lot of ways to run a node. Of course,

30
00:01:29,700 --> 00:01:33,220
you can run a Bitcoin node just about on any machine that has enough hard drive space,

31
00:01:33,340 --> 00:01:36,900
but these days you might also want to run a Lightning set up on top of that.

32
00:01:37,540 --> 00:01:40,920
And so this segment is going to assume you already have a node of some kind. Maybe it's AlbiHub,

33
00:01:41,080 --> 00:01:46,940
LND, Core Lightning, and then some of the deeper stuff we're going to get into down the road might

34
00:01:46,940 --> 00:01:52,640
require you have AlbiHub set up in a certain way if you're going to use AlbiHub, but most of it

35
00:01:52,640 --> 00:01:56,760
should be applicable to just about everybody. And the thing is, is there's a lot that is new

36
00:01:56,760 --> 00:02:01,120
in 2026 when it comes to managing a Bitcoin node. A lot has changed in the last few months.

37
00:02:01,120 --> 00:02:08,260
A lot of it is API driven. A lot of it is more programmable. And a whole lot of things are very

38
00:02:08,260 --> 00:02:13,060
agent friendly now. And that is one of the big shifts in 2026.

39
00:02:22,640 --> 00:02:27,420
Anybody who listens to this show, you probably know you should be running a node.

40
00:02:27,520 --> 00:02:29,420
So the question really isn't, should I run a node?

41
00:02:29,560 --> 00:02:31,560
It's how do you properly run a node?

42
00:02:31,680 --> 00:02:32,880
What can your node talk to?

43
00:02:33,420 --> 00:02:35,040
How does your node get authenticated to?

44
00:02:35,960 --> 00:02:37,480
What's allowed to talk to your node?

45
00:02:37,860 --> 00:02:39,500
How do you monitor how your node is doing?

46
00:02:39,580 --> 00:02:42,080
And how do you keep an agent, if you want to deploy one,

47
00:02:42,400 --> 00:02:45,280
from getting too clever with your scarce money?

48
00:02:45,640 --> 00:02:47,320
This is the new stack we need to talk about.

49
00:02:47,360 --> 00:02:49,100
It's not just wallets and dashboards anymore.

50
00:02:49,100 --> 00:02:52,260
It's APIs, credentials, setting budgets for agents,

51
00:02:52,640 --> 00:02:58,200
event monitoring, and then guardrails. And when you put all of this together, it is not only a

52
00:02:58,200 --> 00:03:03,580
really fun stack, it's an extremely powerful stack that can nearly be automated to run itself.

53
00:03:03,860 --> 00:03:09,120
So I think we should start with Bitcoin Core and kind of talk about maybe what we could describe

54
00:03:09,120 --> 00:03:14,540
as the API ladder here. So you still need Bitcoin Core. It's the foundation of running your node,

55
00:03:14,540 --> 00:03:19,540
and it's the boring and it's the right answer. It's there. It's because it offers a couple of

56
00:03:19,540 --> 00:03:25,400
primitives that some of the tools will rely on like a json rpc for control yeah yeah indeed you'll

57
00:03:25,400 --> 00:03:32,100
see that on a lot of tools actually around here it does look like you can find some supporting

58
00:03:32,100 --> 00:03:38,100
programs like talking via that json rpc you'll find like a bitcoin prometheus exporter which we

59
00:03:38,100 --> 00:03:42,760
can get more into later so a lot of things we'll we'll talk through that there's also a common

60
00:03:42,760 --> 00:03:48,760
pattern with json rpc because you're doing rpc like remote procedure call right so you're kind

61
00:03:48,760 --> 00:03:53,100
of sending commands over the network and it happens to be sent with json instead of something

62
00:03:53,100 --> 00:03:59,100
like xml in the old days and so a common pattern you'll see is sort of like implementing some kind

63
00:03:59,100 --> 00:04:04,980
of proxy or manager that can implement even more trust on top depending on what the actual daemon

64
00:04:04,980 --> 00:04:10,060
underneath implements so you can maybe filter like commands that can do changes on your node

65
00:04:10,060 --> 00:04:14,460
versus read-only reporting commands and so when you get bitcoin d going you've got the json rpc

66
00:04:14,460 --> 00:04:18,240
you're going to get a source of truth for what's the chain sync at,

67
00:04:18,620 --> 00:04:21,380
what's the mempool state, what's your wallet state,

68
00:04:21,460 --> 00:04:23,320
and what's your disk usage, what's the index health,

69
00:04:23,760 --> 00:04:26,080
all of these things, notification hooks and things like that.

70
00:04:26,600 --> 00:04:30,660
Yeah, the other part is, you know, it kind of just provides the base info layer

71
00:04:30,660 --> 00:04:32,000
if you're going to build other things on top,

72
00:04:32,060 --> 00:04:33,800
especially if you're going to have a lightning node on top,

73
00:04:33,840 --> 00:04:36,040
which needs to get all of that underlying chain data.

74
00:04:36,360 --> 00:04:39,080
Right. So then the next thing is the lightning node,

75
00:04:39,080 --> 00:04:43,020
and this really gives you, well, what some people would describe

76
00:04:43,020 --> 00:04:45,140
as the machine interface story.

77
00:04:45,360 --> 00:04:46,700
But it's another way of saying

78
00:04:46,700 --> 00:04:48,200
when you get a Lightning node,

79
00:04:48,260 --> 00:04:49,400
there's a lot of tools available

80
00:04:49,400 --> 00:04:50,620
for agent integration.

81
00:04:51,440 --> 00:04:51,780
Well, right.

82
00:04:51,860 --> 00:04:52,980
So, I mean, a lot of that has to do

83
00:04:52,980 --> 00:04:55,720
with just Lightning versus, like,

84
00:04:55,820 --> 00:04:57,600
base layer on chain Bitcoin, right?

85
00:04:57,700 --> 00:05:00,000
Like, there's a lot of programmability

86
00:05:00,000 --> 00:05:02,440
and ways you can interface with the chain,

87
00:05:02,500 --> 00:05:04,340
but that's the kind of primary thing

88
00:05:04,340 --> 00:05:05,460
you pay attention to is, like,

89
00:05:05,920 --> 00:05:07,540
you know, what new blocks got mined,

90
00:05:07,580 --> 00:05:08,440
what got added onto,

91
00:05:08,560 --> 00:05:10,040
what transactions did that come with?

92
00:05:10,040 --> 00:05:16,660
and lightning is a whole other beast of a layer two on top and kind of by its nature it right it

93
00:05:16,660 --> 00:05:22,900
has new and different things to pay attention to including invoices and liquidity and channels

94
00:05:22,900 --> 00:05:29,980
and it comes with a lot of state that isn't on a blockchain or at least is sort of you know not yet

95
00:05:29,980 --> 00:05:35,780
on the blockchain or only accounted for at sort of larger less granular levels and then you're

96
00:05:35,780 --> 00:05:40,660
going to need extra observability on top. And LND, and you can do it also with CoreLitning,

97
00:05:40,800 --> 00:05:46,460
they have something called a GRPC. What's a GRPC with? Yeah, so this is another format for doing

98
00:05:46,460 --> 00:05:51,240
remote procedure calls. And this is one that kind of developed out its protobuf at the base. It came

99
00:05:51,240 --> 00:05:55,860
out of a lot of stuff that Google had been doing for their own sort of internal calls. You'll also

100
00:05:55,860 --> 00:06:01,340
see a lot of REST APIs. You'll see things called mech runes, which are essentially just tokens you

101
00:06:01,340 --> 00:06:06,140
need security, you know, private key type credentials that allow you to authenticate

102
00:06:06,140 --> 00:06:06,760
to your node.

103
00:06:06,960 --> 00:06:07,460
And scope.

104
00:06:07,640 --> 00:06:12,480
So you can have macaroons that are scoped to certain permissions only, like read only

105
00:06:12,480 --> 00:06:14,840
permissions or only certain things on that node.

106
00:06:15,120 --> 00:06:15,340
Yeah.

107
00:06:15,400 --> 00:06:17,360
And that comes down to the individual demon.

108
00:06:17,360 --> 00:06:21,980
Like this is one area where if you run a core lightning node, by default, they don't

109
00:06:21,980 --> 00:06:24,780
have that kind of granularity built into their macaroon setup.

110
00:06:24,860 --> 00:06:29,540
But on LND, you get that out of the box and you can bake your own macaroons with custom

111
00:06:29,540 --> 00:06:31,320
access controls if you want.

112
00:06:31,340 --> 00:06:35,640
So that's where core lightning has the JSON RPC interface.

113
00:06:35,640 --> 00:06:43,460
And so what's done kind of more over there in that community is often like a proxy or some kind of control that only allows certain RPC commands to go through.

114
00:06:44,140 --> 00:06:45,040
All right. Have we lost you at all, Brent?

115
00:06:45,540 --> 00:06:52,200
Well, it seems to me like the distinction I can find here is that Bitcoin is like the super stable base that doesn't change very often.

116
00:06:52,200 --> 00:06:58,640
And then with lightning on top, there's a bunch of playing around going on there and just a lot of flexibility as well.

117
00:06:59,220 --> 00:06:59,400
Yeah.

118
00:06:59,400 --> 00:07:00,140
Do I get any of that right?

119
00:07:00,140 --> 00:07:00,480
You got it.

120
00:07:00,480 --> 00:07:05,280
And then they're both giving you a set of different APIs or remote procedure calls that you can use.

121
00:07:05,380 --> 00:07:13,180
And the reason why we're harping on this and kind of establishing this space is because this is what you're going to build on top of to manage your node going forward.

122
00:07:13,180 --> 00:07:23,360
And it makes sense to kind of get an idea of what that API surface is because, like, some of them are, you know, closing or opening channels, which commits your real on-chain Bitcoin to things.

123
00:07:23,480 --> 00:07:28,360
And some of them are just, like, getting some info in a JSON format that you can use to update a dashboard.

124
00:07:28,460 --> 00:07:29,900
And those are totally different implications.

125
00:07:30,480 --> 00:07:32,880
And if you have like LND right now, it's built in.

126
00:07:33,540 --> 00:07:35,480
And if you have Bitcoin D, it's built in.

127
00:07:35,900 --> 00:07:36,960
This RPC is already available.

128
00:07:37,020 --> 00:07:39,040
It might not be exposed to the network, but it's available.

129
00:07:39,700 --> 00:07:42,020
But let's clear up something before we go any further.

130
00:07:42,360 --> 00:07:45,200
Because you've mentioned a couple of times, I've mentioned it a couple of times.

131
00:07:45,340 --> 00:07:47,660
There's LND and there's Core Lightning.

132
00:07:48,000 --> 00:07:48,660
What's the difference?

133
00:07:48,660 --> 00:07:53,260
Yeah, well, they're both just different implementations of the Lightning network protocols.

134
00:07:53,580 --> 00:07:57,260
So they're, you know, kind of like with email or other systems, you can have different daemons

135
00:07:57,260 --> 00:07:58,860
that both speak the same protocol.

136
00:07:58,860 --> 00:08:01,300
On Bitcoin, we have Bitcoin Core and Nots.

137
00:08:01,340 --> 00:08:16,780
Exactly. Yeah. So that's the same thing here. So LND is a Go version and they've kind of like, it's like all in one. It's very comprehensive. It has support for like a lot of just like detailed APIs on a large surface area and does a lot of things well.

138
00:08:16,780 --> 00:08:23,040
core lightning the core part is kind of the key it's like really meant to just do the really like

139
00:08:23,040 --> 00:08:27,080
tight minimal essentials of what you need the really hard parts of like the actual network

140
00:08:27,080 --> 00:08:31,000
protocol and doing that safely and securely and you extend it with modules yeah and so it has like

141
00:08:31,000 --> 00:08:37,440
a plug-in system that you can just run any binary talks like standard io kind of style and so you

142
00:08:37,440 --> 00:08:41,080
can extend it with these plugins and that's actually where like how key send is implemented

143
00:08:41,080 --> 00:08:44,920
and even internally a lot of the features that you get out of the box are actually just

144
00:08:44,920 --> 00:08:49,180
modules or plugins of some kind of extensibility feature outside of the true core.

145
00:08:49,720 --> 00:08:54,040
So that enables some things to happen earlier, like they had Bolt 12 support pretty early

146
00:08:54,040 --> 00:08:54,840
on, that kind of stuff.

147
00:08:54,880 --> 00:08:56,960
So a lot of experimental things can get developed.

148
00:08:57,420 --> 00:08:58,080
Right, it's easier to add.

149
00:08:58,080 --> 00:09:05,300
Yes, but it can be a little more do-it-yourself or less out-of-the-box for a Node operator

150
00:09:05,300 --> 00:09:05,740
standpoint.

151
00:09:05,900 --> 00:09:11,260
Yeah, I will say, I think a lot of community how-tos and scripts and services kind of expect

152
00:09:11,260 --> 00:09:12,020
you to have LND.

153
00:09:12,920 --> 00:09:13,700
Yeah, yeah.

154
00:09:13,700 --> 00:09:15,840
compatibility is also not as good.

155
00:09:15,880 --> 00:09:19,980
For instance, like AlbiHub is not nearly as easy to get going on top of a core lightning

156
00:09:19,980 --> 00:09:21,440
node as it is with an L&D node.

157
00:09:21,700 --> 00:09:23,480
Let's talk about AlbiHub because that's one more wrinkle.

158
00:09:23,880 --> 00:09:25,760
And then I think we've got the groundwork laid here.

159
00:09:26,460 --> 00:09:31,440
AlbiHub is software that you can install that includes its own lightning node, or you can

160
00:09:31,440 --> 00:09:33,820
run it on top of your existing lightning node.

161
00:09:34,200 --> 00:09:38,320
Or one more or, there is the AlbiHub cloud product.

162
00:09:38,840 --> 00:09:43,000
That's the least flexible, but probably the most appliance like is AlbiHub cloud.

163
00:09:43,700 --> 00:09:48,980
And then the next would be the entire AlbiHub package that includes its own Lightning configuration and daemon.

164
00:09:49,220 --> 00:09:55,280
Yeah, it uses a thing called the Lightning Development Kit or LDK, which it's saying contains a bunch of the base primitives.

165
00:09:55,280 --> 00:09:59,160
And then AlbiHub wraps that so it can be its own node using that library built in.

166
00:09:59,420 --> 00:10:03,020
Or it can talk to a bunch of different node backends, including LND.

167
00:10:03,320 --> 00:10:07,240
Or it can even talk to another node sort of backend with Nostra Wallet Connect.

168
00:10:07,240 --> 00:10:14,660
And some of the fun stuff we're going to get into later does kind of require that you're on L&D or Core Lightning and not using their built-in Lightning.

169
00:10:15,260 --> 00:10:15,740
Some of it.

170
00:10:16,260 --> 00:10:17,020
Let's talk about some of the stuff.

171
00:10:17,020 --> 00:10:18,740
What, you're saying self-hosting is more fun?

172
00:10:18,840 --> 00:10:19,860
What are you talking about?

173
00:10:20,220 --> 00:10:27,640
Well, even depending on no matter what version of AlbiHub, if you have AlbiHub, you are already kind of set up with Nostr Wallet Connect.

174
00:10:28,000 --> 00:10:30,000
And that's very powerful just on its own.

175
00:10:30,360 --> 00:10:36,140
It's a standard way for apps and services to talk to Lightning Wallet, to your Lightning Wallet, over Nostr.

176
00:10:36,780 --> 00:10:38,800
And it's pretty simple.

177
00:10:38,940 --> 00:10:40,980
You're seeing more and more adoption in different applications.

178
00:10:41,280 --> 00:10:43,760
Fountain recently shipped it, so you can use Fountain's built-in wallet,

179
00:10:43,820 --> 00:10:46,780
or you can connect it to your AlbiHub wallet using Nostra Wallet Connect.

180
00:10:47,640 --> 00:10:52,860
And a lot of the apps that ship today give you permissions to make a payment,

181
00:10:53,440 --> 00:10:56,400
receive a payment, and they let you set strict budgets

182
00:10:56,400 --> 00:10:59,480
and have scoped permissions as part of the Nostra Wallet Connect protocol,

183
00:10:59,580 --> 00:11:00,480
or I guess spec.

184
00:11:00,720 --> 00:11:04,760
Yeah, and the basic idea, right, is it provides a way for you to encrypt

185
00:11:04,760 --> 00:11:07,420
and then can send encrypted commands

186
00:11:07,420 --> 00:11:10,840
and get results back over Nostra relays

187
00:11:10,840 --> 00:11:11,760
to talk to your nodes.

188
00:11:11,840 --> 00:11:14,040
So you can have an app or an interface of some kind

189
00:11:14,040 --> 00:11:15,580
on whatever machine you're on

190
00:11:15,580 --> 00:11:16,940
and your node's somewhere else.

191
00:11:17,040 --> 00:11:18,520
And instead of having to make a direct connection

192
00:11:18,520 --> 00:11:19,740
or do a direct API call,

193
00:11:20,260 --> 00:11:22,200
you will let the Nostra network take care of it.

194
00:11:22,540 --> 00:11:24,480
And really, honestly, that might be all you need

195
00:11:24,480 --> 00:11:26,540
because there are command line interfaces

196
00:11:26,540 --> 00:11:28,460
and MCPs that Albi makes available

197
00:11:28,460 --> 00:11:30,640
and an agent can interact with that.

198
00:11:30,840 --> 00:11:32,780
And if you just want to do basic payments

199
00:11:32,780 --> 00:11:34,360
and check balances and set budgets,

200
00:11:34,760 --> 00:11:38,580
You might be set with just AlbiHub and NostraWallet Connect and a CLI.

201
00:11:38,840 --> 00:11:45,080
Yeah, so you get get info, get balance, make invoice, pay invoice, multi-pay invoice, pay

202
00:11:45,080 --> 00:11:50,020
keysend, lookup invoice, and list transactions, at least in the base sort of NostraWallet

203
00:11:50,020 --> 00:11:51,460
Connect API surface.

204
00:11:51,880 --> 00:11:57,220
That's where maybe if you want to do fancier stuff in terms of like complicated node management

205
00:11:57,220 --> 00:12:01,080
and liquidity management and rebalancing, that won't be sufficient.

206
00:12:01,080 --> 00:12:06,840
But for a lot of the day-to-day stuff, maybe even a lot of automations or agent stuff, that's a pretty decent interface.

207
00:12:07,340 --> 00:12:09,140
So what we've got here, you've got Bitcoin Core.

208
00:12:09,400 --> 00:12:14,340
Then you've got Lightning with a couple of different implementation options, including AlbiHub in there.

209
00:12:14,480 --> 00:12:21,600
And then you've got the APIs that these different services provide that have always been there, but perhaps you've never really been using them.

210
00:12:21,880 --> 00:12:30,480
And now there's tooling that makes them extremely powerful and makes things that maybe were too complicated or took too much time to set up very straightforward.

211
00:12:30,480 --> 00:12:32,600
So that's the foundation you need to understand.

212
00:12:32,960 --> 00:12:35,600
And now here's how you can start to take advantage of them.

213
00:12:42,840 --> 00:12:46,020
Let's start with the low-hanging fruit right here.

214
00:12:46,280 --> 00:12:48,920
You could just use OpenCode.

215
00:12:49,440 --> 00:12:51,520
Learn to love OpenCode.

216
00:12:51,740 --> 00:12:56,100
And it is one of the biggest practical unlocks for node operations.

217
00:12:56,100 --> 00:13:00,920
You can install it locally on your workstation and point it at configs and scripts.

218
00:13:01,060 --> 00:13:10,920
You can have it SSH into your remote node and put it in plan mode at first, have it learn the system, then come back and propose changes before it touches anything.

219
00:13:11,340 --> 00:13:14,040
And we did this with a couple of nodes.

220
00:13:14,680 --> 00:13:18,380
Brent's had a very old Umbral node from the very early days of Umbral.

221
00:13:18,380 --> 00:13:19,340
Yeah, years ago.

222
00:13:19,620 --> 00:13:20,360
On a VPS.

223
00:13:21,880 --> 00:13:22,540
Worst case.

224
00:13:22,540 --> 00:13:24,440
It kind of broke at one point.

225
00:13:24,540 --> 00:13:26,340
We said, oh, we got to get around to fixing that.

226
00:13:26,440 --> 00:13:29,660
And then every time I would visit, we'd say, oh, we should probably get around to fixing that.

227
00:13:29,740 --> 00:13:31,040
And then a couple of years went by.

228
00:13:31,640 --> 00:13:32,900
But you guys fixed it recently.

229
00:13:33,160 --> 00:13:33,260
Yeah.

230
00:13:33,340 --> 00:13:37,560
So we ended up, we had the VPS and we thought, oh, we'll also run IPFS on this thing.

231
00:13:38,100 --> 00:13:38,180
Yeah.

232
00:13:38,300 --> 00:13:42,060
Port conflicts happened, took down the lightning node and just messed things up.

233
00:13:42,060 --> 00:13:43,620
But we wanted to get those channels back up.

234
00:13:43,980 --> 00:13:54,644
And so in you know probably 15 minutes OpenCode was able to assess the problem disable the right services restart things and then continually monitor the Lightning server and make sure things were coming back up

235
00:13:54,664 --> 00:13:56,784
And it noticed, oh, your VPS is running out of RAM.

236
00:13:56,844 --> 00:13:57,844
We can make these adjustments.

237
00:13:58,544 --> 00:13:59,604
It's really great like that.

238
00:13:59,984 --> 00:14:01,564
We also had an Umbral script

239
00:14:01,564 --> 00:14:03,444
that was broken on an old install,

240
00:14:03,744 --> 00:14:05,064
and it recovered that.

241
00:14:05,584 --> 00:14:07,904
It's also really fantastic at verifying

242
00:14:07,904 --> 00:14:09,784
if you're waiting for your services to start.

243
00:14:09,844 --> 00:14:11,304
You don't know, is Lightning starting or not?

244
00:14:11,324 --> 00:14:12,704
It can go in and knows where to check

245
00:14:12,704 --> 00:14:14,844
and tell you what's going on.

246
00:14:14,964 --> 00:14:16,884
Open code can be a fantastic tool

247
00:14:16,884 --> 00:14:19,024
that can take advantage of not only things on the file system,

248
00:14:19,104 --> 00:14:19,924
but also these APIs.

249
00:14:20,404 --> 00:14:22,584
Yeah, I mean, you can get into like finer grained work,

250
00:14:22,664 --> 00:14:23,604
but even just as a default,

251
00:14:23,704 --> 00:14:24,344
and you should be careful

252
00:14:24,344 --> 00:14:25,904
and we can get into the safety part of this.

253
00:14:26,384 --> 00:14:28,424
But, right, like even just the base commands,

254
00:14:28,524 --> 00:14:31,304
you run like a get info command on your lightning node,

255
00:14:31,464 --> 00:14:34,444
that often spits out like a JSON blob

256
00:14:34,444 --> 00:14:36,124
that it's not hard for the human to read,

257
00:14:36,184 --> 00:14:37,784
but it's not really what we're best at.

258
00:14:37,844 --> 00:14:39,904
And it is what these things are best at, you know?

259
00:14:40,204 --> 00:14:42,444
And so it can present that in a nice little table for you

260
00:14:42,444 --> 00:14:43,104
to check out.

261
00:14:43,184 --> 00:14:44,024
It can call out things

262
00:14:44,024 --> 00:14:45,204
that might look like an error.

263
00:14:45,644 --> 00:14:46,764
Or yeah, just report on the status

264
00:14:46,764 --> 00:14:47,264
of like, nope,

265
00:14:47,284 --> 00:14:48,284
we're still waiting to catch up

266
00:14:48,284 --> 00:14:48,784
with the blockchain.

267
00:14:48,984 --> 00:14:49,944
Yeah, you're at block height this.

268
00:14:50,244 --> 00:14:51,744
And by, like one of the things I love

269
00:14:51,744 --> 00:14:52,804
is you're at this block height

270
00:14:52,804 --> 00:14:54,064
and by observing so far,

271
00:14:54,104 --> 00:14:55,404
I estimate it'll be another half hour

272
00:14:55,404 --> 00:14:56,244
before sync is completed.

273
00:14:56,884 --> 00:14:57,864
Yeah, that kind of stuff.

274
00:14:58,424 --> 00:15:00,084
But let's touch on safety

275
00:15:00,084 --> 00:15:02,624
because you do need to be careful.

276
00:15:03,284 --> 00:15:04,264
There's plan mode.

277
00:15:04,344 --> 00:15:04,944
It is helpful.

278
00:15:05,324 --> 00:15:06,744
It's permissions that really matter.

279
00:15:06,904 --> 00:15:08,384
So if the agent is logging in,

280
00:15:08,464 --> 00:15:09,564
it's logging in with whatever

281
00:15:09,564 --> 00:15:11,164
that user has access to,

282
00:15:11,164 --> 00:15:13,144
whatever wallet that user has access to.

283
00:15:13,364 --> 00:15:14,864
You need to be really careful there.

284
00:15:15,524 --> 00:15:18,584
And that's where something like you were trying to play with

285
00:15:18,584 --> 00:15:23,024
is writing some sort of pre-made agent scripts and wrappers

286
00:15:23,024 --> 00:15:26,584
that you can supply with like their own Macaroon style

287
00:15:26,584 --> 00:15:29,084
or like whatever auth, password, et cetera,

288
00:15:29,464 --> 00:15:30,964
stuff that is injected in there.

289
00:15:31,044 --> 00:15:33,624
And then they can just, they just have access to that.

290
00:15:34,184 --> 00:15:34,564
Yeah, exactly.

291
00:15:34,704 --> 00:15:36,664
So we could talk more about Bolts in a minute,

292
00:15:36,664 --> 00:15:45,224
But my LNCLI and bolts commands are wrapped exactly like you say with just certain protections in there and they're designed.

293
00:15:45,384 --> 00:15:52,904
So there's like bolts and then each each lightning node has a bolts dash host name and that is scoped only to that host with only those commands.

294
00:15:53,264 --> 00:15:58,604
And that way there's less work or speculation and agent or a tool like open code has to do.

295
00:15:58,864 --> 00:16:03,244
And then especially with LND, like you can give them some of them could just have the read only macaroon.

296
00:16:03,244 --> 00:16:10,004
Some could have the full commands, maybe gated with special instructions that require more of your, you know, input or authorization.

297
00:16:10,724 --> 00:16:13,104
And you can, like, make a custom one if you needed to.

298
00:16:13,184 --> 00:16:15,104
So it could only do a couple of changing commands.

299
00:16:15,204 --> 00:16:17,124
Like, you can make payments, but not X.

300
00:16:17,804 --> 00:16:28,904
And sticking with the repair and using open code thing for one moment, too, I will just say, before you have it move out of plan mode into build mode, ask it to create a spec.md and review that with your human eyeballs before it works.

301
00:16:29,224 --> 00:16:31,044
And make sure that's, you know, what you want done.

302
00:16:31,044 --> 00:16:38,684
You know, and really, I mean, I think both you and I, including with Brent, have had nodes kind of repaired or rescued with this.

303
00:16:38,984 --> 00:16:42,964
Yeah, I think three is the count. Two that were significantly down for the count.

304
00:16:43,464 --> 00:16:48,564
I specifically remember rescuing nodes with you, Chris, before, you know, these agent times.

305
00:16:48,564 --> 00:16:51,084
Yeah, back when we were first learning Umbral.

306
00:16:51,344 --> 00:16:59,124
It was one of your most hated mornings when you would come into the studio and sit down and be like, oh, the node went down.

307
00:16:59,124 --> 00:16:59,444
Okay.

308
00:17:00,164 --> 00:17:04,344
I got to set aside three hours to try to dive into this and figure out what's going on.

309
00:17:04,504 --> 00:17:07,144
And you would, you'd figure it out, which is great.

310
00:17:07,304 --> 00:17:11,864
But 15 minutes versus three hours, I think we've advanced.

311
00:17:12,204 --> 00:17:12,824
I know, I know.

312
00:17:12,904 --> 00:17:15,044
It really is so much better now.

313
00:17:15,164 --> 00:17:16,304
The tooling is so much better.

314
00:17:16,644 --> 00:17:20,144
I had an issue where I was trying to plug in that was doing some automated fee management

315
00:17:20,144 --> 00:17:20,744
for my node.

316
00:17:21,224 --> 00:17:24,724
But as part of that, it was occasionally opening channels that thought would help my network

317
00:17:24,724 --> 00:17:26,044
like reachability and stuff.

318
00:17:26,044 --> 00:17:30,224
but it kind of ran into an issue where it tried to open some channels but like the fee rate was

319
00:17:30,224 --> 00:17:34,244
too low so they're never going to actually open and then it kind of got into a loop where it just

320
00:17:34,244 --> 00:17:39,704
kept doing that so i had several hundred like phantom channels that were never going to open

321
00:17:39,704 --> 00:17:45,144
yeah yeah and so these kinds of automation tools were super useful and exactly like i could draft

322
00:17:45,144 --> 00:17:49,544
a plan with the exact specific ids so i could make sure i was like not going to touch channels i knew

323
00:17:49,544 --> 00:17:53,764
i still wanted to keep or anything like that very helpful do you recall did you use open code to

324
00:17:53,764 --> 00:17:57,684
take care of that? No, I think this was a little before I was into open code, but I used

325
00:17:57,684 --> 00:18:03,764
some crush and yeah, I think it was well said crush. Yeah. It's so if you take nothing else

326
00:18:03,764 --> 00:18:09,944
from this, like just use what we've talked about so far with open code. However, really the thing

327
00:18:09,944 --> 00:18:14,804
I think would be ideal is to automate this a level further to make this even smoother.

328
00:18:14,804 --> 00:18:18,084
It is 2026. It is the year of the Asians after all.

329
00:18:23,764 --> 00:18:37,344
Now, I suppose we'll really be talking in the context of open claw,

330
00:18:37,444 --> 00:18:40,744
but this would really work with just about any kind of agent,

331
00:18:40,904 --> 00:18:43,044
from the clods to the whatevers.

332
00:18:43,584 --> 00:18:46,104
And it's stacking everything we've talked about

333
00:18:46,104 --> 00:18:48,924
and really turning it into something that's effective for you,

334
00:18:48,924 --> 00:18:50,464
that gives you actionable information,

335
00:18:50,464 --> 00:18:54,524
and maybe even helps you save sats off of your node.

336
00:18:54,684 --> 00:18:55,564
You know, because that's one thing,

337
00:18:55,604 --> 00:18:57,084
I think if you have a Lightning node, you're using it,

338
00:18:57,644 --> 00:18:59,604
you can sometimes collect some sats on there.

339
00:18:59,684 --> 00:19:00,584
It can sit there for too long.

340
00:19:00,644 --> 00:19:01,644
You know it's a hot wallet.

341
00:19:01,764 --> 00:19:03,204
You know you should be getting them off there,

342
00:19:03,284 --> 00:19:04,184
but it takes time.

343
00:19:04,344 --> 00:19:04,944
That's my wallet.

344
00:19:05,384 --> 00:19:06,604
Yeah, yeah, yeah.

345
00:19:07,204 --> 00:19:07,904
Yeah, mine too.

346
00:19:07,964 --> 00:19:09,004
So that's something I wanted to fix.

347
00:19:09,244 --> 00:19:10,744
This is really an intervention episode.

348
00:19:11,224 --> 00:19:12,044
Right, yeah.

349
00:19:12,184 --> 00:19:12,984
I feel called out.

350
00:19:13,404 --> 00:19:13,664
Yeah.

351
00:19:14,164 --> 00:19:17,784
So there's two areas, really, that I wanted to address,

352
00:19:17,784 --> 00:19:19,504
and that was, I guess, three.

353
00:19:19,504 --> 00:19:24,504
I wanted to be able to check the balance of my node from my agent.

354
00:19:24,724 --> 00:19:31,984
I wanted to be able to send a quick payment and I wanted to be able to swap or sweep sats

355
00:19:31,984 --> 00:19:36,144
that are sitting on my node in my hot wallet to a liquid wallet, because that's sort of

356
00:19:36,144 --> 00:19:38,124
my intermediary step before I go to cold storage.

357
00:19:38,784 --> 00:19:42,864
And a lot of this is relying on these APIs we just talked about.

358
00:19:42,964 --> 00:19:48,764
And then one more quintessential killer piece of software that we all love.

359
00:19:48,764 --> 00:19:54,384
we've talked about it before bolts and but not in the way you're used to using it so before before

360
00:19:54,384 --> 00:20:01,404
we go any further quick explainer of what bolts is bolts is a non-custodial swap service that lets

361
00:20:01,404 --> 00:20:07,184
you move between a bitcoin layer to like a lightning or liquid layer or in between any of those without

362
00:20:07,184 --> 00:20:11,504
having to give up your custody it's a clean way to move sats between lightning or on-chain or liquid

363
00:20:11,504 --> 00:20:16,664
when maybe your node needs a little rebalancing so you can use it in the context of your node too

364
00:20:16,664 --> 00:20:25,484
Yeah. You know, for us, it's often an issue kind of depending on how you run your node. Like if you're a merchant, it's going to be one issue. If you're trying to run a routing node, it's another target.

365
00:20:25,784 --> 00:20:27,164
You're just trying to zap or something.

366
00:20:27,364 --> 00:20:31,944
Right. And for us, you know, we often get stuff sent to us very generously from the boost.

367
00:20:31,964 --> 00:20:32,444
A boost.

368
00:20:32,584 --> 00:20:38,804
And so we often need to then rebalance to push sats back out. So we maintain enough liquidity to receive new boosts.

369
00:20:38,824 --> 00:20:41,444
Right. And they need to have sending liquidity and all that.

370
00:20:41,444 --> 00:20:44,144
And so Bolt is one service that's been really helpful to do that.

371
00:20:44,264 --> 00:20:48,264
And one of the mechanisms they offer is what's called a reverse submarine swap.

372
00:20:49,144 --> 00:20:51,664
And it's actually kind of really neat and clever.

373
00:20:51,844 --> 00:20:55,784
And the kind of high-level version is you on your end generate a pre-image.

374
00:20:55,924 --> 00:20:57,204
It's like a random value.

375
00:20:57,344 --> 00:20:59,664
And then you hash that and you send that to Bolt.

376
00:20:59,784 --> 00:21:02,444
And then it creates the swap sort of based around that.

377
00:21:02,804 --> 00:21:06,844
So it's first able to make a special kind of lightning invoice called a hold invoice,

378
00:21:06,844 --> 00:21:12,904
which when you pay it it doesn't actually like fully lock your sats kind of in an intermediate

379
00:21:12,904 --> 00:21:17,944
htlc state because it's waiting for like the actual reveal of the pre-image before it does

380
00:21:17,944 --> 00:21:22,344
anything so you kind of like stash your sats there but in a way that you can recover them

381
00:21:22,344 --> 00:21:28,244
and then once bolt sees you've done that first step it'll make a corresponding sort of staged

382
00:21:28,244 --> 00:21:33,604
contract on whatever base chain you're using so could be on chain or in our case usually liquid

383
00:21:33,604 --> 00:21:40,504
but that's also waiting for a pre-image and so the way it works is once that's done and you see

384
00:21:40,504 --> 00:21:46,124
that that is locked up temporarily and then you can finally reveal the pre-image which lets you

385
00:21:46,124 --> 00:21:52,544
claim the liquid the liquid sent to whatever wallet id you put in at the start and then because

386
00:21:52,544 --> 00:21:59,204
you had to reveal on the liquid chain the pre-image to get it back for yourself that lets bolts then

387
00:21:59,204 --> 00:22:04,544
claim that Lightning transaction and then they get paid out. And so at no time are you at risk

388
00:22:04,544 --> 00:22:09,384
of like actually losing the custody. But at the end, you get to execute this whole smart contract

389
00:22:09,384 --> 00:22:14,204
sort of transaction cross chain stuff that will ultimately do the swap for you. And it's super

390
00:22:14,204 --> 00:22:19,224
powerful because not only can you use it to say, take hot sats off of a hot wallet, but you could

391
00:22:19,224 --> 00:22:25,124
use it maybe to balance liquidity in a channel. You can have a liquid wallet running on the node

392
00:22:25,124 --> 00:22:29,944
because Bolt offers four nodes, Bolt D and Bolt CLI.

393
00:22:30,064 --> 00:22:31,304
And this is something you install.

394
00:22:31,644 --> 00:22:35,184
Some packages for Umbral and Start9 include Boltz with them,

395
00:22:35,524 --> 00:22:38,124
but it's a command line tool you can install on your workstation

396
00:22:38,124 --> 00:22:40,644
and it's a command line tool you can install on your server

397
00:22:40,644 --> 00:22:42,884
as well as a daemon that will run.

398
00:22:43,004 --> 00:22:45,484
And it talks to Lightning and it also creates its own API.

399
00:22:45,964 --> 00:22:46,524
Yeah, exactly.

400
00:22:46,744 --> 00:22:49,324
So Bolt D runs, it talks to your Lightning server

401
00:22:49,324 --> 00:22:52,404
and it supports both LND and Core Lightning.

402
00:22:53,064 --> 00:22:54,964
Boltz actually run both of those on their network.

403
00:22:55,124 --> 00:22:55,784
which is pretty great.

404
00:22:56,364 --> 00:22:57,104
And then on top,

405
00:22:57,144 --> 00:22:58,364
so Bolt2D has its own API.

406
00:22:58,504 --> 00:22:59,544
You can call from your own tools

407
00:22:59,544 --> 00:23:00,264
to interact with it

408
00:23:00,264 --> 00:23:01,304
or it comes with

409
00:23:01,304 --> 00:23:03,404
the Bolt's client CLI tool,

410
00:23:03,524 --> 00:23:05,044
which will just do that for you.

411
00:23:05,044 --> 00:23:05,224
Yeah.

412
00:23:05,564 --> 00:23:06,384
Which is pretty handy.

413
00:23:06,504 --> 00:23:07,724
And then what's nice about Bolt2D

414
00:23:07,724 --> 00:23:09,084
is like that little,

415
00:23:09,204 --> 00:23:10,264
like, you know,

416
00:23:10,344 --> 00:23:11,624
state machine we just walked through.

417
00:23:11,844 --> 00:23:12,764
It's kind of a lot.

418
00:23:12,864 --> 00:23:13,304
Like if you go,

419
00:23:13,404 --> 00:23:14,184
you can do it.

420
00:23:14,224 --> 00:23:15,224
They provide SDKs

421
00:23:15,224 --> 00:23:16,484
if you want to do it programmatically

422
00:23:16,484 --> 00:23:17,384
in your own client.

423
00:23:17,824 --> 00:23:19,084
But like there's some crypto stuff

424
00:23:19,084 --> 00:23:19,624
to get right

425
00:23:19,624 --> 00:23:20,964
and like make sure you do the right order

426
00:23:20,964 --> 00:23:22,324
and account for possible failures.

427
00:23:22,524 --> 00:23:24,244
So Bolt2D kind of wraps that

428
00:23:24,244 --> 00:23:25,664
into a more manageable interface.

429
00:23:26,564 --> 00:23:29,764
And this is really where it gets great in 2026

430
00:23:29,764 --> 00:23:32,144
because Lightning's no longer this thing

431
00:23:32,144 --> 00:23:33,964
that you have to have in a particular app

432
00:23:33,964 --> 00:23:35,064
or in a web page.

433
00:23:35,244 --> 00:23:37,764
Your agent can now inspect your node.

434
00:23:37,984 --> 00:23:39,844
It can pay for an invoice.

435
00:23:40,004 --> 00:23:41,764
It can swap liquidity around.

436
00:23:41,884 --> 00:23:44,784
It can sweep sats to your Lightning wallet.

437
00:23:44,884 --> 00:23:48,304
And the killer combo here is Bolt D and Bolt CLI

438
00:23:48,304 --> 00:23:50,884
with a skill that your agent follows

439
00:23:50,884 --> 00:23:52,664
to interact with it appropriately.

440
00:23:52,664 --> 00:24:03,104
and it works so today i have moved about 250 000 sats from my primary node to my liquid wallet

441
00:24:03,104 --> 00:24:07,844
just through telegram by prompting my agent that's so great and right so the idea here is you

442
00:24:07,844 --> 00:24:12,144
you like sort of pre-put in here's like the address i want you to send it to you which is

443
00:24:12,144 --> 00:24:16,964
a liquid wallet you control so when i tell i i made it really simple so i say sweep five i say

444
00:24:16,964 --> 00:24:23,024
sweep 50,000 sats to liquid. And if I don't supply a wallet, it comes back and it asks me for the

445
00:24:23,024 --> 00:24:26,964
wallet address. And then when I give it the wallet address, it gives me all. Well, before it asked,

446
00:24:27,044 --> 00:24:31,444
before it, before it asked for the wallet address, when I just say sweep 50,000 sats to liquid,

447
00:24:31,684 --> 00:24:36,204
it comes back with a fee estimate. Here's what it's going to cost. Here's the bolts fee. Here's

448
00:24:36,204 --> 00:24:40,504
all of that. So you'll get exactly this amount in your liquid wallet. If you're ready, send me the

449
00:24:40,504 --> 00:24:44,124
address and say yes or whatever. And I, so I give it the address and then it does it all in the

450
00:24:44,124 --> 00:24:48,364
backend, follows the skill that I created, which I will publish in the show notes.

451
00:24:49,024 --> 00:24:50,244
And then it does the swap.

452
00:24:50,364 --> 00:24:55,564
So the skill is about 80, well, probably about 60, 70% complete.

453
00:24:55,824 --> 00:25:00,304
But if people would like to take it and work with it, so far I've managed to make sure

454
00:25:00,304 --> 00:25:01,584
I can inspect the channels.

455
00:25:01,984 --> 00:25:07,564
I can get my entire node balance on chain and lightning, and I can do the sats to liquid

456
00:25:07,564 --> 00:25:08,104
sweep.

457
00:25:08,484 --> 00:25:10,084
And it all works fantastically.

458
00:25:10,524 --> 00:25:15,064
And there's other things, obviously, I want to do inevitably with that, but that's a pretty good start.

459
00:25:15,224 --> 00:25:22,704
If you just want to be able to check on your node through an agent, and this is, I'm using OpenClaw, but it would work with OpenCode, it would work with Clawed, any agent.

460
00:25:23,044 --> 00:25:26,544
I have a question here about security practices, I guess.

461
00:25:26,704 --> 00:25:32,364
You guys are always saying, you know, don't throw your API keys into a bunch of your prompts.

462
00:25:32,364 --> 00:25:38,724
how does it feel about putting all it, you know, node addresses and things like that into some of

463
00:25:38,724 --> 00:25:43,204
these prompts and letting these agents go wild? Yeah, I mean, you should definitely think about

464
00:25:43,204 --> 00:25:47,624
what, you know, what you're going to put on there, what you're going to let it access and control

465
00:25:47,624 --> 00:25:52,764
and what provider you're sending it to. Yeah, there's that. And I suppose if you're really

466
00:25:52,764 --> 00:25:58,524
paranoid about this, Venice AI offers a lot of good solutions, but, and so does Paper, what was it?

467
00:25:58,524 --> 00:25:59,464
pay per query.

468
00:25:59,704 --> 00:26:00,104
Oh, yeah.

469
00:26:00,204 --> 00:26:00,884
That also offers

470
00:26:00,884 --> 00:26:01,604
some privacy there.

471
00:26:02,144 --> 00:26:02,864
The only thing that's

472
00:26:02,864 --> 00:26:03,804
really getting exposed

473
00:26:03,804 --> 00:26:04,624
in this process

474
00:26:04,624 --> 00:26:05,684
is the public

475
00:26:05,684 --> 00:26:07,324
liquid receive wallet address.

476
00:26:08,124 --> 00:26:08,364
Otherwise,

477
00:26:08,604 --> 00:26:09,424
all of the credentials,

478
00:26:09,564 --> 00:26:10,264
all of that stuff's

479
00:26:10,264 --> 00:26:12,164
not in what I'm prompting

480
00:26:12,164 --> 00:26:13,944
to my agent in this case.

481
00:26:14,124 --> 00:26:14,264
Yeah.

482
00:26:14,344 --> 00:26:14,984
Now, there would be more

483
00:26:14,984 --> 00:26:15,604
like when you get

484
00:26:15,604 --> 00:26:17,104
a channel status or whatever,

485
00:26:17,204 --> 00:26:17,944
but a lot of that

486
00:26:17,944 --> 00:26:18,724
ends up being scraped

487
00:26:18,724 --> 00:26:19,464
and sort of revealed

488
00:26:19,464 --> 00:26:20,044
on the network

489
00:26:20,044 --> 00:26:21,084
so the discovery tools.

490
00:26:21,264 --> 00:26:22,304
Yeah, like it'll give me

491
00:26:22,304 --> 00:26:23,304
channel ID information

492
00:26:23,304 --> 00:26:23,724
in the prompt,

493
00:26:23,804 --> 00:26:24,424
but that you could just

494
00:26:24,424 --> 00:26:25,304
get off of Amboss.

495
00:26:25,664 --> 00:26:26,964
So it's not that bad.

496
00:26:27,624 --> 00:26:28,184
And that is also

497
00:26:28,184 --> 00:26:32,364
being able to just see the status of my channels which where they're at where if it's on the send

498
00:26:32,364 --> 00:26:37,424
or receive side extremely useful and then if you have a if you have multiple nodes you're managing

499
00:26:37,424 --> 00:26:42,964
like i do it really is a force multiplier and then you combine that with the capability of bolts

500
00:26:42,964 --> 00:26:49,304
and there's also lncli which i've also wrapped it really it really is a powerful agent combination

501
00:26:49,304 --> 00:26:53,684
there's also actually we were talking about lb but separately they just make a lot of great tools

502
00:26:53,684 --> 00:27:00,324
along with albiub itself yeah and so they have made a pair of tools a cli and an mcp server

503
00:27:00,324 --> 00:27:08,244
for basically being able to talk nostril wallet connect to to node so if you don't want to sort

504
00:27:08,244 --> 00:27:12,724
of like do a direct wrapper but you do want your agent to be able to use nostril wallet connect you

505
00:27:12,724 --> 00:27:17,904
can use the albi nostril wallet connect cli for instance as like an easy way for the agent to be

506
00:27:17,904 --> 00:27:21,924
able to do that but without you having to do a lot of the plumbing uh-huh yeah that is really

507
00:27:21,924 --> 00:27:23,584
See, yeah, we should link to it.

508
00:27:23,584 --> 00:27:24,564
We'll put links in the show notes

509
00:27:24,564 --> 00:27:26,904
because they do have some really good stuff.

510
00:27:26,904 --> 00:27:30,264
So the real unlock though for me this week

511
00:27:30,264 --> 00:27:32,964
was the sweep to my liquid wallet.

512
00:27:32,964 --> 00:27:44,368
Just something that I can you know something that not a huge deal but it is so nice to just have it done Well it kind of changes the task right Before it was it felt like a serious task you wanted to do seriously Yeah so you have to think about it So you be like let me go to the node

513
00:27:44,568 --> 00:27:48,508
I will assess the state of the channels in liquidity, come up with my own plan to then

514
00:27:48,508 --> 00:27:50,048
go try to pull some sets off of here.

515
00:27:50,488 --> 00:27:55,708
And now you can have like a whole other pair of eyes who can pull fresh info from the node

516
00:27:55,708 --> 00:27:57,948
and help you do it and second guess what you're doing.

517
00:27:57,948 --> 00:28:15,628
And in some ways, having it done programmatically where you're, you know, the addresses of the wallet you want to go to are hard, well, soft coded in, in this case, but like better than the human who hasn't slept, you know, for four nights or whatever. So in some ways, it might be more reliable than you doing it manually.

518
00:28:15,628 --> 00:28:26,948
Well, especially because like the flow I've done often, right, is especially like it's between my phone and the computer and I'm copying like exact IDs that need to be exact to get the money to send to the right place.

519
00:28:27,088 --> 00:28:28,968
Right. So it's not really the kind of thing you want to screw up.

520
00:28:29,108 --> 00:28:35,648
And you know what I can do now, too, when I said one of the times I tried to sweep to liquid, it didn't work because I didn't have enough outbound liquidity.

521
00:28:35,948 --> 00:28:38,208
And now I can say, why did that fail?

522
00:28:38,568 --> 00:28:41,208
And the agent figures out, well, this channel didn't.

523
00:28:41,348 --> 00:28:43,388
But you might be able to send it out this channel if you pin it.

524
00:28:43,388 --> 00:28:48,228
And, you know, it comes back with recommendations and actionable suggestions on how to actually get that payment out.

525
00:28:48,468 --> 00:28:50,568
So I can actually say, so why did the payment fail?

526
00:28:50,588 --> 00:28:54,528
And actually get information without having to dig through logs and all of that.

527
00:28:54,968 --> 00:28:55,988
It's great.

528
00:29:06,768 --> 00:29:08,528
You need to keep an eye on things, though.

529
00:29:08,568 --> 00:29:10,368
You need to monitor that stack.

530
00:29:10,368 --> 00:29:15,568
And like we've been mentioning, these APIs, they give you the ability to do just that.

531
00:29:15,668 --> 00:29:23,208
Bitcoin D, LND, Core Lightning, they all offer the ability to monitor them and expose metrics.

532
00:29:23,788 --> 00:29:27,248
And one of them, one of the ways you can do this is through Prometheus.

533
00:29:27,668 --> 00:29:32,488
Yeah, I mean, it's really become, of course, pretty much a metrics standard out there.

534
00:29:32,488 --> 00:29:41,088
Even if you don't use Prometheus itself as a tool, all kinds of different telemetry options, both on the client and the server side, support it.

535
00:29:41,548 --> 00:29:44,768
So like there's Bitcoin Prometheus exporter for Bitcoin D.

536
00:29:45,108 --> 00:29:49,568
And a lot of these even come with, say, a starter Grafana dashboard you can use in conjunction.

537
00:29:50,468 --> 00:29:59,948
And LND has LND Mon, which is a side project that is still a really easy way to get information from your LND node that you want to monitor.

538
00:29:59,948 --> 00:30:05,008
you can see things like invoice flow, channel health, forwarding behavior, peer status, how

539
00:30:05,008 --> 00:30:09,288
the RPC is doing. And that's what's also really good if you want to make sure your agent can talk

540
00:30:09,288 --> 00:30:13,108
to it. Yeah, right. That's how a lot of these tools end up working is like they will go make

541
00:30:13,108 --> 00:30:17,808
the calls, like the limited set of calls to go just collect data and expose that in the Prometheus

542
00:30:17,808 --> 00:30:23,168
metrics format. And it is really, really straightforward to task the agent to build a

543
00:30:23,168 --> 00:30:28,128
Prometheus scrape on this information. Core Lightning kind of has a built-in system here,

544
00:30:28,128 --> 00:30:29,048
which is really nice, right?

545
00:30:29,108 --> 00:30:31,568
Their plugin you can just get, I guess, built-in is...

546
00:30:31,568 --> 00:30:33,268
Yeah, it uses the built-in plugin systems

547
00:30:33,268 --> 00:30:35,548
and it's in the sort of not official,

548
00:30:35,688 --> 00:30:39,008
but sort of official sort of like list of community plugins.

549
00:30:39,008 --> 00:30:40,688
And it seems pretty well rated.

550
00:30:40,848 --> 00:30:43,128
Yeah, whereas with LND, you do need to have LND Mon.

551
00:30:43,588 --> 00:30:45,668
But either you get that plugin or you get LND Mon

552
00:30:45,668 --> 00:30:48,928
and now you can monitor with Grafana and Prometheus.

553
00:30:49,048 --> 00:30:51,408
Prometheus pulls the stats, Grafana visualizes them.

554
00:30:51,948 --> 00:30:54,548
And you can get pretty far.

555
00:30:54,688 --> 00:30:56,328
And if you install Mempool Space,

556
00:30:56,388 --> 00:30:57,728
which a lot of us have on our node,

557
00:30:58,128 --> 00:31:10,488
That also exposes a series of API endpoints that can tell you things about the network state, like the current fees, transaction status, the block height, mempool conditions in general from your node's perspective.

558
00:31:11,048 --> 00:31:19,148
Essentially, all the information about the Bitcoin network that mempool is aware of can be exposed as Grafana endpoints around that.

559
00:31:19,148 --> 00:31:27,448
You know, I think that's a good wider point, too, is there's already a lot of good software and dashboards and ways to surface in-ho around node management.

560
00:31:27,448 --> 00:31:31,348
and a lot of them end up having or using under the hood APIs

561
00:31:31,348 --> 00:31:35,068
that you can tap into, like with Mempool or Ride the Lightning

562
00:31:35,068 --> 00:31:35,988
or a lot of these things.

563
00:31:35,988 --> 00:31:38,888
So I'm now scraping all the data with Prometheus

564
00:31:38,888 --> 00:31:42,128
and then with Grafana, it pulls that data out of Prometheus

565
00:31:42,128 --> 00:31:44,148
and it builds me my own custom dashboard.

566
00:31:44,728 --> 00:31:47,728
So I now have a dashboard that shows me what block height I'm at,

567
00:31:47,988 --> 00:31:50,548
how my node is doing, the memory usage, the disk space usage,

568
00:31:50,668 --> 00:31:52,008
the active lightning channels,

569
00:31:52,388 --> 00:31:55,148
how my inbound versus outbound capacity is doing,

570
00:31:55,148 --> 00:31:57,828
how many sats I've received in the last 24 hours.

571
00:31:57,988 --> 00:32:00,648
It's one Grafana dashboard that's pulling the data

572
00:32:00,648 --> 00:32:03,308
from Bitcoin Daemon, from Lightning Daemon,

573
00:32:03,648 --> 00:32:05,548
all of it, and then into Prometheus,

574
00:32:05,668 --> 00:32:06,568
and then one dashboard.

575
00:32:06,928 --> 00:32:10,528
One panel to view it all to make sure everything's up.

576
00:32:10,848 --> 00:32:12,708
And then with that, you can also base alerts.

577
00:32:13,248 --> 00:32:15,248
Which is also nice since you can now kind of separate things.

578
00:32:15,328 --> 00:32:16,648
You don't have to go log into software

579
00:32:16,648 --> 00:32:19,868
where you might be able to do both read and write actions.

580
00:32:19,868 --> 00:32:21,428
You can just pop open a dashboard

581
00:32:21,428 --> 00:32:22,828
and get a sense of what's going on.

582
00:32:23,028 --> 00:32:24,348
And I actually think it's almost more important.

583
00:32:24,348 --> 00:32:26,768
I'm not a dashboard stand at all

584
00:32:26,768 --> 00:32:28,948
but if you will

585
00:32:28,948 --> 00:32:30,808
it might be more important than ever

586
00:32:30,808 --> 00:32:33,328
because if you're tasking agents to do more stuff

587
00:32:33,328 --> 00:32:34,908
it's probably a good idea

588
00:32:34,908 --> 00:32:37,128
to keep an eye on things and have some alerting built in

589
00:32:37,128 --> 00:32:38,668
and so that's why I'm really kind of saying

590
00:32:38,668 --> 00:32:39,488
now is the time

591
00:32:39,488 --> 00:32:41,108
I've had other reasons in the past

592
00:32:41,108 --> 00:32:42,448
why I really didn't have monitoring set up

593
00:32:42,448 --> 00:32:44,228
but that sort of was like the last

594
00:32:44,228 --> 00:32:45,268
like you got to do this

595
00:32:45,268 --> 00:32:49,348
and this is such a great system now

596
00:32:49,348 --> 00:32:52,228
because a lot of just the day-to-day tasks

597
00:32:52,228 --> 00:32:54,748
the agent can monitor and manage for me.

598
00:32:55,008 --> 00:32:57,128
And then when I still need visibility,

599
00:32:57,128 --> 00:32:59,708
I've got it through Grafana and Prometheus monitoring.

600
00:33:00,448 --> 00:33:01,628
You know, I just have to say this

601
00:33:01,628 --> 00:33:02,648
because it's who I am now,

602
00:33:02,768 --> 00:33:04,648
but for some of our nodes,

603
00:33:04,688 --> 00:33:05,908
we've been using NixBitcoin.

604
00:33:06,068 --> 00:33:06,268
Yeah.

605
00:33:06,348 --> 00:33:07,748
And that really makes a lot of the stuff

606
00:33:07,748 --> 00:33:09,468
really easy to integrate as well.

607
00:33:09,488 --> 00:33:09,708
Yeah.

608
00:33:09,828 --> 00:33:11,888
And the agents can just sort of spin it up

609
00:33:11,888 --> 00:33:13,468
in a declarative way for you.

610
00:33:14,168 --> 00:33:14,428
Yeah.

611
00:33:14,508 --> 00:33:15,448
Like I just tell the agent,

612
00:33:15,548 --> 00:33:17,828
go turn on Prometheus support on Bitcoin, Dean.

613
00:33:17,828 --> 00:33:19,928
It's just a flag in the config and now it's on.

614
00:33:20,128 --> 00:33:21,068
It's so amazing.

615
00:33:21,728 --> 00:33:21,868
Yeah.

616
00:33:22,228 --> 00:33:25,708
There is so many things out there you can use besides this entire stack.

617
00:33:25,888 --> 00:33:27,608
Ride the Lightning is still a really great tool.

618
00:33:28,108 --> 00:33:29,848
I think people should check that out if they haven't.

619
00:33:30,288 --> 00:33:31,068
I know you love Zeus.

620
00:33:31,688 --> 00:33:32,028
Oh, yeah.

621
00:33:32,128 --> 00:33:38,348
If you're going to use something to check in or just send some sets somewhere on Android, Zeus is great.

622
00:33:38,468 --> 00:33:38,588
Yeah.

623
00:33:39,168 --> 00:33:42,948
Really, the point I'm trying to make here is you're not replacing the dashboard with the agent.

624
00:33:43,188 --> 00:33:47,608
You're using the dashboard now to serve the human and monitor the agent's work.

625
00:33:47,608 --> 00:33:53,328
And then the API is being used on the back end from all these tools to give you a single interface.

626
00:33:53,728 --> 00:33:55,408
And that is, it is really great.

627
00:33:55,748 --> 00:34:01,008
Because as long as you have an eye on things, really managing a node is very, very simple.

628
00:34:01,248 --> 00:34:04,188
And now having an eye on things is easier than ever, really.

629
00:34:04,688 --> 00:34:06,848
Well, let's talk about backups really quick.

630
00:34:07,728 --> 00:34:09,768
So NixBitcoin does make backing up really easy.

631
00:34:09,828 --> 00:34:10,948
Do you want to talk about that briefly?

632
00:34:11,768 --> 00:34:13,688
Well, it's just really good at setting things up

633
00:34:13,688 --> 00:34:16,028
so that you have clear delineation

634
00:34:16,028 --> 00:34:17,648
of where secrets are kept

635
00:34:17,648 --> 00:34:20,368
and then where the stateful components

636
00:34:20,368 --> 00:34:23,128
of each of the demons that you're running.

637
00:34:23,508 --> 00:34:25,108
Obviously, with Bitcoin, you have the chain state,

638
00:34:25,208 --> 00:34:27,108
but then for the various lightning demons,

639
00:34:27,408 --> 00:34:28,328
there's seed material,

640
00:34:28,608 --> 00:34:31,008
there's information on the Bitcoin wallets they have.

641
00:34:31,188 --> 00:34:31,808
Your channel information.

642
00:34:31,808 --> 00:34:33,748
And then all the stuff about channels.

643
00:34:34,108 --> 00:34:34,268
Yeah.

644
00:34:34,488 --> 00:34:35,448
And so this is where, too,

645
00:34:35,528 --> 00:34:36,708
you might want to be pretty careful

646
00:34:36,708 --> 00:34:37,528
in terms of, like,

647
00:34:37,968 --> 00:34:39,568
do you turn the node off when you do a backup?

648
00:34:39,568 --> 00:34:44,008
Does it have an API that you can trigger to make sure things are synced before you do a backup?

649
00:34:44,128 --> 00:34:51,088
Because what you don't want to do is be broadcasting false stuff to the network and then get penalized or have your channels forced closed.

650
00:34:52,068 --> 00:34:52,108
Yeah.

651
00:34:52,268 --> 00:34:55,688
And so that's where you also don't ever really want to just like blindly restore from a backup.

652
00:34:56,288 --> 00:35:07,468
And do investigate ways to like newer channel mechanisms exist that allow for better mechanisms of being able to restore a channel without having to take the risk of sort of doing a whole backup

653
00:35:07,468 --> 00:35:09,088
when there might have been advanced state

654
00:35:09,088 --> 00:35:09,888
that you weren't privy to?

655
00:35:10,348 --> 00:35:12,048
I think maybe a takeaway for somebody too

656
00:35:12,048 --> 00:35:13,448
that's building a new node today,

657
00:35:13,508 --> 00:35:15,448
even if you're not in on the agent stuff,

658
00:35:15,728 --> 00:35:17,308
it's go minimal and clean.

659
00:35:17,848 --> 00:35:18,868
Build a clean node.

660
00:35:19,568 --> 00:35:21,928
Focus on surfacing APIs securely

661
00:35:21,928 --> 00:35:22,988
with scoped credentials.

662
00:35:23,848 --> 00:35:25,908
Payments can be something that are programmable now.

663
00:35:26,308 --> 00:35:28,328
You need to think about event-driven automation

664
00:35:28,328 --> 00:35:29,168
for certain things.

665
00:35:29,828 --> 00:35:31,268
Monitor everything that you can

666
00:35:31,268 --> 00:35:32,348
and then keep backups

667
00:35:32,348 --> 00:35:34,368
and make sure those backups are outside

668
00:35:34,368 --> 00:35:36,228
any kind of blast radius of an agent

669
00:35:36,228 --> 00:35:36,988
or anything like that.

670
00:35:36,988 --> 00:35:59,168
This is also where like, you know, using some more stuff, like you can go all the way to the base layer. But if you do choose to use something like AlbiHub, you get some of the nice features, right? Like you get LNURL support out of the box, which can be a nice way for maybe for agents to receive payments. And you can, there's also various ways to build this on top of the base nodes, but you can have like sub wallet support.

671
00:35:59,168 --> 00:36:01,628
so you can maybe give a dedicated wallet to your agent.

672
00:36:01,928 --> 00:36:02,328
I have done that.

673
00:36:02,508 --> 00:36:03,808
Yeah, so one of my agents,

674
00:36:04,288 --> 00:36:06,448
I have a dedicated AlbiHub sub-wallet

675
00:36:06,448 --> 00:36:07,948
and it uses Nostra Wallet Connect.

676
00:36:08,168 --> 00:36:09,588
He's got a very limited balance

677
00:36:09,588 --> 00:36:12,108
with a budget he can spend and it works great.

678
00:36:12,588 --> 00:36:14,228
He's got all the stuff he needs to connect to it

679
00:36:14,228 --> 00:36:16,388
and Nostra Wallet Connect is so easy for them to understand.

680
00:36:16,628 --> 00:36:17,168
And that's where, right,

681
00:36:17,248 --> 00:36:19,708
as is often sort of the boring case of security,

682
00:36:19,808 --> 00:36:21,828
if you can just restrict the ability of things

683
00:36:21,828 --> 00:36:24,328
and have defense in depth in multiple ways.

684
00:36:24,428 --> 00:36:25,708
So, you know, even if it does go crazy

685
00:36:25,708 --> 00:36:26,888
into a loop spending stuff,

686
00:36:27,188 --> 00:36:28,548
if it only ever had a balance of X,

687
00:36:28,548 --> 00:36:29,688
That's all it can ever really damage.

688
00:36:29,768 --> 00:36:29,908
Yeah.

689
00:36:30,268 --> 00:36:33,648
Do you tip your agents or give them an allowance or something like that?

690
00:36:34,348 --> 00:36:35,308
You know, maybe.

691
00:36:35,928 --> 00:36:44,828
What I was setting up was a complete workflow so that if the credit balance ever got too low and I wasn't around, they could auto top off.

692
00:36:44,908 --> 00:36:45,388
Like a buffer?

693
00:36:45,568 --> 00:36:46,928
Yeah, their own credits using.

694
00:36:47,268 --> 00:36:49,168
You can make them pay you when they waste tokens.

695
00:36:49,168 --> 00:36:49,788
I should.

696
00:36:50,248 --> 00:36:51,308
That's a good idea.

697
00:36:51,308 --> 00:37:00,768
So I think, you know, what's been really freaking great is this stuff is ready to go in the agent of or in the era of agents.

698
00:37:00,888 --> 00:37:07,648
There's a lot of a lot of things that are not really agent ready that we're going to have to drag along and make work and build front ends to and all of that.

699
00:37:07,708 --> 00:37:09,548
But all of this is pretty much good to go.

700
00:37:09,708 --> 00:37:13,408
And so and so it's Bitcoin is programmable money, right?

701
00:37:13,468 --> 00:37:13,608
Yeah.

702
00:37:13,608 --> 00:37:15,488
Like it's it's it's here already.

703
00:37:15,688 --> 00:37:18,008
I mean, they've got APIs where there's not APIs.

704
00:37:18,008 --> 00:37:19,168
Albie's making MCPs.

705
00:37:19,168 --> 00:37:22,128
It's like it's really ready today for the agent workflow.

706
00:37:22,388 --> 00:37:24,148
And a lot of them are being very careful.

707
00:37:24,448 --> 00:37:30,648
A lot of the off the shelf stuff is mostly read only or manages scoped payments and stuff like that.

708
00:37:30,768 --> 00:37:44,368
But I think the real power is in the Bolt D and Bolt CLI and getting your agent with the skill that will link to be able to manage liquidity a little bit, tell you about the channels on your node, send payments, sweep to liquid.

709
00:37:44,468 --> 00:37:46,148
That stuff is massive.

710
00:37:46,148 --> 00:37:47,348
And it's just the beginning.

711
00:37:47,348 --> 00:37:49,828
And that skill could use some improvement.

712
00:37:50,068 --> 00:37:51,528
It's not been fully, fully tested.

713
00:37:51,648 --> 00:37:53,088
Just the workflows I've talked about have.

714
00:37:53,548 --> 00:37:54,228
And I'll post that.

715
00:37:54,308 --> 00:37:58,828
And if you've got a wild hare and you want to test it and smoke test it and improve it,

716
00:37:59,328 --> 00:38:00,528
at least submit the changes back up.

717
00:38:00,568 --> 00:38:01,268
I'll put it up on GitHub.

718
00:38:01,868 --> 00:38:03,328
But I have a question, gentlemen.

719
00:38:05,808 --> 00:38:10,708
Out there in the wild, listener, what would you like to do next with your node?

720
00:38:10,848 --> 00:38:13,388
Assuming you've noted up, are you planning to do anything?

721
00:38:13,588 --> 00:38:16,248
Or are you just leaving it and letting it tick-tock next block?

722
00:38:16,688 --> 00:38:19,568
So boost in and tell us what you're planning to do with your node next.

723
00:38:38,448 --> 00:38:42,728
Well, coming up on the show, some clips I feel like playing, your boost, and a lot more.

724
00:38:42,848 --> 00:38:45,368
So you can support the show just by doing what you do.

725
00:38:45,368 --> 00:38:50,308
You want to buy some sats on River? The best way is River in the U.S.

726
00:38:50,368 --> 00:38:53,288
And I have a link in the show notes. Use that link. Supports the show.

727
00:38:53,408 --> 00:38:57,008
Guess what? Any of these. I have a link in the show notes and you use that link.

728
00:38:57,068 --> 00:39:00,628
It supports the show. Bitcoin Well. You're up there in Canada like our buddy Brent.

729
00:39:01,168 --> 00:39:04,608
The Bitcoin Well is an amazing automatic self-custody Bitcoin platform.

730
00:39:04,988 --> 00:39:08,008
They don't host the wallet. You do. Goes from your wallet to your wallet.

731
00:39:08,388 --> 00:39:12,188
The Bitcoin Company. You got sats burning a hole in your pocket. Go spend it with the Bitcoin Company.

732
00:39:12,188 --> 00:39:17,968
all they do is Bitcoin from Lightning to a gift card in just seconds. Now, if you want to passively

733
00:39:17,968 --> 00:39:23,188
stack sats, maybe pay your bills and all that, bold card. Audience loves it. Passively stack those

734
00:39:23,188 --> 00:39:27,408
sats. It's a great way to go. If it's time to get access to your Bitcoin liquidity without selling

735
00:39:27,408 --> 00:39:33,908
it, that's where salt lending comes in. Great platform, low minimums, and some wipeout protection,

736
00:39:34,168 --> 00:39:40,108
which you never know could be useful these days. Links to all of that in the show notes. Thanks to

737
00:39:40,108 --> 00:39:42,228
everybody who supports the show by doing what you do.

738
00:39:57,628 --> 00:40:01,228
Well, guess what? It is time for a few boosts.

739
00:40:02,408 --> 00:40:05,488
And now it is time for le boost.

740
00:40:05,648 --> 00:40:07,068
Get ready for this one, boys.

741
00:40:07,588 --> 00:40:11,028
Derivation Dingus comes in as our baller booster this week,

742
00:40:11,468 --> 00:40:18,348
breaking, I think, our total for last week in one single boost with 190,000 sats.

743
00:40:18,528 --> 00:40:18,868
Wow.

744
00:40:21,868 --> 00:40:24,068
You're the best around.

745
00:40:25,288 --> 00:40:27,368
Nothing's going to ever keep you down.

746
00:40:27,488 --> 00:40:29,068
You're the best around.

747
00:40:30,348 --> 00:40:32,408
Nothing's going to ever keep you down.

748
00:40:32,648 --> 00:40:33,688
Superior ability.

749
00:40:33,868 --> 00:40:34,488
That's enough sats.

750
00:40:34,508 --> 00:40:36,028
Three, superior ambition.

751
00:40:36,388 --> 00:40:38,328
That's enough sats to actually buy some lobster, maybe.

752
00:40:40,188 --> 00:40:40,828
Derivation writes,

753
00:40:40,908 --> 00:40:41,248
Hi, Chris.

754
00:40:41,288 --> 00:40:43,308
I recently, I really appreciate everything you do

755
00:40:43,308 --> 00:40:44,468
and the work you put into the show.

756
00:40:44,908 --> 00:40:46,648
I hope this value makes it a little more worth your time.

757
00:40:47,088 --> 00:40:49,128
Twib is one of the best Bitcoin shows on the internet.

758
00:40:49,568 --> 00:40:50,868
Let's get these numbers up, boys.

759
00:40:51,528 --> 00:40:51,968
Thank you, sir.

760
00:40:52,088 --> 00:40:52,748
Well done.

761
00:40:52,848 --> 00:40:53,288
Make it show.

762
00:40:53,808 --> 00:40:54,988
Appreciate you very much.

763
00:40:55,408 --> 00:40:58,448
You are our baller booster coming in right below there.

764
00:40:58,448 --> 00:41:02,228
Also in the baller category, it is Adversary 17.

765
00:41:02,348 --> 00:41:03,728
Hey, rich lobster.

766
00:41:03,728 --> 00:41:08,708
Coming in with 98,899 sats.

767
00:41:13,268 --> 00:41:14,528
This was a great episode.

768
00:41:14,708 --> 00:41:16,328
I know you're going to try changing the format.

769
00:41:16,508 --> 00:41:18,428
I'm excited to see how that goes.

770
00:41:18,488 --> 00:41:20,648
I just wanted to give you some signal on the current format

771
00:41:20,648 --> 00:41:22,288
as I get a lot of value in each episode.

772
00:41:22,748 --> 00:41:32,752
So when you choose what to cut please don cut the state of the network section I like hearing that each week Oh it not a format change I just wanted to have some fun for one week Everybody I should have said that maybe earlier in the show

773
00:41:33,152 --> 00:41:35,212
People are going to get to 40 minutes of the show until they hear that.

774
00:41:35,532 --> 00:41:36,392
Are you having fun?

775
00:41:37,012 --> 00:41:38,752
Yeah, I'm having a fun.

776
00:41:38,872 --> 00:41:39,232
You did it.

777
00:41:39,752 --> 00:41:40,772
Thank you, adversaries.

778
00:41:41,532 --> 00:41:45,812
Kiwi Bitcoin Guide comes in with $49,999.

779
00:41:46,832 --> 00:41:47,032
Oh.

780
00:41:47,032 --> 00:41:54,492
Hey, Chris, I want to echo some of the other comments here and say that Twib is a highlight

781
00:41:54,492 --> 00:41:59,872
of my week and the signal and value you provide is awesome. The fact that you live and breathe

782
00:41:59,872 --> 00:42:04,952
open source and live off value for value means the content is of the highest quality. It seems

783
00:42:04,952 --> 00:42:09,012
like all the other Bitcoin pods have either lost their values, sold out to advertisers,

784
00:42:09,412 --> 00:42:15,032
or just gone batshit crazy. So we need you here, buddy. I'd like to see more of the memberships

785
00:42:15,032 --> 00:42:17,652
for TWIB, and I think there must be some opportunities.

786
00:42:18,452 --> 00:42:18,692
Wow.

787
00:42:19,172 --> 00:42:20,392
Thank you, KiwiBitcoinGuy.

788
00:42:20,412 --> 00:42:23,732
That's way too nice, and I'm embarrassed, and I appreciate you very, very much.

789
00:42:23,832 --> 00:42:24,412
Yes, hi.

790
00:42:24,912 --> 00:42:25,932
Thank you very much for the boost.

791
00:42:26,532 --> 00:42:27,012
And the value.

792
00:42:28,892 --> 00:42:31,772
JQubed boosted in $36,057.

793
00:42:32,332 --> 00:42:33,332
I like you.

794
00:42:33,732 --> 00:42:34,772
You're a hot ticket.

795
00:42:35,372 --> 00:42:37,412
I got busy and I forgot to boost last week.

796
00:42:37,632 --> 00:42:41,492
Honestly, I'm a little tired of billionaires telling us what we're doing wrong.

797
00:42:41,492 --> 00:42:47,692
Feels like a lack of perspective on the common man at best, and manipulation at the worst.

798
00:42:48,172 --> 00:42:49,852
Maybe I'm getting a little paranoid.

799
00:42:50,272 --> 00:42:50,872
Oh, I agree.

800
00:42:51,112 --> 00:42:52,432
The traders love the ball.

801
00:42:52,612 --> 00:42:53,072
I agree.

802
00:42:53,152 --> 00:42:55,292
Is there any bacon on board, Tim?

803
00:42:55,312 --> 00:42:57,072
Yeah, I do have some bacon somewhere around here.

804
00:42:57,412 --> 00:42:58,832
I always keep bacon nearby.

805
00:42:58,952 --> 00:42:59,952
Do you like it crispy?

806
00:43:00,332 --> 00:43:01,032
No, it wasn't bacon.

807
00:43:01,552 --> 00:43:02,452
I love it, though.

808
00:43:02,492 --> 00:43:04,992
Either way, it's Bigfoot tonight.

809
00:43:06,272 --> 00:43:07,892
I hope that does it for you, J.K.

810
00:43:08,532 --> 00:43:08,972
Perfect.

811
00:43:08,972 --> 00:43:09,172
Perfect.

812
00:43:10,012 --> 00:43:15,072
Hey, Darabish Dingus is back with 21,420 sats.

813
00:43:18,932 --> 00:43:22,712
Just sending a bit more value from the old NixOS node, by the way.

814
00:43:22,972 --> 00:43:23,492
Keep it up.

815
00:43:23,792 --> 00:43:24,472
That's great.

816
00:43:24,892 --> 00:43:26,692
Well, that's very on topic, isn't it?

817
00:43:26,752 --> 00:43:27,192
Indeed.

818
00:43:27,452 --> 00:43:28,372
Thank you very much.

819
00:43:28,812 --> 00:43:29,372
Double ball.

820
00:43:30,092 --> 00:43:34,132
Philippa A. comes in with 21,221 sats.

821
00:43:34,152 --> 00:43:35,932
Put some macaroni and cheese on there, too.

822
00:43:35,932 --> 00:43:36,992
hey Chris

823
00:43:36,992 --> 00:43:37,652
thanks for your

824
00:43:37,652 --> 00:43:39,012
consistency over time

825
00:43:39,012 --> 00:43:39,612
with the show

826
00:43:39,612 --> 00:43:40,572
even hearing your

827
00:43:40,572 --> 00:43:41,152
theme music

828
00:43:41,152 --> 00:43:42,332
calms my nerves

829
00:43:42,332 --> 00:43:43,332
and lifts my spirits

830
00:43:43,332 --> 00:43:43,872
each week

831
00:43:43,872 --> 00:43:45,272
I totally understand

832
00:43:45,272 --> 00:43:45,812
you need to shake

833
00:43:45,812 --> 00:43:46,532
things up a bit

834
00:43:46,532 --> 00:43:47,272
and give yourself

835
00:43:47,272 --> 00:43:47,672
a boost

836
00:43:47,672 --> 00:43:48,992
I've noticed you

837
00:43:48,992 --> 00:43:49,712
getting more and more

838
00:43:49,712 --> 00:43:50,612
upset over the

839
00:43:50,612 --> 00:43:51,972
Bip 110 situation

840
00:43:51,972 --> 00:43:53,272
it does bother me a lot

841
00:43:53,272 --> 00:43:54,512
as the weeks go by

842
00:43:54,512 --> 00:43:54,992
these guys know

843
00:43:54,992 --> 00:43:55,712
I complain about it

844
00:43:55,712 --> 00:43:56,052
a lot there

845
00:43:56,052 --> 00:43:57,572
and not your usual

846
00:43:57,572 --> 00:43:58,332
calm self

847
00:43:58,332 --> 00:44:00,232
change is as good

848
00:44:00,232 --> 00:44:01,032
as a rest

849
00:44:01,032 --> 00:44:02,432
really looking forward

850
00:44:02,432 --> 00:44:02,972
to going to

851
00:44:02,972 --> 00:44:03,912
Cheat Code Bedford

852
00:44:03,912 --> 00:44:04,452
next week

853
00:44:04,452 --> 00:44:05,172
and seeing Lynn

854
00:44:05,172 --> 00:44:10,252
alden et al do their thing and then there's something that got cut off yeah i would love

855
00:44:10,252 --> 00:44:15,872
to hear how that goes love i'd love to meet lynn lynn is a rock star thank you very much that philpa

856
00:44:15,872 --> 00:44:22,952
appreciate that bitcoin is my 401k boosted 21 000 sats oh my god this drawer is filled with

857
00:44:22,952 --> 00:44:29,512
brooves here's 21 000 saps to help keep my favorite bitcoin podcast afloat thank you chris

858
00:44:29,512 --> 00:44:42,512
Thank you. Bitcoin is my 401k. I love that. That's great. I always love it every time. And it's true. It's true. Mac Jollers comes in with 21,000 sats.

859
00:44:42,512 --> 00:44:50,832
gas for air after your hiatus content sweet pure signal yes we're back hopefully people don't mind

860
00:44:50,832 --> 00:44:56,612
the episode 100 party a little early but it's fun to hang out with the boys and talk nodes

861
00:44:56,612 --> 00:45:03,212
thank you very much mac jollers appreciate the boost boba comes in with 21 000 sats

862
00:45:03,212 --> 00:45:16,052
dig me some drum and bass and then uh second message here bad take on btc question mark i

863
00:45:16,052 --> 00:45:21,252
think mr wonderful's break the chain comment on quantum fud was embarrassingly bad considering it

864
00:45:21,252 --> 00:45:25,332
was espoused from the position of informed authority at the time i hate it when they do that

865
00:45:25,332 --> 00:45:31,632
i know and a third message off topic would converting out of liquid into lightning or

866
00:45:31,632 --> 00:45:36,852
back on chain automatically incur a taxable event? Not looking for advice, just a thought experiment.

867
00:45:37,252 --> 00:45:42,972
Tease the season. Yeah, it is, isn't it? My understanding is no, because liquid and Bitcoin

868
00:45:42,972 --> 00:45:48,032
are the same exact value. So there's no change in value there, right? But I could be wrong.

869
00:45:48,472 --> 00:45:52,952
I could be wrong. But you're pegging to a particular price in Bitcoin. Now that I think

870
00:45:52,952 --> 00:45:56,752
about it, I'm not sure. I assume it's not a taxable event, and I like to believe that.

871
00:45:57,132 --> 00:46:00,312
Do you have any instinct either way? What you believe doesn't necessarily mean.

872
00:46:00,312 --> 00:46:07,152
It does seem like, right, if the value is the same, then if you haven't converted that value, good question.

873
00:46:07,812 --> 00:46:10,432
I could see if you're going to stablecoin and back that being taxable then.

874
00:46:11,032 --> 00:46:13,912
And probably maybe even between something like ETH and BTC.

875
00:46:14,132 --> 00:46:22,512
But like, say you put 10,000 sats into Liquid five years ago, you would still get today's amount of 10,000 sats back.

876
00:46:22,912 --> 00:46:25,732
You would get the same, so you would always get the same amount of Bitcoin value back.

877
00:46:26,232 --> 00:46:27,532
It might just change in Liquid.

878
00:46:27,532 --> 00:46:28,692
Yeah, there's no ratio that differs.

879
00:46:28,692 --> 00:46:29,252
Yeah, yeah.

880
00:46:29,252 --> 00:46:31,772
So I don't think it's a taxable event, but I'm honestly not.

881
00:46:31,872 --> 00:46:36,292
And if anybody out there has a better understanding, of course, not tax advice, just your opinion.

882
00:46:36,412 --> 00:46:37,852
Please do boost it and let us know.

883
00:46:38,332 --> 00:46:38,812
I'd love to know.

884
00:46:39,492 --> 00:46:44,012
Moon and I sent in just slightly over 9,000 sats with 9,001 sats.

885
00:46:45,792 --> 00:46:49,292
It's a shame that the sat flow into the show is so low.

886
00:46:49,572 --> 00:46:56,792
I've been getting a ton of value out of your podcast, as you seem to be one of the very few Bitcoin podcasters that has their head screwed on straight.

887
00:46:56,792 --> 00:47:05,012
I've grown pretty tired of the podcast that's spent all day interviewing weird culture war people and financial dudes that have never had a real job.

888
00:47:05,172 --> 00:47:08,232
And it shows in how they view the economy.

889
00:47:08,672 --> 00:47:14,092
That ranting aside, I really appreciate the work you're doing with Twib, so I'll be bumping up my sats.

890
00:47:14,332 --> 00:47:16,792
Thanks, Moodyne. I really appreciate that.

891
00:47:17,632 --> 00:47:21,612
I'm not saying I agree, but, you know, I really appreciate that boost.

892
00:47:22,092 --> 00:47:25,572
Hey there, Gene Bean's back, 6,492 sats.

893
00:47:25,572 --> 00:47:26,752
Well, that's Eric Goodbody.

894
00:47:27,272 --> 00:47:30,292
He's blown away at the $3 billion in expenses and interest today.

895
00:47:30,372 --> 00:47:38,212
He says, your description of just how bad Luke is trying to centralize political power over Bitcoin could be explained by him disliking the key thing that makes Bitcoin different from Ethereum.

896
00:47:38,852 --> 00:47:39,492
No CEO.

897
00:47:40,012 --> 00:47:43,772
Maybe he wants to make Ocean the CEO of the network with the biggest market cap.

898
00:47:44,252 --> 00:47:45,792
Yeah, I know I'm wearing my tinfoil hat here.

899
00:47:46,312 --> 00:47:48,292
He says, how is that JB mining pool coming along?

900
00:47:49,292 --> 00:47:52,492
I think Adversaries was working on that when you were out there with him, right?

901
00:47:52,892 --> 00:47:54,932
Yeah, and didn't you have a little miner on the-

902
00:47:54,932 --> 00:47:55,732
I'm a bottleneck.

903
00:47:55,732 --> 00:47:56,732
On the soundboard.

904
00:47:56,792 --> 00:47:57,572
there for a little while.

905
00:47:57,652 --> 00:47:58,692
I'm such a bottleneck.

906
00:47:58,792 --> 00:48:00,372
I am such a bottleneck to this stuff.

907
00:48:00,832 --> 00:48:01,392
It's horrible.

908
00:48:01,492 --> 00:48:01,792
I don't know.

909
00:48:02,152 --> 00:48:03,812
I think adversaries has made some really good progress.

910
00:48:03,932 --> 00:48:05,212
So I got to sit down.

911
00:48:05,412 --> 00:48:08,692
Adversary 17 and I are going to have a chat and we'll figure it out at some point.

912
00:48:08,752 --> 00:48:09,712
I am the bottleneck there.

913
00:48:09,892 --> 00:48:12,012
And I just because things are so busy.

914
00:48:12,852 --> 00:48:15,972
I don't know when things are maybe in four or five years and my kids are all growing up.

915
00:48:16,032 --> 00:48:16,212
Maybe.

916
00:48:16,332 --> 00:48:16,932
I don't know.

917
00:48:17,152 --> 00:48:17,952
It'll be too late.

918
00:48:18,052 --> 00:48:18,852
I don't know.

919
00:48:19,952 --> 00:48:20,632
Thank you, Gene.

920
00:48:20,632 --> 00:48:23,732
And when I do know, I think you're going to be the first person I tell.

921
00:48:23,732 --> 00:48:27,612
user 888 comes in with 2,000 sats

922
00:48:27,612 --> 00:48:30,312
thanks for doing what you do

923
00:48:30,312 --> 00:48:31,532
thank you user 88

924
00:48:31,532 --> 00:48:32,592
appreciate you

925
00:48:32,592 --> 00:48:35,292
Cosnow also came in with 2,500 sats

926
00:48:35,292 --> 00:48:36,432
but no message found

927
00:48:36,432 --> 00:48:39,192
OB came in with 2,000 sats

928
00:48:39,192 --> 00:48:40,092
no message found

929
00:48:40,092 --> 00:48:40,592
make it so

930
00:48:40,592 --> 00:48:42,732
and Ace Ackerman came in with

931
00:48:42,732 --> 00:48:43,632
Rodex

932
00:48:43,632 --> 00:48:46,012
that's 2,222 sats

933
00:48:46,012 --> 00:48:47,532
keep TWIP alive and healthy

934
00:48:47,532 --> 00:48:48,212
with a boost

935
00:48:48,212 --> 00:48:49,072
boost

936
00:48:49,072 --> 00:48:53,732
Jetpack81 sends in 4,200 sats

937
00:48:53,732 --> 00:48:54,052
Hey

938
00:48:54,052 --> 00:48:56,032
No message on the first one

939
00:48:56,032 --> 00:48:57,032
But thank you

940
00:48:57,032 --> 00:48:59,152
This is my favorite Bitcoin podcast

941
00:48:59,152 --> 00:48:59,612
Aw

942
00:48:59,612 --> 00:49:01,112
Thank you very much

943
00:49:01,112 --> 00:49:02,612
Okay

944
00:49:02,612 --> 00:49:04,112
Bug-Eyed Stormtrooper's here

945
00:49:04,112 --> 00:49:06,892
And he's got 2,042 sats

946
00:49:06,892 --> 00:49:08,572
I feel like I got something for him

947
00:49:08,572 --> 00:49:08,772
Right?

948
00:49:08,812 --> 00:49:09,452
I got something

949
00:49:09,452 --> 00:49:11,052
Miss Bustin' with happiness

950
00:49:11,052 --> 00:49:11,872
See you in a second

951
00:49:11,872 --> 00:49:13,232
This is the way

952
00:49:13,232 --> 00:49:14,132
Hello there

953
00:49:14,132 --> 00:49:16,332
Suppose that BIP-110 does pull it off

954
00:49:16,332 --> 00:49:16,992
And it goes bad

955
00:49:16,992 --> 00:49:18,792
Is it possible for the community to roll it back?

956
00:49:18,792 --> 00:49:20,352
or is it a one-way street?

957
00:49:22,112 --> 00:49:22,392
Hmm.

958
00:49:22,672 --> 00:49:23,612
I don't know if I have an answer.

959
00:49:24,712 --> 00:49:25,912
I mean, it depends on how far it goes

960
00:49:25,912 --> 00:49:27,652
and how much, you know,

961
00:49:27,852 --> 00:49:29,552
mining power they would actually be able to get.

962
00:49:29,732 --> 00:49:31,352
The length of diverged history

963
00:49:31,352 --> 00:49:34,492
is going to increase the pain over time, right?

964
00:49:34,552 --> 00:49:34,932
That's it.

965
00:49:35,032 --> 00:49:35,412
That's it.

966
00:49:35,752 --> 00:49:35,912
Yeah.

967
00:49:36,452 --> 00:49:37,412
And now we just don't know really

968
00:49:37,412 --> 00:49:38,352
until it happens, I suppose,

969
00:49:38,672 --> 00:49:39,472
and how far it gets.

970
00:49:39,992 --> 00:49:40,692
It's one of the things

971
00:49:40,692 --> 00:49:41,872
I just don't even want to have to worry about.

972
00:49:41,992 --> 00:49:42,792
I really...

973
00:49:42,792 --> 00:49:42,892
Yeah.

974
00:49:43,652 --> 00:49:44,592
Like Philip, I mentioned,

975
00:49:44,732 --> 00:49:45,612
like it does bother me.

976
00:49:45,712 --> 00:49:46,772
It really bothers me.

977
00:49:47,012 --> 00:49:48,552
It bothers me because I, you know,

978
00:49:48,552 --> 00:49:50,372
I've been following this for nearly 16 years.

979
00:49:50,472 --> 00:49:51,372
It's pretty important to me.

980
00:49:51,512 --> 00:49:53,312
And I think it's pretty important to the world.

981
00:49:53,492 --> 00:49:55,472
And it's just, it's crazy where you...

982
00:49:55,472 --> 00:49:55,692
Yeah.

983
00:49:56,252 --> 00:49:58,052
I have a box of soap here if you need it.

984
00:49:58,052 --> 00:49:58,292
Thank you.

985
00:49:58,632 --> 00:49:58,732
Yeah.

986
00:49:59,172 --> 00:50:00,192
All right, let me wrap this up.

987
00:50:00,252 --> 00:50:03,012
Paranoid Coder comes in with 2,000 sats.

988
00:50:03,652 --> 00:50:06,552
I mentioned Spark on these booths a couple of times now,

989
00:50:06,592 --> 00:50:08,452
and I just noticed that Primal recently switched

990
00:50:08,452 --> 00:50:10,532
from using Lightning via embedded Spark Wallet

991
00:50:10,532 --> 00:50:13,332
to a custodial Spark Wallet that auto-swaps to Lightning.

992
00:50:13,572 --> 00:50:15,892
Pretty cool to see this technology actually get adopted.

993
00:50:16,372 --> 00:50:17,552
Big Primal update.

994
00:50:17,552 --> 00:50:22,152
Primal being the Noster front end, Primal 3.0 is huge.

995
00:50:22,312 --> 00:50:23,852
Yeah, and they redid the wallet stuff.

996
00:50:23,932 --> 00:50:25,192
I haven't had a chance to play with it yet.

997
00:50:25,772 --> 00:50:31,432
I did see some people talking about Spark custodial services being not ideal for privacy, but what custodial service is.

998
00:50:31,912 --> 00:50:33,332
Well, I think this one was self-custodial.

999
00:50:33,352 --> 00:50:34,112
Yeah, exactly.

1000
00:50:34,512 --> 00:50:35,832
So that seems like a much better route.

1001
00:50:36,392 --> 00:50:36,952
Very cool.

1002
00:50:37,072 --> 00:50:38,372
And I have Primal 3 installed.

1003
00:50:38,452 --> 00:50:39,852
I'm going to start playing around with the wallet feature.

1004
00:50:40,412 --> 00:50:41,152
But thank you for that boost.

1005
00:50:41,212 --> 00:50:42,152
Thank you, everybody.

1006
00:50:42,612 --> 00:50:44,092
Thank you, everybody else who streams sats.

1007
00:50:44,092 --> 00:50:47,732
You collectively stacked 71,688 sats for the show.

1008
00:50:47,832 --> 00:50:49,312
Not too bad at all.

1009
00:50:49,512 --> 00:50:50,972
B-O-O-S-T.

1010
00:50:51,172 --> 00:50:53,732
When you combine that with our boosters, we had great support.

1011
00:50:53,872 --> 00:50:58,852
This episode, we stacked 616,555 sats.

1012
00:51:11,312 --> 00:51:14,012
If you'd like to support the show, a boost is a great way to do it.

1013
00:51:14,012 --> 00:51:15,372
Fountain FM makes it really easy.

1014
00:51:15,452 --> 00:51:20,852
There's also a membership option in Fountain as well as Jupiter.party if you want to support the entire network.

1015
00:51:21,032 --> 00:51:21,912
No advertiser.

1016
00:51:22,032 --> 00:51:23,692
Just do it for the love of it.

1017
00:51:23,932 --> 00:51:26,072
And of course, for the long term stacking of those sats.

1018
00:51:26,172 --> 00:51:27,672
Support the show by sending a boost.

1019
00:51:27,672 --> 00:51:44,212
All right. So the last couple of weeks, I've been trying to put together what the hell's going on with the billionaires.

1020
00:51:44,212 --> 00:51:53,832
Why is Ray Dalio and Chamath and others coming out who were pro Bitcoin now saying Bitcoin's it's a loser? It's no good.

1021
00:51:53,832 --> 00:51:58,472
And I knew there must be some sort of shitcoin play in the works.

1022
00:51:58,632 --> 00:52:01,072
And I believe, boys, I have put it together.

1023
00:52:01,392 --> 00:52:01,912
Oh, wow.

1024
00:52:02,252 --> 00:52:05,512
Oh, and it's a doozy.

1025
00:52:05,692 --> 00:52:06,672
I'll get my wallet ready.

1026
00:52:06,812 --> 00:52:12,532
To be honest with you, it deserves more of my time to fully dig into it because this is a big one.

1027
00:52:12,772 --> 00:52:15,492
And I have just begun to scratch the surface.

1028
00:52:16,092 --> 00:52:18,872
And it's really something.

1029
00:52:19,452 --> 00:52:21,092
So, let's see, where do we even start?

1030
00:52:21,092 --> 00:52:24,492
The token that we're going to talk about today is called Tau.

1031
00:52:24,692 --> 00:52:26,552
And again, if you're listening, you know more about this.

1032
00:52:26,672 --> 00:52:27,652
Please boost in a correction.

1033
00:52:28,212 --> 00:52:32,332
But Tau is in a league of its own because it's an AI play.

1034
00:52:32,672 --> 00:52:37,712
Things that has really stuck out to me is this intersection of Bitcoin and crypto and artificial intelligence.

1035
00:52:37,712 --> 00:52:44,512
And it feels like there's a lot of folks that are talking about like agentic payments and stable coins and Bitcoin and all that kind of stuff.

1036
00:52:44,772 --> 00:52:49,712
I think you see some other areas where that intersection of Bitcoin and AI are going to show up.

1037
00:52:49,712 --> 00:52:52,472
Talk about what you're excited about there, what you guys are spending time on.

1038
00:52:52,992 --> 00:52:59,612
Yeah, I think most of it is kind of bullshit in that, you know, a lot of projects are saying, hey, we're AI.

1039
00:53:00,512 --> 00:53:07,152
There is clearly, I think, a big opportunity around the convergence of crypto and AI.

1040
00:53:07,632 --> 00:53:10,692
This is Billy, Billy, this, Billy, that's great.

1041
00:53:10,772 --> 00:53:11,932
This is Barry Silbert.

1042
00:53:12,292 --> 00:53:13,132
He's very famous.

1043
00:53:13,132 --> 00:53:16,832
You ought to look up Barry and why he owes people a lot of money.

1044
00:53:16,832 --> 00:53:27,272
And there's certainly, you know, we're definitely, we're obviously seeing it with, on the infrastructure side, with compute and Bitcoin miners diversifying into or pivoting into kind of into AI.

1045
00:53:27,512 --> 00:53:36,332
But I do think that the ability to incentivize contribution, the ability to incentivize stakeholders.

1046
00:53:36,992 --> 00:53:40,052
The other word they use is to create a marketplace for GPUs.

1047
00:53:40,052 --> 00:53:43,972
in unique ways around AI is super exciting.

1048
00:53:44,132 --> 00:53:46,192
And so we got involved in something called Bitensor,

1049
00:53:46,752 --> 00:53:50,612
which is a decentralized open source protocol,

1050
00:53:50,772 --> 00:53:51,512
just like Bitcoin.

1051
00:53:51,932 --> 00:53:53,092
Just like Bitcoin, guys.

1052
00:53:53,092 --> 00:53:54,752
I bet it's one-to-one.

1053
00:53:54,752 --> 00:53:58,372
But instead of incentivizing security of the network,

1054
00:53:58,472 --> 00:54:01,972
it incentivizes people to essentially kind of compete

1055
00:54:01,972 --> 00:54:04,952
and try to solve complex problems in the world.

1056
00:54:05,332 --> 00:54:09,532
So instead of doing silly SHA-256 throwaway math

1057
00:54:09,532 --> 00:54:15,052
or whatever, you know, just stuff that's just burning stupid electricity, just dumb mining.

1058
00:54:15,552 --> 00:54:20,152
This is the same thing as Bitcoin, but it's solving AI problems.

1059
00:54:21,052 --> 00:54:25,692
But Tensor is comprised of over 100 of these different subnets.

1060
00:54:26,292 --> 00:54:32,312
These subnets are competitions where people are trying to predict sports, sport outcomes

1061
00:54:32,312 --> 00:54:36,072
or discover drugs or incentivizing commute or storage.

1062
00:54:36,072 --> 00:54:39,192
Super, super interesting intersectional kind of crypto AI.

1063
00:54:39,532 --> 00:54:44,972
There's a few other projects that I think are interesting, but this definitely is the first one that has reached escape velocity.

1064
00:54:45,352 --> 00:54:48,932
And the token that the entire network operates on is this Tau token.

1065
00:54:49,492 --> 00:54:50,252
And yeah, go ahead.

1066
00:54:50,392 --> 00:54:53,192
Wait, well, he said solve the world's biggest problems.

1067
00:54:53,312 --> 00:54:56,552
And then the first example he came up with was baseball betting.

1068
00:54:57,552 --> 00:55:00,872
Well, that's, you know, I mean, that's a big problem.

1069
00:55:01,012 --> 00:55:02,612
If you're losing a lot of money on your baseball bets.

1070
00:55:03,032 --> 00:55:04,052
That is a problem, I guess.

1071
00:55:04,532 --> 00:55:07,232
I also, are we, you know, like we have like DevSecOps.

1072
00:55:07,232 --> 00:55:08,012
Are we doing that?

1073
00:55:08,092 --> 00:55:09,012
Is it crypto AI now?

1074
00:55:09,012 --> 00:55:10,472
it's just one word, crypto AI.

1075
00:55:10,472 --> 00:55:11,652
I guess so, yeah.

1076
00:55:11,652 --> 00:55:13,512
Agentic crypto AI, you can make a three.

1077
00:55:13,512 --> 00:55:14,512
Good point.

1078
00:55:15,512 --> 00:55:16,932
But it's funny you caught that.

1079
00:55:16,976 --> 00:55:21,836
Brent, because, yeah, the Tau token and the subnet, which sometimes there are individual subnet tokens.

1080
00:55:22,276 --> 00:55:24,256
Don't worry, they're coming to Robinhood and Coinbase.

1081
00:55:24,536 --> 00:55:26,056
How does one buy that?

1082
00:55:26,196 --> 00:55:30,296
By the way, this is Jason Calacanis, who has become cheerleader number one for Tau.

1083
00:55:30,396 --> 00:55:33,916
Because Tau is listed on Robinhood and Coinbase now or not yet?

1084
00:55:34,576 --> 00:55:36,856
Tau itself is on Coinbase.

1085
00:55:36,976 --> 00:55:38,196
I'm not sure if it's on Robinhood.

1086
00:55:38,856 --> 00:55:39,176
It's not.

1087
00:55:39,276 --> 00:55:40,016
I don't think it is.

1088
00:55:40,056 --> 00:55:40,996
I've looked for it before.

1089
00:55:41,156 --> 00:55:42,276
But Tau, you can get at Coinbase.

1090
00:55:42,336 --> 00:55:44,136
I've actually gotten it on Coinbase, so I know it's on there.

1091
00:55:44,336 --> 00:55:46,216
So it's in full shill mode right now.

1092
00:55:46,216 --> 00:55:47,936
It's going to be on Coinbase.

1093
00:55:48,056 --> 00:55:49,836
It's going to be on Robinhood.

1094
00:55:50,356 --> 00:55:52,876
Let's talk about the shilling a little bit in a minute.

1095
00:55:53,076 --> 00:55:57,396
I don't want to get there just yet because I want to still talk about how they're really kind of trying to compare it to Bitcoin.

1096
00:55:57,396 --> 00:56:04,336
You could get like 50K a day, this mining contestonomic thing that makes mining programmable.

1097
00:56:04,596 --> 00:56:05,436
They're already making history.

1098
00:56:05,596 --> 00:56:07,756
They spent less than a million dollars.

1099
00:56:08,036 --> 00:56:10,396
They release a lot of hype videos on social media.

1100
00:56:10,556 --> 00:56:12,576
Compared to Anthropic, which has spent billions.

1101
00:56:13,056 --> 00:56:16,136
Most of them are probably going to be bad startups.

1102
00:56:16,216 --> 00:56:16,936
Probably.

1103
00:56:17,416 --> 00:56:20,836
It's the most important thing that's happened in crypto since Ethereum.

1104
00:56:21,016 --> 00:56:22,096
People are using this stuff.

1105
00:56:22,296 --> 00:56:28,756
In Earth's largest supercomputer, in aggregate, it 3x'd the efficiency and speed.

1106
00:56:28,756 --> 00:56:31,036
So if you can sell the same thing for 90% off.

1107
00:56:31,216 --> 00:56:35,316
Do you think that BitTensor could outgrow the big giants?

1108
00:56:35,436 --> 00:56:37,556
Suddenly I was competitive and suddenly I could earn.

1109
00:56:38,196 --> 00:56:40,936
So these hype videos come out there all the time.

1110
00:56:41,276 --> 00:56:43,576
These 3x'ing and 90%ing of what?

1111
00:56:43,576 --> 00:56:47,016
There's no base number, no baseline ever established.

1112
00:56:47,256 --> 00:56:47,516
How convenient.

1113
00:56:47,816 --> 00:56:57,596
And one of the reasons why they consider it a lot like Bitcoin, because one of the things they've done like Bitcoin, is they have built in a halving mechanism.

1114
00:56:57,736 --> 00:56:58,636
In fact, it just halved.

1115
00:56:58,796 --> 00:56:59,176
It's halving.

1116
00:56:59,436 --> 00:57:02,116
Tau just halved, actually, and it is up as a result.

1117
00:57:02,516 --> 00:57:04,416
This is one of the evangelists kind of explaining.

1118
00:57:05,136 --> 00:57:09,876
Well, don't forget, Tau BitTensor is built very similar to Bitcoin.

1119
00:57:09,996 --> 00:57:10,316
Of course.

1120
00:57:10,316 --> 00:57:15,196
21 million fixed supply of 21 million tokens having every four years.

1121
00:57:15,296 --> 00:57:17,136
You could just see those two things alone.

1122
00:57:17,336 --> 00:57:20,856
How many mids are going to get completely sucked in just by those two things alone?

1123
00:57:21,356 --> 00:57:23,456
The only thing that's different is BitTensor.

1124
00:57:23,736 --> 00:57:33,496
Besides the fact that it has a CEO, besides the fact that Barry's behind it and that Barry's the organizer of it and that he's selling early tokens to guys like Chamath and Rydalio.

1125
00:57:33,956 --> 00:57:36,136
Besides that, the only difference is.

1126
00:57:36,136 --> 00:57:41,916
21 million, fixed supply of 21 million tokens, a halving every four years. The only thing that's

1127
00:57:41,916 --> 00:57:49,216
different is BitTensor, again, the tau is the token, BitTensor abstracted away the incentive

1128
00:57:49,216 --> 00:57:53,356
mechanism. So it's a very similar idea. Let's give incentives for the people who help us. So

1129
00:57:53,356 --> 00:57:56,316
Bitcoin does that, gives incentives to the miners who validate transactions.

1130
00:57:56,616 --> 00:57:59,856
Yeah, it's called the scarcest asset on earth. Pretty good incentive. Okay.

1131
00:58:00,136 --> 00:58:05,896
But BitTensor gives incentives to people who come up with better and better AI models or whatever

1132
00:58:05,896 --> 00:58:08,736
the problems are that the subnets are trying to solve.

1133
00:58:08,996 --> 00:58:09,836
So it really is.

1134
00:58:09,896 --> 00:58:11,636
It's like the Bitcoin of entrepreneurship.

1135
00:58:12,476 --> 00:58:24,542
What do you think so far What is your how do you validate How do you validate that Like it such a subjective idea that well you saying someone who comes out with a better ai model well well so you have

1136
00:58:24,542 --> 00:58:30,722
to be in on the idea that ai is the most revolutionary technology ever and the most

1137
00:58:30,722 --> 00:58:36,122
scarcest precious thing we have is electricity and gpus this is something that this is something

1138
00:58:36,122 --> 00:58:40,182
that chamath on the all-in show has been positioning they had nvidia ceo on recently

1139
00:58:40,182 --> 00:58:42,062
and they talked about this.

1140
00:58:42,782 --> 00:58:44,182
Two days ago, you may not have seen this

1141
00:58:44,182 --> 00:58:45,262
because you were busy on stage,

1142
00:58:45,362 --> 00:58:47,302
but there was a training run

1143
00:58:47,302 --> 00:58:49,042
that happened in this crypto project

1144
00:58:49,042 --> 00:58:49,922
called BitTensor.

1145
00:58:50,402 --> 00:58:52,442
Subnet 3, they managed to train

1146
00:58:52,442 --> 00:58:54,322
a 4 billion parameter LAMA model,

1147
00:58:54,762 --> 00:58:55,662
totally distributed,

1148
00:58:56,002 --> 00:58:57,022
with a bunch of people

1149
00:58:57,022 --> 00:58:59,782
contributing excess compute.

1150
00:59:00,022 --> 00:59:01,602
But they were able to do it statefully

1151
00:59:01,602 --> 00:59:02,982
and manage a training run,

1152
00:59:03,362 --> 00:59:04,622
which I thought was like a pretty

1153
00:59:04,622 --> 00:59:06,482
crazy technical accomplishment.

1154
00:59:06,722 --> 00:59:06,942
Yeah.

1155
00:59:07,142 --> 00:59:08,242
Because it's like random people

1156
00:59:08,242 --> 00:59:09,782
and each person gets a little share.

1157
00:59:10,182 --> 00:59:12,362
Our modern version of folding at home.

1158
00:59:12,662 --> 00:59:13,102
Exactly.

1159
00:59:13,342 --> 00:59:13,462
Yeah.

1160
00:59:13,582 --> 00:59:16,842
So what do you think about the end state of open source?

1161
00:59:16,942 --> 00:59:22,642
Do you see this decentralization of architecture as well and decentralization of compute to

1162
00:59:22,642 --> 00:59:28,522
support open weights and a totally open source approach to making sure AI is broadly available

1163
00:59:28,522 --> 00:59:28,842
to everyone?

1164
00:59:28,842 --> 00:59:36,002
I believe we fundamentally need models as a first class product, proprietary product,

1165
00:59:36,002 --> 00:59:38,882
as well as models as open source.

1166
00:59:38,882 --> 00:59:47,882
These two things are not A or B. It's A and B. There's no question about it. And the reason for that is because models is a technology, not a...

1167
00:59:47,882 --> 01:00:05,522
Let's be clear what's happening here. Chamath is using this moment with the world's most famous CEO to pump his shitcoin. And Jensen's doing probably the best he can to give a sort of generic answer here. But Chamath is using this moment, maybe one of the largest moments for the show in this year, to pump a shitcoin.

1168
01:00:05,522 --> 01:00:16,222
Yeah, right. Maybe the idea of distributed training of models, that can be interesting. The idea of figuring out a way to exchange value to pay for that, sure. None of that seems to necessitate this exact technology.

1169
01:00:16,222 --> 01:00:33,102
No. Also, his buddy Jason Calacanis has been on X telling people to sell their Bitcoin and buy Tau. And now he's turned his podcast This Week in Startups basically into a Tau advocacy podcast. Today's episode's all about it. Here's a moment from last week's episode.

1170
01:00:33,102 --> 01:00:44,202
And I don't give financial advice, but if anybody's listening and you had a hundy that you were going to spend on some margaritas, I'm going to say, maybe drink some water a Friday night.

1171
01:00:44,902 --> 01:00:47,762
You know, get some filtered water, tap water, whatever, have a nice tea.

1172
01:00:48,142 --> 01:00:52,322
Put the other $99 into just buying a little towel for yourself.

1173
01:00:52,582 --> 01:00:53,142
Why not?

1174
01:00:53,342 --> 01:00:54,102
Not financial advice.

1175
01:00:54,682 --> 01:00:56,742
I think I'll take a margarita and some Bitcoin places.

1176
01:00:56,762 --> 01:00:59,542
It's starting to sound like an LML.

1177
01:00:59,962 --> 01:01:00,842
Yeah, it is.

1178
01:01:00,942 --> 01:01:01,782
Multi-level marketing.

1179
01:01:01,782 --> 01:01:03,362
Yeah, well, anyway, it is.

1180
01:01:03,862 --> 01:01:05,942
These guys kind of have a history of doing this.

1181
01:01:06,482 --> 01:01:11,022
I've played clips before on the show where they bragged about they got access to Solana.

1182
01:01:11,182 --> 01:01:31,769
And so they get some sort of stake in like a company and then they get the tokens And the stake in the company is locked up but the tokens aren And so they get to just dump on retail all they want And I had a clip I played I don know if I could find it but I had a clip I played maybe last year There was them just having a good old laugh In fact you know I bet you I could find it here

1183
01:01:31,769 --> 01:01:35,649
YouTube, they're inside of Twitter. And what these folks would do...

1184
01:01:35,649 --> 01:01:39,269
Okay, so this is the first part of the clip where Chamath, who is now, by the way,

1185
01:01:39,469 --> 01:01:43,709
pumping Tao, tells you how the scam works. This is from a couple of years ago.

1186
01:01:43,949 --> 01:01:48,089
YouTube, they're inside of Twitter. And what these folks would do when we talked about this,

1187
01:01:48,089 --> 01:01:52,769
the game that they played was they would get a team, they would create a token,

1188
01:01:53,389 --> 01:01:59,889
they would also buy equity at some crazy valuation. The equity was locked up, but the tokens were not.

1189
01:01:59,889 --> 01:02:04,929
and then they would put them on an exchange and sell them to unsuspecting people and they would

1190
01:02:04,929 --> 01:02:11,889
be able to dump these tokens and if you look inside of that trend what you're going to see

1191
01:02:11,889 --> 01:02:17,329
and brian just mentioned this those were the sale of securities except it was done in a completely

1192
01:02:17,329 --> 01:02:23,169
unregulated way so if the sec is really and the doj is really going to take this ftt token

1193
01:02:23,169 --> 01:02:28,809
issue seriously and what happened to ftx which they haven't this was back after ftx crashed

1194
01:02:28,809 --> 01:02:30,129
and everybody's like, something's got to change.

1195
01:02:30,569 --> 01:02:34,929
They're going to start to look at a bunch of other tokens and token sales,

1196
01:02:34,929 --> 01:02:38,169
and you're going to end up looking at some very well-known venture firms

1197
01:02:38,169 --> 01:02:39,049
inside of Silicon Valley.

1198
01:02:39,189 --> 01:02:40,049
Including his own.

1199
01:02:41,169 --> 01:02:44,949
Then, about 10 months after that, this next clip comes in.

1200
01:02:45,369 --> 01:02:47,529
So I saved this for us because I thought this might come back up.

1201
01:02:48,089 --> 01:02:49,609
This is later on the All In podcast.

1202
01:02:49,609 --> 01:02:50,329
They're heavy.

1203
01:02:50,509 --> 01:02:51,249
Good Lord.

1204
01:02:51,449 --> 01:02:53,009
They're heavy, dragging you down.

1205
01:02:53,129 --> 01:02:56,209
That's where you're hiding all that Solana, under your eyes.

1206
01:02:56,209 --> 01:03:00,689
you better clear that solana position what's your lockup 24 months

1207
01:03:00,689 --> 01:03:06,289
fuck no he's trying to sell it to me on text message yeah of course we're negotiating discounts

1208
01:03:06,289 --> 01:03:12,309
i just had the fact hey you're fucking the whole thing up bro you don't you don't think i'm holding

1209
01:03:12,309 --> 01:03:16,769
i'm holding you think i buy hundreds of millions of dollars of anything without a discount

1210
01:03:16,769 --> 01:03:21,529
everything is a discount everything's discounted you want to clear that position in an llc are you

1211
01:03:21,529 --> 01:03:25,429
saying i got a billion dollars of solana no bro i'm saying i have one but you know i brought it

1212
01:03:25,429 --> 01:03:31,069
to discount but you're holding correct ish yes okay yeah me too

1213
01:03:31,069 --> 01:03:50,209
all right let's wrap up with the state of the network it's block height 942 217

1214
01:03:50,209 --> 01:03:57,509
The price is currently $71,210 to one US, you know, you know what I'm saying.

1215
01:03:58,129 --> 01:03:58,869
It is what it is.

1216
01:03:59,409 --> 01:04:01,209
It is per dollars, 1,404.

1217
01:04:02,029 --> 01:04:02,429
I like that.

1218
01:04:02,449 --> 01:04:04,809
I got distracted by the 404 and lost my train of thought.

1219
01:04:05,009 --> 01:04:06,769
Did you mean Fiat fund coupons?

1220
01:04:06,849 --> 01:04:07,449
Yes, thank you.

1221
01:04:07,929 --> 01:04:28,855
Now we are still down 43 from our all high which was now a long cold 170 days ago if you can believe it October 6 2025 Our retarget date is set for April 4 2025 with an estimated difficulty upward adjustment of 3 Reachable Bitcoin nodes

1222
01:04:28,855 --> 01:04:35,535
on the network continues to decline at 23,957. Hopefully, we'll change that a little bit. This

1223
01:04:35,535 --> 01:04:41,935
network can get you firing up a node. Node up, everybody. And of course, whenever the network

1224
01:04:41,935 --> 01:04:45,775
fees are low, it's also a great time to experiment with Lightning. So take advantage of that.

1225
01:04:46,295 --> 01:04:50,675
Looking at everything, though, we're moving right along. Bitcoin Core 30 continues to get a bit more

1226
01:04:50,675 --> 01:04:56,055
adoption. And Bitcoin's looking better and better when priced in gold this week. So that's a nice

1227
01:04:56,055 --> 01:04:58,895
positive to see. And the state of the network is strong.

1228
01:04:58,895 --> 01:05:14,855
well thank you so much for joining me and boys thank you so much for joining us thanks for having

1229
01:05:14,855 --> 01:05:19,475
us it's nice to change it up a little bit i think it was just the boost i needed we'll be back to

1230
01:05:19,475 --> 01:05:24,335
the regular format i got so many clips and so many things to talk about but we'll have some very

1231
01:05:24,335 --> 01:05:28,875
useful links at thisweekinbitcoin.show so go check that for some of the resources and then

1232
01:05:28,875 --> 01:05:34,975
Let me know what you thought about some of the information and what other bits of node management you'd like to be covered in the future.

1233
01:05:35,055 --> 01:05:35,775
I don't know what it might be.

1234
01:05:35,855 --> 01:05:36,775
There's a lot of topics.

1235
01:05:37,135 --> 01:05:38,655
So we could use your suggestions.

1236
01:05:39,575 --> 01:05:42,635
Send us a boost with what you'd like us to explore in the future.

1237
01:05:43,275 --> 01:05:44,575
I'm sure we could probably cover it again.

1238
01:05:44,575 --> 01:05:47,815
And if you do make a node, you know, boost in and open a channel.

1239
01:05:48,055 --> 01:05:48,195
You're right.

1240
01:05:48,295 --> 01:05:48,515
Let us.

1241
01:05:48,595 --> 01:05:49,115
Yeah, dude.

1242
01:05:49,235 --> 01:05:55,535
If you, oh, if you set up a node this week and you got anywhere close to what we talked about, that's next level stuff.

1243
01:05:55,695 --> 01:05:57,575
I mean, what we talked about today is pretty advanced.

1244
01:05:57,575 --> 01:06:00,235
if you get close to it, you're doing really, really great.

1245
01:06:00,575 --> 01:06:01,755
So you got to let us know.

1246
01:06:01,995 --> 01:06:03,335
You got to send it in if that happens.

1247
01:06:03,695 --> 01:06:04,895
All right, that wraps it up for us.

1248
01:06:05,235 --> 01:06:07,435
Thanks so much for joining us on this week's episode of This Week in Bitcoin.

1249
01:06:07,915 --> 01:06:08,515
See you next week.

1250
01:06:27,575 --> 01:06:57,555
Thank you.

1251
01:06:57,575 --> 01:07:27,555
Thank you.