Awesome Miner is not using the individual json files for each coin, because that would be too much hardcoding in Awesome Miner and too many requests sent to the WhatToMine web server.
I'm currently working with the author of WhatToMine to get more coins from the standard coins.json API or similar from WhatToMine. This is really the best solution, because I want any coin that is getting added to WhatToMine to automatically show up in Awesome Miner. That concept works already today, but the WhatToMine coins-API doesn't include some of the new coins.
This is why i think it would be better to create a template design similar to the way you added the ability to add new algos to online services. Literally every website whattomine, coinmarketcap, etc... all those websites are pulling data from the coin explorers... i dont see why we cant just pull the data from the coin explorers for each individual coin. The amount of data being transferred from a json request is very minimal honestly. This would reduce the requirement to pull all this data from whattomine.
Example: SIGT
Add a 4th option under the "optional section"
Labeled: Json Profitability Calculator Properties
JSON URL:
Then add the ability to dictate within the data the values are found, maybe add a pull data button, which would pull in data and dynamically fill in empty boxes with data detected after each comma, then check the parts the data is found in and assign it to difficulty, block reward, and price....
idk maybe it would be easier to just had a preprogrammed option with just the whattomine json format already formatted, all the user does is add the new coin json url and it populates the rest.... You could set this as an non default option so the users can do it when new coins come out if they are dedicated to mining enough update it daily like this on new coins.
Good point. But for WhatToMine, if the author is adding all coins automatically to the combined coins.json file requested by Awesome Miner, there isn't much need to specify individual coin files from WhatToMine. It's only right now before that's in place on WhatToMine it could make sense.
For other statistics sources out there like coin explorers, they all provide slightly different API's so there is no single standard here, making it difficult to have generic support for it in Awesome Miner. Your suggestion to define rules for JSON processing is however taking care of that scenario, so that idea is for sure something I will consider. Thanks!
What some of the larger customers of Awesome Miner is doing is to write their own C# scripts inside Awesome Miner, where they pull JSON data from whatever sources they want, process it and then using the C# scripting API in Awesome Miner to update the coin profitability statistics. This is for sure more complex, but it gives full flexibility and can support any data source out there, do any calculations and also combine data from multiple sources into a single coin.
Maybe multiple JSON requests should be used to update different aspects of a coin, because block explorers give some information, while you need exchange data for others.