Posting this thread from nostr:nprofile1qyw8wumn8ghj7mn0wd68yttjv4kxz7fwwak8vuewwdcxzcm9qythwumn8ghj7mn0wd68ytnxd46zuamf0ghxy6t6qqsqyredyxhqn0e4ln0mvh0v79rchpr0taeg4vcvt64te4kssx5pc0sk99k65 here on Nostr for everyone's reference and my analysis of it: https://x.com/adam3us/status/1963830548012372324

My take:

**ADAM BACK DID NOT MENTION KNOTS**

People who called Adam “pro spam” (and worse) for weeks are now celebrating that “Adam is back.”

NEWSFLASH: he never left.

Obviously Adam freaking Back is not “pro spam” and never was.

He simply did not agree with the efficacy of the proposed "solution" (Knots node implementation) from a technical perspective (and still does not agree that node filtering of spam is a viable solution, based on my reading of his thread).

Instead, Adam is trying to lay out the *economic* case for how to deal with incentives to filter spam at the *miner/pool* level, while clearly stating “bitcoin is about money, spam has no place in the timechain. what defaults the bitcoin core project puts in the reference client matter in this."

Again, clearly Adam is not "pro spam."

A key line that jumped out to me was “to prevail, we have to make economic sense (or we work against our own objectives)”.

Adam focuses on *miners/pools*—and their economic incentives, or lack thereof—not on node implementations.

If you’ve spent the past weeks bashing Adam because you think he is a “spam apologist,” now is a good time to check your assumptions and consider that Adam wants what is best for bitcoin... as do you... as do I.

We ALL want what’s best for Bitcoin to make sure it succeeds as unfuckable sound money and a censorship-resistant medium of exchange.

No serious person is like "OOOH YEAH I LOVE SPAM! MORE JPEGS ON THE TIMECHAIN, PLEASE!"

It is possible to disagree with the efficacy of a proposed solution *without* being a "spam apologist."

Just because someone has a different opinion than you do about a solution does not mean that person is your enemy or has been "compromised."

This should be obvious but apparently it needs to be said...

nostr:nprofile1qyw8wumn8ghj7mn0wd68yttjv4kxz7fwwak8vuewwdcxzcm9qythwumn8ghj7mn0wd68ytnxd46zuamf0ghxy6t6qqsqyredyxhqn0e4ln0mvh0v79rchpr0taeg4vcvt64te4kssx5pc0sk99k65 -- I hope I have not misrepresented anything you said -- just trying to help parse your thread for my fellow plebs. Thanks for all you do.

Reply to this note

Please Login to reply.

Discussion

Lol. People thought the inventor of PoW spam prevention likes spam?

Well he didn't like knots so he's obviously pro spam (and also a big blocker). All cleared up now. #winning

Respectully, thats not how that works. If you broadcast a transaction to the network through your node, it goes to all the nodes you are connected too in order to be included into their mempool. The nodes will recieve that transaction and decided to included it or not. If one of the nodes that receives your transaction has a mempool policy that doesnt allow transactions with more than 80 bytes of op_return data (just an example) and your transaction has 120 bytes of data, that node will not included it in its mempool nor broadcast it to its peers. However, if there are enough nodes in the network that accept 120 byte transactions into their mempools and it makes it to a node run by MARA, MARA can decided to include that transaction in a block if it fits with their block template and mempool policy on their node. I hope that helped

What is Back saying to do specifically?

Just curious, do you expect to be spoon fed all the time, or are you able to chew on your own?

Ah. So “Respectfully” was a lie then 🖕

My bad. I figured somebody would be a bit more techinally inclined but I got you! Take your thumb and out and put it at the top of the screen and move it to the bottom until you see a link. Don't go to far though cuz you might miss it. What he said is in a link to another website called X where Adam put down what he said in English. I believe in you man! You got this!

The idea that running knots stops spam is silly.

And the idea that taking about user choice over mempool policy is also silly.

Therefore, run Knots, and pick whatever mempool policy you like, because Core doesn't trust you to make your own configuration decisions.

Or don't, and enjoy your custodial config file maintainers.

This is still a good sign. People need to come together. We agree on so much more than we disagree on

(Hopefully) looks like there’s gonna be massive pressure in these last 30 days before core 30 is shipped out to persuade core devs to change their mind.

Nobody was ever for raising from 80 bytes to100’000 bytes and taking away user configuration options. This is what was always all about, of course nobody wants spam in btc

Adam has admitted that filters work, in plain text: "filters mostly worked because people assumed they worked or most people are not sociopaths"

nostr:nevent1qqsft2gcmx3z4yp93t3qgxl9flf7hk3gw8637tr0cgcy6t6rafj2gkqpzpmhxue69uhkummnw3ezumt0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy2hwumn8ghj7un9d3shjtn90p5hgtnsw43z7t52jc6

The persistent asterisks helped me hear mean girl “no duh” tone and, ya know, it was effective.

The main issue here is core attitude.