Author

Topic: 1 satoshi (0.00000001) Deposits (Read 1061 times)

legendary
Activity: 2058
Merit: 1452
October 01, 2014, 02:17:24 PM
#12
locked because similar topics already exist.
newbie
Activity: 28
Merit: 0
October 01, 2014, 01:03:18 PM
#11
I receive them too. Probably some casino or gambling site  Roll Eyes
member
Activity: 94
Merit: 10
★Bitin.io★ - Instant Exchange
October 01, 2014, 12:26:45 PM
#10
Those are sent out just for advertising purposes. The 1enjoy 1sochi addresses are still going strong, bloating the transaction network daily. I'm sure the network could handle a much bigger stretch test than this one though. Those transactions are harmless to you.
legendary
Activity: 1456
Merit: 1001
This is the land of wolves now & you're not a wolf
October 01, 2014, 12:24:33 PM
#9
I receive a ton of them.   I usually get them right after withdrawing BTC from a dice site or something like that.   I don't usually just get them randomly, they always seem to follow immediately after I do a different transaction.  Some of them confirm, and then some of them end up disappearing...
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
October 01, 2014, 12:05:55 PM
#8
Spam, see here [1] as well as the other 500 [2] threads lately.


[1] https://bitcointalksearch.org/topic/1-satoshi-deposits-with-label-blockchain-accounts-hacked-805879
[2] might actually be less.
sr. member
Activity: 381
Merit: 250
October 01, 2014, 11:55:53 AM
#7

Looks like its the Laxotrade spamming account, search the forums for the word: Laxotrade several people have already created threads about this in the past.
legendary
Activity: 1330
Merit: 1003
October 01, 2014, 11:50:15 AM
#6
I've been receiving these as well.
sr. member
Activity: 250
Merit: 253
October 01, 2014, 11:47:34 AM
#5
No.  It inflates the size of the transaction when you process a send, possibly increasing your tx fee.
Yes, but it's still possible to spend these in a no-extra-fee or even 0-fee transaction (the dust limitations are on outputs, not inputs). I did this myself recently (0-fee) with one dust and some of my other money, just because. I suppose it hurts the network some tiny amount, but it helps me some larger, but still tiny amount.
Shouldn't the miners be disallowing these 1 satoshi transactions?  Why are they even being allowed in the first place?  I thought "dust" was rejected?
As long as you pay a sufficient transaction fee to create the transaction outputs (usually 0.0001 per 1000 bytes), typical miners will accept it. Miners don't mind creating or spending dust, as long as you pay for it (they get paid, why not?). The ones I saw creating dust would have something like a 0.0004007 input, 70 1 satoshi outputs, and a 0.0004 fee (and come in just under 4000 bytes), thus meeting all requirements.
sr. member
Activity: 318
Merit: 251
October 01, 2014, 11:40:47 AM
#4
It's just more of a nuisance than anything.

No.  It inflates the size of the transaction when you process a send, possibly increasing your tx fee.  Shouldn't the miners be disallowing these 1 satoshi transactions?  Why are they even being allowed in the first place?  I thought "dust" was rejected?
full member
Activity: 306
Merit: 100
October 01, 2014, 11:39:41 AM
#3
Just one, unfortunatelly not a lot of them as you  Smiley

You dont need touch the satoshi, and maybe in 20 years the one satoshi become somehow usefull  Cheesy
hero member
Activity: 798
Merit: 1000
October 01, 2014, 11:33:26 AM
#2
I'm getting those too. We think it's some kind of blockchain spam. Really it doesn't interfere with your ability to use Bitcoin that's already confirmed and in your wallet. It's just more of a nuisance than anything.
hero member
Activity: 1008
Merit: 502
October 01, 2014, 11:30:10 AM
#1
Is anyone else getting these.

I dont know who keeps sending them or why but I get a lot of them.

What could be a good reason to send someone 1 satoshi? Does these transactions mess with when I send coins too?



Heres the Blockchain transaction from the most recent one


http://blockchain.info/tx-index/96bd4e207814ce34729b934b976a4f10b44ae16322a9415e0f18956d7dfe49a1
Jump to: