Random Satoshi's + OCD = Bad!

[TikiShack]

I'm I the only one here who extremely dislikes all the random 0.xxxxxxxxxx1 payments due to OCD.

I just moved some funds into paper wallets and I put 1 BTC into each address but now I have a 1 BTC payment and now I have a bunch of random Satoshi's being sent to my addresses...

First time it has happened to me!

[JohnnyBTC]

the trick is not to post your btc address anywhere, then their scraping programs won't see it

[TikiShack]

the trick is not to post your btc address anywhere, then their scraping programs won't see it

It was a fresh cold storage address, I think they got it from the recent transactions on sites like blockchain.info

[odolvlobo]

the trick is not to post your btc address anywhere, then their scraping programs won't see it

You don't have to post an address. They send to addresses in the block chain.

Here is the solution for all the OCD types. It is not simple, but it works.

1. Send all bitcoins (except the dust) from any address that has dust to a new address.
2. Optionally, get the private keys for the old addresses and import them into a new separate wallet just for dust.
3. Delete the old addresses containing only dust from your wallet.

Now you have a clean wallet and a wallet that just holds dust.

[toleng]

the trick is not to post your btc address anywhere, then their scraping programs won't see it

You don't have to post an address. They send to addresses in the block chain.

Here is the solution for all the OCD types. It is not simple, but it works.

1. Send all bitcoins (except the dust) from any address that has dust to a new address.
2. Optionally, get the private keys for the old addresses and import them into a new separate wallet just for dust.
3. Delete the old addresses containing only dust from your wallet.

Now you have a clean wallet and a wallet that just holds dust.

Step 2 would often not work as the dust is less then the amount of TX fees that a dust TX would likely require to get confirmed.

I think the best solution would be to create a TX with no outputs and have the inputs be only the dust so the miners can get something from the dust

[odolvlobo]

the trick is not to post your btc address anywhere, then their scraping programs won't see it

You don't have to post an address. They send to addresses in the block chain.

Here is the solution for all the OCD types. It is not simple, but it works.

1. Send all bitcoins (except the dust) from any address that has dust to a new address.
2. Optionally, get the private keys for the old addresses and import them into a new separate wallet just for dust.
3. Delete the old addresses containing only dust from your wallet.

Now you have a clean wallet and a wallet that just holds dust.

Step 2 would often not work as the dust is less then the amount of TX fees that a dust TX would likely require to get confirmed.

I think the best solution would be to create a TX with no outputs and have the inputs be only the dust so the miners can get something from the dust

Step 2 works because you aren't sending anything. You are just importing addresses into a different wallet so you don't have to see the dust.

Your idea is interesting. Just give the dust to the miners.

[phillipsjk]

Peter Todd wrote a Dust-be-gone script that functions similar to Coinjoin transactions.

All the dust is bundled into one large transaction that is paid to the miners.

[R2D221]

I don't think that's OCD, to be honest.

[a447513372]

the trick is not to post your btc address anywhere, then their scraping programs won't see it

You don't have to post an address. They send to addresses in the block chain.

Here is the solution for all the OCD types. It is not simple, but it works.

1. Send all bitcoins (except the dust) from any address that has dust to a new address.
2. Optionally, get the private keys for the old addresses and import them into a new separate wallet just for dust.
3. Delete the old addresses containing only dust from your wallet.

Now you have a clean wallet and a wallet that just holds dust.

Step 2 would often not work as the dust is less then the amount of TX fees that a dust TX would likely require to get confirmed.

I think the best solution would be to create a TX with no outputs and have the inputs be only the dust so the miners can get something from the dust

Step 2 works because you aren't sending anything. You are just importing addresses into a different wallet so you don't have to see the dust.

Your idea is interesting. Just give the dust to the miners.

Are you suggesting that the keys be swept into an existing wallet via blockchain transfer or simply creating a new wallet file with the old private keys with the remaining dust transactions?

If you are going to be sweeping the keys (for example via the sweep key function on blockchain.info) then the TX will never confirm or you will pay more in TX fees then the sum of the total imputs. 

[kaykawa]

i received the same few days back, like 3 times.... this is bad ??