pull down to refresh
31 sats \ 8 replies \ @pakovm 16 Aug \ on: A Real SPAM solution: People using Bitcoin bitcoin
This is literally why non-filtards have been saying for 2 years.
Filters are retarded and a waste of time, just outbid the spammers, its that easy.
Not interested in hosting your cat jpegs or wizard pics. This database isn't some "common good". I have to run the damn thing. No Spam. Get out.
reply
It's impossible, from my limited understanding, to separate 'spam transactions' from 'spam data'.
A government could spam the chain by including transactions that literally move the same sats over and over... to the same addresses over and over.
Address A -> Address A -> Address A -> Address A...
Is a 'spam' transaction.
Is it spam? Yes. Do you 'store' it on your node? Yes. It's data, that your node stores unfortunately.
However Blocks are limited to 4 mb.
The way to 'stop' or 'mitigate' the spam? Outbid it.
reply
Those are monitarty transactions. Is it spam? No. I'm not filling up op return with stupid shit.
reply
If a government wanted to spend A to A to A to A at high fee rates over and over...
They could. It could bloat the chain, drive up fees, and make Bitcoin 'less' usable in a given time period.
Just because it doesn't have op_return or op_if -> op_endif doesn't mean it's not spam.
reply
reply
Let's start by not modifying the op return to allow unlimited filth.
reply
reply
To play the devil's advocate...
It's cheaper generally to spam in the witness than in op_return. Op_return is limited by 1 mb of block size...
Witness script is limited to ~ 4mb...
Spammers want to go where it does the most "damage" right?
reply