I've said this myself. I know it's not much to go on. If I had more I'd give you more. If I had more, I'd probably figure it out my damn self!you have to understand that you are not giving us anything to work with.
You're absolutely right! Never should have posted it.arguing here is moot.
I should know better than to think I'd find anything other than pumptrolls acting like complete assholes, then calling me the asshole...stop being an ass.
i can't help it... LMAO...camosoul First off, let me apologize for harming you intellectually with my MN guide....Please don't read it again to save yourself some headache. Now, as far as the current topic, I agree, dude, you got to get in touch with Evan: He can help you way more than any of us!
I have proven it. No matter what proof I present, it will be ignored and "more" proven will be needed...No one attacked you because you have the issue. You got jumped on cuz you claim you have something proven when you do not.
I have proven it. No matter what proof I present, it will be ignored and "more" proven will be needed...If you here to just report is state so and not claim you have a proof it happens.
I left BCT because I am the only stable, rational adult I could find there. Seems I'm finding a theme...Anyway am out, you're too unstable for my liking.
I have proven it.
Sounds promising...Dump is in hexdeci slash delimieted I think... Still not human readable... working... Lots of key entries. Just can't read them. It's probably in here.
I'm not sure where to go from here. It's clearly int here, but base count is unclear. It's not hexdecimal... Performed a dump without the -p for more clarity. Confirmed that I don't know where to go from here, lols.Sounds promising...
Try pywalletDump is in hexdeci slash delimieted I think... Still not human readable... working... Lots of key entries. Just can't read them. It's probably in here.
python pywallet.py --datadir=/home/YourUserName/.darkcoin/ --dumpwallet --otherversion=76 > wallet.txt
--passphrase=PASSPHRASE
I was already on that route when I stopped. Noticed the jj fork...Try pywallet
you can try it in separate VBoxI was already on that route when I stopped. Noticed the jj fork...
When I went to install the pywallet deps, apt-get wanted to uninstall everything berkleydb related... So, yeah, I stopped there...
I encrypt my entire drive, so, encrypting the wallet seems redundant and adds difficulty in such fiddling. At least this much I'm prepared for, lols.
Yep. Did that. It tells me the file is corrupt and it won't do anything with it. lols...you can try it in separate VBox
It's pretending that the file is open... Which adds credence to my theory that something is going wrong with the wallet.dat dump when the client fails out of RAM... Looks like a copy-while-qt-is-running, but that is absolutely not true.fail said:ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
any debug output from python?Yep. Did that. It tells me the file is corrupt and it won't do anything with it. lols...
Where would I find pywallet.py's debug output? Beyond the error I posted, it says nothing.any debug output?
I left BCT because I am the only stable, rational adult I could find there. Seems I'm finding a theme...