Revision history · Transcript
Transcript: The Case for a Third Implementation | Pleb Slop Pulitzer Price Pieces Episode 4
1 revision · first seen 2026-08-12 · last edited 2026-08-12 · 0 by Henry 1 by a human
- bugle-ingest[bot] 2026-08-12 Ingest: 0 new episode(s) — raw sources + transcripts 32a9a2b
Show changes
diff --git a/wiki/transcripts/the-case-for-a-third-implementation-pleb-slop-pulitzer-price-pieces-episode-4.md b/wiki/transcripts/the-case-for-a-third-implementation-pleb-slop-pulitzer-price-pieces-episode-4.md new file mode 100644 index 00000000..bb230f8f @@ -0,0 +1,27 @@ +--- +title: "Transcript: The Case for a Third Implementation | Pleb Slop Pulitzer Price Pieces Episode 4" +type: transcript +episode: the-case-for-a-third-implementation-pleb-slop-pulitzer-price-pieces-episode-4 +generated: true +date: 2026-04-17 +audio: "https://feeds.fountain.fm/R8scBF2Wiykm0YVldsHQ/items/fhcO8m7UmwXipeN499n0/files/AUDIO---DEFAULT---b9694872-3786-4da9-aa25-fc418a7a276b.mp3" +duration: "3:32" +sources: + - raw/episodes/the-case-for-a-third-implementation-pleb-slop-pulitzer-price-pieces-episode-4/bundle.json +--- + +<p class="cue-p"><a class="cue-t" href="#t-0">0:00</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-0" data-t="0">Hey, Queens. This is Rudy Dazleworth again. Boy, do I have a special one for you today. This one is called The Third Way,</span> <span class="cue" id="t-8" data-t="8">The Case for a Third Implementation</span> <span class="cue" id="t-10" data-t="10">by Jimmy Song. Buckle up buttercups because this is another episode of Plebslot Pulitzer Prize</span> <span class="cue" id="t-19" data-t="19">Pieces. Bitcoin development has gotten political.</span> <span class="cue" id="t-22" data-t="22">Over the past year, the accusations, name calling, and tribalism have gotten out of hand. People aren't debating technical merits.</span> <span class="cue" id="t-30" data-t="30">They've essentially been reduced to picking teams.</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-33">0:33</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-33" data-t="33">I don't think this is because Bitcoiners are bad people. I believe this is a structural problem.</span> <span class="cue" id="t-39" data-t="39">The way Bitcoin software development is organized creates bad incentives and bad dynamics.</span> <span class="cue" id="t-45" data-t="45">And in this post, I'm going to show you how a third implementation is the fix, the monopoly problem.</span> <span class="cue" id="t-52" data-t="52">For most of Bitcoin's history, there has been one dominant implementation,</span> <span class="cue" id="t-57" data-t="57">which means power is concentrated in one place.</span> <span class="cue" id="t-61" data-t="61">One process for everything,</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-63">1:03</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-63" data-t="63">one set of gatekeepers,</span> <span class="cue" id="t-65" data-t="65">one on ramp for developers.</span> <span class="cue" id="t-67" data-t="67">One implementation</span> <span class="cue" id="t-68" data-t="68">is, by definition, a single point of failure.</span> <span class="cue" id="t-71" data-t="71">The incentives under a monopoly are terrible.</span> <span class="cue" id="t-74" data-t="74">First,</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-75">1:15</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-75" data-t="75">goals are unclear or nonexistent.</span> <span class="cue" id="t-78" data-t="78">Having them is actually problematic as you get accusations of centralization</span> <span class="cue" id="t-82" data-t="82">and favoritism.</span> <span class="cue" id="t-84" data-t="84">But without explicit goals for the project,</span> <span class="cue" id="t-86" data-t="86">visibility becomes the goal.</span> <span class="cue" id="t-88" data-t="88">Developers get rewarded for shipping something big and attention grabbing,</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-92">1:32</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-92" data-t="92">not for doing the boring work of securing the network. They need to make their mark so they can attract grants and keep funding flowing.</span> <span class="cue" id="t-100" data-t="100">That may or may not have anything to do with what Bitcoin needs. I don't blame the developers for this, because the structure made it inevitable.</span> <span class="cue" id="t-108" data-t="108">The other problem with a monopoly is that it's one size fits all.</span> <span class="cue" id="t-112" data-t="112">There are many different reasons to run a node, and many different kinds of node operators.</span> <span class="cue" id="t-117" data-t="117">A miner has very different priorities from a merchant.</span> <span class="cue" id="t-121" data-t="121">An exchange cares about things a home node runner doesn't. A block explorer would love to have an address index, but Bitcoin Core doesn't have an address index, and probably never will, because they don't wanna be everything to everybody.</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-135">2:15</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-135" data-t="135">But when you're the only implementation,</span> <span class="cue" id="t-137" data-t="137">that's exactly what you end up having to be, and you end up serving nobody particularly well.</span> <span class="cue" id="t-143" data-t="143">Worst of all, users have almost no say under a monopoly.</span> <span class="cue" id="t-147" data-t="147">Their preferences have to filter through GitHub issues and development processes that most of them don't understand or participate in,</span> <span class="cue" id="t-155" data-t="155">and developers have very little incentive to listen.</span> <span class="cue" id="t-159" data-t="159">That's not to say that they don't. I'm sure many of them care about what users want.</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-164">2:44</a><span class="cue-body"><b class="cue-who">Richard Greaser</b> <span class="cue" id="t-164" data-t="164">But the incentive to listen isn't there because there's no real alternative.</span> <span class="cue" id="t-168" data-t="168">If you wanna run Bitcoin, you run core.</span> <span class="cue" id="t-171" data-t="171">The devs know that. They're not incentivized to be attentive to user feedback because the users have nowhere else to go.</span> <span class="cue" id="t-178" data-t="178">In other words, there's no market pressure and no accountability loop. The developers are incentivized to answer to their grant funders and to each other,</span> <span class="cue" id="t-187" data-t="187">not to the people actually running the software.</span></span></p> + +<p class="cue-p"><a class="cue-t" href="#t-190">3:10</a><span class="cue-body"><b class="cue-who">Rod Palmer</b> <span class="cue" id="t-190" data-t="190">You have just listened to a preview of Plebslop</span> <span class="cue" id="t-192" data-t="192">Pulitzer prize pieces with Rudy Dazleworth.</span> <span class="cue" id="t-195" data-t="195">If you would like to hear the full piece, please subscribe to the Bugle weekly on the Fountain podcasting app. By subscribing, you get access to all sorts of premium content as well as the opportunity to support the world's most thermodynamically</span> <span class="cue" id="t-208" data-t="208">sound credentialed journalism.</span> <span class="cue" id="t-210" data-t="210">Thank you for being a listener of the Bugle Weekly.</span></span></p>