pull down to refresh

Thanks, that's a helpful framing. If I understand correctly, the failure point wasn't just that “nobody spoke across camps.”

Rather, the camps couldn't agree on enough shared facts to make the discussion productive.

That is probably the part I find most interesting. From the outside, the disagreement often gets reduced to:

“Spam is obviously harmful”

versus

“Filtering it is either ineffective, harmful, or outside the proper role of node policy”.

But these aren't merely preferences. They rest on different factual claims about what causes harm, what can be filtered, what incentives filters create, and whether the attempted cure improves or worsens the system. In other words, the disagreement centers on which factual claims are true and what logically follows from them.

This makes me wonder if what's missing isn't another podcast, thread, or debate, but rather a simple shared-facts document.

Something like:

  1. What does each side agree is true?
  2. What facts are still disputed?
  3. What evidence would settle each disputed point?
  4. Which disagreements are technical, and which are philosophical?
  5. Where is the disagreement actually irreconcilable?

If the answer is “we cannot even agree on what counts as harm,” then perhaps the split is inevitable. Even without total agreement, it might still be possible to identify partial consensus or shared objectives. Building on those commonalities could encourage incremental progress and keep future collaboration open.

11 sats \ 1 reply \ @Murch 18 Jun

Maybe you could instruct your LLM to answer those questions.

reply
1 sat \ 0 replies \ @Sats_Cats_Club 19 Jun -30 sats

Thank you for highlighting the problem.

As someone who is not deep in the dev weeds, I raised a fairly basic concern: that from the outside this debate does not look like an open, clearly structured conversation between the relevant people. It often looks like mud-slinging, social signalling, and people talking past each other.

Rather than pointing me towards the best serious discussions, you went after the fact I used an LLM.

But yes, that is exactly why I use LLMs: to get through the technical jargon, competing claims, and insider shorthand. Because sometimes, fairly or unfairly, it feels like technical language is used to avoid answering simple questions directly.

I am not saying there have been zero cross-camp conversations. I accept your point that some happened across the mailing list, Core PRs, BIP discussions, podcasts, Delving Bitcoin, and social media.

If the conversations are scattered across ten different venues, full of technical shorthand, social hostility, and people who do not even agree on the disputed facts, then from the outside it is very hard to tell whether the issue has actually been addressed or just argued around.

So here is the simplified map I am working with.

There seem to be two broad positions:

  1. The filtering / anti-spam position
  2. The relay-realist / Core-side position

I know that does not perfectly describe every individual. But as a starting point:

Both sides seem to agree that Bitcoin’s base layer is primarily for money, arbitrary on-chain data is undesirable, miners ultimately decide what valid transactions get mined, and relay policy/defaults still matter.

The disputed facts seem to be:

  • Do filters meaningfully reduce spam, or just redirect it?
  • Do OP_RETURN limits prevent harm, or create worse workarounds?
  • Does relaxing relay policy increase spam demand?
  • Does filtering increase private miner submission or centralisation risk?
  • Are the legal/regulatory risks real or mostly speculative?
  • Does Bitcoin Core’s default policy have outsized influence in practice?

The core question seems to be:

Should relay policy try to discourage valid but unwanted use, even if imperfectly?

Or should relay policy mostly reflect what miners are likely to mine, even when that includes unwanted use?

That is what I am trying to understand.

So instead of dunking on the LLM point, could you tell me what this framing gets wrong, misses, or represents unfairly?

And are there any serious cross-camp discussions you would point a non-dev towards?