Firstly Ocean and DATUM are two distinct things, I do not use Ocean but I use DATUM. Secondly other miners don't "validate" so if you want to just be pithy and pedantic, I can too.
I'm not confused, you either misread or didn't understand.
As for the why, beyond the bulwark of property rights and I can do whatever I want, refusing to propagate spam forces it to got through other channels that are more fragile. Where as Shinobi seems to think spam centralization is bad, I see it as good because it has one avenue of propagation and if that method fails, no spam.
I never once argued about performance. This is a property rights issue. And compelled speech issue. I don't want to "say" to the network I am passing along a spammers message. The fact that the spammer found another way to "say" that message is irrelevant. But on my property, with my speech, I refuse or at the very least reserve the right to refuse.
You node validates blocks from other miners that include the spam no matter what you do with datum and your miner. Perhaps I was unclear but I wasn't wrong.
Property rights is an argument I can respect. I think they should have changed the default but left the setting. I still think you are destroying your own property to spite your neighbors by running the mempool filter.
You absolutely said a slower ETH. Don't lie to my face about it 1 post later.
What speech is more important to you? Transient in your mempool gossip or what you share as valid block data with everyone for all eternity? If you help encourage them to op_return you can drop op_return entirely from your chain for all eternity, jokes on them.
I get that you see you node data as speech and don't want to stupid shit. I agree on principle. I'm valuing hosting that monkey jpg on chain for all eternity more than 10 minutes in my mempool gossip. You are choosing the opposite. No one knows a way to never share the monkey.
The ETH comment is the end result I forsee when the spammers use the witness anyway when Nodes start pruning OP_RETURN. I don't know where I lied exactly but I take your word that I wasn't clear either.
A year and a half ago there was an initiative to fix the filters but that was pushed aside as "censorship" so, that's perhaps why we never solved the monkey sharing problem.
Regardless, I think we see each other's postion we just disagree on outcome which neither of us know.
My assumption is that the kind of person who would trade in monkey jpgs isn't informed enough know any of those details about where on chain it is stored or going to take any path other than the cheapest possible to the next block.
1MB base and 3MB witness. I think they will end up split on chain once base is full and witness is empty.
2 problems with filters that combine to keep block validation filters from being taken seriously.
1 is they are just way harder than you think to get right if you've never had to write a regex.
2 is that any filter on valid blocks must allow all existing blocks or fork and rollback. we don't know what our adversary has cooked up to sneak through the filter till it hits mempool, or in your case gets in a block. That is too late to get the fixed filter in place.
Points taken. I have tried to write regex, did not go well. Put me off of coding entirely.
As for my filter removing my info on current attacks, I watch attacks outside of my own nodes. I query mempool.space nodes and a few others to keep up on what traffic that I don't relay. I still get the info just not on my own node.
That is fine for setting fees for manual on chain transactions but not very sovereign. It also not helpful for lightning justice transactions.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
