|
Title: Need to recover my sister coins from old official client Post by: speeder on April 04, 2013, 01:31:48 AM I Don't know the version of the client.
Anyway, the only information I could extract is this: o seu endereço bit coin 1C69jwHJn9HsvyKyBcoUeWZLjnaDhXAF1V Estado: 0/não confirmado Data: 1/2/2013 15:24 Destinatário: 18cB1JqWs4QGZ43rkR2pmxBuen7MDpMXBm Débito: -9.80 Quantia Net: -9.80 How I get back those 9.8 BTC? The intention was send them to mtgox to sell, but it never worked out (0/not confirmed) so... what now? Title: Re: Need to recover my sister coins from old official client Post by: speeder on April 04, 2013, 03:06:39 AM I think this is the address that holds the limbo-ed money: 1HGM9JYuX6K359b19XQj3ohzxjYoJDey1o
How I move the money out of this address? (rather, how I tell the old client that the money is still there?) Title: Re: Need to recover my sister coins from old official client Post by: TiagoTiago on April 04, 2013, 03:12:16 AM Try starting the client with the -rescan commanline option perhaps?
Title: Re: Need to recover my sister coins from old official client Post by: CIYAM on April 04, 2013, 03:21:35 AM Certainly there are 9.8 BTC at that address: https://blockchain.info/address/1HGM9JYuX6K359b19XQj3ohzxjYoJDey1o and the other address that 9.8 was supposedly sent to has 0 BTC: https://blockchain.info/address/18cB1JqWs4QGZ43rkR2pmxBuen7MDpMXBm
Am not sure what might have gone wrong with the tx as being a single UTXO and being very old it should not even require a fee. Try starting the client with the -rescan commanline option perhaps? You could try that but assuming you are wanting to *not* broadcast that tx now then you should stop running bitcoin (as it will keep trying to broadcast the tx every 30 minutes or so). And assuming you have a backup of the wallet that was *prior* to that attempted tx (but does have the original 9.8 BTC) then replace the current wallet with your backup (keep a copy of the current wallet *just in case*). Assuming all looks fine when you restart Bitcoin then you should upgrade your client to the latest (you need to do this by May 15th anyway). |