Post
Topic
Board Bitcoin Technical Support
Re: Encrypted wallet.dat, lost password, any solutions?
by
KieranJones1
on 01/12/2013, 00:16:16 UTC
Since neither Feathercoin nor Protoshares seem to have their own daemon versions, or even accept an argument to make them run as daemons, I've been trying to use bitcoind.exe to crack them.

Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\\AppData\Roaming\Bitcoin). Click here for a copy of my bitcoin.conf, which is the Bitcoin wiki's "example" of a bitcoin.conf file, with the relevant lines uncommented. (The RPC username in my version is "hello1"; the RPC password is "hello2".)
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
Code:
bitcoind -server -daemon -rpcuser=hello1 -rpcpassword=hello2 -rpcport=8332
If you enter this correctly, the title of the command prompt window should permanently change and you won't be able to type anything anymore.
4. Leave this command prompt window open, and open another command prompt window. Navigate to a folder containing bitcoind.exe (yes, again) and type
Code:
bitcoind getinfo
If you get information (screenshot), instead of an error, your bitcoind server is accessible via RPC. If you get an error, post what you did and I can try and fix it. Tongue
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Code:
ruby brute.rb

Let me know how this goes for you guys!

EDIT: if step 4 brings up an error saying "couldn't connect to server", just try the command again, and again, and again. When it happened to me, I just left the server on for about 15 minutes, then tried it and it worked.