API issue.

[Serpent6877]

Currently setup for ETC. On the hourly stats the poolHashRate seems to be incorrect when it hits 300 million.

{
  "stats": [
    {
      "poolHashRate": 0.0,
      "connectedMiners": 0,
      "created": "2017-10-30T02:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T03:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T04:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T05:00:00"
    },
    {
      "poolHashRate": 210937280.0,
      "connectedMiners": 2,
      "created": "2017-10-30T06:00:00"
    },
    {
      "poolHashRate": 252204576.0,
      "connectedMiners": 2,
      "created": "2017-10-30T07:00:00"
    },
    {
      "poolHashRate": 267447680.0,
      "connectedMiners": 2,
      "created": "2017-10-30T08:00:00"
    },
    {
      "poolHashRate": 269532768.0,
      "connectedMiners": 2,
      "created": "2017-10-30T09:00:00"
    },
    {
      "poolHashRate": 257787168.0,
      "connectedMiners": 2,
      "created": "2017-10-30T10:00:00"
    },
    {
      "poolHashRate": 231941776.0,
      "connectedMiners": 2,
      "created": "2017-10-30T11:00:00"
    },
    {
      "poolHashRate": 268492480.0,
      "connectedMiners": 2,
      "created": "2017-10-30T12:00:00"
    },
    {
      "poolHashRate": 264365072.0,
      "connectedMiners": 2,
      "created": "2017-10-30T13:00:00"
    },
    {
      "poolHashRate": 259825152.0,
      "connectedMiners": 2,
      "created": "2017-10-30T14:00:00"
    },
    {
      "poolHashRate": 2.692994E+08,
      "connectedMiners": 2,
      "created": "2017-10-30T15:00:00"
    },
    {
      "poolHashRate": 295922240.0,
      "connectedMiners": 2,
      "created": "2017-10-30T16:00:00"
    },
    {
      "poolHashRate": 2.680819E+08,
      "connectedMiners": 2,
      "created": "2017-10-30T17:00:00"
    },
    {
      "poolHashRate": 2.891924E+08,
      "connectedMiners": 2,
      "created": "2017-10-30T18:00:00"
    }
  ]
}

It does show correct in the pools output:

 "donationsPercent": 0.1,
      "poolStats": {
        "connectedMiners": 2,
        "poolHashRate": 311678850

Also why are the miner specific stats ascending and the all the other output is descending times?

Miner stats:

      "poolId": "etc1",
      "miner": "0x24a0dc797d584f13b92ffcee41449b0f4e6427e6",
      "hashrate": 311678850,
      "workerHashrates": {
        "ferrari": 256070373,
        "lambo": 55608478
      },
      "created": "2017-10-30T18:20:00.0171145Z"
    },
    {
      "poolId": "etc1",
      "miner": "0x24a0dc797d584f13b92ffcee41449b0f4e6427e6",
      "hashrate": 255308473,
      "workerHashrates": {
        "lambo": 43238294,
        "ferrari": 212070179
      },
      "created": "2017-10-30T18:10:00.0135562Z"

Hourly stats:

  "stats": [
    {
      "poolHashRate": 0.0,
      "connectedMiners": 0,
      "created": "2017-10-30T02:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T03:00:00"

[oliverw]

The hashrate values over 300M are not a bug. The values are simply represented in scientific notation which is perfectly legal in JSON and accepted by all compliant parsers.