Trust me, I more than understand someone could design malicious code. But I personally just lack the context. I don't quite understand the idea Ethereum network functionality myself. If I say something that seems to make little sense it's likely just because my knowledge of the network is limited, and by limited I mean nonexistent. Just trying to figure out how you would actually integrate it within the network is all

You said 'all the miners run the smart contract code'. Do you mean that they use the code themselves in some way to leverage it against the algorithm they're attempting to solve for the block? Or do you mean that when they run and attempt to solve an algorithm they'll attempt to solve the code within the smart contract? If you mean the latter of the two, then how do the miners access the smart contract code?

I was always under the impression that the process was something like:

1. network generates algorithm in need of solving --> 2. miner receives algorithm and begins to work --> 3. work is comprised of throwing as many computations as possible against the algorithm in hopes of solving it --> 4. miner solves the algorithm, relays it to network --> 5. miner is granted block reward, etc.

and MY interpretation of what you're saying is that the process could be exploited like:

1. network generates algorithm in need of solving --> 2. you know the answer to the algorithm --> 4. miner solves the algorithm, relays it to network --> 5. miner is granted block reward, etc.

which would effectively cut out the third step in the process, reducing the time required to solve a block, thus granting you the ability to receive the block reward all on your own.

What confuses me, though, is where the smart contract comes in to play. I don't quite see how it could affect the miner unless the algorithm that generates the block and the required problem needing to be solved to produce the block somehow produces the same algorithm as the exploit requires. You said I may be 'downplaying the flaws in smart contract cryptocurrencies' but I assure you I'm not, I just don't understand/have knowledge of any of these flaws 

In short, It seems to me that you're saying 1 + 1 = 2 and mining/smart contracts (being 1 and 1) are easily connected resulting in the output of 2 (representing the exploit); but my understanding was that it was set up more along the lines of 0 + 2 = 2 or 2 + 0 = 2 and neither the miner nor the smart contract have any communication with one another related to the solution of a block. I can't wrap my head around how a smart contract affects the solution of a block to exploit the reward. Would be great to have you clarify my misunderstandings!

I PM'd you back accidentally last night by tabbing forward and due to my rank couldn't send another immediately 

Anyway, you replied and validated what I had thought regarding n1 != n2 being set prior to randomizing n1 in the contract. But I guess what I'm not understanding is, how does the contract have any effect of the mining reward? How would one benefit from the mining reward by running the smart contract? By mining on the same node as the one hosting the contract? I just don't see what the mining has to do with the contract that would 'cheat' it. Perhaps I'm missing something simple as my knowledge of the Ethereum network is limited, forgive me if its basic.

PM limit was reached temporarily; might be a stupid question but outside of the file creation date listed under the properties where would I find the exact file creation timestamp you mention? Also, I do recall that one of the wallets was created pre-2013 and renamed to be in line with the current naming standard at some point in time. I can't recall why it was done, but had no compatibility issues or any problems at the time, so assume that it never did any damage.

Sent you a PM, and thanks for the help.

Anyone else who has suggestions for possible solutions or things to try, suggest away! Hit a bit of a brick wall myself, not much that I can think of to try outside of re-scanning the drive and (potentially) picking up other fragments of the files to fill in any null bytes. Even then, doubtful that I could/would and even more doubtful it'd make a difference with the state of the files.

Wanted to provide an update:

Was able to successfully get pywallet to dump a private key for one address, which contained a grand total of 0 BTC 

Oh well, onto the others! Unfortunately, the above didn't work. Electrum 1.9.8 either crashes or simply does nothing when asked to open any of the files. Opening them up within notepad++ reveals very, very little useful information and many, many [NUL] bytes and overwritten/encrypted data. Sadly, I think these may be too far gone; but I'd love for someone to prove me wrong, and I'm open to trying damn near anything to get into them, even if the payoff is 0 and it's a lesson in cryptography by the end of it 

I have successfully pulled ~20 characters of hex from one wallet, but sadly, after transcribing them, it simply translates to 'bestblock' from the file, and nothing useful.

I was not aware of the version difference issues in Electrum. Thanks, I will try this after work. I believe most of them were run on pre-2.0 electrum, except for a couple files (which I have been able to dump the private keys from with pywallet) that were used with 2.8, so very recently. That second link looks helpful too, will report back with any progress later!

Long story short I was able to get my hands on my old system today. Recovered the HDD to find ~8 wallet files. Some or all may be worthless, some may contain upwards of ~50BTC.

None, however, are able to be imported properly into electrum. What is the best/easiest way of repairing wallet files? I have a number of them that simply state 'cannot read file' when being imported into electrum, some of them crash the client, and one produces the following error:

"Cannot load wallet: 'charmap' codec can't decode byte 0x8f in position 13: character maps to <undefined>"

I cannot say what version of electrum these were last created or run on, but I do know they are all electrum wallets. Any help will be greatly appreciated; and if anything is to come out of the 'hunt' here, rewarded as well.

Hey everybody, I just booted up my rig and I'm having some issues with it. Wondering if anyone here can help me troubleshoot. Started my own thread but it's more relevant to this specific program I believe, here's a copy-paste of my issue:

I set up my first rig today, 3x Nvidia 1070 founder's for my GPU's. After dealing with some hardware install hiccups everything seems to be working smoothly, except my hashrate is far from expected. I have yet to tinker with the cards and OC, as I wanted to test on stock settings first. I'm using Claymore's Dual Miner for ETH+LBC and currently I am running into the following issues:

1. SOLVED

2. My LBC hashrate is REALLY low, I mean, almost nonexistent from my understanding. Currently getting about 60mh/s for all three cards. From my understanding I should be looking at about 250+mh/s PER CARD! I'm nowhere near that. Is this because I have yet to OC the cards and LBC is most efficiently mined that way? Really have no idea. However, LBC is showing up on suprnova just fine for my monitoring, the hashrate is just awful.

If anyone can offer input and give a newbie a hand, it would be hugely appreciated. Thanks!

Hey everyone,

I set up my first rig today, 3x Nvidia 1070 founder's for my GPU's. After dealing with some hardware install hiccups everything seems to be working smoothly, except my hashrate is far from expected. I have yet to tinker with the cards and OC, as I wanted to test on stock settings first. I'm using Claymore's Dual Miner for ETH+LBC and currently I am running into the following issues:

1. My ETH hashrate is about right for stock 1070s, 70-73mh/s for all three cards. However I'm using ethermine.org and whenever I search my address in their 'check' function to see if my miner is loaded on their side, nothing shows up at all. No active miners are listed at all, but Claymore says the connection is fine, and it's proceeding to mine just fine. And yes, I've quadruple checked to make sure the address I've input is mine! FIXED! Just took a while to load the information.

2. My LBC hashrate is REALLY low, I mean, almost nonexistent from my understanding. Currently getting about 60mh/s for all three cards. From my understanding I should be looking at about 250+mh/s PER CARD! I'm nowhere near that. Is this because I have yet to OC the cards and LBC is most efficiently mined that way? Really have no idea. However, LBC is showing up on suprnova just fine for my monitoring, the hashrate is just awful.

If anyone can offer input and give a newbie a hand, it would be hugely appreciated. Thanks!