Topic: YIIMP style API - what are the units? (AHashPool, zPool, etc) (Read 195 times)
looks like nobody knows. From examining the source code nobody thought about it and the units are not fed into the API result ..
Can anyone point me in some direction how to interpret the yiimp API result, which column should be used to get the current profit per algo, and which units are those fields meant in?
example from zPool:
{"name":"nist5","port":3833,"coins":6,"fees":2,"hashrate":36290627388,"workers":144,"estimate_current":"0.00000189","estimate_last24h":"0.00000309","actual_last24h":"0.00205" .... }
the "actual_last24" is in an "unknown" unit, looks like it can be figured out by looking on the website if it is mentioned (but that is often wrong or incomplete for zPool) .. so this column is basically useless for auomated parsing because it does not report the unit and the unit differs per algo
"estimate_current" & "estimate_last24h" it seems, those are always in BTC/Gh/day .. (is that true?) - but those values are unrealiable as well because if an algo goes down for whatever reason on the pool (exchangeproblem, like it happened with LUXCOIN at ahashpool recently), those fields are still populated and therefore wrong.
Is there any chance to get the "actual" column in a fixed unit? It's not really the brightest idea to return a value with an unknown unit in an API response ..
example from zPool:
{"name":"nist5","port":3833,"coins":6,"fees":2,"hashrate":36290627388,"workers":144,"estimate_current":"0.00000189","estimate_last24h":"0.00000309","actual_last24h":"0.00205" .... }
the "actual_last24" is in an "unknown" unit, looks like it can be figured out by looking on the website if it is mentioned (but that is often wrong or incomplete for zPool) .. so this column is basically useless for auomated parsing because it does not report the unit and the unit differs per algo
"estimate_current" & "estimate_last24h" it seems, those are always in BTC/Gh/day .. (is that true?) - but those values are unrealiable as well because if an algo goes down for whatever reason on the pool (exchangeproblem, like it happened with LUXCOIN at ahashpool recently), those fields are still populated and therefore wrong.
Is there any chance to get the "actual" column in a fixed unit? It's not really the brightest idea to return a value with an unknown unit in an API response ..
Jump to: