Just checked your api again and Actual_last24h is still reporting all algos in BTC instead of mBTC.
I bring up this issue because it REALLY throws off the estimates that Miner Control calculates if a user wants to use the actual_last24h metric.
here is your API output:
quark: {
name: "quark",
port: 4033,
coins: 5,
fees: 4,
hashrate: 4999611313,
estimate_current: 0.00027572,
estimate_last24h: 0.00024218,
actual_last24h: 0.1856,
rental_current: 0.28721017
},
and here is YAAMP's API output:
quark: {
name: "quark",
port: 4033,
coins: 1,
fees: 3,
hashrate: 1000000,
estimate_current: 0.0002578,
estimate_last24h: 0.0002578,
actual_last24h: 0.0002416
}
your value for actual_last24h in this example should be 0.0001856 instead of 0.1856
*rental_current is also reporting in BTC instead of mBTC, but we don't use that value in Miner Control