If you have never had to write a regex for input validation and parsing of data you didn't create, you don't know what you don't know and what you don't know is a fuck of a lot.

This community is built around a proof of work project. Do the proof of work. Read inventing bitcoin, read mastering bitcoin, and read mastering the lightning network. write some code that manipulates a large data set you didn't create and then fix all your edge cases until it actually works.

If you can't pass a test that shows you have equivalent knowledge to those experiences, you should not be writing public lists of "facts" about how bitcoin works acting like an expert who deserves to tell other people what node to run.

Opinions about how to solve a complicated and newly discovered problem can vary. Spreading incorrect facts about the problem doesn't help anything but your ego. If your knowledge about the subject is only from a few nostr posts and 2 podcasts by the guy you agree with, please shut the fuck up.

Reply to this note

Please Login to reply.

Discussion

Looks like assumptions again, Bill.

What I have found is if a majority of the network filters certain transactions, miners mining those transactions take on orphaning risk (due to worse compact relay) which can lead to them losing revenue.

This also makes it more expensive and involved to store data as Mara charges 2x the standard mempool fee, and methods like public keys cost more than inscriptions.

This does not stop data storage, but it does make it harder and more costly, eventually leaving them with nothing to do.

But filters don't and can't work for their stated goal.

The new wave of bitching is that a malicious actor could put CSAM on the chain leading to node runner arrests. All possible CSAM content is an infinite space and all possible encoding is an infinite space, so double impossible to filter preventatively. It would be hundreds or more blocks deep before the first arrests and we found out.

Anyone with that level of malice isn't going to be deterred by 2 sat a vbyte and possibly waiting 20 minutes instead of 10 on the 1 in 100 chance ocean hits the next block.

The XOR PR is a valid potential fix for that issue. Filters aren't. They are out here running a victory lap for a race they haven't even shown up for.

What % has to filter to reach that threshold?

Exponential curve with higher nodes = more impact per node

Not an exact one, depends of how much junk is in blocks too. Unlike the block size limit it does not discriminate against SegWit or normal data

In 2013, I had a friend working on a “regex project” while we were in college and living together and learning regex to support him in that endeavor was a lightbulb moment for me

nostr:nevent1qqs9492fgdfsehhvnh32acc9h3t3mnus7gakj8hfxte64dc9pk5elggpramhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtmfdemx76trv4esvm96tq

No. You’re speaking about the technology side of #BTC. It’s 2025. There is far more to #bitcoin than just the technology.

People can still accomplish #POW without code. 👩🏻‍💻 we have #artists #poets #military #etc

While I respect 🫡 those who built

The initial … #WeAreSatoshi is for everyone.

We want mass adoption in #USA. It won’t happen unless we have a larger nest 🪺

And no one has ever heard me ever try to speak about nodes 🤣. We all have our differences and it’s beautiful

😍

Respect 🫡