1
00:00:00,000 --> 00:00:05,980
Hey guys, this is Rudy Dazzleworth coming back at you with another plebslop Pulitzer article.

2
00:00:06,400 --> 00:00:14,300
This one is titled, How Overnight Not Grubbles Abandoned Everything He Believed About Bitcoin Spam by Justin Beckler.

3
00:00:14,800 --> 00:00:20,140
The article was originally posted on Twitter and can be found on Justin's Twitter page.

4
00:00:20,140 --> 00:00:29,680
The article includes multiple screenshots I will not be reading, just for efficiency in getting you this groundbreaking piece of pleb journalism.

5
00:00:30,000 --> 00:00:37,560
Something is happening to Bitcoin's anti-spam movement.

6
00:00:38,240 --> 00:00:42,460
One by one, accounts that spent years raging against inscriptions,

7
00:00:43,160 --> 00:00:47,000
warning about blockchain bloat and defending the right of ordinary node runners

8
00:00:47,000 --> 00:00:52,560
to sync and verify Bitcoin without downloading a sudden flood of spam have reversed completely.

9
00:00:53,160 --> 00:00:58,660
Or over two years, not Grubbles was one of Bitcoin's clearest and most aggressive voices

10
00:00:58,660 --> 00:01:00,100
against spam on the network.

11
00:01:00,600 --> 00:01:02,060
I was his biggest fan,

12
00:01:02,240 --> 00:01:03,640
and there are hundreds of tweets

13
00:01:03,640 --> 00:01:05,320
that could be embedded in this article

14
00:01:05,320 --> 00:01:07,200
to document why so many of us

15
00:01:07,200 --> 00:01:09,660
who are toxically opposed to spam on Bitcoin

16
00:01:09,660 --> 00:01:12,220
fist pumped every time he posted.

17
00:01:12,900 --> 00:01:14,600
Then something happened in August,

18
00:01:15,080 --> 00:01:18,620
a sudden and shocking 180 degree reversal

19
00:01:18,620 --> 00:01:20,080
on Bitcoin spam.

20
00:01:20,640 --> 00:01:23,000
This is the documented record of that reversal,

21
00:01:23,600 --> 00:01:27,020
sourced entirely from his own public posts on X.

22
00:01:27,020 --> 00:01:34,440
Note, since research for this article began, Grubbles has been actively deleting posts from his timeline

23
00:01:34,440 --> 00:01:40,560
and several damning tweets cited in earlier drafts are no longer accessible because I was a dummy

24
00:01:40,560 --> 00:01:43,940
and screenshots weren't captured before they disappeared

25
00:01:43,940 --> 00:01:50,300
Phase 1, the anti-spam warrior, 2023-2024

26
00:01:50,300 --> 00:01:56,580
when the first four megabyte inscription block was mined at the very beginning of the inscriptions

27
00:01:56,580 --> 00:02:05,000
exploit on February 1st, 2023 at Not Grubbles reacted the way any principled bitcoiner concerned

28
00:02:05,000 --> 00:02:10,720
about block space abuse would react. He wanted to filter it. He wanted to apply spam filtering to his

29
00:02:10,720 --> 00:02:19,600
own Bitcoin node. He saw Luke Dascher's filter patch as a sensible, necessary tool. In early 2023,

30
00:02:20,300 --> 00:02:25,740
This was a considered, technically informed position from someone who understood what was at stake.

31
00:02:26,240 --> 00:02:28,160
Over the following weeks, he went further.

32
00:02:28,620 --> 00:02:32,580
He raised alarms about what inscription spam was doing to the network's infrastructure,

33
00:02:33,100 --> 00:02:37,340
and he understood the problem through the lens of the people who actually run Bitcoin nodes.

34
00:02:37,880 --> 00:02:40,680
This is a precise, technically sound argument.

35
00:02:41,260 --> 00:02:47,680
Inscription spam bloats the blockchain, pressures node operators into pruning, and centralizes archival data.

36
00:02:48,240 --> 00:02:52,200
Fewer archival nodes means slower IBD for new participants.

37
00:02:53,120 --> 00:02:54,660
He understood the externalities.

38
00:02:55,120 --> 00:02:58,520
He articulated them clearly, and we all know that he was right.

39
00:02:59,020 --> 00:03:02,460
He called it what it was, repeatedly, without hedging.

40
00:03:02,460 --> 00:03:08,000
He also understood, and stated clearly, that spam degrades the ability to run a node.

41
00:03:08,620 --> 00:03:26,738
On December 9 2023 he connected the dots between spam and the real cost of syncing Bitcoin Harder to sink a full node Those are his words That was his concern He will abandon this argument completely within 18 months

42
00:03:27,358 --> 00:03:35,298
By late December the 20th, 23, his position had only hardened. When the Atomicals ARC20 Quark

43
00:03:35,298 --> 00:03:40,378
token launched, requiring approximately 1 million on-chain transactions to mint out,

44
00:03:40,378 --> 00:03:48,018
his response was unambiguous. He warned about JPEG spam outpricing lightning on-chain operations,

45
00:03:48,498 --> 00:03:53,858
precisely the kind of economic displacement that spam inflicts on legitimate Bitcoin users.

46
00:03:54,438 --> 00:04:07,798
In November 2024, he was still fighting the same fight. Phase 2. The Last Stand, April to June 2025.

47
00:04:07,798 --> 00:04:15,118
Through the first half of 2025, Not Grubbles maintained his anti-spam position with full conviction.

48
00:04:15,838 --> 00:04:19,978
He was the favorite repost of those of us in the toxic anti-spam group.

49
00:04:20,518 --> 00:04:29,518
He praised Luke Dasher's work, defended Bitcoin Nots, and continued warning about what non-monetary arbitrary data, spam, was doing to Bitcoin.

50
00:04:30,338 --> 00:04:31,278
You know he's right.

51
00:04:31,278 --> 00:04:35,978
Those are his words about the developer who has dedicated years of his life to

52
00:04:35,978 --> 00:04:40,898
building spam filtering tools for Bitcoin. The Stallman comparison is very

53
00:04:40,898 --> 00:04:45,278
specific. It means Luke is the uncomfortable truth-teller who's correct

54
00:04:45,278 --> 00:04:49,538
about spam and filtering even when the crowd doesn't want to hear it. In June,

55
00:04:49,538 --> 00:04:53,338
he was still articulating the case against blockchain bloat with the

56
00:04:53,338 --> 00:04:57,978
precision of someone who genuinely understood what was at stake for the

57
00:04:57,978 --> 00:05:04,398
people who actually run this network. It's significant to note that Post is from June 16th.

58
00:05:04,838 --> 00:05:12,238
He's explaining, in his own words, why monetary arbitrary data, spam, on Bitcoin degrades nodes

59
00:05:12,238 --> 00:05:19,098
and harms decentralization. On the same day, he called uploading JPEGs to a proof-of-work

60
00:05:19,098 --> 00:05:25,598
blockchain stupid and expressed visceral frustration about AML-compliant freezable

61
00:05:25,598 --> 00:05:31,598
runes being deployed on Bitcoin. He was also still defending the ability of ordinary people

62
00:05:31,598 --> 00:05:37,118
to run nodes on limited hardware and still thinking about centralization pressure from

63
00:05:37,118 --> 00:05:45,638
blockchain bloat. August 2025. Something changed. In August, Not Grebbles reversed his entire

64
00:05:45,638 --> 00:05:52,418
position on Bitcoin spam. The transition was sudden and stark. There's no post explaining why,

65
00:05:52,418 --> 00:05:57,738
no engagement with his former arguments, no retraction of the Stallman comparison.

66
00:05:58,538 --> 00:06:02,258
The reversal simply happens, like a switch was flipped.

67
00:06:02,718 --> 00:06:06,178
What's publicly known is that NotGrebles currently works at Second,

68
00:06:06,658 --> 00:06:11,978
a company building Bitcoin apps and payment infrastructure on Bitcoin using the ARK protocol.

69
00:06:12,618 --> 00:06:14,678
Before that, he was at Blockstream.

70
00:06:15,218 --> 00:06:17,778
The Blockstream connection deepens the pattern.

71
00:06:17,778 --> 00:06:25,778
Blockstream, where CEO Adam Back has followed a strikingly similar reversal arc on Bitcoin spam.

72
00:06:25,778 --> 00:06:42,176
Andy er I mean Adam was also once one of the clearest voices against non abuse of block space yet has also done a shocking complete about Not Grubbles appears to have carried this institutional DNA with him

73
00:06:42,716 --> 00:06:44,836
The trajectory is almost identical.

74
00:06:45,596 --> 00:06:50,596
Principled opposition to spam, proximity to companies whose revenue models benefit from

75
00:06:50,596 --> 00:06:56,636
keeping block space open to arbitrary data, and then a quiet capitulation under the pretense

76
00:06:56,636 --> 00:07:01,976
of intellectual evolution, but staunchly maintaining the absurd pretense of

77
00:07:01,976 --> 00:07:05,616
very, very opposed to spam on Bitcoin, of course.

78
00:07:06,196 --> 00:07:08,036
When the same reversal keeps happening

79
00:07:08,036 --> 00:07:10,056
to people connected to the same institutions,

80
00:07:10,376 --> 00:07:12,796
at some point you stop calling it a coincidence

81
00:07:12,796 --> 00:07:15,296
and start calling it a sinister pipeline.

82
00:07:16,036 --> 00:07:20,836
Phase three, the brand new not grubbles, August to present.

83
00:07:21,476 --> 00:07:24,556
By August, the account that years calling inscriptions

84
00:07:24,556 --> 00:07:27,496
JPEG spam and fighting for node runners

85
00:07:27,496 --> 00:07:30,176
began mocking anti-spam advocates

86
00:07:30,176 --> 00:07:34,176
and attacking anyone who wanted to protect Bitcoin's monetary purpose.

87
00:07:34,176 --> 00:07:40,976
By October, the man who once called a million shitcoin transactions an obvious spam attack

88
00:07:40,976 --> 00:07:46,476
was dismissing the entire phenomenon as tourist hype that had already resolved itself.

89
00:07:47,176 --> 00:07:53,536
By October 19th, anti-spam advocates were no longer fellow Bitcoiners with legitimate concerns.

90
00:07:54,176 --> 00:07:55,156
They were tyrants.

91
00:07:55,956 --> 00:08:01,356
By November, he was openly mocking anyone who believed spam had harmed Bitcoin at all.

92
00:08:01,856 --> 00:08:05,336
And on December 14th, he gave up the game entirely.

93
00:08:05,336 --> 00:08:09,576
The small block size and fee market already solved spam, he said,

94
00:08:09,896 --> 00:08:13,696
as if his years of raging about inscription spam had never happened.

95
00:08:14,356 --> 00:08:17,216
He had turned on Luke Dascher entirely,

96
00:08:17,816 --> 00:08:21,436
publicly questioning whether Luke should retain his DNS seed privileges.

97
00:08:21,436 --> 00:08:26,376
the developer whose filter he once considered patching into his own node

98
00:08:26,376 --> 00:08:30,456
the man he compared to Richard Stallman had become a target

99
00:08:30,456 --> 00:08:34,096
and then came December 14th, 2025

100
00:08:34,096 --> 00:08:39,956
he admits he was early on pretty determined to hinder the ability to spam Bitcoin

101
00:08:39,956 --> 00:08:41,816
he acknowledges the flip

102
00:08:41,816 --> 00:08:47,316
then he calls the people still holding the same position he held for years the real threat

103
00:08:47,316 --> 00:08:52,856
The anti-spammers will actually destroy Bitcoin if they get their way.

104
00:08:53,536 --> 00:08:56,836
He once said Luke Dascher was right about spam filtering.

105
00:08:57,456 --> 00:09:00,816
He now says the people who agree with Luke will destroy Bitcoin.

106
00:09:01,376 --> 00:09:05,636
By early 2026, the transformation was shockingly complete.

107
00:09:06,476 --> 00:09:07,476
Follow the incentives.

108
00:09:08,356 --> 00:09:14,796
He works at Second, a company building the ARK protocol and lightning payment infrastructure on top of Bitcoin.

109
00:09:14,796 --> 00:09:17,776
Before second, he was at Blockstream.

110
00:09:18,376 --> 00:09:21,696
His career depends on building application layers on Bitcoin.

111
00:09:22,256 --> 00:09:29,676
Companies that build applications and protocols on Bitcoin's data infrastructure have a financial interest in a permissive base layer.

112
00:09:30,316 --> 00:09:34,376
They benefit when block space accommodates broad usage patterns.

113
00:09:35,116 --> 00:09:40,476
They are harmed when the community enforces monetary discipline on what belongs in a Bitcoin block.

114
00:09:40,476 --> 00:09:47,696
A developer at a company building dApps on Bitcoin who simultaneously advocates for filtering

115
00:09:47,696 --> 00:10:01,414
non data from blocks has a problem That problem resolved itself publicly in August 2025 Correlation is not causation but when a person reverses every logical sensible

116
00:10:01,934 --> 00:10:04,194
technically sound position they held for years

117
00:10:04,194 --> 00:10:07,234
in a matter of days with no public explanation,

118
00:10:07,774 --> 00:10:10,134
while employed by a company whose business model

119
00:10:10,134 --> 00:10:11,314
benefits from the reversal,

120
00:10:11,894 --> 00:10:13,874
the conclusion is pretty obvious.

121
00:10:14,454 --> 00:10:15,214
Who benefits?

122
00:10:16,074 --> 00:10:20,214
Every company building non-monetary applications on Bitcoin

123
00:10:20,214 --> 00:10:25,274
benefits from the anti-spam movement losing a vocal and credible advocate.

124
00:10:25,954 --> 00:10:27,654
Opponents of Bitcoin benefit.

125
00:10:28,354 --> 00:10:28,894
Who loses?

126
00:10:29,754 --> 00:10:30,274
Node runners.

127
00:10:30,894 --> 00:10:35,674
Every ordinary Bitcoiner, not Grubbles, once claimed to be fighting for.

128
00:10:36,234 --> 00:10:41,774
Yet another tax on nodes and yet another compromise for which the node runner is not incentivized.

129
00:10:41,774 --> 00:10:47,374
The irony is that two years ago, Grubbles would have been the first person to write this article.

130
00:10:47,374 --> 00:10:52,754
He would have found the receipts, posted the screenshots, and called it exactly what it looks like.

131
00:10:53,154 --> 00:10:54,274
What happened to Grubbles?

132
00:10:55,094 --> 00:10:56,894
Stefan Lavera is next.

133
00:11:00,434 --> 00:11:05,454
Thank you for listening to this special episode of Plebslop Pulitzer Prize Pieces.

134
00:11:05,894 --> 00:11:10,814
My name is Rudy Dazzleworth, and I hope you have a fantastically fruity day.

135
00:11:11,174 --> 00:11:12,294
I'll see you soon.

136
00:11:17,374 --> 00:11:47,354
Thank you.

137
00:11:47,374 --> 00:12:17,354
Thank you.

138
00:12:17,374 --> 00:12:47,354
Thank you.

139
00:12:47,374 --> 00:13:17,354
Thank you.