|
Hi
Is Devcoin still actively developed?
|
|
|
|
|
Great list
I'll give it a try with the show/hide button
|
|
|
|
Yes I am  Still a few weeks left before I can come back for real! BTW I'm looking at the code I produced and I'm kinda ashamed of this ugly code, it's obvious I used pywallet to learn Python  That makes me wonder, is it still useful to have something like an updated pywallet? Because I see that the bitcoin clients have included many features and I don't know (I couldn't follow Bitcoin news for months) exactly which ones It's good to have an updated pywallet. I would like pywallet to extract private keys in bulk from altcoins that don't have the "dumpwallet" command. To generate a bunch of addresses. Multi-sigs. ... Or if you really hate your ugly code to do it over from scratch (using the old code as a "guide".) I have a rewritten pywallet lying around, I'll have to find it and update it with the features it misses |
|
|
|
I openly ask for a .25 BTC upfront so that I can spend 2 days of time read the dat file manually and try to find out keys or possibilites to recover the keys. This is not to scam. I just wanted to get my time useful to try.
If you're willing to use my time, please send me dat file with all the dumps or files you think worth to research.
Note: 0.25 btc is a huge amount to try some unknown thing. However, I suggest you to try only if you really get worth NMC if the search becomes successful.
 |
|
|
|
I've already tried, no luck  . So the mkey is necessary to decrypt, am i correct? Yes the mkey is necessary I finished looking at your wallet and can't find any mkey or things alike (m?ey, ?key, mk?y...) Really sorry man  Fuck linux! Thank you very much everybody for your help. I believe even Windows "queue" when copying to external disks Saying the copy is done when it's actually in progress or waiting, is really something I don't get either I hope you didn't lose a huge amount |
|
|
|
I've already tried, no luck . So the mkey is necessary to decrypt, am i correct? Yes the mkey is necessary I finished looking at your wallet and can't find any mkey or things alike (m?ey, ?key, mk?y...) Really sorry man |
|
|
|
Hey jackjack, you're alive! Yes I am Still a few weeks left before I can come back for real! BTW I'm looking at the code I produced and I'm kinda ashamed of this ugly code, it's obvious I used pywallet to learn Python That makes me wonder, is it still useful to have something like an updated pywallet? Because I see that the bitcoin clients have included many features and I don't know (I couldn't follow Bitcoin news for months) exactly which ones |
|
|
|
Oh wait, I didn't notice that, this is no good: --recov_size 1Mo
You must put the size of the hard disk in --recov_size, and I bet it's more something around 500Go
You must put at least the size of the file, is your wallet.dat really <1Mo?
It is 135 kb. Is having the mkey necessary to decrypt some private key? Because if that parameter is necessary we'd better stop here since i can't find it in my corrupted wallet. Are you 100% sure you don't have mkey? Because "Found 1 possible wallets" means pywallet found 1 mkey What i posted was the output for a valid NMC encrypted wallet. If i run the same command with the corrupted wallet the output is Found 0 possible wallets. Oh sorry, then TBH I don't think there's much hope left Last hope ever: run pywallet recovery on your HD (according to what happened that is hopeless though) and on your external HD (maybe a bit less hopeless) I don't think this will work but maybe the Namecoin Gods are around... |
|
|
|
No because in his case pywallet found the keys |
|
|
|
Oh wait, I didn't notice that, this is no good: --recov_size 1Mo
You must put the size of the hard disk in --recov_size, and I bet it's more something around 500Go
You must put at least the size of the file, is your wallet.dat really <1Mo?
It is 135 kb. Is having the mkey necessary to decrypt some private key? Because if that parameter is necessary we'd better stop here since i can't find it in my corrupted wallet. Are you 100% sure you don't have mkey? Because "Found 1 possible wallets" means pywallet found 1 mkey |
|
|
|
Oh wait, I didn't notice that, this is no good: --recov_size 1Mo
You must put the size of the hard disk in --recov_size, and I bet it's more something around 500Go
You must put at least the size of the file, is your wallet.dat really <1Mo?
It is 135 kb Isn't that small for a wallet file? BTW in Pywallet I have hardcoded formats for ckeys that could be different from Namecoin, if you're OK you can send me your wallet (it is encrypted I can't use private keys) and I'll try pywallet without checks to see what I can find. |
|
|
|
|
Oh wait, I didn't notice that, this is no good: --recov_size 1Mo
You must put the size of the hard disk in --recov_size, and I bet it's more something around 500Go
You must put at least the size of the file, is your wallet.dat really <1Mo?
|
|
|
|
Hi! Try this without --namecoin: sudo python ./pywallet.py --recover --recov_device /path/to/corrupted_wallet.dat --recov_size 1Mo --recov_outputdir /home/username/Desktop/recovery What does it return? What is "no success"? And how did you find 8 "ckeyA"? How many "ckey" do you find? |
|
|
|
I am sure this is an great bitcoin wallet but why do python developers call everything pyxxxx? I mean, a chess game is called pychess instead of CrazyBishop, SuperSquare, MikaTal or pow8_2? Once, when I was looking for a calculator I found pycalc. What if everybody do the samething? we would end with jcalc, ncalc, scalacalc, rubycalc, calc++ and so on.
Why do you think the language is important?
I know this is old but 1) I didn't choose the name (I continued the development after joric "disappeared") and 2) there is JCalcHi, when I'm trying to run pywallet.py, I get following error stayerc@C855-arch:~/.bitcoin$ ./pywallet.py --web
File "./pywallet.py", line 852
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^
SyntaxError: invalid syntax
Please help Pywallet requires Python 2, not 3 Does anyone know how to use this tool to recover Namecoin private keys from a corrupted encrypted wallet?
I've already tried to run the following command but everything it returns are Bitcoin public and private keys.
sudo python ./pywallet.py --recover --namecoin --recov_device /dev/sdb --recov_size 16Gio --recov_outputdir /home/username/Desktop/recovery
If the wallet is recent I'm afraid you may not be able to recover it (wallet format has changed since I last updated Pywallet) But if it did return public/private keys then you may be lucky In this case this should be rather easy to translate them into Namecoin, but before, do you know how to import a private key into a Namecoin wallet? |
|
|
|
I knew there was something fishy with bitcoin Thanks OP for finding out the vulnerability This is for you  |
|
|
|
Nearly everything has been said I think You can also try to generate many empty WIF private keys, write them down and then compare your writings with the original ones With much luck you may find what errors you tend to make: mixing one letter with another, mixing two consecutive letters, capitalizing downcase letters, etc |
|
|
|
I think this might be something to do with new blocks in 0.12.x, Maybe pywallet needs updating or such.
This I don't know the format of the new blocks, I'll try to find specs and potential fix but I can't promise it will happen soon |
|
|
|
|
Nope, I didn't have the time to fix that yet but it's the first thing I'll do once I'm able to free up some time
|
|
|
|
It was indeed fixed, but I shouldn't have updated. All my settings are gone and I can't import or change them because of the username bug. Sorry for that Next thing I'm fixing is the username bug |
|
|
|
BTW, I made an "Ignore threads" user script 2 weeks ago. People could probably use both scripts at same time, but if you want to copy my script into BT++ that's fine too (although I was lazy and used jQuery, but should be easy to convert.) I noticed that you already had a "ignored threads" input val, but the UI is not as easy as my script, so might be better to merge that. My topic is here (with screenshots): https://bitcointalk.org/index.php?topic=1451483.0 Source here: https://github.com/NLNicoo/itob/I really like your way of doing this I also think people can use both at the same time but if you prefer sure we can merge them, it's really your call Could you fix this? The message is shown by Tampermonkey when using Bitcointalk++ on Chrome.
I'll look at this and report any update here EDIT: Shoud be OK with 0.2.98 |
|
|
|
|
Show Posts
