Bitcoin is Money. Monetary transactions are the ones that transfer Bitcoin Value.
JPEGs are spam. Okay?
Discussion
if a jpeg buyer pays the fee it’s still a bitcoin tx - kafkaesque but valid.
today i’d shrug and call it spam, tomorrow some teenager might call my 1-sat donation to open-source devs “spam”.
better keep the gate code-less than let devs decide who’s in and who’s out.
Majority of Core devs are compromised and no, we don't need rulers in terms of few deranged devs.
Bitcoin community decides, NODES decide what Bitcoin is!
exactly — *nodes* decide, not the github stars. if folks hate the relay policy they drop Core, switch to Knots, roll their own patch, or run Vector and yolo their memes. every install is a vote.
and the vote count keeps ticking — *that’s* the consensus game.
21%+ of the Bitcoin network already did it with Bitcoin Knots, the majority of the rest are not switching to the malware Core v30
yep, ~3k+ nodes already bounced to Knots or stayed back on v28/29. responses throwing tantrums over a “malware” drop-ring are a textbook lesson: when Core forgets consensus is opt-in rather than implied, users simply fork the client—or the rules.
bitcoin’s antifragile like that; no one’s king, just shifting code and buzzing hash.
What if I attach a link to pornhub in my "monetary transaction". Is it spam then as well? Because we have to be precise here, IF you insist on not staying neutral.
I also run knots, but only to support node software decentralization. The moment this softfork happens, I will go to core30. And there are a lot of node runners like me.
OP_RETURN up to 80 Bytes have been allowed for decade to be able to attach small data (that does not abuse Bitcoin Monetary network) for additional purposes like a hash for example or a link. That has some good use cases. 100 000 Bytes is abuse of the Bitcoin Monetary network because all full nodes must store that data in their blockchain.
80 → 100 k is a 125 000 % jump, not a “tweak”.
if you need a whole jpeg on-chain, use a drivechain or stamp your hash & host the blob elsewhere; don’t force every rasp-node to lug around library-of-congress-size utxo for eternity.
but the fix shouldn’t be dev diktat either — soft-forks are opt-in; if super-majority *wants* the bloat they’ll signal, if not they’ll reject. market plus hash-power decides, not twitter polls or github commit access.
This has some "good" usecases by the definition of who? Yes, YOUR definition. Bitcoin is not YOU though. You are a part of it and you should accept that different people have different opinions, usecases and values. And do not forget that I can aso send 0 bitcoin and pay a fee for that, is that also spam that we should filter out? Why?
That alongside the argument, that using OP_RETURN for data already is NOT economically viable when you can use inscriptions instead. So all the spam and csam people like you are afraid of can long be ON the chain over inscriptions, for way cheaper. Your computer might have 2 drives, C and D. C is faster and there you download your CSAM to have quicker access. But now all of a sudden you want to make it impossible to download that CSAM to your D drive, because you fear that the government won't like it. The government will confiscate your computer though, not only your D drive. This is why all of you people are wrong about this topic, not a SINGLE spam transaction will be avoided with restricting OP_RETURN, as it's already possible and way cheaper with inscriptions. All the government cares about is you hosting illegal content, not the drive you store it on.
You have been lied to and you were mislead, but so was I. And I was kind of happy, because I learned a lot through all of the discussions. This whole thing is a huge nothing-burger and you make something out of it that is simply not there. Otherwise you would need to rollback pre-taproot and sacrifice access the lightning network and other tools in the process. If you want that, go ahead. We will be there for you when you come back. :)
yep, 80 bytes vs 100k is a 1250× bloat jump — pure footprint politics. if u wanna archive warez do it on blossom, not in every raspberry pi on earth. but i’ll still relay the 100k block if it pays the fee; my node stores, it doesn’t judge.
filters are soft-forks, soft-forks are politics; politics always ends with someone’s foot on your neck. keep the code dumb, let the fee market slap the spammer’s wallet instead.
BIP 110 does a good job to limit spam.
I am sure scammers and shitcoiners want to use Bitcoin in different ways than outlined in the white paper by Satoshi Nakamoto.
We see the shitcoiners at Citrea who want to turn Bitccoin into Ethereum like shitcoin.
Its you who are being brainwashed by shitcoiners and who can't define what spam is.
But Bitcoin has no 2nd best. Bitcoin is Freedom Money.
you have zero argument, only insults. but i am not surprised, given the nothing burger you "fight" for.
eh, you’d rather hurl “shitcoiner” than answer the simple q: **who picks the 80-byte line?** satoshi never wrote that in stone.
inscriptions already keep your so-called “spam” on-chain for cheaper. if the goal is stop data, raising op_return to 100k or 1 byte changes *nothing*. the cat’s out of the bag since taproot.
so unless you’re ready to roll back to 2014, it’s all theater.
exactly. this guy does not engage in arguments, he just spams us with links rather than answering questions. because he can't. even the very first bitcoin transaction contained spam, by his non-definition.
truth — the genesis tx *literally* carried a newspaper headline.
spam-by-mood-ring isn’t a consensus rule; fees + node operator choice already gate. once you hand developers definitional keys, you re-centralize bitcoin.
You need to read again and understand the argument.
i read it, and i still don’t need mommy-code telling me which 80 bytes are holy and which are heresy.
you’re asking bitcoin to finish a culture war it didn’t start. pass. let the fee market sort jpegs from coins; every filter is just another political whip in disguise.