Check the graphs for my address, AFnYPruQpNqzi4UEquWPmA4vV2xf6gNGa1. I think the reason for the hashrate graph weirdness is caused the fact that ralph12 and I are probably both putting out around 100 kh/s. The graphs seem to calculate a hashrate using the amount of time between shares while using the share difficulty as a weight. The problem is that the hashrate is only calculated over a span of 1-3 minutes, and if a share isn't submitted in that time, it goes back down to 0. That means that the minimum hasrate that can be displayed is the hashrate needed to generate 1 share per 1-3 minutes. This explains why all the spikes you see are far higher than our actual hashrates. As for the odd spaces between payouts, I have no idea.

On a related note, I just got my .5 CGA for mining all day today! Thanks wzttide!

Thanks man. If the price predictions hold up, I'll sell a few CGA, buy some cheapo refurbished hardware, add another worker to the network, then rinse and repeat, so, who knows, check on me in may, and I might have so much hashpower that I have to install a second A/C system in here to keep from dying of heatstroke. Course, then again, considering I live in south florida, my rig's located 6 feet from my bed, and I've overclocked the card to the point that it's pulling around 300 W, I'm almost at that point with less than a hundredth of what you have...

I started mining on the 4th with an old ghetto-rigged and heavily duct taped 4850. It's putting out 102 kh/s. I have 11 coins. It's turtles all the way down.

Dude, awesome! Thank you.

Just one problem though (and I'm sure it has nothing to do with compiling), I started up the new client about 5 minutes ago, and I'm connected to 88.198.198.94 AKA node1.anomalypool.com, but I still have yet to download a single block. I assume this is because the server is being bombarded right now, can anyone confirm?

Edit: While writing that post, it connected to 2 additional nodes, including the second anomalypool node. Still no blocks downloaded.

Edit: Got it to resync like normal now. If anyone has this problem in the future, delete your chainstate folder and restart the program.

Well, I know this isn't exactly breaking news, but at least one of those aren't. I was connected to those hardcoded nodes just long enough to get the info and copy/paste it into a notepad window (max, could've taken 60 seconds), before I went back to only connecting to one of anomalypool's nodes and found that my wallet had forked in that short time. If it only took 1 minute to fork my wallet, I can't help but think that must mean that the majority of peers I was connected to were forked as well.

Devs, you got your work cut out for you. Good luck, and here's a tip I learned from a programming class I took a while back, when I had to finish 2 weeks of work for my final that was due in 2 days, and still got a 100/100 on it: 1. Drink a 5 Hour Energy, 2. wait an hour, 3. either drink a coffee or an energy drink (note: adjust this to your caffeine tolerance. If you don't drink caffeine, ignore this altogether.). Repeat step 3 on hour 2, 3.5, and 5, then repeat the entire process on hour 5. The 5 hour energy will keep you from crashing, while the caffeinated beverages will allow you to write code much faster than what is usually considered humanly possible.

For the rest of us who aren't fluent in c++, let's all pray to our respective god(s) that this next version will finally defeat this forking problem.

Guys, I just removed all the addnodes from my .conf file and started the v1.1.1.2 binary with just the hardcoded nodes to connect to. Then I let it connect and typed "getpeerinfo" into the debug console.

I think I found the culprit:




getpeerinfo


15:00:18


{
"addr" : "70.176.73.232:13931",
"services" : "00000003",
"lastsend" : 1391975633,
"lastrecv" : 1391975637,
"bytessent" : 1943,
"bytesrecv" : 14644,
"blocksrequested" : 0,
"conntime" : 1391975633,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12660,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "64.188.167.211:13931",
"services" : "00000003",
"lastsend" : 1391975661,
"lastrecv" : 1391975663,
"bytessent" : 229,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1391975661,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12384,
"banscore" : 0
},
{
"addr" : "162.243.225.132:13931",
"services" : "00000003",
"lastsend" : 1391975691,
"lastrecv" : 1391975869,
"bytessent" : 229,
"bytesrecv" : 7226,
"blocksrequested" : 0,
"conntime" : 1391975690,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12384,
"banscore" : 0
},
{
"addr" : "50.147.39.37:13931",
"services" : "00000003",
"lastsend" : 1391975697,
"lastrecv" : 1391975704,
"bytessent" : 229,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1391975696,
"version" : 70002,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"startingheight" : 8211,
"banscore" : 0
},
{
"addr" : "68.43.46.243:13931",
"services" : "00000003",
"lastsend" : 1391975949,
"lastrecv" : 1391975974,
"bytessent" : 6515,
"bytesrecv" : 111250,
"blocksrequested" : 0,
"conntime" : 1391975702,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12713,
"banscore" : 0
},
{
"addr" : "78.130.202.203:13931",
"services" : "00000003",
"lastsend" : 1391975975,
"lastrecv" : 1391975975,
"bytessent" : 5395,
"bytesrecv" : 7531,
"blocksrequested" : 0,
"conntime" : 1391975770,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12714,
"banscore" : 0
},
{
"addr" : "71.105.130.10:13931",
"services" : "00000003",
"lastsend" : 1391975772,
"lastrecv" : 1391975773,
"bytessent" : 229,
"bytesrecv" : 6925,
"blocksrequested" : 0,
"conntime" : 1391975770,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12660,
"banscore" : 0
},
{
"addr" : "149.210.168.71:13931",
"services" : "00000003",
"lastsend" : 1391975974,
"lastrecv" : 1391975974,
"bytessent" : 473,
"bytesrecv" : 11981,
"blocksrequested" : 0,
"conntime" : 1391975871,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12716,
"banscore" : 0
}

You have a forked blockchain. Same thing happened to me, here's how to fix it:

Just a note, I'm not looking at the picture you posted right now, so I can't be sure, but I'm assuming you're on Windows. If not, you'll have to figure out the filepath yourself.

Anyway, close the program, then open up Explorer and navigate over to C:\Users\<your username>\AppData\Roaming\Cryptographicanomaly . Either delete or rename the folders named "blocks" and "chainstate", then open up your cryptographicanomaly.conf file and replace all of the "addnode=" entries with the line "connect=88.198.198.94". Save the file and open up your wallet again, and it should start downloading the correct blockchain. Wait a bit for it to sync, and you're good to go!

I just mined MNC block # 266,528 with a gaming laptop powered by a very slow mobile NVIDIA GPU, that, even while resting on the ice packs I was using to cool it, was still only mining at about 7-10 kilohashes per second. The network difficulty was 147K, and my submitted share was more than 4 times that, at 621K. Words are cheap, so go to https://www.multipool.us/stats.php?curr=mnc , and you should see my username next to the aforementioned block. If you click on the block number, then search my name, you'll find that I only mined one share - the solution to the block - in the 4 minutes between blocks, and at the lowest weighted share difficulty possible. If you want more proof, I took a screenshot of my Cgminer window shortly after this happened, and I'll post it if you want.

So, here's the question I registered here to ask: What are the odds that this will ever happen again?

I mean, even I can't think of a good reason for why I was trying to mine on this machine, considering how stupidly impossible it would be to ever make any sort of usable profit, and the risk that such a prospect would have on poorly ventilated laptop hardware. Even thinking about attempting this sort of thing means ignoring every piece of good advice the cryptocurrency community has to offer. And, even as impossible as laptop mining may be, it somehow gets less and less profitable as time goes on, due to the ever escalating arms war that mining has become.

So, considering the fact that there are no reasons to ever attempt to do this, and that success is getting less likely by the second, would I be wrong if I said that it's likely that this "achievement" will never be earned again?