Here's what is finished: - Make menus hidable
- Export priv keys to file (csv)
- Import priv keys from file (csv)
- Merge two wallets
I'd like a few beta testers to play with it before releasing it, anybody interested? Also, if there are people that love CSS and that want to help, that would be awesome. Apart from that, you can still ask features you want to see implemented |
|
|
|
|
Both added to the todo list
ATI drivers broke my system... Development paused...
ATI drivers broken, recovery menu of Ubuntu broken, no help whereas the problem is reported on Launchpad for more than half a year... Installing a new Ubuntu is even more a pain than before
At least it's finished now, I can focus on pywallet...
|
|
|
|
welcome back, happy to see this awesome tool being usable again for newer bitcoin versions! the WUI is proper  a good feature: import/export all privkeys to a file And I'm happy to come back! You mean unencrypted privkeys? I'll implement that, but I'll add a warning about security then That's what I'd like to see with support for handling the wallet encryption with whatever passphrase you set.
What do you mean by handling? I'm about to add the import of any (un)encrypted (un)compressed key to a wallet, but before any release I still need to find why sometimes compressed keys added to an unencrypted wallet corrupts it... |
|
|
|
|
After a quick look at the wallet file I thought the format didn't change, but yeah, looks like Bitcoin now stores compressed keys.
I left for a while so I don't know much about compressed keys yet, but now you made me look closer at that, everything is clear.
Thanks a lot for the tip, I hope I'll soon post here that everything's fine
|
|
|
|
I've encountered a problem, and it's kinda difficult to investigate more as I still have 40000+ blocks to download. I made a new Bitcoin wallet (with bitcoin 0.8.1, linux). Obviously it has default keys. Let's take the main one. {
"addr": "1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC",
"hexsec": "3d423fb2f8b7af14e590230d87ec9067cba3ad29261f829c4f2476ade4278aa0",
"label": "",
"privkey": "3081d30201010420543d423fb2f8b7af14e590230d87ec9067cba3ad29261f829c4f2476ade4278aa08185308182020101302c06072a8648ce3d0101022100fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f300604010004010704210279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798022100fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141020101a1240322000302519ca3be493a26d62e96a814388b441bf972f6cf16f07ba49b993f3a12db69",
"pubkey": "0302519ca3be493a26d62e96a814388b441bf972f6cf16f07ba49b993f3a12db69",
"sec": "5JHGMYGpfoD7HK3jSNrKgRry9yRZGEGJEXBk6w3KPfAdjQRyawb"
}
This is a dump from Joric's pywallet. 1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC is what Bitcoin software shows. The thing is, when I use pywallet (Joric's one, which is up-to-date) to import the private key (here as hexsec or sec) into another wallet, the message it returns to me mentions the address 1MUVkGv8TWjvdJ87VMGoNyhG3NLYE87WQT, and not 1Co8KFDHnwyuCxfyBWPK1ifRjGiR7AeXDC. If I had access I would have transfered 1 mBTC to each address and tried to retrieve both to see what would happened... So in the mean time, can anyone tell me what I can do to check where is the error? And can someone check to which address the private key 3d423f... corresponds? Thanks for any help |
|
|
|
Hi all, I'm back online for good this time I missed everything since 0.3.23 so leave me some time to update I won't answer to previous questions in this thread because it's been a long time and I think their posters aren't interested in the answer anymore (if not, drop me a PM) Looks like the wallet format hasn't changed much since my departure so I'll work on pywallet again Please post what you would like to see coming in pywallet (a proper GUI is already considered but it's not a top priority since Qt doesn't work on iPhone/Android) I'll keep this list updated, by order of priority Fix the corrupting bug when importing compressed key in unencryted wallet (in 2.0b2)Make menus hidable (in 2.0b2)Export priv keys to file (csv) (in 2.0b2)Import priv keys from file (csv) (in 2.0b2)Merge two wallets (in 2.0b2)Stop asking to update in a beta version (in 2.0b3)Repair passphrase setting when merging wallets (in 2.0b4)- Forbid things when encrypted wallet and bad passphrase (this doesn't corrupt wallets, so low priority)
|
|
|
|
|
Hi there,
I had to leave the Bitcoin community for a long time, since 0.3.23
As a dev I'd like other dev(s) to tell me what big changes occured since then
Of course, I'm looking into that and I'm not just waiting to be spoon-fed but that would help a lot, just to be sure I'm not missing a key point before developping again.
Even just the name of the feature like "wallet encryption" would help.
Thanks in advance!
|
|
|
|
Very nice tool. Can this be used for litecoin wallets?
If it uses the same type of wallet, yes. Anyway, make a backup of your litecoin wallet and make a try |
|
|
|
so i've been spammed with dust on namecoin and my wallet is 200mb... and won't load any more
i've tried deleting all transactions but there are still a lot of addresses made (200mb worth? the wallet size didn't change with deleting transactions...)
any idea on a solution? i think i will need to use pywallet so i'm asking here because it would be the best place to find people that know how to use it and what it can do...
The problem is that Namecoin download all the transactions when you launch it (it uses it to calculate the balance) The better thing to do is to create a new address, send all your namecoins to this address, and import this address in a new wallet |
|
|
|
|
Many thanks Joric!
I didn't manage to find a working library for it and you found 3 of them...
I have exams this week, so I think I will put that in my fork this week-end or maybe next week
|
|
|
|
|
I think "authentique" fits best, or maybe "certifié"
|
|
|
|
so no one just has a priv/pub pair creator for namecoin?
Run this in pywallet directory: tr -dc a-f0-9 < /dev/urandom | head -c 64 | xargs ./pywallet.py --info --importhex --otherversion 52 --importprivkey It will give you something like: Address (Namecoin): NJFPUnVCWkydLxF8QUCW7aeWG51weGj9uB
Privkey (Namecoin): 744ZPRLRJ1d9WGcb8MBmVPkS2cgFyCGnateqhq8Rm3wLu1UZHay
Hexprivkey: 9968c22c6091e18589496d6d378a29654ef4e350a5aded88c972e05a9fbb0a88 PS: you might want a better source of entropy |
|
|
|
|
Christmas update
New feature: Pywallet checks if it is up-to-date and if not, shows a link to update (automatically)
Encryption still in progress, cryptographic functions in python are such a pain...
|
|
|
|
|
Thanks a lot Gavin, this will be very helpful!
|
|
|
|
|
If your wallet is not encrypted it's 'easy' with pywallet: grab the privkey of the address, delete it with pywallet then import it back as a change address
If it's encrypted you'll have to wait for a patch or for me to find how to take care of encrypted wallets (btw if anybody can help me about that please pm me)
|
|
|
|
Is there any documentation about key encryption? Or anybody knowing how to encrypt/decrypt privkeys? I can continue my research but if somebody already knows that it would be better I have the passphrase and these data about the master key, how can I decrypt encrypted privkeys? "encrypted_key": "bda3f31ce15e5e2072fb4fbe7b6e6a55c2da23b067c4f5599a50fa053e617f72aecb31d73dea36bed72b57d19736ea93",
"nDerivationIterations": 62351,
"nDerivationMethod": 0,
"nID": 1,
"otherParams": "",
"salt": "f325081b21a3b80e"
|
|
|
|
My today's success story: Computer of friend of mine crashed two days ago. He went to some IT guy, asking for repair. That guy recommended "format & reinstall" (wow, are all issues with Windows still solving this way?) and asked, if backup of office document and some other stuff is enough for him. Today, friend called me that he has reformatted harddisk and fresh install of Windows and he completely forgot to his bitcoin wallet with 80 BTC, asking me if there is any way how to recover them. I played with pywallet some time ago and I barely noticed such cool feature of finding private keys on raw device, so I told him I'll try the recovery.
It went smooth (except that issue with corrupted blocks - which btw means that "format & reinstall" didn't fix previous issues with Windows) and his wallet has been fully recovered. Thank you jackjack for so cool application, small donation is going your way.
I'm glad it worked even after a reinstall! Thanks for the donation I keep getting errors for anything I try to do from the web interface, but dumping the wallet and importing keys from the command line work fine. Is this an issue with 5xxxx wallet versions?
What's written in the console? atm i havent enough time, gonna send u a message when il have enough time until then i work a bit on my own changing ur code if this is ok  greetings Thanks Also I just add the --dont_check_walletversion option to use 0.3.25+ wallet versions |
|
|
|
I'm trying wallet recovery on corrupted notebook disk, but it failed on IOError when pywallet touched corrupted sector. Following code fixes this issue by skipping bad block in first_read(): try:
data = os.read (fd, inc)
except Exception as exc:
os.lseek(fd, inc, os.SEEK_CUR)
print str(exc)
i += inc
continue
Thanks, this will be added very soon |
|
|
|
|
Show Posts
