You seem to still have trouble with his name. :-)
If you still can't figure out who I am talking about, go get your crayons and construction paper, and I will slowly explain it to you.
Anyway, one person's "spam" is someone else's transaction.
That is false, what spam is on bitcoin is not up to me or my feelings.
The issue with defining all non-monetary data as spam (as was proposed on the dev list) is that it eliminates functionality Bitcoin has relied on since inception.
You either copied someone else's response on the email list, or you are that person re-using the argument here.
You are not aware of my reply to it as it keeps getting censored on the email list. So I will explain it here again.
By definition, if the data is required for bitcoin to function as money, it is monetary data, and not non-monetary data, and not spam. The idea that span and non-monetary data is required for bitcoin to work as money is non-sense.
Furthermore, the Cat BIP does not address all non-monetary data. The Cat only addresses proven spam like jpegs and spam UTXOs under 1000 sats. Things like op_return data and coinbase miner data are left unchanged.
Bitcoin was designed from v0.1 as a distributed timestamp server and ordering system, not solely as a payment processor. The genesis block contains non-monetary data, and early Proof-of-Existence uses pre-dated OP_RETURN.
Neither op_return nor proof-of-existance are needed or helpful for bitcoin to work as money. And neither op_return nor proof-of-existance are addressed or affected by the Cat.
Time-locked contracts (nLockTime) have existed since v0.1 and underpin CLTV/CSV-based constructions, including the Lightning Network, DLCs, and off-chain adjudication. Sidechain anchoring and systems like OpenTimestamps depend on Bitcoin’s immutability as a distributed order of events. Protocol upgrades themselves rely on non-monetary signaling via version bits and miner flags.
None of those you listed above are addressed or affected by the Cat. Please stop spinning your wheel over nothing at all.
As stated in the whitepaper, the proof-of-work chain is a solution to distributed timestamping and majority decision-making. Monetary transactions depend on this ordering. If all non-monetary data is defined as spam, Bitcoin cannot function as Bitcoin. The opcodes in v0.1 clearly show that it was intended to do more than "Send X from A->B"-and they weren't disabled due to philosophical opposition, but DOS, consensus etc concerns. Please note, this does not imply that bulk data storage belongs on L1, merely that "spam is easy to define as anything non-monetary" isn't as easy as one might think.
You are repeating the bullshit either you or someone else wrote on the email list.
None of the things you list here are affected by the Cat BIP. So you bringing them up us just a waste of time and energy.
Nobody is claiming that all non-monetary data is spam.
If a set of data is required for bitcoin to work as money, it is by definition monetary data, not spam.
And none of the stuff you listed is affected by the Cat BIP. And all data required for bitcoin to work as money is preserved with BIP110.
NO. People were putting down Luke Dash Jr.'s SOLUTION to those transactions that they don't like, NOT putting him down because he got his coins stolen.
Now you are just being dumb by reducing the definition of spam as "just transactions I don't like". It's absurd reductionism.
Bitcoin is money, period. If your transactions is not money, if it's obfuscating bullshit spam jpegs or BRC tokens or stamps, or whatever other bullshit in fake pubkey, fake scripthash, fake witness data, and shirting the dust limit, your transaction is not money, it's spam.
Your bullshit " interesting use cases" are not welcomed on bitcoin. And Satoshi just happened to agree with me when an other "use case" other than money was pushed on bitcoin:
Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin and BitDNS can be used separately. Users shouldn't have to download all of both to use one or the other. BitDNS users may not want to download everything the next several unrelated networks decide to pile in either.
The networks need to have separate fates. BitDNS users might be completely liberal about adding any large data features since relatively few domain registrars are needed, while Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.
So, as you see, those are not only "transactions I don't like", they are also transactions Satoshi didn't like.
Because if you believe Knots is the solution to "stop spam", you're definitely wrong.
Knots, BIP110, the Cat, and the Lynx are all steps in the right direction. If they are not enough, we will keep working until your stupid spam is out of bitcoin and you are sent back to your bullshit shitcoins.