Quote from: Temporel on October 15, 2017, 05:32:39 PM

Quote from: ZenFr on October 15, 2017, 04:24:58 PM

Quote from: Temporel on October 15, 2017, 04:11:42 PM

Quote from: ZenFr on October 15, 2017, 04:05:29 PM

Quote from: gurupool on October 15, 2017, 03:50:33 AM

The first block of our pool (https://zpool.guru) is found with DSTM Grin

I just have a test with you pool : with a 200 sol/s miner, no share, O, null.
I stop the test after few minutes.
In the same time, few minutes, with SuprNova, I get a lot od shares.
Why I get 0 share with your pool, smallest than suprnova ?

of course it is smaller than suprnova, never join a new or small pool unless its a new coin.

The best pool for ZEC so far is Flypool:
https://www.reddit.com/r/gpumining/comments/729ixq/flypool_is_the_most_profitable_zcash_pool/

Ok, I will try this pool "FlyPool"
But you didn't explain why never join a new or small pool unless it is a new coin ?
I understand the "unless it is a new coin (sometime, there only one new pool for a new coin), but not the rest...

bigger the pool = more chance = more for you
Its basic math/stats
Google it

Considering the fact that flypool is too close to 51% (attack), and that it keeps under reporting my hashrate compared with what the local miners report (both dstm and ewbf) I was willing to give it a try for a day or two and see how it goes. So far it's reporting slightly higher hashrate than flypool. Let's when (hopefully not if...) it pays how that goes.
@zcash.guru if you could, please simply the API, the hashrate as number, I don't know what it is, but is way off... Like 50000 times the hashrate, which means I would have to estimate the hashrate from it. The hashrate as String is no fun reading as it requires string parsing.
For starters, all it needs is the current and average hashrate (real number) for the whole address, and the same (current and average) for each worker.
Then you might need to implement the immature balance, as it will stop people from raiding the pool.
Also there is a spelling error in the API documentation. Stats appears twice.