New penny-flood attack on network (very weak attempt)

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

Quote from: pooya87 on July 20, 2015, 02:24:19 AM

correct me if i am wrong but i have always though that you can not even send amounts that are less than the dust amount !
i think it is 5430 and if you try to send any amount less than that it is automatically being considered as fees and won't send it anywhere.

The "isDust" check was for 5430, but is now reduced to 543 Satoshi typically[1]. It will not prevent anyone from creating a TX with an output smaller not will it prevent miners from confirming it. All it does is that bitcoin core consideres the TX "dust" and does not relay it. This hinders propagation of transactions with these small outputs, but thats about all it does.

[1] https://github.com/bitcoin/bitcoin/blob/7cdefb927e928780cdbbb3a9b2ffe37716eebae1/src/primitives/transaction.h#L143

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: pooya87 on July 20, 2015, 02:24:19 AM

correct me if i am wrong but i have always though that you can not even send amounts that are less than the dust amount !

technically you can send amount = 1 satoshi and even 0 satoshi

Quote

i think it is 5430 and if you try to send any amount less than that it is automatically being considered as fees and won't send it anywhere.

wrong

pooya87

legendary

Activity: 3444

Merit: 10558

correct me if i am wrong but i have always though that you can not even send amounts that are less than the dust amount !
i think it is 5430 and if you try to send any amount less than that it is automatically being considered as fees and won't send it anywhere.

Soros Shorts

donator

Activity: 1616

Merit: 1003

Quote from: amaclin on July 19, 2015, 01:29:07 PM

Quote from: Herbert2020 on July 19, 2015, 01:25:02 PM

wow looks like blockchain.info does really ban showing these small inputs (spams) it was time they did something to prevent their service from going down so often!

Are you listening me?
Services like bc.i can ignore only unconfirmed transactions. These dust transactions are confirmed. And all fullnodes (and bc.i) have to handle these dust until somebody spend it.

While there is no way to ignore dust transactions that are already in blocks, there is no need to relay unconfirmed dust transactions or place them in memcache. A lot of dust transactions never get confirmed because many nodes are starting to filter them out and ignore them before then can even get confirmed.

wadili89

legendary

Activity: 1106

Merit: 1000

one day when hopfully bitcoin will be worth of 10,000 USA for 1 bitcoins then these spammers will regret even sending 1 satoshi for no reason however this is very small flood attack on bitcoin network i have seen alot bigger then this but still all the system survived it so i think spammers should take some lesson from this

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: Herbert2020 on July 19, 2015, 01:25:02 PM

wow looks like blockchain.info does really ban showing these small inputs (spams) it was time they did something to prevent their service from going down so often!

Are you listening me?
Services like bc.i can ignore only unconfirmed transactions. These dust transactions are confirmed. And all fullnodes (and bc.i) have to handle these dust until somebody spend it.

Herbert2020

legendary

Activity: 1946

Merit: 1137

wow looks like blockchain.info does really ban showing these small inputs (spams) it was time they did something to prevent their service from going down so often!

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: amaclin on July 19, 2015, 01:14:23 PM

Quote from: achow101 on July 19, 2015, 01:09:27 PM

Also, full nodes can be configured to reject or keep certain types of transactions.

Full nodes and miners have to keep all unspent outputs even dust if these outputs are confirmed in blocks.
They can not reject or prune confirmed transactions.

If the transactions are still unconfirmed, they can reject and prune them. Once the transaction becomes confirmed, the node will ask its peers for it and so on and so forth until every node has that transaction.

Lets just hope those dust transactions don't get confirmed.

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: achow101 on July 19, 2015, 01:09:27 PM

Also, full nodes can be configured to reject or keep certain types of transactions.

Full nodes and miners have to keep all unspent outputs even dust if these outputs are confirmed in blocks.
They can not reject or prune confirmed transactions.

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: amaclin on July 19, 2015, 12:41:35 PM

Quote from: dothebeats on July 19, 2015, 12:26:58 PM

1 satoshi isn't worth a penny yet.
Good thing that the network per se doesn't allow this kind of outputs to get through by means of not confirming them.

The problem that all fullnodes have to keep unspent transaction outputs in database.
And this database is growing.
BTW, some miners confirm transactions with such outputs.
For example, service www.originstamp.org send his shit-dust once a day from the address 1Fri

Well small outputs are considered dust. Dust transactions are typically considered non-standard and most full nodes will reject the transaction, refuse to relay, and not add it to their mempool. This pruning keeps the database size smaller and prevents the spam from affecting too many people. Also, full nodes can be configured to reject or keep certain types of transactions. There are commands and flags that can be used to set minimums for the fees and outputs.

AtheistAKASaneBrain

hero member

Activity: 770

Merit: 509

As far as I know spam attacks have been happening forever. Some people became aware of them only after the mega planned attack that got in the headliness, but other than that, i've been having the occasional dust incoming transaction since years ago.

SpanishSoldier

sr. member

Activity: 686

Merit: 255

Quote from: amaclin on July 19, 2015, 12:41:35 PM

Quote from: dothebeats on July 19, 2015, 12:26:58 PM

1 satoshi isn't worth a penny yet.
Good thing that the network per se doesn't allow this kind of outputs to get through by means of not confirming them.

The problem that all fullnodes have to keep unspent transaction outputs in database.
And this database is growing.
BTW, some miners confirm transactions with such outputs.
For example, service www.originstamp.org send his shit-dust once a day from the address 1Fri

WoW... that's a critical finding Wink

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: dothebeats on July 19, 2015, 12:26:58 PM

1 satoshi isn't worth a penny yet.
Good thing that the network per se doesn't allow this kind of outputs to get through by means of not confirming them.

The problem that all fullnodes have to keep unspent transaction outputs in database.
And this database is growing.
BTW, some miners confirm transactions with such outputs.
For example, service www.originstamp.org send his shit-dust once a day from the address 1Fri

dothebeats

legendary

Activity: 3542

Merit: 1352

Cashback 15%

1 satoshi isn't worth a penny yet. Good thing that the network per se doesn't allow this kind of outputs to get through by means of not confirming them.

amaclin

legendary

Activity: 1260

Merit: 1019

Spam attack started 2-3 weeks ago is over. Today all dust addresses have been cleaned by dust-collectors

Now I see new attempt to flood the network with 1-satoshi outputs on my radars

Code:

e02e835c7649dafabd39d5b917e4befec1bc559829056cb3101b84e874ece787:427   0.00000001    16kXBahWnydJakZLjBeZLiJugLdFcgWEPZ
48b55293769a816416286d9341ce044dc6302513d4198330104e028b7e0c3324:73    0.00000001    1DJy7PpWbYJaXzaEXTx4onYEiLMGeGfAD2
0ce87560f83fe0357213be0673a8def51b025b45c5c3f31aa4bdb9d329e93f8f:62    0.00000001    18v2mXSfvGuTFeHfXNQZnhT3AFRuZ9VfQW
a5271a1f1f79f44d4698e5b17dc524aba8e1c50a4623649659c5de94f315ed9c:0     0.00000001    16kkcN7JfNk7HHojLECH2XjkfbzbpTn7Bf
76821f1bcf0e17a68312c2815ac38571b3afc7b2a10644801ced414a80f26ac7:31    0.00000001    1AbamLM19UEWuzGhG69vwT9MVpiundSXMF
76821f1bcf0e17a68312c2815ac38571b3afc7b2a10644801ced414a80f26ac7:62    0.00000001    1DB2xRXRm5GGgzrG53WS8fjSMLia96s5V1
2edbd9adf30a68d8e9e1deee08fc3a48c6cd13da90174e59ac0f753aac8fc046:65    0.00000001    1KykLZguCHxZ5WpZrWWPhzeZJ9a4yVb7CW
0cd0461b2c567fc53178da70a20ef78d53821f0569b3155afd711ed97e28f100:42    0.00000001    1KYkWtYFV6mij4ZNRFzeQxa4MAJxEQbBQp
5f27fab24f3553ee08eff2b6e76e136ad7d92cc41f7c376a4bd9c225f57b626a:53    0.00000001    1DB2xRXRm5GGgzrG53WS8fjSMLia96s5V1
5f27fab24f3553ee08eff2b6e76e136ad7d92cc41f7c376a4bd9c225f57b626a:65    0.00000001    1egtgBEiggZk7N7o4NwMY6c8MffyWiZgK
5370ae3fb1c985b17d68d15a46e59fbde16107333c35d2081cf0d3fbe26c0717:7     0.00000001    1PVCwuyCPYBN4Q5D1iCUZm4jsjkeR747BW
dc3c51d970c1e131b04d684e0122b61fa0914363f4b5636db48f873384d007db:0     0.00000001    1Dx1gbLLK4GrFumxiUTSqhKVj5kzv4HVna
dc3c51d970c1e131b04d684e0122b61fa0914363f4b5636db48f873384d007db:27    0.00000001    1371Eqo1zues6eFVeHVzjPRYgGpZQCHWk7
af8a6ee44ddc224ddefea77bfec1612a8d1468bb410f256c4fdeca0fb8e9a8b2:28    0.00000001    1GgG93uVi6yBEsHZf9rzT5C2mU65dQZ4AR
6c6cd4ad154b84b8f4a21174c844a65890c968f12b504c466425f44ed5beecaf:66    0.00000001    18TNv91HhH279rfGYchJQVEjmMERed2sEm

Fortunately, Bitcoin network is tolerant to such small outputs.
Miners treat such transactions as non-standard and do not confirm them.
Most nodes do not relay them also.

A word to spammer: may I ask you to send at least 1000 satoshi per output? Grin

Topic: New penny-flood attack on network (very weak attempt) (Read 664 times)