<p>I don't know exactly what features are available on your version, but here are some ideas to try.</p>

<p>First, take a backup of your <code>wallet.dat</code> file.</p>

<ol>
<li>In the debug window (help menu?), make sure that your peer is actually connected to some other peers so that your transaction will be broadcast to the network.</li>
<li>Make sure your node is fully synced to the latest block.</li>
<li>Start the application with the <code>-zapwallettxes=1</code> argument to delete the transactions that are not in the blockchain from your wallet.</li>
<li>Start again with the <code>-rescan</code> argument to scan the blockchain for bitcoins assigned to your private keys. This will take a long time (hours possibly).</li>
<li>Your bitcoins should be available again, so try to send the transaction again with a higher fee. You can use <a href="https://bitcoinfees.earn.com/" rel="nofollow noreferrer">https://bitcoinfees.earn.com/</a> to decide what an appropriate fee is.</li>
</ol>

<p>If you really want to export your private keys, you can use the <code>dumpprivkey "address"</code> command from the console inside the debug window (if the console is available in your version). But be very careful when moving your private keys around, they could get stolen by a key logger, screen grabber, other malware, or phishing sites, etc.</p>

CC BY-SA 3.0
2017-12-03T11:31:14.500Z
Wow - thanks Adam for this great information. Getting closer!  But unfortunately the version I have does not have either a Help or Debug window.  I have found a program called PyWallet which is a Python script which can run using MacPorts so that could help. But of course I would like to be able to perform these commands. The only way I can see to do that would be to somehow upgrade my v0.6.2.2 to the earliest version that has the debug/Help window.  But so far I can't find any accessible higher versions...   Tricky!!!
Jozwolf
CC BY-SA 3.0
2017-12-03T11:36:13.453Z
Also - Adam - I am not sure if this version I have (v0.6.2.2) actually can properly synchronise with the modern version of what the Bitcoin servers do....  Eponymous thinks it cant. But on the other hand the first transfer I did did show up in Exodus wallet, but since it had no fee attached it sits there unconfirmed.  I notice that the transaction id has a -0000 at the end of it for both transactions.  Is this supposed to carry the fee I wonder?
Jozwolf
CC BY-SA 3.0
2017-12-03T11:44:03.977Z
Tricky. Importing the key into a new wallet may be the easiest solution, although also the riskiest. Looking at the source code for 0.6.2.2, it has the `dumpprivkey` command, so it looks like you have some hope, if you can work out how to run it. https://github.com/bitcoin/bitcoin/blob/v0.6.2.2/src/bitcoinrpc.cpp#L2056
Adam Millerchip
CC BY-SA 3.0
2017-12-03T12:46:22.020Z
Hey Adam THANKS - well it probably is syncing - phew!  Unfortunately I know nothing about Python scripting.  There is no obvious way to give the program a command line command from its user interface. I suspect that came in a later version.  I can find later versions at  https://github.com/bitcoin/bitcoin/tags?after=v0.7.0 but the instructions on how to build them might as well be written in Martian as far as my humble knowledge goes.  If you could point me at all in the right direction I would  try to upgrade... but....
Jozwolf
CC BY-SA 3.0
2017-12-03T12:49:15.573Z
but....  here is a naive approach (???) - if I just wait a few days until the mempool loses interest could I just start my horrid early version of QT and restore it from the backup I made before all this began.  If I did that would it just give me back my bitcoin?  In that case I could try using the program to send the coin with the correct fee. Might work.....  Alternatively given you can read the version of the program I have would you be able to tell me how best to move forward to get dumpprivkey to work ?????  I feel so out of my depth in this!!!!
Jozwolf
CC BY-SA 3.0
2017-12-03T12:55:29.910Z
Oh damn - I know I am going to strain your patience. But from something I read Bitcoin Core has an upgrade option which is supposed to upgrade from earlier versions....   Would it be able to read in the .dat file and get me up to speed - or am I in danger of losing the lot, corrupting the files... I have all the fears of ignorance here!
Jozwolf
CC BY-SA 3.0
2017-12-03T18:11:34.277Z
@Jozwolf Remember the first thing Adam said in his answer: "First, take a backup of your wallet.dat file". It would even be sensible to make 2 or more, and keep at least 1 off site. You'll want backups of the new Exodus wallet too, in case the transactions get confirmed. With those (and any required passwords), you shouldn't have much risk of losing the lot.
Highly Irregular
CC BY-SA 3.0
2017-12-03T23:00:56.420Z
Any version of Bitcoin Core before 0.8.0 is going to break when it gets to some blocks in 2013. It won't be able to sync past then without some special configuration. You should instead upgrade Bitcoin Core.
Ava Chow
CC BY-SA 3.0
2017-12-04T00:17:48.067Z
I'm tempted to delete this answer because it looks like my advice is no good for the version question and Andrew's advice looks good. But I'll leave it in case its useful for others with later versions that read this.
Adam Millerchip
CC BY-SA 3.0
2017-12-04T04:23:34.063Z
Thanks all of you for GREAT and expert advice. OK - so I have bitten the bullet, set up the XCode tools, MacPorts, set up python 2.7.7, set up the dependencies, downloaded pywallet.py, learned enough Unix and python to get the wallet.dat file in a folder with pywallet and navigated to it as Directory, and successfully run a python pywallet.py --dumpwallet > txt. So I have all the keys in JSON format in a txt file. Phew! Who says 71 year olds can't learn new tricks :-) So which one is the private address I import into a new wallet?
Jozwolf
CC BY-SA 3.0
2017-12-04T04:23:39.043Z
I can see what I interpret as pairs of public and "sec" private keys.  I can identify the one which initially received the money. And there are two I sent payments to.  The rest are all reserve addresses. And of course there is an initial default address.  If I could get a pointer on this I reckon I may be home, and possibly hosed (whatever that means) :-)
Jozwolf
CC BY-SA 3.0
2017-12-04T04:48:04.843Z
Oooops - in the meantime there is Andrew's advice - from 5 hours ago, and Adam's endorsement of it. So I could just put my very old Bitcoin-QT v 6 wallet.dat into Bitcoin Core (latest version) and it would work if I remove the other stuff Andrew mentions? Well I can try that.....  If it works I have still learned heaps of interesting stuff along the way!
Jozwolf
CC BY-SA 3.0
2017-12-03T11:04:40.087Z
2017-12-03T11:16:48.780Z
2017-12-03T11:16:48.780Z
Adam Millerchip
<p>Since your blockchain is likely very small and syncing up to the current point with modern software will be very quick, I highly suggest that you just upgrade to Bitcoin Core 0.15.1 and delete everything in the Bitcoin Core datadir except for your wallet.dat file.</p>

<p>This will cause Bitcoin COre 0.15.1 to download the entire blockchain, which will happen much more quickly than Bitcoin Core 0.6.x can sync.</p>

<p>The wallet database structure has not changed since Bitcoin Core 0.6.x, so your current wallet should work with the latest version of Bitcoin Core. You should make a backup of your wallet regardless.</p>

CC BY-SA 3.0
2017-12-04T05:01:55.227Z
Thanks Andrew - it seems to have read the transactions from the old wallet.dat perfectly well and is now synchronising.  And now I have the command window to do any of the little tasks I need.  Thanks a HEAP.  Everyone has been so helpful I could hug you all :-)
Jozwolf
CC BY-SA 3.0
2017-12-03T23:02:44.000Z
2017-12-03T23:02:44.000Z
Ava Chow
<p>I bought a couple of bitcoin in 2012 where they languished on my successive Mac Book Pros in a Bitcoin-QT v0.6.2.2 wallet.  I now realise they are worth - ahem - something!  The wallet still fires up even though it is still calls itself a beta wallet and so I thought I would first try to send my lovely bitcoin to a new and glossy Exodus wallet.</p>

<p>Now being completely new to this I got my receive address for my Exodus Wallet and tried sending 0.1 BTC to my Exodus wallet. Eventually (maybe 5 hours later) it showed it had arrived but with zero confirmations. This first transaction still shows with 0.1 BTC "Pending" in the Exodus Wallet (sent Friday Dec 1st 10.04.10 PM).</p>

<p>I realised I had not included any fee on this first send but  I didn't see anything I could do about that.</p>

<p>Anyway I then sent the balance of BTC in my Bitcoin-QT wallet, but this time included a 0.0004 BTC fee to the same address.  But, 34 hours later it does not even show it having arrived at the Exodus wallet.</p>

<p>Now I really do not know what to do.  I assume if I leave my Bitcoin-QT wallet up and running it will keep broadcasting the transactions and so they may never disappear. So I have quit the wallet.  But suppose I leave it for a few days. If I fire up the wallet then I assume it will broadcast again and I will be back in the same situation?  I could start it up offline and restore from a backup I did just prior to sending the first transaction - I guess that would cut out the re-broadcasts.  Would that be the thing to do?</p>

<p>The Bitcoin wallet reports that the Transaction Ids are:</p>

<p>(Second transaction with 0.0004 BTC fee):</p>

<p><code>60efa66a8aef482cc3f2ce2ae348427e74feb12db91b579ed4c7ea955fbea0bf</code></p>

<p>(First transaction with fee not added :-(:</p>

<p><code>a0a70213c2e94119357cdac865e404e1ca6f44cf40a4acf9a6e272d4f0dd3f21</code></p>

<p>However when I put those into <a href="https://blockchain.info/" rel="nofollow noreferrer">https://blockchain.info/</a> I am told the transaction does not exist. The same with <a href="https://pool.viabtc.com/tools/txaccelerator/" rel="nofollow noreferrer">ViaBTC Transaction accelerator</a>.</p>

CC BY-SA 3.0
2017-12-03T05:22:09.120Z
Set an even higher fee.
MCCCS
CC BY-SA 3.0
2017-12-03T05:37:27.277Z
You simply can't use this software today, upgrade it.
Claris
CC BY-SA 3.0
2017-12-03T10:06:26.740Z
And thanks MCCCS about idea of setting a higher fee. But if Eponymous is right I can't use the software (although the earlier transaction shows, but unconfirmed) in the Exodus wallet.  And even if I can use the software I am not sure how I could set a higher fee unless I just wait and hope that somehow the bitcoin will restore in the old wallet and then try again.....
Jozwolf
CC BY-SA 3.0
2017-12-03T10:23:44.033Z
Thanks Eponymous - I am not clear how to upgrade from the v0.6.2.2 version of Bitcoin-QT.  I understand that the database structure changed around 8.0.0 so that you cannot do a direct upgrade from 6.2.2 to a higher version.  However, I cannot find v 7.0.0 etc.  I can find a repository of Bitcoin Core at https://github.com/bitcoin/bitcoin/releases?after=v0.11.0rc3 so can I upgrade using these, and if so can you tell me how to go about it or where I can find that out? I really appreciate your help but of course I am nervous about corrupting the data that I have on my existing bitcoin. Tnx!!!!
Jozwolf
CC BY-SA 3.0
2017-12-03T10:25:39.107Z
Obviously if I could extract the private key from my Bitcoin-QT data then I could simply move the data to a new wallet like Exodus - but then I don't know how to extract it either!!!  eeeeeek!!!!
Jozwolf
CC BY-SA 3.0
2017-12-03T23:04:11.730Z
@Jozwolf BItcoin Core 0.6.x (any version before 0.8.0 really), won't be able to sync the blockchain because of this incident: https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki
Ava Chow
<bitcoin-core><wallet><unconfirmed-transactions>
Sending bitcoin from Bitcoin-QT v0.6.2.2 wallet
Jozwolf
# Sending bitcoin from Bitcoin-QT v0.6.2.2 wallet

(Asked by: username_0 on 2017-12-03)

I bought a couple of bitcoin in 2012 where they languished on my successive Mac Book Pros in a Bitcoin-QT v0.6.2.2 wallet. I now realise they are worth - ahem - something! The wallet still fires up even though it is still calls itself a beta wallet and so I thought I would first try to send my lovely bitcoin to a new and glossy Exodus wallet.

Now being completely new to this I got my receive address for my Exodus Wallet and tried sending 0.1 BTC to my Exodus wallet. Eventually (maybe 5 hours later) it showed it had arrived but with zero confirmations. This first transaction still shows with 0.1 BTC "Pending" in the Exodus Wallet (sent Friday Dec 1st 10.04.10 PM).

I realised I had not included any fee on this first send but I didn't see anything I could do about that.

Anyway I then sent the balance of BTC in my Bitcoin-QT wallet, but this time included a 0.0004 BTC fee to the same address. But, 34 hours later it does not even show it having arrived at the Exodus wallet.

Now I really do not know what to do. I assume if I leave my Bitcoin-QT wallet up and running it will keep broadcasting the transactions and so they may never disappear. So I have quit the wallet. But suppose I leave it for a few days. If I fire up the wallet then I assume it will broadcast again and I will be back in the same situation? I could start it up offline and restore from a backup I did just prior to sending the first transaction - I guess that would cut out the re-broadcasts. Would that be the thing to do?

The Bitcoin wallet reports that the Transaction Ids are:

(Second transaction with 0.0004 BTC fee):

`60efa66a8aef482cc3f2ce2ae348427e74feb12db91b579ed4c7ea955fbea0bf`

(First transaction with fee not added :-(:

`a0a70213c2e94119357cdac865e404e1ca6f44cf40a4acf9a6e272d4f0dd3f21`

However when I put those into <https://blockchain.info/> I am told the transaction does not exist. The same with [ViaBTC Transaction accelerator](https://pool.viabtc.com/tools/txaccelerator/).

**Tags:** bitcoin-core, wallet, unconfirmed-transactions

> **Comments:**
> **username_1**: Set an even higher fee.  
> **username_2**: You simply can't use this software today, upgrade it.  
> **username_0**: And thanks username_1 about idea of setting a higher fee. But if Eponymous is right I can't use the software (although the earlier transaction shows, but unconfirmed) in the Exodus wallet.  And even if I can use the software I am not sure how I could set a higher fee unless I just wait and hope that somehow the bitcoin will restore in the old wallet and then try again.....  
> **username_0**: Thanks Eponymous - I am not clear how to upgrade from the v0.6.2.2 version of Bitcoin-QT.  I understand that the database structure changed around 8.0.0 so that you cannot do a direct upgrade from 6.2.2 to a higher version.  However, I cannot find v 7.0.0 etc.  I can find a repository of Bitcoin Core at https://github.com/bitcoin/bitcoin/releases?after=v0.11.0rc3 so can I upgrade using these, and if so can you tell me how to go about it or where I can find that out? I really appreciate your help but of course I am nervous about corrupting the data that I have on my existing bitcoin. Tnx!!!!  
> **username_0**: Obviously if I could extract the private key from my Bitcoin-QT data then I could simply move the data to a new wallet like Exodus - but then I don't know how to extract it either!!!  eeeeeek!!!!  
> **username_3**: @username_0 BItcoin Core 0.6.x (any version before 0.8.0 really), won't be able to sync the blockchain because of this incident: https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki  

---

## 2 answers

### Answer by username_4 on 2017-12-03. Score: 1

I don't know exactly what features are available on your version, but here are some ideas to try.

First, take a backup of your `wallet.dat` file.

1. In the debug window (help menu?), make sure that your peer is actually connected to some other peers so that your transaction will be broadcast to the network.
2. Make sure your node is fully synced to the latest block.
3. Start the application with the `-zapwallettxes=1` argument to delete the transactions that are not in the blockchain from your wallet.
4. Start again with the `-rescan` argument to scan the blockchain for bitcoins assigned to your private keys. This will take a long time (hours possibly).
5. Your bitcoins should be available again, so try to send the transaction again with a higher fee. You can use <https://bitcoinfees.earn.com/> to decide what an appropriate fee is.

If you really want to export your private keys, you can use the `dumpprivkey "address"` command from the console inside the debug window (if the console is available in your version). But be very careful when moving your private keys around, they could get stolen by a key logger, screen grabber, other malware, or phishing sites, etc.

> **Comments:**
> **username_0**: Wow - thanks username_4 for this great information. Getting closer!  But unfortunately the version I have does not have either a Help or Debug window.  I have found a program called PyWallet which is a Python script which can run using MacPorts so that could help. But of course I would like to be able to perform these commands. The only way I can see to do that would be to somehow upgrade my v0.6.2.2 to the earliest version that has the debug/Help window.  But so far I can't find any accessible higher versions...   Tricky!!!  
> **username_0**: Also - username_4 - I am not sure if this version I have (v0.6.2.2) actually can properly synchronise with the modern version of what the Bitcoin servers do....  Eponymous thinks it cant. But on the other hand the first transfer I did did show up in Exodus wallet, but since it had no fee attached it sits there unconfirmed.  I notice that the transaction id has a -0000 at the end of it for both transactions.  Is this supposed to carry the fee I wonder?  
> **username_4**: Tricky. Importing the key into a new wallet may be the easiest solution, although also the riskiest. Looking at the source code for 0.6.2.2, it has the `dumpprivkey` command, so it looks like you have some hope, if you can work out how to run it. https://github.com/bitcoin/bitcoin/blob/v0.6.2.2/src/bitcoinrpc.cpp#L2056  
> **username_0**: Hey username_4 THANKS - well it probably is syncing - phew!  Unfortunately I know nothing about Python scripting.  There is no obvious way to give the program a command line command from its user interface. I suspect that came in a later version.  I can find later versions at  https://github.com/bitcoin/bitcoin/tags?after=v0.7.0 but the instructions on how to build them might as well be written in Martian as far as my humble knowledge goes.  If you could point me at all in the right direction I would  try to upgrade... but....  
> **username_0**: but....  here is a naive approach (???) - if I just wait a few days until the mempool loses interest could I just start my horrid early version of QT and restore it from the backup I made before all this began.  If I did that would it just give me back my bitcoin?  In that case I could try using the program to send the coin with the correct fee. Might work.....  Alternatively given you can read the version of the program I have would you be able to tell me how best to move forward to get dumpprivkey to work ?????  I feel so out of my depth in this!!!!  
> **username_0**: Oh damn - I know I am going to strain your patience. But from something I read Bitcoin Core has an upgrade option which is supposed to upgrade from earlier versions....   Would it be able to read in the .dat file and get me up to speed - or am I in danger of losing the lot, corrupting the files... I have all the fears of ignorance here!  
> **username_5**: @username_0 Remember the first thing username_4 said in his answer: "First, take a backup of your wallet.dat file". It would even be sensible to make 2 or more, and keep at least 1 off site. You'll want backups of the new Exodus wallet too, in case the transactions get confirmed. With those (and any required passwords), you shouldn't have much risk of losing the lot.  
> **username_3**: Any version of Bitcoin Core before 0.8.0 is going to break when it gets to some blocks in 2013. It won't be able to sync past then without some special configuration. You should instead upgrade Bitcoin Core.  
> **username_4**: I'm tempted to delete this answer because it looks like my advice is no good for the version question and Andrew's advice looks good. But I'll leave it in case its useful for others with later versions that read this.  
> **username_0**: Thanks all of you for GREAT and expert advice. OK - so I have bitten the bullet, set up the XCode tools, MacPorts, set up python 2.7.7, set up the dependencies, downloaded pywallet.py, learned enough Unix and python to get the wallet.dat file in a folder with pywallet and navigated to it as Directory, and successfully run a python pywallet.py --dumpwallet > txt. So I have all the keys in JSON format in a txt file. Phew! Who says 71 year olds can't learn new tricks :-) So which one is the private address I import into a new wallet?  
> **username_0**: I can see what I interpret as pairs of public and "sec" private keys.  I can identify the one which initially received the money. And there are two I sent payments to.  The rest are all reserve addresses. And of course there is an initial default address.  If I could get a pointer on this I reckon I may be home, and possibly hosed (whatever that means) :-)  
> **username_0**: Oooops - in the meantime there is Andrew's advice - from 5 hours ago, and username_4's endorsement of it. So I could just put my very old Bitcoin-QT v 6 wallet.dat into Bitcoin Core (latest version) and it would work if I remove the other stuff Andrew mentions? Well I can try that.....  If it works I have still learned heaps of interesting stuff along the way!  

---

### Answer by username_3 on 2017-12-03. Score: 1

Since your blockchain is likely very small and syncing up to the current point with modern software will be very quick, I username_5 suggest that you just upgrade to Bitcoin Core 0.15.1 and delete everything in the Bitcoin Core datadir except for your wallet.dat file.

This will cause Bitcoin COre 0.15.1 to download the entire blockchain, which will happen much more quickly than Bitcoin Core 0.6.x can sync.

The wallet database structure has not changed since Bitcoin Core 0.6.x, so your current wallet should work with the latest version of Bitcoin Core. You should make a backup of your wallet regardless.

> **Comments:**
> **username_0**: Thanks Andrew - it seems to have read the transactions from the old wallet.dat perfectly well and is now synchronising.  And now I have the command window to do any of the little tasks I need.  Thanks a HEAP.  Everyone has been so helpful I could hug you all :-)  

---

