If you are running a node you are already storing questionable data. This bip won’t stop data you don’t like but it will destroys bitcoins ability to prevent itself from becoming the kyc coin.
Discussion
Fucking insane take. I just want the devs to focus on stopping the current spam. Not making future spam easier.
Using taproot inputs for inscriptions is fundamentally different than allowing large chunks of data in OP_RETURN. Inscriptions are backdooring the intended use of taproot. Opening op_return makes the data the intended use. Its not hard to understand.
Op_return was put in place a decade ago to prevent utxo pollution. You can’t stop utxo pollution, and it’s far worse for Bitcoin than OP_return spam.
You have the right to run your own node you don’t have the right to change the rules and roll back the chain to remove valid transactions.
Where in the link does it talk about rolling the chain back?
Sure, but nodes have the ability to make certain transactions invalid if the operators dont want to store bullshit on their computers for eternity.
Line 180 “If, however, some content appears in the chain that causes significant risks, we can fall back to the reactive method, which is a retroactive chain reorganization to invalidate the offending block (and any subsequent blocks) while immediately activating the new rules.”
This is the most retarded suggestion I have ever read. If you support this you are also retarded.
Ok i was uninformed. My b. I dont like the reactive approach but I dont see anything wrong with the proactive one.
OP_RETRUN change from 80 Bytes to 100 000 Bytes welcomes more spam and csam because it does not fix anything else.
It’s cheaper to use the witness discount.
It will always be possible to string together multiple transactions and pollute the utxo set.
Your constant accusations and harassment against people who are far more intelligent and with far more understanding of Bitcoin has backfired . You all sound retarded.
Weak propaganda from a spammer.
Just calling balls and strikes here pal. I find spam to be just as retarded as most of your comments, but I think handing over our future to lunatics like Luke jr is insane.
This proposal is ridiculous. A chain reorg? Where does it end. Do we go back to the genesis block and strip away satoshi’s message? Do we strip out Luke’s gay ass Bible shit?
Running a node is cheap as chips and nothing short of making the block size bigger is going to change that. Try holding some bitcoin if life is getting too expensive.
Bitcoin is Freedom Money.
Not a spam, csam, jpegs or any other arbitrary data dumpster.
By blowing up OP_RETRUN you invite more of it and you support that. That makes you a spammer.
Of course your bs propaganda speaks volumes too.
Here is Nick Szabo answer for you.
If it’s cheaper to other methods for some types of spam op return size is irrelevant.
If some types of spam is going to pollute the utxo set if it can’t use op return because of its size it is preferable to increase the op_return size than to encourage utxo bloat.
That is why there is this soft fork bip that fixes a lot of weaknesses that are exploited from spammers 🤙
New output scriptPubKeys exceeding 34 bytes are invalid, unless the first opcode is OP_RETURN, in which case up to 83 bytes are valid.
OP_PUSHDATA* with payloads larger than 256 bytes are invalid, except for the redeemScript push in BIP16 scriptSigs.
Spending undefined witness (or Tapleaf) versions (ie, not Witness v0/BIP 141 nor Taproot/BIP 341) is invalid.
Witness stacks with a Taproot annex are invalid.
Taproot control blocks larger than 257 bytes (a merkle tree with 128 script leaves) are invalid.
Tapscripts including OP_SUCCESS* opcodes anywhere (even unexecuted) are invalid.
Tapscripts executing the OP_IF or OP_NOTIF instruction (regardless of result) are invalid.
It doesn’t fix all spam vectors so all this means is more transactions and more utxo pollution. To fix all spam vectors you will have to destroy any hope of bitcoin scaling and multisig….and even then spam will find a way.
The reactive activation chaotic chain reorg portion is the most retarded thing I have read in a bip. Anyone supporting this will be outed as a glowie or a useful idiot. Which one are you?