Equihash125 down again

Equihash125 down again and still listed in API

MrPlus wrote: Equihash125 down again and still listed in API

I'll ask Chris to look into this again as soon as he gets up.

My understanding from earlier is that there was a coin that was going into error frequently, and Chris had resolved the issue. I guess that fix was incorrect.

More importantly, when failures occur on stratums, we need the algo to be delisted in the API so miners will stop trying and mine another algo until stratums gets back. This will avoid loss of hashrate for all, miners and ProHashing.

I just wanted to provide an update.

Vance got back to me about this issue. He agreed that we need to point out when an algorithm has all coins in error, but we aren't quite sure what the best way to implement that is.

We plan to work on this during the week of July 19 and will probably talk to you here before then to solicit feedback.

Thanks for the update.
This is happening again right now by the way...

From an API perspective. I'd suggest the algo to be removed from the API in such case. (As other pools do)

MrPlus wrote: Thanks for the update.
This is happening again right now by the way...

From an API perspective. I'd suggest the algo to be removed from the API in such case. (As other pools do)

I think that the plan is to add a new field that specifies whether all of the algorithm's coins are currently in error. Would that be fine?

You (or anyone who uses the API) could workaround this issue right now by looking through the data and returning True once a single coin associated with the algorithm is found to have no errors. Otherwise, if you get through the entire list, you could return False.

Steve Sokolowski wrote: I think that the plan is to add a new field that specifies whether all of the algorithm's coins are currently in error. Would that be fine?

You (or anyone who uses the API) could workaround this issue right now by looking through the data and returning True once a single coin associated with the algorithm is found to have no errors. Otherwise, if you get through the entire list, you could return False.

Thanks for getting back.

I'm unsure how that will work. Most mining tools working on standard Yiimp based API do not work this way. They simply ignore an algo when it is no longer listed on the API or the API report zero as a estimated price. Would be best to stick to this I think.

Talking about price. Will it take into account that a coin is down?
Or will the estimation still consider this coin?