Re: The Cat, BIP draft discussion.

Dec 11 - Jan 22, 2026

  • The discourse within the Bitcoin development community encompasses a broad spectrum of opinions on how to manage and mitigate spam within the Bitcoin network, as well as the broader implications for the network's functionality and philosophical underpinnings.

Notably, the conversations reflect a deep engagement with both the technical and philosophical aspects of Bitcoin's design and operation.

One significant thread of discussion addresses the challenge of defining what constitutes spam on the Bitcoin blockchain. There is a recognition that non-monetary data has been part of Bitcoin's architecture from its inception, serving various functions beyond simple payment transactions. The Bitcoin network, conceptualized as a distributed timestamp server and order system, supports a range of applications including time-locked contracts, sidechain anchoring, and protocol upgrades through non-monetary signaling mechanisms. This multifaceted utility underscores the difficulty in categorizing non-monetary data as spam without undermining the network's foundational capabilities.

Another focal point of debate revolves around the nature of consensus-valid transactions, such as those involving inscriptions, ordinals, and OP_RETURN outputs. These transactions, which pay fees and are included by miners, challenge narrow definitions of spam as solely transactions that DoS (Denial of Service) the network. The contention here lies in the distinction between transactions that some may subjectively view as undesirable and those that technically burden the network. This raises questions about the role of miners, the fee market's effectiveness, and the potential dangers of imposing protocol-level censorship based on subjective judgments of transaction legitimacy.

Critics of proposals aimed at curbing certain uses of the Bitcoin network argue against conflating personal disapproval with technical definitions of spam. They highlight the importance of adhering to the consensus rules codified in the network's codebase rather than interpretations of Satoshi Nakamoto's original intent. Concerns are raised about the implications of attempting to police transaction purposes, emphasizing the autonomy of node operators to filter transactions according to their policy rules without resorting to changes in the protocol that could be perceived as censorship.

Throughout these discussions, there is an evident struggle to balance the desire for an open, decentralized network with the need to maintain its efficiency and integrity. Participants express a commitment to preserving the network's core principles while navigating the evolving challenges posed by its diverse uses. The dialogue reflects a nuanced understanding of Bitcoin's technical framework, the economic incentives at play, and the ideological commitments that guide the community's approach to development and governance.

Link to Raw Post

Thread Summary (17 replies)

Dec 11 - Jan 22, 2026

Message History

18 messages

Bitcoin MechanicOriginal Post
Dec 11, 2025/20:54 UTC
TwoLargePizzas
Dec 12, 2025/01:49 UTC
IP draft discussion Jonathan Voss
Dec 12, 2025/17:13 UTC
Greg Maxwell
Dec 12, 2025/23:40 UTC
Melvin Carvalho
Dec 13, 2025/03:54 UTC
Ataraxia
Dec 13, 2025/07:07 UTC
Greg Maxwell
Dec 13, 2025/15:02 UTC
Pepe Hodler
Dec 14, 2025/01:51 UTC
Nona YoBidnes
Dec 15, 2025/10:35 UTC
Greg Maxwell
Dec 15, 2025/16:04 UTC
Jonathan Voss
Dec 17, 2025/16:22 UTC
Greg Maxwell
Dec 19, 2025/03:31 UTC
John
Dec 21, 2025/05:07 UTC
Greg Maxwell
Dec 23, 2025/19:12 UTC
waxwing/ AdamISZ
Dec 24, 2025/17:19 UTC
Antoine Riard
Dec 30, 2025/14:36 UTC
Pepe Hodler
Jan 19, 2026/01:11 UTC
Claire Ostrom
Jan 22, 2026/01:14 UTC
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback