Better explanation of config value and vardiff pools

[aleqx]

Hi,

Thanks for this proxy! I'm trying to use it with Hashvault which says I can set the username to wallet+DIFF to fix the difficulty of the shares (which I don't think it works, it seems to be vardiff regardless). I'd like to understand how to best configure the proxy.

Let's assume for the sake of the argument that I have 700 miners, each doing 70 H/s connected to the proxy, and that I use a single pool, hence I set share: 100 in config.json

• if the pool is vardiff starting at diff=5000, what value should I set for shareTargetTime, minDiff and maxDiff
• if I could set a fixed diff at the pool's side (not proxy), what value should I set that to? What values do I then set for shareTargetTime, minDiff and maxDiff?

A side question: how could I actually determine the difficulty of the job sent by the pool? I'm trying to use user=wallet+DIFF on Hashvault in order to fix the difficulty (as they say here https://electroneum.hashvault.pro/en/#!/ports) but the rate at which the proxy is submitting shares changes after the second job is received, suggesting the pool has changed the difficulty ...

Also, is there a way to set failover pools in config.json? That is, configure 2 pools in config.json, but use the second pool only if the first goes offline (rather than always send shares to both).

Many thanks in advance

[NoleA1]

I would love to know this as well. Have 300 miners, each running 800 hs.

[bobbieltd]

I don’t think those affect much the efficiency. Only shareTargetTime that you can try to reduce. I think proxy works with fixed diff if the pool supports it.