I loaded the 218 keys and swept them, the transaction window says there were 4 individual transactions totaling 2504.52489 mBTC. So the default transaction fees amounted to 0.00225 BTC, which is nice
Thanks for all of the input,
kev.
Topic: Bitcoin Wallet v0.8.6 beta (Read 1670 times)
OK Success,
I loaded the 218 keys and swept them, the transaction window says there were 4 individual transactions totaling 2504.52489 mBTC. So the default transaction fees amounted to 0.00225 BTC, which is nice
Thanks for all of the input,
kev.
I loaded the 218 keys and swept them, the transaction window says there were 4 individual transactions totaling 2504.52489 mBTC. So the default transaction fees amounted to 0.00225 BTC, which is nice
Thanks for all of the input,
kev.
Theoretically, I think you can just attempt to sweep all the private keys and it will just discard the ones with zero balance... so you don't need to go through them all one by one.
Alternatively, you can create a new Electrum wallet using the "Use public or private keys" option in Electrum and it will let you import all those private keys in one go so you can pretty much instantly see the entire transaction history of all your keys/addresses... and what your final balance currently is.
I wouldn't recommend keeping them in a public/private key Electrum wallet long term. I would suggest that after you are happy that you have all your coins, that you then send the coins to an address in a new HD "seeded" Electrum wallet for the added safety that a seeded wallet provides (full restore from just 12 word seed etc). This is effectively what sweeping does anyway.
Alternatively, you can create a new Electrum wallet using the "Use public or private keys" option in Electrum and it will let you import all those private keys in one go so you can pretty much instantly see the entire transaction history of all your keys/addresses... and what your final balance currently is.
I wouldn't recommend keeping them in a public/private key Electrum wallet long term. I would suggest that after you are happy that you have all your coins, that you then send the coins to an address in a new HD "seeded" Electrum wallet for the added safety that a seeded wallet provides (full restore from just 12 word seed etc). This is effectively what sweeping does anyway.
Thanks very much for that input.
I do not have an in depth knowledge of the intricacies of the QT wallet so I am confused to say the least.
When I used pywallet to dumpprivkey contents to wallet.txt, it gave about 200 addresses and keys. I only ever used the single address for transactions so perhaps some of those addresses listed are "change addresses" as previously pointed out by achow.
Now that I have the keys, I want to sweep them into my Electrum wallet so if I use Blockchain.info and identify all the change addresses from my transactions, I can cut and paste the privkeys from the wallet.txt file into Electrum for sweeping along with the key for what I consider as my main wallet address. I'll give it a go and see what happens
cheers,
kev
I do not have an in depth knowledge of the intricacies of the QT wallet so I am confused to say the least.
When I used pywallet to dumpprivkey contents to wallet.txt, it gave about 200 addresses and keys. I only ever used the single address for transactions so perhaps some of those addresses listed are "change addresses" as previously pointed out by achow.
Now that I have the keys, I want to sweep them into my Electrum wallet so if I use Blockchain.info and identify all the change addresses from my transactions, I can cut and paste the privkeys from the wallet.txt file into Electrum for sweeping along with the key for what I consider as my main wallet address. I'll give it a go and see what happens
cheers,
kev
Yes, pywallet dumped the data and there were 200+ addresses each with a list of keys including a "sec" key so I am assuming that is the privkey for each address as each one starts with the suffix you mentioned.
I found my wallet address in among the data along with the "change" address you identified, so it looks like it worked
So all of those change addresses which are shown on Blockchain.info are in the wallet.txt too?
I am a little confused because I have been through all of the outgoings and incomings recorded in my wallet and the final balance comes to 2.50677 BTC and this is what it shows as confirmed balance. Yet BCI says balance is Zero.
cheers,
kev
I found my wallet address in among the data along with the "change" address you identified, so it looks like it worked
So all of those change addresses which are shown on Blockchain.info are in the wallet.txt too?
I am a little confused because I have been through all of the outgoings and incomings recorded in my wallet and the final balance comes to 2.50677 BTC and this is what it shows as confirmed balance. Yet BCI says balance is Zero.
cheers,
kev
I used a website called walletexplorer to check your address 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb. It estimates all the other addresses in a wallet.dat and their balances. You can see the results here.
https://www.walletexplorer.com/wallet/045bba007c5923b5/addresses
It shows this address containing 0.01229653 Bitcoins as part of your wallet
17LXn6KpumyBbyuz9MyeZ6WVLZwfBpF92s
It also shows this address containing 0.0104441 Bitcoins as part of your wallet
17gKbFaoRjdpDyNKpdBVkqevdKR5kAS3Mi
Apart from that all the other addresses it shows are empty. Do you recognise either of the addresses containing coins?
Walletexplorer only estimates which addresses are in a wallet, so there might be others it missed.
Yes, pywallet dumped the data and there were 200+ addresses each with a list of keys including a "sec" key so I am assuming that is the privkey for each address as each one starts with the suffix you mentioned.
I found my wallet address in among the data along with the "change" address you identified, so it looks like it worked
So all of those change addresses which are shown on Blockchain.info are in the wallet.txt too?
I am a little confused because I have been through all of the outgoings and incomings recorded in my wallet and the final balance comes to 2.50677 BTC and this is what it shows as confirmed balance. Yet BCI says balance is Zero.
cheers,
kev
I found my wallet address in among the data along with the "change" address you identified, so it looks like it worked
So all of those change addresses which are shown on Blockchain.info are in the wallet.txt too?
I am a little confused because I have been through all of the outgoings and incomings recorded in my wallet and the final balance comes to 2.50677 BTC and this is what it shows as confirmed balance. Yet BCI says balance is Zero.
cheers,
kev
Very strange....
The last transaction on your link is a send to: 1EExPs6ykuk7hfHbQZfpdf39cqMuC5LuWL @ 4.4999 BTC on 23rd Jan 2014.
There is no record of this in my wallet transactions:
Yes there is, the transaction that you highlighted is that transaction. 1EE... is a change address of yours; the other output in that transaction corresponds to who you actually sent the Bitcoin to as indicated by the transaction list.The last transaction on your link is a send to: 1EExPs6ykuk7hfHbQZfpdf39cqMuC5LuWL @ 4.4999 BTC on 23rd Jan 2014.
There is no record of this in my wallet transactions:
Did pywallet work? Your private keys will be 51 or 52 characters long and begin with a 5, K, or L. If you see any strings like that, then you have private keys which you can try to import into another wallet.
It would appear that that address is empty anyway (and has been since Jan 2014): https://blockchain.info/address/13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb
Perhaps your coins are contained in other addresses? You might want to start checking all the addresses that pywallet dumped on a block explorer and see if you can find the one(s) that has your 2.5 BTC
Another option could be to backup the wallet file... and then update the bitcoin client? Not necessarily to the very latest, but at least something after 0.8.6 and see if it is more stable.
Perhaps your coins are contained in other addresses? You might want to start checking all the addresses that pywallet dumped on a block explorer and see if you can find the one(s) that has your 2.5 BTC
Another option could be to backup the wallet file... and then update the bitcoin client? Not necessarily to the very latest, but at least something after 0.8.6 and see if it is more stable.
Very strange....
The last transaction on your link is a send to: 1EExPs6ykuk7hfHbQZfpdf39cqMuC5LuWL @ 4.4999 BTC on 23rd Jan 2014.
There is no record of this in my wallet transactions:
I have been through every transaction listed in my wallet and the balance shown is correct, yet it does not tally with your link. The 4.4999 BTC transaction above is worrying??
cheers,
kev
In Electrum 2.0, you cannot import private keys in a wallet that has a seed. You should sweep them instead.
If you want to import private keys and not sweep them you need to create a special wallet that does not have a seed. For this, create a new wallet, select “restore”, and instead of typing your seed, type a list of private keys, or a list of addresses if you want to create a watching-only wallet.
If you want to import private keys and not sweep them you need to create a special wallet that does not have a seed. For this, create a new wallet, select “restore”, and instead of typing your seed, type a list of private keys, or a list of addresses if you want to create a watching-only wallet.
Thanks for that,
The last transaction from this wallet was on 12th February 2014 where I sent 1 BTC.
I noticed whilst the wallet was syncing it got to 116 weeks to go and the confirmed balance was still 2.5 odd BTC. The coins are unlikely to be stored under another address as I only ever used the single address in this particular wallet.
It has been dormant on a disused laptop since it was last used, offline with full encryption.
I am checking through all the transaction list now.
cheers,
kev
The last transaction from this wallet was on 12th February 2014 where I sent 1 BTC.
I noticed whilst the wallet was syncing it got to 116 weeks to go and the confirmed balance was still 2.5 odd BTC. The coins are unlikely to be stored under another address as I only ever used the single address in this particular wallet.
It has been dormant on a disused laptop since it was last used, offline with full encryption.
I am checking through all the transaction list now.
cheers,
kev
It would appear that that address is empty anyway (and has been since Jan 2014): https://blockchain.info/address/13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb
Perhaps your coins are contained in other addresses? You might want to start checking all the addresses that pywallet dumped on a block explorer and see if you can find the one(s) that has your 2.5 BTC
Another option could be to backup the wallet file... and then update the bitcoin client? Not necessarily to the very latest, but at least something after 0.8.6 and see if it is more stable.
Perhaps your coins are contained in other addresses? You might want to start checking all the addresses that pywallet dumped on a block explorer and see if you can find the one(s) that has your 2.5 BTC
Another option could be to backup the wallet file... and then update the bitcoin client? Not necessarily to the very latest, but at least something after 0.8.6 and see if it is more stable.
As soon as I enter walletpassphrase 600 the client crashes saying it has requested runtime to terminate in an unusual manner.
when I enter dumpprivkey it returns:
20:50:46

dumpprivkey 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb
20:50:48

Private key for address 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb is not known (code -4)
?
Passphrase is correct as shown from the text dump using pywallet
cheers,
kev
when I enter dumpprivkey
20:50:46

dumpprivkey 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb
20:50:48

Private key for address 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb is not known (code -4)
?
Passphrase is correct as shown from the text dump using pywallet
cheers,
kev
Did you do the "walletpassphrase " command?
Something like: walletpassphrase thisIsMyPassword 600
Then try the dumpprivkey command again.
Something like: walletpassphrase thisIsMyPassword 600
Then try the dumpprivkey command again.
Just tried the "dumprivpkey" in the wallet again and it gave:
18:32:06

dumpprivkey 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb passphrase
18:32:09

dumpprivkey
Reveals the private key corresponding to. (code -1)
18:33:05

dumpprivkey 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb
18:33:05

Private key for address 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb is not known (code -4)
cheers,
kev
18:32:06

dumpprivkey 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb passphrase
18:32:09

dumpprivkey
Reveals the private key corresponding to
18:33:05

dumpprivkey 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb
18:33:05

Private key for address 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb is not known (code -4)
cheers,
kev
Thanks very much,
I tried all of that, put the following in the Pywallet.py command
C:\pywallet-master> pywallet.py --dumpwallet actual wallet address > wallet.txt --passphrase actual passphrase
and I got the following:
WARNING:root:pycrypto or libssl not found, decryption may be slow.
Now there is now a wallet.txt file in the pywallet folder contains:
'ecdsa' package is not installed, pywallet won't be able to sign/verify messages
Wallet data not recognized: {'__type__': 'orderposnext', '__value__': '\x93\x00\x00\x00\x00\x00\x00\x00', '__key__': '\x0corderposnext'}
The wallet is encrypted and the passphrase is correct
{
"bestblock": "numerical code here",
"ckey": [],
"defaultkey": "13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb",
"keys": [
There are a list of addresses (none of which I have ever used) and associated "encrypted-privkey", "hexsec" , "pubkey" , "sec" , "secret" data
Not sure if it has dumped the privkey for 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb ??
cheers,
kev
I tried all of that, put the following in the Pywallet.py command
C:\pywallet-master> pywallet.py --dumpwallet actual wallet address > wallet.txt --passphrase actual passphrase
and I got the following:
WARNING:root:pycrypto or libssl not found, decryption may be slow.
Now there is now a wallet.txt file in the pywallet folder contains:
'ecdsa' package is not installed, pywallet won't be able to sign/verify messages
Wallet data not recognized: {'__type__': 'orderposnext', '__value__': '\x93\x00\x00\x00\x00\x00\x00\x00', '__key__': '\x0corderposnext'}
The wallet is encrypted and the passphrase is correct
{
"bestblock": "numerical code here",
"ckey": [],
"defaultkey": "13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb",
"keys": [
There are a list of addresses (none of which I have ever used) and associated "encrypted-privkey", "hexsec" , "pubkey" , "sec" , "secret" data
Not sure if it has dumped the privkey for 13oxYTF1CDzz63FV6FDMT7xuzpH8TRnYgb ??
cheers,
kev
Perhaps itr might be better if I uninstall everything I have done so far and start over,
I have other wallet.dat files which I need to get keys from so this route would be the best option
This is a guide you published in Dec 2015, please can you review it and add any changes?
I have other wallet.dat files which I need to get keys from so this route would be the best option
This is a guide you published in Dec 2015, please can you review it and add any changes?
Sure.
Quote
Go to https://www.python.org/downloads/ and download python 2.7.11. Run the installer and it will install python. Make sure that when you get to the "Customize features" screen you scroll down and click the dropdown next to "Add python.exe to path" Select "Will be installed on local hard drive" then you can continue.
Then download this file: https://github.com/downloads/jackjack-jj/pywallet/PWI_0.0.3.exe (just click the link)
Run the program and have it extract to whatever folder you want. Follow the wizard. Once it finishes, go to that folder. If you do not see a file named pywallet.py, double click the file named install.bat. A command prompt will appear briefly and then disappear. Once it is gone, you should now see the pywallet.py file.
In the folder where pywallet.py is located, make sure that nothing is selected. Then do Shift + Right Click and in the menu that pops up select "Open command window here". In the window that pops up, type
This command will dump everything from the wallet to a file in the same folder called wallet.txt. If you have a passphrase on the wallet, add the option --passphrase to the command after pywallet.py and --dumpwallet. Make sure there are spaces between them all. If the directory where your wallet is located is not the Bitcoin default, then you will also need the --datadir= option also added in in the same manner as the passphrase.
Then download this file: https://github.com/downloads/jackjack-jj/pywallet/PWI_0.0.3.exe (just click the link)
Run the program and have it extract to whatever folder you want. Follow the wizard. Once it finishes, go to that folder. If you do not see a file named pywallet.py, double click the file named install.bat. A command prompt will appear briefly and then disappear. Once it is gone, you should now see the pywallet.py file.
In the folder where pywallet.py is located, make sure that nothing is selected. Then do Shift + Right Click and in the menu that pops up select "Open command window here". In the window that pops up, type
Code:
pywallet.py --dumpwallet > wallet.txt
This command will dump everything from the wallet to a file in the same folder called wallet.txt. If you have a passphrase on the wallet, add the option --passphrase
Perhaps itr might be better if I uninstall everything I have done so far and start over,
I have other wallet.dat files which I need to get keys from so this route would be the best option
This is a guide you published in Dec 2015, please can you review it and add any changes?
Go to https://github.com/jackjack-jj/pywallet and download the zip file. Extract the stuff to another folder.
Then go to https://www.python.org/downloads/ and download python 2.7.11. Run the installer and it will install python. Make sure that when you get to the "Customize features" screen you scroll down and click the dropdown next to "Add python.exe to path" Select "Will be installed on local hard drive" then you can continue.
Then go to https://pypi.python.org/pypi/zope.interface/4.1.3#downloads and select the correct file. The file you want will be either zope.interface-4.1.3-py2.7-win32.egg or zope.interface-4.1.3-py2.7-win-amd64.egg depending on if your windows version is 32 bit (the first file) or 64 bit (second file).
Then download https://bootstrap.pypa.io/ez_setup.py. If that link brings you to a page of text, right click and select "save as"
Go to the folder where you saved the ez_setup file and make sure that nothing is selected. Then do Shift + Right Click and in the menu that pops up select "Open command window here". In the window that pops up, type
Code:
ez_setup.py
After that runs, close that window and go to the folder where you installed python. Then go to the scripts folder within that. Copy the zope interface file you downloaded to that folder. Then open the command window again. This time type
Code:
easy_install.exe
where is the name of the file you copied.
Then go to the folder where you extracted the pywallet files and open another command window. Here just type
Code:
pywallet.py --dumpwallet > wallet.txt
This command will dump everything from the wallet to a file in the same folder called wallet.txt. If you have a passphrase on the wallet, add the option --passphrase to the command after pywallet.py and --dumpwallet. Make sure there are spaces between them all. If the directory where your wallet is located is not the Bitcoin default, then you will also need the --datadir= option also added in in the same manner as the passphrase.
cheers,
kev
I have other wallet.dat files which I need to get keys from so this route would be the best option
This is a guide you published in Dec 2015, please can you review it and add any changes?
Go to https://github.com/jackjack-jj/pywallet and download the zip file. Extract the stuff to another folder.
Then go to https://www.python.org/downloads/ and download python 2.7.11. Run the installer and it will install python. Make sure that when you get to the "Customize features" screen you scroll down and click the dropdown next to "Add python.exe to path" Select "Will be installed on local hard drive" then you can continue.
Then go to https://pypi.python.org/pypi/zope.interface/4.1.3#downloads and select the correct file. The file you want will be either zope.interface-4.1.3-py2.7-win32.egg or zope.interface-4.1.3-py2.7-win-amd64.egg depending on if your windows version is 32 bit (the first file) or 64 bit (second file).
Then download https://bootstrap.pypa.io/ez_setup.py. If that link brings you to a page of text, right click and select "save as"
Go to the folder where you saved the ez_setup file and make sure that nothing is selected. Then do Shift + Right Click and in the menu that pops up select "Open command window here". In the window that pops up, type
Code:
ez_setup.py
After that runs, close that window and go to the folder where you installed python. Then go to the scripts folder within that. Copy the zope interface file you downloaded to that folder. Then open the command window again. This time type
Code:
easy_install.exe
where
Then go to the folder where you extracted the pywallet files and open another command window. Here just type
Code:
pywallet.py --dumpwallet > wallet.txt
This command will dump everything from the wallet to a file in the same folder called wallet.txt. If you have a passphrase on the wallet, add the option --passphrase
cheers,
kev
Spent most of the afternoon trying to research then follow JJ's pywallet approach which you suggested. I found one of your very detailed and step by step posts on how to go about the whole dl process and thought... hey... even I can do this. but as I confidently opened up cmd and typed in ez_setup.py I was met with: 'ez_setup.py is not recognized as an internal or external command, operable program or batch file.' uninstalled everything and started again, making double sure I followed your instructions and downloaded the correct files but same again.
You need to install python 2 and when you install it, make sure that it is added to the path (I think there is an option for that in the installer). Then when you want to run any of the python scripts, you need to do Code:
python
10 minutes after I entered the dumpprivkey cmd:
2017-06-22 14:31:26 *** System error: CDB() : can't open database file wallet.dat, error -30974
2017-06-22 14:31:26 *** System error: CDB() : can't open database file wallet.dat, error -30974
The wallet immediately freezes so I cannot enter the wallet debug log file
Could you post the debug.log file?
You do not need to run the wallet to open the debug.log file. The file is in your DATADIR (the place where you normally find your wallet.dat file). thanks,
got it
Shouldn't it at least give some sort of response?
cheers,
kev
cheers,
kev
Anyway, I followed your advice and the Client just crashes every time I try and put my encryption password and dumpprivkey cmd into the PRC Console.
Could you post the debug.log file?You can also try using pywallet: https://github.com/jackjack-jj/pywallet. There are instructions at that link to get pywallet running, but it does require you to use the command line. You can run it with the web interface --web option and should be able to export the private keys from there.
Spent most of the afternoon trying to research then follow JJ's pywallet approach which you suggested. I found one of your very detailed and step by step posts on how to go about the whole dl process and thought... hey... even I can do this. but as I confidently opened up cmd and typed in ez_setup.py I was met with: 'ez_setup.py is not recognized as an internal or external command, operable program or batch file.' uninstalled everything and started again, making double sure I followed your instructions and downloaded the correct files but same again.
went to RPC console on my syncing wallet and entered: "dumpprivkey
?
went to the debug notepad in datadir and it doesnt look like there is anything in the last few minutes related to these commands
2017-06-22 14:00:52 SetBestChain: new best=000000000000000003fb1f638f26c2fc021ef12ff0b140362d140cc642ac1f8d height=350766 log2_work=82.562755 tx=64512496 date=2015-04-05 01:24:52 progress=0.493472
2017-06-22 14:01:18 Committing 3607 changed transactions to coin database...
2017-06-22 14:01:18 SetBestChain: new best=0000000000000000049bd399adb8f8a925e18b0a4560a8d4d9ed92c2ae9542a5 height=350767 log2_work=82.562795 tx=64513813 date=2015-04-05 02:03:08 progress=0.493487
2017-06-22 14:01:18 SetBestChain: 19 of last 100 blocks above version 2
2017-06-22 14:01:31 Committing 1549 changed transactions to coin database...
2017-06-22 14:01:31 SetBestChain: new best=000000000000000017402a1d80a3b4e08d32cfa3e0fd2fc73e95d655eb2a61ad height=350768 log2_work=82.562836 tx=64514462 date=2015-04-05 02:09:12 progress=0.493492
2017-06-22 14:01:31 SetBestChain: 19 of last 100 blocks above version 2
2017-06-22 14:01:47 Committing 2205 changed transactions to coin database...
2017-06-22 14:01:47 SetBestChain: new best=00000000000000000ecdbea97f34d87c402cacc75d096e68d902d35c523de520 height=350769 log2_work=82.562877 tx=64515368 date=2015-04-05 02:25:03 progress=0.493500
2017-06-22 14:01:47 SetBestChain: 18 of last 100 blocks above version 2
2017-06-22 14:01:49 SetBestChain: new best=00000000000000000c2c2deeb24cf946cdf320a5f94959fa1f97914f88a740d4 height=350770 log2_work=82.562917 tx=64515427 date=2015-04-05 02:26:52 progress=0.493501
2017-06-22 14:01:57 SetBestChain: new best=000000000000000005bfb2b8e418b588f839529ce150b177182e6112c0aab118 height=350771 log2_work=82.562958 tx=64515950 date=2015-04-05 02:40:33 progress=0.493507
2017-06-22 14:02:05 SetBestChain: new best=0000000000000000004dbf7fe1d0bc1457817bfde1f20b541cd3295fa6fab934 height=350772 log2_work=82.562998 tx=64516691 date=2015-04-05 03:01:45 progress=0.493515
2017-06-22 14:02:20 Committing 6603 changed transactions to coin database...
2017-06-22 14:02:21 SetBestChain: new best=0000000000000000106c00add86e9083b2fbd221ed0b572e712110ddf9f5107a height=350773 log2_work=82.563039 tx=64518167 date=2015-04-05 03:36:00 progress=0.493530
2017-06-22 14:02:21 SetBestChain: 20 of last 100 blocks above version 2
2017-06-22 14:02:24 Pre-allocating up to position 0x1100000 in rev00251.dat
2017-06-22 14:02:24 SetBestChain: new best=00000000000000000fbe1740f7f9584cc59aea94dae205ac78b898ce3cdddd4f height=350774 log2_work=82.563079 tx=64518660 date=2015-04-05 03:38:45 progress=0.493533
2017-06-22 14:02:31 SetBestChain: new best=0000000000000000177d45abcb7ce3b4d772bfe5cf93ad11381747043dc0dce5 height=350775 log2_work=82.56312 tx=64519311 date=2015-04-05 03:48:16 progress=0.493539
2017-06-22 14:02:45 Committing 5006 changed transactions to coin database...
2017-06-22 14:02:45 SetBestChain: new best=0000000000000000045edc9dabfb99a7c1d01e63875a687f5024c0c1a7cc1215 height=350776 log2_work=82.56316 tx=64520246 date=2015-04-05 04:09:53 progress=0.493548
2017-06-22 14:02:45 SetBestChain: 20 of last 100 blocks above version 2
2017-06-22 14:02:54 SetBestChain: new best=000000000000000002fd5595530d0d5fb53a6baa063988d8a47fa5fa483e8787 height=350777 log2_work=82.563201 tx=64520909 date=2015-04-05 04:19:53 progress=0.493554
2017-06-22 14:02:59 SetBestChain: new best=000000000000000012647e97404bae479ec33bf613e8b5982d6c7a2552bc4843 height=350778 log2_work=82.563241 tx=64521172 date=2015-04-05 04:25:12 progress=0.493556
2017-06-22 14:03:10 Committing 3990 changed transactions to coin database...
2017-06-22 14:03:10 SetBestChain: new best=000000000000000011c44a17582e5add75e8e4c35e4f9846bfed105bfe653baa height=350779 log2_work=82.563282 tx=64521810 date=2015-04-05 04:39:58 progress=0.493563
2017-06-22 14:03:10 SetBestChain: 20 of last 100 blocks above version 2
2017-06-22 14:03:18 SetBestChain: new best=0000000000000000133dc1577c49520c5e25b07f0f9a90db5819da5841747614 height=350780 log2_work=82.563322 tx=64522415 date=2015-04-05 04:50:23 progress=0.493568
2017-06-22 14:03:25 SetBestChain: new best=0000000000000000155f78ff9800416771362242de8b30a04fee1f68c3a59fa0 height=350781 log2_work=82.563363 tx=64522878 date=2015-04-05 04:58:40 progress=0.493573
2017-06-22 14:03:34 SetBestChain: new best=0000000000000000149da4eace9da6968142fa2491a0c830202cd45c8809c1f2 height=350782 log2_work=82.563403 tx=64523696 date=2015-04-05 05:14:00 progress=0.493580
2017-06-22 14:03:38 SetBestChain: new best=000000000000000012d24ce222e3c81d4c148f2bce88f752c0dba184c3bc6844 height=350783 log2_work=82.563444 tx=64524040 date=2015-04-05 05:20:56 progress=0.493583
2017-06-22 14:03:38 nActualTimespan = 1142845 before bounds
2017-06-22 14:03:38 GetNextWorkRequired RETARGET
2017-06-22 14:03:38 nTargetTimespan = 1209600 nActualTimespan = 1142845
2017-06-22 14:03:38 Before: 181788f2 00000000000000001788f2000000000000000000000000000000000000000000
2017-06-22 14:03:38 After: 18163c71 0000000000000000163c71514e4a39f8f4e4a39f8f4e4a39f8f4e4a39f8f4e4a
2017-06-22 14:03:38 SetBestChain: new best=000000000000000010f21b105b759b2c1df9c20f749ecd9d6e410a06a9d82b2a height=350784 log2_work=82.563487 tx=64524075 date=2015-04-05 05:22:25 progress=0.493584
2017-06-22 14:03:40 SetBestChain: new best=000000000000000001aa0f63c69427014d3985c227ba522f490ff88e3ced100d height=350785 log2_work=82.563529 tx=64524340 date=2015-04-05 05:27:34 progress=0.493586
2017-06-22 14:03:45 SetBestChain: new best=00000000000000000d085c7af6e08006fef507af55bac3b0a8ee0bb692583efa height=350786 log2_work=82.563572 tx=64524815 date=2015-04-05 05:37:10 progress=0.493591
2017-06-22 14:03:47 SetBestChain: new best=000000000000000014013f77a12a567375726862e9932b0e00f2ca645b7e1dd7 height=350787 log2_work=82.563615 tx=64525077 date=2015-04-05 05:45:30 progress=0.493594
2017-06-22 14:03:53 SetBestChain: new best=0000000000000000029be712dd59ea6e86626f8536867df9d4394395e59dedcb height=350788 log2_work=82.563658 tx=64525497 date=2015-04-05 05:54:29 progress=0.493598
2017-06-22 14:03:56 SetBestChain: new best=000000000000000013141cb42068a8c9efeca8661054e642d41544e3b4961965 height=350789 log2_work=82.563701 tx=64525770 date=2015-04-05 06:00:21 progress=0.493601
2017-06-22 14:03:58 SetBestChain: new best=00000000000000001346f0404826ceba4469d3470f2225a657c26f5847f6149a height=350790 log2_work=82.563744 tx=64525940 date=2015-04-05 06:03:40 progress=0.493603
2017-06-22 14:04:13 Committing 10676 changed transactions to coin database...
2017-06-22 14:04:14 SetBestChain: new best=00000000000000000b91c5c3d22671595b0947147e5d7a3308be688d256edde0 height=350791 log2_work=82.563787 tx=64526565 date=2015-04-05 06:12:49 progress=0.493608
2017-06-22 14:04:14 SetBestChain: 15 of last 100 blocks above version 2
2017-06-22 14:04:28 Committing 1507 changed transactions to coin database...
2017-06-22 14:04:29 SetBestChain: new best=000000000000000000a2f774b3cc230bc7b3b46c3c1d0c3156bcffdd272d9596 height=350792 log2_work=82.56383 tx=64527124 date=2015-04-05 06:25:01 progress=0.493613
2017-06-22 14:04:29 SetBestChain: 15 of last 100 blocks above version 2
2017-06-22 14:04:30 SetBestChain: new best=00000000000000000068763c0666852b6a5c8c9fa8be462932a01dbd69bdf75e height=350793 log2_work=82.563872 tx=64527235 date=2015-04-05 06:26:54 progress=0.493614
2017-06-22 14:04:59 Committing 3717 changed transactions to coin database...
2017-06-22 14:05:00 SetBestChain: new best=000000000000000003293c2857c25bac15565671e104c7b82de5a1792fd8a5a4 height=350794 log2_work=82.563915 tx=64528630 date=2015-04-05 06:52:58 progress=0.493627
2017-06-22 14:05:00 SetBestChain: 15 of last 100 blocks above version 2
2017-06-22 14:05:05 SetBestChain: new best=0000000000000000110ad4a49d2a049eb9544f1f4310438c04b7628516a123df height=350795
Anyway thanks for everyones help and suggestions,
Its very much appreciated.
cheers,
kev
I am assuming you have a windows operating system.
Try installing your Bitcoin Wallet v0.8.6 beta into a different folder to the one it's presently installed in. Afterwards right click the bitcoin-qt.exe and select "Create shortcut" from the list that appears. Right click the shortcut and select "properties" from the list that appears.
Click the "shortcut" tab in the properties window, then look for the first text box in it labelled "target". Copy the line of text below and paste it to the end of whatever is in the "target" text box.
-datadir=.
Make sure you copy the leading space and trailing . from the line of text above.
The text box should look something like this.
Afterwards click the "apply" button, then the "OK" button to close the shortcut properties window.
Put a copy of your wallet.dat file in the same folder as the bitcoin-qt.exe shortcut, then double click the shortcut you created to start bitcoin-qt.exe running.
Hopefully it should start without any error. The procedure above makes a portable bitcoin-qt wallet that doesn't use any of the files in appdata.
Try installing your Bitcoin Wallet v0.8.6 beta into a different folder to the one it's presently installed in. Afterwards right click the bitcoin-qt.exe and select "Create shortcut" from the list that appears. Right click the shortcut and select "properties" from the list that appears.
Click the "shortcut" tab in the properties window, then look for the first text box in it labelled "target". Copy the line of text below and paste it to the end of whatever is in the "target" text box.
-datadir=.
Make sure you copy the leading space and trailing . from the line of text above.
The text box should look something like this.
Afterwards click the "apply" button, then the "OK" button to close the shortcut properties window.
Put a copy of your wallet.dat file in the same folder as the bitcoin-qt.exe shortcut, then double click the shortcut you created to start bitcoin-qt.exe running.
Hopefully it should start without any error. The procedure above makes a portable bitcoin-qt wallet that doesn't use any of the files in appdata.
The wallet immediately freezes so I cannot enter the wallet debug log file
Could you post the debug.log file?
You do not need to run the wallet to open the debug.log file. The file is in your DATADIR (the place where you normally find your wallet.dat file).
As soon as I enter the passphrase 600 I get a runtime error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: bitcoin-qt.exe
Application Version: 0.8.6.0
Application Timestamp: 4d44aa00
Fault Module Name: bitcoin-qt.exe
Fault Module Version: 0.8.6.0
Fault Module Timestamp: 4d44aa00
Exception Code: 40000015
Exception Offset: 00fb640a
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: ab72
Additional Information 2: ab7287280a13fdaeadadb227ed690030
Additional Information 3: 0aa9
Additional Information 4: 0aa971706823820736b94a69b100f3c0
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
The wallet immediately freezes so I cannot enter the wallet debug log file
cheers,
kev
Problem signature:
Problem Event Name: APPCRASH
Application Name: bitcoin-qt.exe
Application Version: 0.8.6.0
Application Timestamp: 4d44aa00
Fault Module Name: bitcoin-qt.exe
Fault Module Version: 0.8.6.0
Fault Module Timestamp: 4d44aa00
Exception Code: 40000015
Exception Offset: 00fb640a
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: ab72
Additional Information 2: ab7287280a13fdaeadadb227ed690030
Additional Information 3: 0aa9
Additional Information 4: 0aa971706823820736b94a69b100f3c0
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
The wallet immediately freezes so I cannot enter the wallet debug log file
cheers,
kev
Anyway, I followed your advice and the Client just crashes every time I try and put my encryption password and dumpprivkey cmd into the PRC Console.
Could you post the debug.log file?You can also try using pywallet: https://github.com/jackjack-jj/pywallet. There are instructions at that link to get pywallet running, but it does require you to use the command line. You can run it with the web interface --web option and should be able to export the private keys from there.
Thanks for that advice,
During my search on this subject I saw you give pretty much the same advice, although a little more detailed to another member re the same problem.
Anyway, I followed your advice and the Client just crashes every time I try and put my encryption password and dumpprivkey cmd into the PRC Console.
cheers,
kev
During my search on this subject I saw you give pretty much the same advice, although a little more detailed to another member re the same problem.
Anyway, I followed your advice and the Client just crashes every time I try and put my encryption password and dumpprivkey cmd into the PRC Console.
cheers,
kev
The wallet.dat file is a Bitcoin Core specific thing, just as the Electrum wallet format is an Electrum specific thing. In order to move your Bitcoin to Electrum, you will need to export your private keys by using the dumpprivkey RPC command. You must use this command for all of your addresses, including change. Then you can make a new Electrum wallet and go to Wallet > Private Keys > Sweep and sweep the Bitcoin into your new Electrum wallet. Sweeping makes a transaction that spends all of the Bitcoin from the private keys you specified and sends the Bitcoin to an address in your Electrum wallet.
Hi Fellas,
Have a v0.8.6 beta wallet containing 2.5 Bitcoins that is out of sync by 148 weeks. I just worked out that at my current internet speed, it will take minimum 7 days and 8 hours to sync with the network. It is currently syncing but seems really unstable, keeps crashing for whatever reason and I have to restart it.
I have just downloaded a new and clean Electrum 2.8.3 wallet on another computer.
So my question is:
can i copy and paste the wallet.dat file from the QT wallet to the Electrum wallet in Apps/roaming, reboot and hey presto funds transferred? If not, is there a way that I can transfer contents of wallet A to wallet B and access the funds before the QT wallet has synced with the blockchain?
cheers,
Kev
Have a v0.8.6 beta wallet containing 2.5 Bitcoins that is out of sync by 148 weeks. I just worked out that at my current internet speed, it will take minimum 7 days and 8 hours to sync with the network. It is currently syncing but seems really unstable, keeps crashing for whatever reason and I have to restart it.
I have just downloaded a new and clean Electrum 2.8.3 wallet on another computer.
So my question is:
can i copy and paste the wallet.dat file from the QT wallet to the Electrum wallet in Apps/roaming, reboot and hey presto funds transferred? If not, is there a way that I can transfer contents of wallet A to wallet B and access the funds before the QT wallet has synced with the blockchain?
cheers,
Kev
Jump to: