1% fee Diamond pool
No registration necessary (just point your miners to stratum+tcp://groestlcoin.biz:3334 and use your wallet address as login)
No transaction fees
Payouts every hour (from 0.1 DMD)
Location: Amsterdam
Now with per uses statistics: http://groestlcoin.biz/workers
PS: I finally made it work, 5 blocks found so far. Payouts work ok.
Great news, you got it working.
I don't really understand why people get so many rejects from stratum at dmdpool.digsys.bg -- my miners get virtually zero rejects. Perhaps --no-submit-stale will help?
I thought of that No-submit-stale switch and did add it. Though it only stops the miner from sending it to the stratum (in vain). The actual share is still unusable (stale) although it does not show up on the Pool dashboard...and CGwatcher will still keep a record of it. The truth is still that 4% of the shares I create are of no use. Resulting in me only running at 96% of my capacity. I suspect that the problem is primarily on the location of the server, which probably is quite far from me. Though I am not requesting you to move it as it probably suits a hell of a lot of other people. My second guess would be the exceptional workload that your server receives as you currently host 80% of poolminers.
Im saying all this without knowing your specifics, but the main point being that the problem is not yours to solve As more pools arise and ppl start spreading the hash it will all auto-correct.
Might be the network round trip time. What ping times you see to dmdpool.digsys.bg?
The server is not loaded at all. In fact, it runs a number of other tasks, over a dozen pools and... from time to time I do run an CPU miner just to fill up more the CPU cores
It does have some kind of disk bandwidth bottleneck, primarily because too many things write too many log files, but still far away from loaded. That is being addressed anyway.
Other than that, I still do believe it is my task to identify and resolve issues with the service I started (the Diamond mining pool and permanent node). So, if the server somehow causes you to generate rejects, I am looking for ways to fix it.