2

I have an old "BitCoin-QT" Core client at version 'V0.7 2-beta' - that I just want to move coins from, to a Ledger Nano, (and then not need to ever fire up this local QT software again). My BitCoin-QT Core client is about 3 years out of date with regard to the Blockchain..

Without having to go through the whole Client Upgrade path.. last night I tried to move a small BTC transaction off via the Client as a Test.

After a few hours the transaction status on the client was given as "Status: 0/unconfirmed, broadcast through 28 nodes". I sent the nominal BTC transaction to an address beginning with "1B.." a legacy BTC address.

I looked this morning for my Transaction via the Bitcoin Block Explorer (blockchain.info) - but nothing was showing.

Is this telling me :

  • I just need to wait longer? (how long approx?), or
  • My transaction will never get processed? (its in an old format or something). If so how would I claim the coins sent (and fees charged?) for this failed attempt?, or
  • I definitely need to upgrade my QT core client first before I can send any coins from this old client? If so, what is the Min QT Client version I should target to upgrade to ? (ie to avail of the latest Forks, BTC Cash offerings etc?).

Much thanks, L

  • The status message sounds like MultiBit, not Bitcoin-QT. – Anonymous Nov 9 '17 at 2:33
1

There haven't been any Bitcoin hard forks in the last 3 years so your old client should still work fine. Of course it won't be able to use new features like SegWit but that shouldn't matter.

Does your v0.7.2 client have the "Transactions" menu option. Double clicking the pending transaction will tell you it's status. If you don't have that menu option where are you getting the transaction ID from?

If you're still getting nowhere with your old client then in your shoes I'd take the following steps:

  • If you haven't already backed up your wallet then in your v0.7.2 client do File->Backup Wallet and save it to a USB drive or somewhere safe,
  • Download the latest Bitcoin Core client and install it,
  • Run the new client and it should update your wallet if it needs to,
  • If your blockchain is not synchronised then unfortunately you may have to wait a long time (days) for it to catch up,
  • Try another test transaction with the new client.

There are other options that you could do with your existing client, such as extract your private key with the Debug Window->Console, but that could go wrong very easily. Your number one concern is obviously not to lose your private key(s) and even if it takes a number of days to sync your new client that's a small price to pay.

  • re "Transactions" menu - yes, I got "Status: 0/unconfirmed, broadcast through 28 nodes".Got Trx id - but that is not on the blockchain.info - is that the right place to look ? Re upgrade and Wallet.dat - I got a copy on my Mac, via 'Copy' / Paste. Is the "File->Backup Wallet" method needed for correct version? Re latest QTCore client install - I got advice that I need to make that a 2 step process (i) V0.7 2-beta' TO Bitcoin Core 0.14.2 (ii) Bitcoin Core 0.14.2 to Bitcoin Core 0.15.X - perhaps this is not correct?, and I can do it in 1 step to a 0.15.X ? My QT client is 4 years old. – Jose Nov 10 '17 at 1:05
  • blockchain.info should show up your tx even if it's unconfirmed so maybe your v0.7.2 client does generate invalid tx's somehow. I'd backup your wallet file using a copy-paste of wallet.dat AND the File->Backup Wallet. After that install the latest available client and see if it is able to upgrade your wallet. If it fails you might have to try your luck with the devs by logging an issue at github.com/bitcoin/bitcoin/issues. Someone there will have written the wallet upgrade code and hopefully they'll respond. – sipwiz Nov 10 '17 at 4:59
  • 2
    0.7 may still produce high-S signatures which are now nonstandard. – Pieter Wuille Jan 8 '18 at 10:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.