Don't bother, just answer the following question and I'll tell you what to do:
How do you import private keys into Electrum? ie do you type the "fac86293d82838..." private key by hand?
I just click on Import -> Private Keys. Am i wrong?
Topic: PYWallet Help - Dumping encrypted private key - page 2. (Read 8785 times)
Don't bother, just answer the following question and I'll tell you what to do:
How do you import private keys into Electrum? ie do you type the "fac86293d82838..." private key by hand?
I just click on Import -> Private Keys. Am i wrong?
Don't bother, just answer the following question and I'll tell you what to do:
How do you import private keys into Electrum? ie do you type the "fac86293d82838..." private key by hand?
Oh I see, I misread your post
You are trying to dump keys to a CSV, is it what you really want to do?
If not (or if in doubt), use "Dump your wallet"
If you really want to use CSV export, tell me and I'll tell you what to do
You are trying to dump keys to a CSV, is it what you really want to do?
If not (or if in doubt), use "Dump your wallet"
If you really want to use CSV export, tell me and I'll tell you what to do
I need all private keys, including those of hidden change address, for importing my balance, addresses and history to Electrum.
As i'm trying to do here.
Oh I see, I misread your post
You are trying to dump keys to a CSV, is it what you really want to do?
If not (or if in doubt), use "Dump your wallet"
If you really want to use CSV export, tell me and I'll tell you what to do
You are trying to dump keys to a CSV, is it what you really want to do?
If not (or if in doubt), use "Dump your wallet"
If you really want to use CSV export, tell me and I'll tell you what to do
What is written in the console?
2013-09-03 17:02:43+0200 [HTTPChannel,0,127.0.0.1] Wallet Dir: /home/simpic/.bitcoin
2013-09-03 17:02:43+0200 [HTTPChannel,0,127.0.0.1] Wallet Name: wallet.dat
2013-09-03 17:02:44+0200 [HTTPChannel,0,127.0.0.1] Wallet data not recognized: {'__type__': 'orderposnext', '__value__': '\x0b\x01\x00\x00\x00\x00\x00\x00', '__key__': '\x0corderposnext'}
2013-09-03 17:02:44+0200 [HTTPChannel,0,127.0.0.1] The wallet is not encrypted
Hello,
I can't dump keys. I installed pywallet but when I click on "Dump Keys" (on web page) i get "File not written" error.
Maybe it happens because .bitcoin directory is a symlink. So i tried to enter the right path, but the same error occurs.
How can i solve this?
Thank you.
I can't dump keys. I installed pywallet but when I click on "Dump Keys" (on web page) i get "File not written" error.
Maybe it happens because .bitcoin directory is a symlink. So i tried to enter the right path, but the same error occurs.
How can i solve this?
Thank you.
What is written in the console?
Hello,
I can't dump keys. I installed pywallet but when I click on "Dump Keys" (on web page) i get "File not written" error.
Maybe it happens because .bitcoin directory is a symlink. So i tried to enter the right path, but the same error occurs.
How can i solve this?
Thank you.
I can't dump keys. I installed pywallet but when I click on "Dump Keys" (on web page) i get "File not written" error.
Maybe it happens because .bitcoin directory is a symlink. So i tried to enter the right path, but the same error occurs.
How can i solve this?
Thank you.
Bitcoin isn't running. I have full 777 permissions in that directory. If I rename wallet.dat to otherwallet.dat, and then run Bitcoin (to generate new wallet.dat file), then stop Bitcoin, then execute the exact same command, then it will work. Does this indicate a corrupted wallet.dat file?
Likely, try the wallet recovery feature on this corrupted fileAlso, you may want to tell the user something before changing his wallet selection. When I went pywallet.py --walletdump --wallet=otherwallet.dat (the file I then renamed to wallet.dat) it just walletdumped wallet.dat because it couldn't read otherwallet.dat or something. That managed to confuse me a bit.
This is REALLY oddThis is not an expected behavior, nor something I ever heard...
Are you sure this is what is happening?
No symlinks?
Would you mind sending me the corrupt wallet.dat (it's encrypted, right?) so that I can see what I can do on my side?
Bitcoin isn't running. I have full 777 permissions in that directory. If I rename wallet.dat to otherwallet.dat, and then run Bitcoin (to generate new wallet.dat file), then stop Bitcoin, then execute the exact same command, then it will work. Does this indicate a corrupted wallet.dat file?
Likely, try the wallet recovery feature on this corrupted fileAlso, you may want to tell the user something before changing his wallet selection. When I went pywallet.py --walletdump --wallet=otherwallet.dat (the file I then renamed to wallet.dat) it just walletdumped wallet.dat because it couldn't read otherwallet.dat or something. That managed to confuse me a bit.
This is REALLY oddThis is not an expected behavior, nor something I ever heard...
Are you sure this is what is happening?
No symlinks?
I have no idea. There is a symlink, so I didn't have to put in the datadir param. But if I do the same thing setting datadir to go "around" the symlink, same thing is happening.
Bitcoin isn't running. I have full 777 permissions in that directory. If I rename wallet.dat to otherwallet.dat, and then run Bitcoin (to generate new wallet.dat file), then stop Bitcoin, then execute the exact same command, then it will work. Does this indicate a corrupted wallet.dat file?
Likely, try the wallet recovery feature on this corrupted fileAlso, you may want to tell the user something before changing his wallet selection. When I went pywallet.py --walletdump --wallet=otherwallet.dat (the file I then renamed to wallet.dat) it just walletdumped wallet.dat because it couldn't read otherwallet.dat or something. That managed to confuse me a bit.
This is REALLY oddThis is not an expected behavior, nor something I ever heard...
Are you sure this is what is happening?
No symlinks?
EDIT: No, not a permissions problem. For some reason it refuses to use any wallet but my own. Can that error also happen because of a corrupted wallet or something? Here's what i'm getting, now that I've made the target file the wallet.dat file:
Bitcoin isn't running. I have full 777 permissions in that directory. If I rename wallet.dat to otherwallet.dat, and then run Bitcoin (to generate new wallet.dat file), then stop Bitcoin, then execute the exact same command, then it will work. Does this indicate a corrupted wallet.dat file?
Also, you may want to tell the user something before changing his wallet selection. When I went pywallet.py --walletdump --wallet=otherwallet.dat (the file I then renamed to wallet.dat) it just walletdumped wallet.dat because it couldn't read otherwallet.dat or something. That managed to confuse me a bit.
Quote
> pywallet.py --walletdump
WARNING:root:pycropto or libssl not found decryption may be slow
`ecdsa` package is not installed, pywallet won't be able to sign verify messages.
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
WARNING:root:pycropto or libssl not found decryption may be slow
`ecdsa` package is not installed, pywallet won't be able to sign verify messages.
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
Bitcoin isn't running. I have full 777 permissions in that directory. If I rename wallet.dat to otherwallet.dat, and then run Bitcoin (to generate new wallet.dat file), then stop Bitcoin, then execute the exact same command, then it will work. Does this indicate a corrupted wallet.dat file?
Also, you may want to tell the user something before changing his wallet selection. When I went pywallet.py --walletdump --wallet=otherwallet.dat (the file I then renamed to wallet.dat) it just walletdumped wallet.dat because it couldn't read otherwallet.dat or something. That managed to confuse me a bit.
Figured out problem, I was specifying a different wallet file, but for some reason (
) it was failing to open that file, so (I think?) it defaulted back to the normal wallet.dat file, and since my own wallet.dat file is significantly weird I managed to confuse myself. It appears to have just been a fancy permissions problem. Fixed now, sorry to waste your time.
) it was failing to open that file, so (I think?) it defaulted back to the normal wallet.dat file, and since my own wallet.dat file is significantly weird I managed to confuse myself. It appears to have just been a fancy permissions problem. Fixed now, sorry to waste your time.
This chunk comes from the "pool" part of the dump
There must be another occurence of "1ktfy4LrHRQ2bmLauCdstbgGJEpPa8Qm6" in the dump
Do you use the correct syntax for the keydump?
There must be another occurence of "1ktfy4LrHRQ2bmLauCdstbgGJEpPa8Qm6" in the dump
Do you use the correct syntax for the keydump?
Sorry if this is a dumb question which makes me look like an idiot, but I have been unable to extract the private keys from the wallet.dat file. I've been trying to use pywallet.py, but each time I do, I get the following:
{
"addr": "1ktfy4LrHRQ2bmLauCdstbgGJEpPa8Qm6",
"n": 101,
"nTime": 1378059316,
"nVersion": 80300,
"public_key_hex": "03e9795fcadcba658da6550517bc239c8bcd86d00741c527533ffb22ac4474eb2c"
}
There is no privkey section. When I try to go through the web interface to do keydump, I get "File not written". In fact all I can get to work is wallet dump. All of the other commands cause errors.
Any idea what might be causing this?
{
"addr": "1ktfy4LrHRQ2bmLauCdstbgGJEpPa8Qm6",
"n": 101,
"nTime": 1378059316,
"nVersion": 80300,
"public_key_hex": "03e9795fcadcba658da6550517bc239c8bcd86d00741c527533ffb22ac4474eb2c"
}
There is no privkey section. When I try to go through the web interface to do keydump, I get "File not written". In fact all I can get to work is wallet dump. All of the other commands cause errors.
Any idea what might be causing this?
Jump to: