At some point you are going to have to cut those non confirmed shares free.
They have been hanging around a bit now.
True, but we're reluctant to spend other people's btc.. If it were you, what would you say if you found out your btc was gone?
Yeah I see it.. weird.. Was sent just like any other from bitcoind.. the other tx has 0 confirmations. Don't see the 13f8a84654acff8483f84074054ff8bf357bf3ceae08201f7342b289f5766f35 tx anywhere in the logfiles.. If anyone has any bright ideas as to how it got there..
Cheers,
It seems that the relay used there is broke. It relayed more transactions with different tx id's that are noted as double spend.
https://blockchain.info/ip-address/133.242.180.170I think that client is broken or doing something it shouldn't. As far as I can see it doesn't affect the div payment. We are however still looking into it just to make sure..
EDIT: Apparently those clients are trying to "help" MtGox:
http://www.reddit.com/r/Bitcoin/comments/1x93tf/some_irc_chatter_about_what_is_going_on_at_mtgox/cf99yac There is a design flaw in the Bitcoin protocol where its possible for a third party to take a valid transaction of yours and mutate it in a way which leaves it valid and functionally identical but with a different transaction ID. This greatly complicates writing correct wallet software, and it can be used abusively to invalidate long chains of unconfirmed transactions that depend on the non-mutant transaction (since transactions refer to each other by txid).
My current understanding and inference is that the remaining issues are because while MtGox was producing transactions of the bad form that the network won't relay anymore— some people decided to help out by 'fixing' these transactions like BC.i did for iphone users— making the signatures normal and broadcasting them. Of course, the new transactions— while functionally identical— have different TXIDs.
The difference here is that the MtGox wallet software appears to have not handled this case gracefully at all, and apparently simply wouldn't notice transactions that it "didn't make" spending its own coins.
TL;DR Some people are trying to (purposely) change txid's of transactions in the hope that their modified tx makes it in the block. Custom clients (like Gox) then think the tx didn't go through and send the btc again. No harm was done to our transaction. Even better; the "wrong tx" just got "failed status" so the double spend warning is gone as well:
https://blockchain.info/tx/54585341ef96a683d43e1547db782401c97d7b17fa75938a7ae8fe0cc4600609Cheers