Search results

Great job!

When running db4.8_dump what commands did you try? #host#> db4.8_dump wallet.dat | db4.8_load wallet-new.dat is something I found on a board with someone complaining about a btc wallet corruption. Weird thing is I'm having a PITA trying to get db4.8-util to work in 14.04. It seems to only want...

In all my experience when i've tried everything possible in software I tend to look into the hardware layer. Solar flare flipped a bit who knows, but it's possible. Unless you are using ECC ram chips, power cleaning UPS', etc, etc, you never know it could be hardware. That seems to be the only...

I had an old file that you couldn't dump at first then after running --web mode I was able to dump it. That file was just sent to evan he worked his magic and recovered coins. Is that still not an option? I'm still testing way's to corrupt a wallet.dat file and can't seem to come up with a way.

evan82@klaus:~/test$ python /usr/bin/pywallet.py --datadir=/home/evan82/.darkcoin/ --dumpwallet --otherversion=76 > wallet.txt This indeed gave me a human readable list of keys from the wallet.dat file on the test box.

Bad ram chips in that machine? If it's unreproducible in software perhaps it's hardware related?

I was talking about making a backup of hte corrupted wallet.dat file before you try dumping it to a human readable error. Just trying to save you from having your next comment be, "I corrupted it even worse now and forgot to make a backup before I tried the db dump"

"What happen's in Vegas stay's in Vegas..." What happen's in old client versions on old wallet.dat files really has no bearing on what's happening on a current wallet client on a brand newly created wallet.dat file. When you first described your issue you mentioned creating 8 brand new...

.... DarkcoinBot> coingun: 1000.0 DRK @ 0.00556468 DRK/BTC (source:cryptsy|54s) = 5.564680 BTC / 1952.48 USD (source:bitstamp:1m13s) .... It's $1952.48 USD we are talking about here. You aren't dumping anything on anyone. You made a mistake we all do not backing up before sending. I know I...

Just setting up a test environment so I didn't test this but a couple google searches on human read-able wallet.dat found this... --- paste incoming First, this will only work if you used the encrypt wallet function of 0.6.0rc1. Second, make a backup. Run: db4.8_dump -p wallet.dat >wallet.txt...

Weird I was just thinking using the word PROVEN (in all caps) and then not actually providing any proof seemed a bit like trolling. Perhaps not Straw Man trolling but maybe some other category?

I guess the part that throws me off is your title is, "PROVEN - client is corrupting wallet upon exit". Usually when something is proven there is proof. We don't even have any debug info from you to give to a developer that could fix the problem if any problem existed. When I see a title like...

http://en.wikipedia.org/wiki/Software_versioning#Version_1.0_as_a_milestone Important part..."the free-software community tends to use version 1.0 as a major milestone, indicating that the software is "complete", that it has all major features, and is considered reliable enough for general...

Don't be such a drama queen. There has been extensive testing of this stuff and it is all working very well. Sure there might be some edge cases but to have a small issue and to then go swear off the whole process as "broken" cause you don't want to take the steps to protect yourself could be...

Got any other specifics about your setup? OS version? Wallet Version? Any of those would be helpful. On a different note. I don't ever send any coins to a new wallet until I have done the following: Opened the wallet and closed it successfully. Opened the wallet again and run the encryption...

LOL! i never even actually tried running it. I was like oh i can't get hte dep's no way it will work stop!!!! I'll test again and let you know.

This is 14.04 LTS Desktop. Seems like perhaps you were building for 12.04 or back? Most of the stuff on 14.04 seems to mention either python-pip or python3-pip. Let me know if you need any other test boxen. Would love to get this rolling for all the testnet masternodes!

What flavor was this built on? I'm testing it on 14.04 and am having trouble finding both the pip install's suggested. tester@ubuntu:~/Desktop/smut28$ sudo pip install urllib2 Downloading/unpacking urllib2 Real name of requirement urllib2 is urllib3 Could not find any downloads that...

Great work on this. I have just found it and am going to run it through it's paces on some of my testnet gear. Will report back! Edit: Had a quick peak through the source code. Doesn't appear to be any Masternode coin stealing hidden features. Must have been those red head's you took you earlier!

Example's please! You can't tease us with this goodness and then hold out the tables!