Unchained Podcast Summary

Episode: Bitcoin Core vs Knots: Why Developers Are Fighting Over a Coming Change (Ep. 918)

Host: Laura Shin
Guests: Chris Guida (Bitcoin & Lightning Dev, Educator), Adam Back (CEO, Blockstream)
Date: October 7, 2025

Episode Overview

This episode centers on the escalating debate within the Bitcoin developer community about the role of spam on the network and the appropriate response to a proposed change in Bitcoin Core. At the heart is a conflict between two Bitcoin node implementations—Bitcoin Core and Bitcoin Knots—over how to handle arbitrary data storage in Bitcoin blocks, especially in light of recent spam attacks, NFT-style data storage, and the technical and philosophical implications for Bitcoin's future as money.

Key Discussion Points & Insights

1. Defining the Debate: Spam vs. Censorship

• Spam on Bitcoin: Both guests agree that “spam” has been a recurring challenge, but disagree on the best way to address it.
  • Adam Back (02:02): Characterizes spam as an arms race, with new attempts rising as old solutions are circumvented.
  • Chris Guida (04:47): Sees a tension between fighting spam and preserving censorship resistance. Extreme spam filtration, he warns, can look a lot like censorship.

Notable Quotes:

• Chris Guida (07:59):

  “Basically, they just created all of this noise on bitcoin. They made it harder to sync a node and they made it harder to transact as somebody who's just trying to do payments... those are the most harmful kinds of spam.”

• Adam Back (10:59):

  “Knots is blocking some of those [protocols] and I think it gets pretty gray because some of them can be used to carry tether. Probably some bank, you know, demo or actual.”

2. Technical Background: What is Being Proposed?

• OP_RETURN Limit Change:
  The upcoming Bitcoin Core release proposes raising the “OP_RETURN” size limit for data in transactions from 83 bytes (policy limit) to potentially as much as 1 megabyte.
  • Bitcoin Core: Argues this would allow legitimate protocols to anchor data efficiently and safely, and that spam cannot be fully prevented.
  • Bitcoin Knots: Contends this would only encourage more spam, harming payments and node decentralization; advocates keeping the 80-byte limit.
• Taproot and Inscriptions:
  Sets context for ordinals and recent data-heavy NFT/meme token protocols.

Notable Quotes:

• Chris Guida (23:32):

  "What happened is in 2014... we would give these applications... a little space of 80 bytes.... And then in 2023... Casey Rodimore found a hack... a different way of putting arbitrary data in the chain which is not filtered... And so, you know, this went on for years. It's got more expensive to run."

• Adam Back (15:32):

  “As soon as you have a programming system, it can be... have data hidden in it in numerous ways. So... the original introduction of Opera turn in this format in 2014 was reactive to people spamming.... they made the OP return to at least say, well, if you're going to store application data and we can't deter you from it, at least do it in a way that doesn't get on the node up.”

3. Risk to Bitcoin as Money & Network Centralization

• Guida’s Concern:
  The priority should be payments; storage of large amounts of non-transactional data threatens the primary use case and usability for everyday transactions and merchants.
• Back’s Counterpoint:
  From a node operator perspective, large images are actually less harmful than protocols that bloat the UTXO set, and relentless spam filtering may provoke more harmful operator behaviors (“arms race” analogy).

Notable Quotes:

• Chris Guida (38:31):

  “If Bitcoin has to be saved by cramming data into blocks and... 100% of the activity on Bitcoin is data and 0%... is payments, then can you really call Bitcoin money anymore?”

• Adam Back (42:46):

  “Actually, lots of big images is a lot lower overhead for a node because the thing that slows the node down at worst is the BRC 20s, lots of abandoned UTXOs, large UTXOs. So actually a blockchain full of images is... the simplest and lightest thing for a node to process. Right. But that's nothing anybody wants, so it's kind of...”

4. Incentives, Economic Realities & Miner Behavior

• Spam “Whack-a-Mole”:
  Both recognize that completely filtering spam is likely impossible, as economically motivated actors will find ways around filters, especially if incentives are high.
  • Adam Back (46:38): “It’s not exactly futile, but you gotta be careful that the cure isn't worse than the problem. …as long as they're consensus-valid, they can go to a miner and get their blocks, their transactions processed.”
• Counter-history:
  Guida argues that hostility toward spam worked in 2014—pushing actors like Vitalik Buterin to create alternative blockchains.
  • Guida (48:49): “It's a cat and mouse game...it's a game that the...cat can kind of easily win.”

5. Layer-2s & “What’s Legitimate”

• What Counts as a True Scaling Solution?
  • Chris Guida (50:48): Draws a distinction between Lightning/Ark (which he considers legitimate, as they allow “trustless exit”) and newer protocols like Citria, which he views as insufficiently decentralized.
  • Adam Back (52:36): Pushes back, arguing these distinctions are arbitrary and harmful to developer experimentation.

6. The Node Count – Is Knots Support Real?

• Questions arose about the true popularity of Knots nodes; some analysis suggests many are not truly independent (“sybil” nodes), but both agree social consequences are more important than raw numbers.
  • Adam Back (56:27): "I think ultimately it doesn't really matter. And I think the bigger point is that even if naughts got to 90% or 99% or 100%, it wouldn't stop the spam."
  • Chris Guida (59:47): Points out that a lot of Knots nodes run on Tor, possibly undercounted.

7. Could This Lead to a Hard Fork or Major Split?

• Both guests suggest the risk of an actual chain split is low; the real effect is differences in relaying and node resource use, not consensus rules.
  • Adam Back (60:34): "The main damage from running a knots node is it creates a bit of extra load for other... nodes which are relaying more faithfully... but effectively it has nearly zero effect on spam and on the network ultimately. So it's not a fork issue."
  • Chris Guida (61:16): “If 80 or 90% of us are running the filters... we've seen that that's effective.”

Memorable Moments & Notable Quotes (with Timestamps)

• Chris Guida (06:55):

  “The biggest one recently has been, for lack of a better term, shitcoins, or as I like to call them, altcoin Ponzi. And these cause a lot of disruption on Bitcoin because they cause something called UTXO set bloat, which... makes it more costly to run a node. And then the other big problem is that it causes high fees, which crowds out merchants that are trying to use lightning.”

• Adam Back (28:02):

  "If about 10%... of nodes decide to relax a filter, the filter stops having any effect in the network as a whole. And there's a reason for that, which is there's many ways that data can route through the network and just organically connecting at random."

• Chris Guida (63:33):

  “Full RBF—the vast majority of node runners agreed with full RBF...Those are not that harmful. And that's why...when Core was filtering something that's harmless for that filter to go away...substat transactions are not that harmful and full RBF is not that harmful...Inscription spam, by contrast, is harmful.”

Important Timestamps

• [02:02–04:47] Introduction of the spam versus censorship dilemma.
• [06:46–08:32] Details on UTXO set bloat from NFTs and altcoin meta protocols.
• [15:32–21:34] Deep dive into OP_RETURN, its origins, and current debate.
• [23:32–26:09] Chris explains the history and consequences of increasing the OP_RETURN limit.
• [38:31–41:19] What’s at stake if data/pseudo-payments crowd out real usage; Adam’s “least-bad option” case.
• [46:38–48:49] Cost-benefit and futility of spam filtering; economic actors will find a way.
• [50:48–54:31] Layer-2s and legitimacy—arguments over what constitutes a “real” scaling protocol.
• [55:56–60:09] Node count, Sybil analysis, and social reality of Knots support.
• [60:34–62:26] Is a fork coming? Both say probably not: it’s a social policy fight, not a consensus code split.

Conclusion

This episode captures a pivotal moment in Bitcoin’s technical governance—a clash between pragmatic risk management (allowing larger OP_RETURN as the "least bad" output, per Core) and a principled defense of Bitcoin’s money/payments use case (Knots). Both guests underscore the complexity of trying to filter or block spam in a decentralized and economically driven system, wrestling with the legacy and future direction of the world's leading cryptocurrency.

The discussion is deeply technical, but also philosophical: What is Bitcoin for? Should it be a payments-first system or a general-purpose public data store? The answer, and the code change arriving Friday, will ripple through the Bitcoin world for years to come.