A way to prevent spam | Bitcointalksearch.org

squatter

legendary

Activity: 1666

Merit: 1196

STOP SNITCHIN'

Quote from: erre on December 20, 2017, 12:50:57 PM

I was just wandering if there is a way to prevent spam tx from being included in the mempool.
If there is a way to identify irrational spam txts (like this guy do: https://mobile.twitter.com/sbetamc/status/943433491097714688 ) there should be a way to make them illegal without censhorship the blockchain...or not?

Systematically prohibiting/blacklisting transactions is censorship, and that would be particularly problematic at the protocol level. Miners are free to reject transactions that appear to be spam. Priority calculations were historically used to identify spam, and now the fee market deters it.

The problem is that an attacker with significant hash power can do the following: significantly drop the hash rate after difficulty adjusts upwards, spam the blockchain at different fee levels, and collect the block rewards (including his own spam). Part of the genius of Bitmain setting up several different pools is that it's very difficult to definitively prove this activity is occurring.

Stedsm

legendary

Activity: 3052

Merit: 1273

Anybody care to explain why "all" high fee as well as multi-output transactions should be considered spam? There are many entities such as exchanges, sportsbooks, gambling sites and even signature campaign managers who use to send multiple outputs into one to save all those fees, how is that considered as part of spam attack? (Correct me if I'm wrong here).

Though, I believe there's nothing that could classify those type of transactions out of the blockchain due to the protocol itself being bound to take each and every transaction involved to keep the ledger fully updated. But yeah, I saw some shitheads sending 1-100 satoshis to many addresses without any purpose and fee is way too high compared to the output itself and such transactions should really be stopped as they badly interrupt and mess up the whole network as well as mempool.

Ned Kelly

full member

Activity: 170

Merit: 101

Quote from: erre on December 20, 2017, 12:50:57 PM

I was just wandering if there is a way to prevent spam tx from being included in the mempool.
If there is a way to identify irrational spam txts (like this guy do: https://mobile.twitter.com/sbetamc/status/943433491097714688 ) there should be a way to make them illegal without censhorship the blockchain...or not?

Actually, you can for you own node mempool. Just change dust threshold and min fee for higher values.

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Quote from: erre on December 20, 2017, 12:50:57 PM

I was just wandering if there is a way to prevent spam tx from being included in the mempool.
If there is a way to identify irrational spam txts (like this guy do: https://mobile.twitter.com/sbetamc/status/943433491097714688 ) there should be a way to make them illegal without censhorship the blockchain...or not?

No. You can't exclude any transactions in Bitcoin or that would be considered as censoring, no matter what your agenda is.

There isn't a definitive way of telling which transactions are created with the intention to spam or not. Any statistics out there is a hunch at best. Even if you do implement this, you will have to get clients to reject blocks with those transaction in them since they are still considered as valid, albeit non-standard. It isn't a solution at all.

teyasio

member

Activity: 86

Merit: 10

Eventually people will wise up and not use BTC to transfer money. Which is what I'll do since my coins been tied up for nearly 2days. Never using a btc transaction ever again.

erre

legendary

Activity: 1694

Merit: 1207

I was just wandering if there is a way to prevent spam tx from being included in the mempool.
If there is a way to identify irrational spam txts (like this guy do: https://mobile.twitter.com/sbetamc/status/943433491097714688 ) there should be a way to make them illegal without censhorship the blockchain...or not?

Topic: A way to prevent spam (Read 230 times)