Author

Topic: How did this double spend happen? (Read 1705 times)

legendary
Activity: 1680
Merit: 1014
August 09, 2013, 03:38:30 AM
#7
It would still be irreversible as soon as there is 1 confirmation present. Until that point that transaction is anyway in a suspended mode. I mean, already today if no confirmations are done within 24 hours, the funds are returned to your address. That's how Blockchain.info handles stuff. What I suggest is to allow a manual abort so that you don't have to wait those 24 hours for transaction to be rolled back.
legendary
Activity: 3682
Merit: 1580
August 08, 2013, 05:26:49 PM
#6
I didn't mean just double-spending, but any transaction that you "just" pushed out. There should be a best-effort mechanism to signal from your sending address (signed by your private key) that you want that transaction to be cancelled so as there no confirmations present.

Bitcoin is supposed to be irreversible. If you allow what you are proposing it will no longer be irreversible.
legendary
Activity: 1680
Merit: 1014
August 07, 2013, 05:31:13 AM
#5
I didn't mean just double-spending, but any transaction that you "just" pushed out. There should be a best-effort mechanism to signal from your sending address (signed by your private key) that you want that transaction to be cancelled so as there no confirmations present.
vip
Activity: 1316
Merit: 1043
👻
August 07, 2013, 04:16:38 AM
#4
I guess I'll just wait.

There should be a mechanism to signal to the network that an unconfirmed transaction should be removed from the confirmation queue...

It doesn't need to. The second doublespending transaction a client hears about is automatically discarded.
legendary
Activity: 1680
Merit: 1014
August 07, 2013, 02:33:02 AM
#3
I guess I'll just wait.

There should be a mechanism to signal to the network that an unconfirmed transaction should be removed from the confirmation queue...
full member
Activity: 126
Merit: 100
August 07, 2013, 02:29:14 AM
#2
I am not quite sure how double-spends are possible at all, but it happened in my Blockchain.info wallet, when I was transferring a minuscule sum between my 2 addresses to consolidate transactions. It was staying as "Unconfirmed" for about a day, then disappeared and then after a few hour a new "Unconfirmed" trans appeared.
Now, it hangs there as unconfirmed, and when I click on it, I get all red:

"Warning! this transaction is a double spend of 83677841. You should be extremely careful when trusting any transactions to/from this sender. "

Here are those transactions:
https://blockchain.info/tx/e84e5f2d72badfaa7d730e03923853073f5493a7153eb58241ef263c573f068c
https://blockchain.info/tx/ac48023657b8dca62e99f6fb643a3e8f513e5fc850eccc2c30404ca80a3ac961

Interestingly, I only see the "e84" trans on the address list:
https://blockchain.info/address/1DodoExzsNPvVRXFrgkKw6E259VjfUW8Kh
Not the "ac4", which is nowhere to be seen.

What should I do about it? Can I cancel that trans somehow? How could it happen in the first place?



The long confirm times is probably due to the dust that you are sending (multiple inputs less than < 0.01). As for the doublespend, this isn't actually a double spend but an attempted double spend. Eventually one of the transactions will be confirmed and the other will be invalid and removed (along with any transactions originating from that transaction). Also, blockchain.info allows transactions other clients would consider non-standard, so this is probably how it happened in the first place.
legendary
Activity: 1680
Merit: 1014
August 07, 2013, 02:21:37 AM
#1
I am not quite sure how double-spends are possible at all, but it happened in my Blockchain.info wallet, when I was transferring a minuscule sum between my 2 addresses to consolidate transactions. It was staying as "Unconfirmed" for about a day, then disappeared and then after a few hour a new "Unconfirmed" trans appeared.
Now, it hangs there as unconfirmed, and when I click on it, I get all red:

"Warning! this transaction is a double spend of 83677841. You should be extremely careful when trusting any transactions to/from this sender. "

Here are those transactions:
https://blockchain.info/tx/e84e5f2d72badfaa7d730e03923853073f5493a7153eb58241ef263c573f068c
https://blockchain.info/tx/ac48023657b8dca62e99f6fb643a3e8f513e5fc850eccc2c30404ca80a3ac961

Interestingly, I only see the "e84" trans on the address list:
https://blockchain.info/address/1DodoExzsNPvVRXFrgkKw6E259VjfUW8Kh
Not the "ac4", which is nowhere to be seen.

What should I do about it? Can I cancel that trans somehow? How could it happen in the first place?

Jump to: