Glizlack: The latest version better supports new algorithms, and you can add coins manually in Coin Manager (Settings->Other Tools...->Manage Coins). Otherwise, coin data is loaded from your selected provider - CoinChoose or CoinWarz. So you'd need to get in touch with those developers about adding new coins to their data. I tried to write it so that if coins with new algorithms are added, CGWatcher can handle them without requiring a software update. Even without knowing what words they'll both use for new algorithms, once I find them out I should be able to update the website where CGWatcher gets its algorithm data from and CGWatcher will pick this data up about every hour.

Regarding your stratum question, I'm not sure what you're referring to. CGWatcher doesn't limit anything you can do with the miner, so anything that the miner supports you should be able to do with CGWatcher.


Ninetoe: In version 1.4.0 (available now), there are a few new settings (Settings->Miner). The first is to disable using a temporary config file. The reason CGWatcher uses a temporary config file is because some users share config files between miners, then use arguments or variables to customize settings for each miner. Using a temporary file ensures one miner doesn't affect another. Using a temporary config file also allows arguments to override config file settings because CGWatcher applies the arguments to the temporary config file before launching the miner. Otherwise if the same setting is defined in both arguments and a config file, the config file value is used.

The downside to using a temporary config file is that if there are significant changes to config file format (e.g. new pool property settings in SGMiner 4.2.1), it requires a software update. (CGWatcher can handle unknown settings, but currently not unknown pool settings).

If you disable the use of temporary config file, CGWatcher may then need to modify your original config file before launching the miner (and then restore it after the miner is launched). The reason it may need to modify the original config file is to a) enable the API if it is not properly enabled, and b) replace variable names with values if you're using variables. The way it enables the API here is different than when using a temporary config file, in that it just inserts text if needed so if your config file has settings unknown to it (including pool settings), they won't be touched.

If you disable using a temporary config file, there is then a second setting "Do not modify original config file to enable API during miner start". Enabling this will prevent CGWatcher from inserting the API-enabling settings, essentially leaving your config file untouched. The only reason it will make changes now is if you're using variables, in which case it will restore the original config file contents once the miner has started. If this setting is enabled, it requires the user to make sure the API is properly enabled.

So hopefully these two settings will make it easier to use CGWatcher with new config file settings without worrying that CGWatcher doesn't know what those settings are and doesn't use them in the temporary config file.


kidyubyub: I don't have any experience with a Block Erupter Cube. If it runs mining software on the device itself, it is probably better suited for CGRemote. You may be able to use bfgminer as a proxy similar to how it can be done with Block Erupter Blades. In that case, you would run bfgminer on a Windows PC with CGWatcher, and the device would show up in bfgminer. You can find more information in bfgminer's README.ASIC document.


cryptomole/Ntrain2k: Can you send me the config file or arguments you use to start bfgminer outside of CGWatcher? I'd also suggest disabling the use of temporary config file (Settings->Miner->Disable temporary config file creation during miner start). That way if there is anything unique about the config file that CGWatcher is having a hard time with, it is less likely to modify it. Your config file/arguments should tell me if there is a new specific setting CGWatcher needs to know about, and if that's the case I'll get an update released today with the changes.