I don’t recall nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze's dashboard having any issues when I tried it out months ago, but now it doesn’t seem to report hashrate accurately. It’s either 0 Th/s or a large value that’s higher than the spec of the miner (e.g. 18.76 Th/s for an S9).

Does anyone else experience this? #asknostr

Cc: nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr

yep

Reply to this note

Please Login to reply.

Discussion

Hmm weird, I've never had that problem, is it the 60second or the last 3 hours hashrate that you are referring to?

Yeah it’s the 60 second mainly.

The only options I see are 1 week, 1 month, and 6 months--and they all look jacked up. On average it's correct, but the spikes do look weird.

If you're not turning machines on and off(would cause severe spikes) the. It's probably just the variance in hashrate the machines are producing. I had an S19 today do 175th on the 60 second 😂

I just turned them on today and it seems the 3hr hashrates are starting to look “correct”. So I’m happy with that at least.

It still would be nice if the 60s and status columns are useable (looks like the miners are reported as offline whenever the 60s hashrate is 0 Th/s).

I don't think that's an Ocean issue, it is just the nature of ASICs, sometimes in 60 sec and S19 creates 175th on average and sometimes it only makes 45th, but on average (3hrs) it will end up near 100th.

Braiins does a 5 min hashrate which would be much smoother. But I prefer the 60 sec. Because I can tell quickly if my "full" hashrate is getting to the pool.

Gotcha. Thanks for explaining. I didn’t know the hashrate could go past what’s indicated on the machine. I guess it makes sense since it sounds like that’s where it’ll average out.

Your Lightning address isn’t working btw.

Yeah I should fix that

Check out coinos.io 🤙