Agreed. If the difficulty go down tomorrow and those 2 stop mining, we the rest of the miners will get biggest shares also since the difficulty will drop even further after their stoppage. Point is that we need to mine in many pools and not in nanopool only since that centralization in mining is bad for any cryptocoin.

Who knows what command we need to add in the miner's options for Claymore and CastXMR to allow us to mine after the fork?

Thank you for your good work and support on your miners Claymore

15% orphan blocks in the last 24 hours is terrible for the network. I wonder why that increase happened while monero network is close to 3% at all times and electroneum was already close to 5% average since it started.

Does anyone knows a way to force RX580 get the settings of start.bat or config.txt for cc, mc and voltages with latest AMD drivers in windows 7?

Happened to me today when testing in windows 10 even with the default settings from the miner's file. Even when having the UAC deactivated as Claymore suggested in readme troubleshooting. Any ideas @Claymore?

Update: That is solved when one runs the shortcut of the miner.exe setup to run as administrator after we put the start.bat options in the shortcut. After the 1st time it starts correctly and reboot it works properly from the start.bat as usual for Claymore's miners.

I have the same problem too but it relates to Claymore's devfee mining only. Don't know how to solve it, so I expect the pool and Claymore to solve it somehow.

You should just put the settings about core and memory clock and voltage in the config.txt instead of the start.bat (1 line per command). In Ethereum miner it works in the opposite way. Weird that there isn't any mention about that in the readme file but at least it is a 2 way experiment, so it is relatively easy to find out where the settings work.

Thanks a lot for your work on miners Claymore.

This CPU miner though is crashing my cmd.exe to the point that it isn't able to be closed as a program by any means (task manager for instance cannot close it or your miner's exe either). Even restarting process is stuck and not proceeding properly. My CPU is a FX8350. It worked yesterday for 2-3 times and from this morning it cannot go past the point shown in the link below. Does anyone know if something pool related is responsible for this or something else? Crazy bug here. 

https://imgur.com/a/ZPIpi

UPDATE:

All good after putting exceptions on Kaspersky for the exe of the miner.