FWIW, one of the outputs in f75b455b4df94bcdcd54985b4aeea9948d2a1dca0f63c65b85ad2d941050c5cf sends 1 Satoshi to an address I own, that has been used as a change address in a previous transaction. So it looks like the outputs aren't random, or at least not all of them. Someone has scanned the blockchain are they are sending outputs to existing addresses.
I discovered this thread because I noticed someone had sent 1 Satoshi to me on July 8, and the transaction ID led me to this thread.
Topic: Why did this transaction confirm? (Read 2623 times)
Quote
Some of the addresses in transaction are also quite interesting: 1P1ease..., 1Give..., 1hint...
Nothing interesting. You have missed topic https://bitcointalksearch.org/topic/arg-puzzle-with-35-btc-private-key-prize-game-over-661781 (I do not remember the exact page)
The transaction with vanity addresses was used as a "public message".
Yes, missed totally
. Thank you for the link, looks that the puzzle was great fun. Quote
Some of the addresses in transaction are also quite interesting: 1P1ease..., 1Give..., 1hint...
Nothing interesting. You have missed topic https://bitcointalksearch.org/topic/arg-puzzle-with-35-btc-private-key-prize-game-over-661781 (I do not remember the exact page)
The transaction with vanity addresses was used as a "public message".
Hmm. I also see some strange things that have never seen before.
Lets take transaction https://blockchain.info/tx/4af1a19fd6940758e2c4a3e779cb25023d93668c75a313f93e8008c0b075488e
Lets take transaction https://blockchain.info/tx/4af1a19fd6940758e2c4a3e779cb25023d93668c75a313f93e8008c0b075488e
Some of the addresses in transaction are also quite interesting: 1P1ease..., 1Give..., 1hint...
Hmm. I also see some strange things that have never seen before.
Lets take transaction https://blockchain.info/tx/4af1a19fd6940758e2c4a3e779cb25023d93668c75a313f93e8008c0b075488e
it was created ant sent a ~week ago with 0 fees and very-very low priority (date on bc.i is incorrect - tx is older)
No miner wanted to include this transaction into a block.
There was no reason to include this transaction
Yesterday somebody re-broadcasted it (bc.i forgot the first copy) again
Yesterday I redeemed it with
https://blockchain.info/tx/8a1f0f07fb397b2aa0e77995723f2dac9aee7df63a6f05a7db7d168d62a60f94
with a fee of 0.0001
So, there is a reason now for a miner to include both transactions - miner gains 0.0001 (which is more than default 0.00001 per kb)
And these two transactions were mined! Of course, in same block (309837) because miner would not include first transaction without second.
----
Update 1: No. Block 309837 contains a lot of free transactions.
----
Update 2: child-pays-for-parent?
Lets take transaction https://blockchain.info/tx/4af1a19fd6940758e2c4a3e779cb25023d93668c75a313f93e8008c0b075488e
it was created ant sent a ~week ago with 0 fees and very-very low priority (date on bc.i is incorrect - tx is older)
No miner wanted to include this transaction into a block.
There was no reason to include this transaction
Yesterday somebody re-broadcasted it (bc.i forgot the first copy) again
Yesterday I redeemed it with
https://blockchain.info/tx/8a1f0f07fb397b2aa0e77995723f2dac9aee7df63a6f05a7db7d168d62a60f94
with a fee of 0.0001
So, there is a reason now for a miner to include both transactions - miner gains 0.0001 (which is more than default 0.00001 per kb)
And these two transactions were mined! Of course, in same block (309837) because miner would not include first transaction without second.
----
Update 1: No. Block 309837 contains a lot of free transactions.
----
Update 2: child-pays-for-parent?
Yes, but there seems to be no information about bcpool.io. Their "about" page:
https://bcpool.io/index.php?page=about&action=pool
Is also exactly the same this "about" page:
https://chunkypools.com/aur/index.php?page=about&action=pool
And doesn't contain any information about them at all.
It looks like https://blockchain.info/tx/ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8 is just one of many spam transactions that have been mined recently.
Yep. I noticed this one last week:
https://blockchain.info/tx/cff61bad78a1759cf71cf287d67f3a6d63f9f9c2f0566735c06446455834b231
Interesting. That one was sent from "SPAM SEND" (1DkRWKXpfQwm5b1pGL2QdpPdrUdKSdzbnG) and mined by Discuss Fish. I checked the two blocks mined recently by BCPool (blocks 309740 and 309657) and indeed they mined another 120 satoshi spam outputs from "SPAM SEND" in addition to the 17,976 from 1Enjoy that I reported earlier.
What's interesting is that BCPool also includes some transactions that consolidated a bunch of dust too:
https://blockchain.info/address/1MQQAxLKLKt3RznFMLmxXMieEuCqKXbMoe
So, who is BCPool?
It looks like https://blockchain.info/tx/ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8 is just one of many spam transactions that have been mined recently.
Yep. I noticed this one last week:
https://blockchain.info/tx/cff61bad78a1759cf71cf287d67f3a6d63f9f9c2f0566735c06446455834b231
It looks like https://blockchain.info/tx/ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8 is just one of many spam transactions that have been mined recently. If you look up the 1Enjoy address, you'll see that several transactions were included in blocks 309740 and 309657. Both these blocks were mined by the same group, as the coinbase was awarded to https://blockchain.info/address/19RZPWsNmVM2cVVDMtkzo2UtkFBFc6nFE8 in each case. BCPool.io shows that they were the pool responsible for mining these two blocks. In fact, as far as I can tell, these are the only blocks ever mined by BCPool.
In total, 17,976 satoshi dust outputs sent from 1Enjoy have been mined in the last two days by BCPool.io.
In total, 17,976 satoshi dust outputs sent from 1Enjoy have been mined in the last two days by BCPool.io.
Code:
BLOCK #309740: 10,486 DUST OUTPUTS
ADDRESS SENT FROM TX HASH N_OUTPUTS
===================================================================================================================
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z b2b6112e73cbe0937a1b60c9abfc4c2ca6e26b2612c90ec598b1cd28787a553e 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 5e5d17901378b8835861d8cc0df2b5f9bf3c86759c3821f96470cd852344d799 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z b2bf7525618ed5402024d5bff6f477a2093965d3f11ececbc2b6a9b5bbe1f5d5 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 3df8f4a7e06486bb3b0700935a16fc6d4fad397dcb6c88b9c4b6a7453301aa54 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z ae05ddfc8aa206b213c71ec0e96723dcd4ff03a71ca76b469d225d1c60d9e262 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z f75b455b4df94bcdcd54985b4aeea9948d2a1dca0f63c65b85ad2d941050c5cf 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z a22186cbcf82cac66da17183209f20f76088934c931bec131fe71ad2f250e8f8 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 0469286403543b7d794fe52661135a80142c47ac541793c703fd637a4e9dc0bf 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z a71dc9abd8bae377b661b0c288222acf2ab62fc7bf96b0bab2dd5354fbc91643 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z f437d94c1cfe818c44f4505f3e6506839113ec747d815a867e953a4164276047 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z eb95d902eb841ce23c9c1466e010cbb05d43d1c248376440f9dd56ee1bc8b3e5 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z b62416ceb3453d6dcba95213e4e222915438a4b70eba37e09099110b20be0d52 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z f3aba1c064e9c9a1d49db3bce42c07c184a0b329366994000fa49f0bc8f3ba16 749
BLOCK #309657: 7,490 DUST OUTPUTS
ADDRESS SENT FROM TX HASH N_OUTPUTS
===================================================================================================================
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 2e7fdb43e2a0fe17cfe2d283a2da4d375204700aef4bf2c31056125f4383b121 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 3d1105d7c2cd36705b2163fa2d0f74973377467aefea72156a30444f330acf71 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 5c4e56943f3128629ebecb41f5916bd7bc1dceaccc37f29e59c385464f2bf558 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 536adfb745ffaa8c1fb698414475f5ca7d82846eadd912cfe0a76045d78c3198 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 45c7544374e88de47d9be2e3e100f4aa10aafd9469c4dba8d55a870f83c312ab 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z e7ae2378a44a940a8c872a63e43fa67c5a023df4df3f9ca8011611422fc2861c 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z d864e3cc07dc79f221bd91210b274e136159ccbb5c9eafad906d9d08c5558ce5 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 3dedbc086d5cfc81bd3614a1b3fab1bb4d73d8982d9552e811f84f0118a1fc12 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 7337d7ac353a9283c65a1ab99d28f97997784a0fb26d0dc0b59f2fa2556c4460 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 634a7fdcba3fe91da07f44e6b9bee1c659cbfca27076bd8b61984d062c071651 749
ADDRESS SENT FROM TX HASH N_OUTPUTS
===================================================================================================================
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z b2b6112e73cbe0937a1b60c9abfc4c2ca6e26b2612c90ec598b1cd28787a553e 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 5e5d17901378b8835861d8cc0df2b5f9bf3c86759c3821f96470cd852344d799 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z b2bf7525618ed5402024d5bff6f477a2093965d3f11ececbc2b6a9b5bbe1f5d5 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 3df8f4a7e06486bb3b0700935a16fc6d4fad397dcb6c88b9c4b6a7453301aa54 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z ae05ddfc8aa206b213c71ec0e96723dcd4ff03a71ca76b469d225d1c60d9e262 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z f75b455b4df94bcdcd54985b4aeea9948d2a1dca0f63c65b85ad2d941050c5cf 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z a22186cbcf82cac66da17183209f20f76088934c931bec131fe71ad2f250e8f8 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 0469286403543b7d794fe52661135a80142c47ac541793c703fd637a4e9dc0bf 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z a71dc9abd8bae377b661b0c288222acf2ab62fc7bf96b0bab2dd5354fbc91643 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z f437d94c1cfe818c44f4505f3e6506839113ec747d815a867e953a4164276047 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z eb95d902eb841ce23c9c1466e010cbb05d43d1c248376440f9dd56ee1bc8b3e5 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z b62416ceb3453d6dcba95213e4e222915438a4b70eba37e09099110b20be0d52 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z f3aba1c064e9c9a1d49db3bce42c07c184a0b329366994000fa49f0bc8f3ba16 749
BLOCK #309657: 7,490 DUST OUTPUTS
ADDRESS SENT FROM TX HASH N_OUTPUTS
===================================================================================================================
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 2e7fdb43e2a0fe17cfe2d283a2da4d375204700aef4bf2c31056125f4383b121 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 3d1105d7c2cd36705b2163fa2d0f74973377467aefea72156a30444f330acf71 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 5c4e56943f3128629ebecb41f5916bd7bc1dceaccc37f29e59c385464f2bf558 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 536adfb745ffaa8c1fb698414475f5ca7d82846eadd912cfe0a76045d78c3198 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 45c7544374e88de47d9be2e3e100f4aa10aafd9469c4dba8d55a870f83c312ab 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z e7ae2378a44a940a8c872a63e43fa67c5a023df4df3f9ca8011611422fc2861c 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z d864e3cc07dc79f221bd91210b274e136159ccbb5c9eafad906d9d08c5558ce5 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 3dedbc086d5cfc81bd3614a1b3fab1bb4d73d8982d9552e811f84f0118a1fc12 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 7337d7ac353a9283c65a1ab99d28f97997784a0fb26d0dc0b59f2fa2556c4460 749
1Enjoy1C4bYBr3tN4sMKxvvJDqG8NkdR4Z 634a7fdcba3fe91da07f44e6b9bee1c659cbfca27076bd8b61984d062c071651 749
Quote
and the loss of priority will me that person must pay more fees in the future.
What are you talking about? This person can send free transactions each second block!309655 https://blockchain.info/tx/0e7f9ab6e5b2916b390f749c6b980f669e1dc1e02fc9d795b833451889524ded
309657 https://blockchain.info/tx/bddbbc8d0e9d8dc8e4fd1b48bfd9582318648ba501243015887082773b48a860
309659 https://blockchain.info/tx/ce9862e3cadc5d9b87da119b52b8f2b1c6a6a7e6d86d9df108febcc715c5a89d
S/he does not pay fees at all!
Quote
They are technically spendable but they cost more in marginal fees than they are worth...
No. It is possible to collect dust-outputs with free-transactions.Look here https://blockchain.info/address/155M7TvBRww6WFdtGQgTYUH8DuLheNafCf
Quote
They are technically spendable but they cost more in marginal fees than they are worth...
No. It is possible to collect dust-outputs with free-transactions.Look here https://blockchain.info/address/155M7TvBRww6WFdtGQgTYUH8DuLheNafCf
Quote
Normal nodes do not relay old transactions...
They have a "mempool" request and everyone is able to take all transactions from a node and re-broadcast them to the network.You know that it is very easy to do. Even my buggy-script do it for some transactions sometimes.
I see several of these outputs are already spent. How are they supposed to be unspendable?
They are technically spendable but they cost more in marginal fees than they are worth... It's altruistic to redeem them but not rational to do so otherwise. 
If you've received some of this 1e-8 dust to a bitcoin-core wallet, https://github.com/petertodd/dust-b-gone is a good way to get rid of it.
The only person I know that got one of these say he/she has no other unspent output on this address so I guess it's easier to just remove it from his/hers bitcoin core. Still curious what kind of problems he/she can run into when trying to spend it though.
Since the dust limits were put in place most miners intentionally DO NOT include these dust outputs because they are unspendable and they will bloat the UTXO and increase the cost of all nodes forever.
I see several of these outputs are already spent. How are they supposed to be unspendable?
Some node ( may be not bcpool.io ) keeped it in its memory pool and relayed today
bcpool.io got it, checked and included into a block.
Normal nodes do not relay old transactions... but, indeed, could have just been them not updated after all this time.bcpool.io got it, checked and included into a block.
The one I searched for got not hits, good sleuthing.
By the way.
This is not new spam-attack from enjoy-sochi.
It is echo of past events.
Transaction https://blockchain.info/tx/ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8
was created and sent in February. You can find in in google archives.
For example
http://webcache.googleusercontent.com/search?q=cache:WhRSCSqOMC4J:hibitcoin.com/bitcoin/unspent/18qQzy6SR6HmMpCLs1nHb2jraTMoXPPkW6
Some node ( may be not bcpool.io ) keeped it in its memory pool and relayed today
bcpool.io got it, checked and included into a block.
This is not new spam-attack from enjoy-sochi.
It is echo of past events.
Transaction https://blockchain.info/tx/ee61b911610f66f539832699fbbf4ab3955c8bd5ad0cfa570ff500dedcde5bf8
was created and sent in February. You can find in in google archives.
For example
http://webcache.googleusercontent.com/search?q=cache:WhRSCSqOMC4J:hibitcoin.com/bitcoin/unspent/18qQzy6SR6HmMpCLs1nHb2jraTMoXPPkW6
Some node ( may be not bcpool.io ) keeped it in its memory pool and relayed today
bcpool.io got it, checked and included into a block.
Blockchain.info indicates that the block with the offending TX (Block #309,740) was relayed by "Unknown 37.187.90.171" and is the only block relayed by that IP address in the last 24 hours. May I ask how you were able to contact them?
BC.i's analysis is ... seldom good. Just look in the coinbase of the block.
Hopefully we can build community awareness around the important difference between "blockchain bloat" and "UTXO bloat"--I think many users erroneously lump these two topics as one in their minds. A more intelligent way to limit unnecessary growth of the UTXO set like we just saw with ee61b911... might be one of the few hard forks I'd support.
By the way, recent analysis of the UTXO set by DeathAndTaxes as of Block #305,303 indicates that the "dust rule" has had a notable impact. If dust rules had been in place since 2009, we'd have a much cleaner UTXO set today with essentially no loss of function to bitcoin.
Blockchain.info indicates that the block with the offending TX (Block #309,740) was relayed by "Unknown 37.187.90.171" and is the only block relayed by that IP address in the last 24 hours. May I ask how you were able to contact them?
By the way, recent analysis of the UTXO set by DeathAndTaxes as of Block #305,303 indicates that the "dust rule" has had a notable impact. If dust rules had been in place since 2009, we'd have a much cleaner UTXO set today with essentially no loss of function to bitcoin.
I've already nagged the miner in question about the wad of dust floods they just mined.
Blockchain.info indicates that the block with the offending TX (Block #309,740) was relayed by "Unknown 37.187.90.171" and is the only block relayed by that IP address in the last 24 hours. May I ask how you were able to contact them?
Jump to: