They are all in here. Cooling is quite good as the rest run close to 80. I'm sure its a failing card or a card issue. I have it underclocked and undervolted and its still hot. Frankly, I don't really think its a problem but we will see.

Also, I've had a 7970 running at 95-100 degrees for 3 months now. Just waiting for it to fail I guess (others all run mid 70s to 80s).

I've found after a year that pushing my machines to the limit is less productive than a nice stable continuous hash day after day after day. But maybe I suck at this.

yes, i am soloing with my desktop GPU just for fun - about 735 mMh Kh/s

followed the setup detailed here for another crypto  https://forum.feathercoin.com/index.php?topic=1453.0

i'm back on coinyechain now

Also possibly diff suppression.

I've noticed too. Am switched to another pool that is up.

Can someone explain this whole crypto-begging thing to me? I don't get it.

Alts bumping their offers or people really cold asking for coins?

Well, I am "mining" on the new "miner" at 9717 hashes/sec. It only detected my CPU so I'm letting it run overnight hoping for 666,666 when I wake up.

this is my first launch
I f'ed around for the first 45min sorting a problem - worker username was wrong (did not realize I needed username. preceding it)

mined for about a minute a difficulty 1, then 16

just venting

I'm trying to verify the installers on Windows 7.

Verifying the hash works fine with the workflow above.

As for verifying the sig, I get this message in Kleopatra "Could not determine whether this is an S/MIME or OpenGPG signature - maybe it is not a signature at all?"

FWIW, I get the same message using Kleopatra to verify the Litecoin-qt installer. I get a confirmed sig when I verify my own signed documents.

Any insight?

Thanks

I misspoke in my write up. The rpc password is in the config file but i did not add it to the ruby script. I could not get it to run if I did. I do not understand the reasoning but that is how it worked for me. I have edited it.

After a wallet encryption fiasco that I finally sorted out, I am left with one Bitcoin-qt wallet that is behaving strangely.

It has a 0.00 BTC  balance with 1.5986... BTC Unconfirmed

It lists about 40 transactions that are LTC deposits from a mining pool plus 2 transactions that are in BTC but are from a different BTC wallet address.

The passphrase for the BTC wallet does not work, but the passphrase for a LTC wallet does work.

Attempts to transfer the 1.59 BTC to another BTC wallet show "insufficienct funds". Attempt to transfer to an LTC wallet shows invalid address.

It seems I have a wallet.dat that is a combination of LTC and BTC data and function. Has anyone seen this and how can it be fixed?

In the meantime, I am trying to track down a older copy of the wallet.dat that is not corrupted.

Thanks

Once I found the right passphrase I sent to another address within 10 seconds

So the mistakes are all user errors (me). There are two passcodes involved. One for a bitcoin wallet and one for litecoin. I created these both on the same day in July 2013. I found my original notes on paper today at work (after of course, I had found the correct passphrases using the Ruby script).

For BTC, the actual passphrase was d5VcQG+Rp8EqJ!x+Zsb. I had recorded in my notes and in my documentation as d5VckQG+Rp8EqJ!x+Zsb. My theory is either I omitted the k twice or the k was working inconsistently on the laptop I used. In trying to figure out the passphrase I tried omitting characters but in my haste (stressed state) I must not have been complete. 27 btc recovered.

For LTC, the actual passphrase was hMH#8vB2SqjCZdV&!6d9. I have that exact passphrase hand written in my notes I found at work today but in my documentation I recorded hMV#8vB2SqjCZdV&!6d9 substituting V for H. This must have been a problem transcribing from my notes to my documentation I kept with the wallet.dat files. 485 ltc recovered.

I have learned that in long random strings of characters, I have a high error rate in transcription. So much so that I am very nervous about doing that again. I have not decided what to do yet but am considering a mix of multiple online and offline wallets. I know this will increase the chances of errors and hacking but at least I wouldn't loose it all at once.

Yes I am thinking of way to protect against my self.

So, as follow up I was able to "brute force it". I used the Ruby script from this thread https://bitcointalk.org/index.php?topic=85495.300 posted by Revalin. See my post #312 for all the details.

Very grateful to everyone who helped me think this through.

As a follow up I was able to discover the actual passphrase by using the ruby script from this thread https://bitcointalk.org/index.php?topic=85495.300.

Much thanks to all who helped. It was a stressful and frustrating experience - from which I learned a lot.

After about 12 hours of working on it, I successfully ran the script and found my actual passcode for both a Bitcoin and Litecoin wallet within hours of running the script. They were 20 character random passphrases. For Bitcoin, the problem was a character deletion. For Litecoin, it was a mistyped character.

This successfully ended a 4 day stressful quest during which I learned a lot. It was very frustrating at times but ultimately rewarding in a sense of personal accomplishment. I do not have any coding experience and no Windows admin experience. With the kind help and recorded knowledge of posters to this forum thread I was able to figure it out. For those of you this comes easy, good on you. But remember there are those of us out there who have to work really hard to understand this stuff and make it work.

What follows is a laymen’s description of how to get this to work in Windows 7. Hopefully other novice users like me will find it useful if they come across this. I apologize for any errors or misinformation - hopefully it can be corrected by others who know more.

Revalin's ruby passcode cracking script workflow for Windows 7 for both Bitcoin and Litecoin wallets.

(If needed, substutue Litecoin and litcoind for Bitcoin and bitcoind in the instructions below.)

Preparation Phase:

1) Install Ruby 1.9 or newer for Windows http://rubyinstaller.org/downloads/

2) Choose one of the scripts in this thread that best fits your needs. (I chose a version recorded here http://pastebin.com/nWTBxPES - but frankly do not recall how I came across the link). Cut and paste the script into Notepad and save as "brute.rb"  using  the quotations. Right click on the file and open it in edit. Edit the top of the script putting your expected passphrase between the quotations in the line passphrase = "oops". Save the changes. I saved it to the desktop.

3) Drag and drop that brute.rb file into the folder C:\Program Files (x86)\Bitcoin\daemon. It will then be in a folder with the bitcoind application file.

*4) Add a config file for bitcoind at C:\Users\addyourusername\AppData\Roaming (or wherever your computer has the wallet.dat file for Bitcoin-qt). Name the config file bitcoin.conf and put the following in it:

rpcuser=bitcoinrpc
rpcpassword=anypassword (apparently any random password will work here)

Note: Other instructions call for adding the line rpcpassword=anypassword to the ruby script. This did not work for me and only worked when I did not add it to the script.

Running Phase:

1) Navigate to C:\Program Files (x86)\Bitcoin\daemon. Double click on the bitcoind application. An empty command promp will open (not even a blinking cursor) with C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe in the title bar. Leave this open and running.

2) Open the Windows start button and type Ruby in the search bar. Then select and open Start Command Prompt with Ruby. A command propt will open with some version of the following:  ruby 1.9.3p484 (2013-11-22) [i386-ming32] and a blinking cursor at C:\Users\yourusername>

type ruby brute.rb

The script should start running and you will see it fill with lines of attempted and failed passphrases. If it succeeds, it stops running and prints Found it! youractualpasscode

*Note: for step 4 above, I still do not know the proper way to make a config file for windows 7. I struggled with this and finally got something to work. If anyone can give some simple and complete instructions please add them.

[quote/]Sounds like you are just not using the correct (meaning older) passphrase for your backed up wallet.[/quote]

That is what I have finally come to realize. Unfortunately, at that time I would not have grasped the consequence of resetting the passkey (ie re-encrypting the wallet.dat) and not creating a new backup of wallet.dat.

If this is indeed the mistake I made, I have only a vague recollection of doing it and certainly no record of the older passphrase.

Loosing those 42 coins has been hard to swallow. At least knowing why will hopefully let me get some sleep for the first time in two days.

I think I figured out something that could replicate my scenario.

1) encrypted wallet
2) copy wallet.dat
3) change passphrase
4) did not make new copy of wallet.dat

First encrypted copy would not decrypt with the new passphrase.

Can someone confirm this would occur this way?

Thanks

Can a wallet.dat file be corrupted in a way that it does not throw an error when loading bitcoin-qt but fails to recognize the passphrase?

I created two offline wallets in July. Went to access them and the recorded passphrases are incorrect for both of them. I never printed the private keys so now can't access either wallet. I know I could have typed incorrectly or cut and pasted improperly when I created the pass-phrase and I am definitely working on that possibility.

For this thread I am looking for any insight into other technical problems that may have occurred that make the wallet.dat file unable to recognize the passphrase. I had multiple copies of the wallet.dat stored in multiple locations. They all work in terms of making coins appear (about 42 in total) but as I said they do not recognize my expected passphrase. By the way the passphrase is 20 char random generated by the LastPass password generator.

Any and all ideas are welcomed.

Thanks