Network difficulty is still set to the old N (0.017). According to coinmine.pl there will be 24hours before the difficulty drop (to 0.01).

I notice that after N change the CPU miner (minerd-yacoin-stratum on 5 Xeon cores) isn't getting much slower in term of hash rate but my laptop GPU (GT640M running on cudaminer) gets to 1/3 of N14 hash rate. Now these CPU and GPU miners run at about the same hash rate. YAC is a CPU coin again I have to stop my bigger NVdia GPU because it's getting 90C ! Probably due to summer, not the new N.

With a 6 X R7 240 4GB rig, I am getting a total U share rate of 6 shares/m vs 15 shares/m on NFactor 15 (hashrate can be a little misleading).

I only changed the lookup gap from 2 to 3. I don't think I can do much better than that...

I think this will be the most profitable cpu coin once the difficulty adjusts. Is this something someone can confirm?My I7-3770k was getting 0.82 khash/s before, and now it is getting exactly half at 0.41 khash/s.

With a 6 X R7 240 4GB rig, I am getting a total U share rate of 6 shares/m vs 15 shares/m on NFactor 15 (hashrate can be a little misleading).

I only changed the lookup gap from 2 to 3. I don't think I can do much better than that...

I think this will be the most profitable cpu coin once the difficulty adjusts. Is this something someone can confirm?My I7-3770k was getting 0.82 khash/s before, and now it is getting exactly half at 0.41 khash/s.

My i7 3610 laptop CPU is around 400 H/sec - half of what it was at NF=14. That's no surprise whatsoever. My 2GB R7 250 cards lost quite a bit though and are only twice that of the CPU, but are still using less wattage.

U on R7 240 4GB cards is about 1.1, down from around 2.7 (i think)R7 250 2GB cards are stinking up the place... U of < 0.7

Yea, wowww. Your prediction was spot on. I assume the only real change we can make to those R7 240 cards is lookup gap? With my R7 250 4gb, I think increasing R value to 8 times shader count helped clear HW errors, but I will have to get back to you on that after a little more testing.

My question is... will the R7 240 4gb be as obsolete, as the 2gb now seems to be, by the next NFactor change??? The new NVidia 880 might be the only hope for gpu mining YAC at that point, and it wouldn't even come out for a couple months after that NFactor change allegedly.

My question is... will the R7 240 4gb be as obsolete, as the 2gb now seems to be, by the next NFactor change??? The new NVidia 880 might be the only hope for gpu mining YAC at that point, and it wouldn't even come out for a couple months after that NFactor change allegedly.

Nope, it will still be rocking around LG=5 or LG=6. It just happens to be a good combination of low power and high memory... almost like an OpenCL ASIC that can drive your monitor too...

I think this will be the most profitable cpu coin once the difficulty adjusts.

I can almost see botnets on the horizon.

Quote from: mhps

Network difficulty is still set to the old N (0.017). According to coinmine.pl there will be 24hours before the difficulty drop (to 0.01).

Now 11 hours later the block time is 3min and there are 616 blocks to go. There will be 30 hours before the difficulty drop (to 0.005). Difficulty has (hopefully temporarily ) reached escape velocity.. this has better not become the beginning of vicious difficulty cycles: difficulty drops to the floor when retargetting -> miners dive in and mine like there is no tomorrow -> difficulty goes through the roof and retarget-> miners leave and mining almost stops -> slow confirmation time -> difficulty drops to floor -> long wait -> repeat

Now 11 hours later the block time is 3min and there are 616 blocks to go. There will be 30 hours before the difficulty drop (to 0.005). Difficulty has (hopefully temporarily ) reached escape velocity.. this has better not become the beginning of vicious difficulty cycles: difficulty drops to the floor when retargetting -> miners dive in and mine like there is no tomorrow -> difficulty goes through the roof and retarget-> miners leave and mining almost stops -> slow confirmation time -> difficulty drops to floor -> long wait -> repeat

difficulty adjusts every block, and it will be on a downward plummet for a day or two. Look at what it did for NF=14 - it was a veritable roller coaster of ups and downs, but no huge swings that it couldn't come back from...

Now 11 hours later the block time is 3min and there are 616 blocks to go. There will be 30 hours before the difficulty drop (to 0.005). Difficulty has (hopefully temporarily ) reached escape velocity.. this has better not become the beginning of vicious difficulty cycles: difficulty drops to the floor when retargetting -> miners dive in and mine like there is no tomorrow -> difficulty goes through the roof and retarget-> miners leave and mining almost stops -> slow confirmation time -> difficulty drops to floor -> long wait -> repeat

difficulty adjusts every block, and it will be on a downward plummet for a day or two. Look at what it did for NF=14 - it was a veritable roller coaster of ups and downs, but no huge swings that it couldn't come back from...

Yeah, I think most mining pools use the litecoin difficulty adjustment calculations (because it is already built into the pool 'template'). I find myself looking at it quite often, but then I have to remind myself YAC adjusts each block. It would be nice to see the actually next block estimated difficulty in pools though...

Now 11 hours later the block time is 3min and there are 616 blocks to go. There will be 30 hours before the difficulty drop (to 0.005). Difficulty has (hopefully temporarily ) reached escape velocity.. this has better not become the beginning of vicious difficulty cycles: difficulty drops to the floor when retargetting -> miners dive in and mine like there is no tomorrow -> difficulty goes through the roof and retarget-> miners leave and mining almost stops -> slow confirmation time -> difficulty drops to floor -> long wait -> repeat

difficulty adjusts every block

How come the block time is almost 3 min for so long ? It should go back to ~1min soon after the N change, right?