No sudden spike, correct, but 1 month after (with 10% of nodes running Core 30) there should already be a visible effect, if the theory that "Core 30 incentives spam" is true.
But it isn't, there is no such incentive. I will continue to observe.
You would have to be incredibly naive to believe that core 30 facilitates an other way to spam the chain, and that somehow no spammer anywhere is going to take advantage of it.
We knew and agreed on both sides that the existing offenders won't switch to op_return. Both sides have made that very clear.
Core failed to provide the nodes with any sort of filters since this spam attack started some 5 years ago. Always the same excuses:
- Those are valid transactions
- They paid their miner fees
- We can't do it, and even if we could, we shouldn't.
- It would compromise the censorship resistance of the network.
- Miner fees will drive them out but by pure magic not drive out real bitcoiners.
All those were excuses not to do anything about the spam as if it did not constitute an attach.
But they went too far when they started to reject PR's with code already done to implement filters. All over bullshit reasons. Because spammers were bitching about censorship and based on a new definition of arbitrary data they just came up a week earlier.
Than they blew wide open the op_return filter. Effectively creating a new use case for spammers.
Sorry friend, core has been marked as deprecated.
You're contradicting yourself. Does OP_RETURN now increase spam? Well, if not, what's the problem then?
Core 30 is creating a new use case for spam. How long before they figure that out and start spamming the chain? Let me consult my crystal ball, shall I?
Hint: It won't increase spam levels
That is incredibly naive.
but if data protocol developers care about Bitcoin, they will slowly switch from harmful fake public keys to less harmful OP_RETURN. That's all that's intended with that change.
Bitcoin is money, not an arbitrary data storage facility. If your protocol requires 100,000 bytes of dara to be stored on 25,000 machines until the end of time, I say go back to your drawing table. Design your shit better.
And I'm annoyed that you think for the changes to affect spammers, they would have to act right away. But for the changes to affect legit devs, that takes time. You use two different yard sticks here.
No, there is no new use case. Everything is possible already with the old techniques.
Everything we are seeing is possible with the old techniques, yes. But none of it was sanctioned. They had to trick the system with things like fake pubkeys, and pass off a picture as a legit witness, along other tricks to fool the system.
It was clear to everyone involved, they were crashing the party.
But that's no longer true. Now we have a sanctioned space for them in op_return. They are no longer crashing the party with they junk, they would be effectively using the system as it's designed for them to use.
I have written in other threads that indeed this is an argument that sounds good at a first glance.
But I don't think it will have any effect. Not on the "degens", as they call themselves, (who are proud of their Taproot hack) that use Ordinals and Stampchain. And much less on people doing illegal stuff.
And OP_RETURN means "nothing to see here". It is a signal to nodes that they can ignore everything behind that opcode. It's thus a signal that data isn't wanted or needed on the Bitcoin blockchain.
Attention economy exists too.
While I admit talking about it might raise their antenna sooner, it's not an important part.
No, because it doesn't work until you don't tackle the fake public key spam.
There is a way to stop fakevpubkeys from occurring, it's not very popular, and would require sweeping changes in every existing wallets.
In any way, fake pubkeys have always been accesible. I believe if we get rid of the other spam methods, we would get far less spam over all.
An ordinal, or a runestone, or a brc-20 token in a fake pubkey would still be visible and still could be filtered out.
Creating more and more ways to spam, not doing anything about spam, those are not the right way to deal with it.
Please propose an effective filter and I'll ready to support it if it has no negative side effects (like confiscating coins).
Well, for starters, a segwit filter already exists in Knots. It limits the amount of data you can put in Segwit. So that would make ordinal spam drastically more expensive.
Ultimately, you have to ask yourself why they keep repeating the stoopit idea that filters don't work. Than go ahead and try to turn off the filters.
If the filters don't work, why would they need to turn off the filter? Citrea might as well us the op_return with the filters up, no?
It's contradictory. Filters don't work but they need to turn them off in order to do the very thing the filters were preventing you from doing. It's absurd logic.
