6 Days ago we had a killer day but since then the pool is struggling to find pools? Is there anything you changed. We have had increased hash rates but lower block findings.

Please could you have a look

Thanks

To make sure the nobody gets left out when our one of our low-hashrate pools finally finds a block, the PPLNS Window for the following pools has been made twice as large:

• Monero
• AEON
• Litecoin
• Ethereum
• Ethereum Classic
• ZCash

I've come across a trick that increases hash rate of CPU mining on Windows 10. I managed to squeeze about 30% extra on average out of my i7. Worked for @JPB18 as well. You might want to give it a try guys.

From the Start menu, open Local Security Policy (under Administrative Tools).
Under Local Policies\User Rights Assignment, double click the Lock Pages in Memory setting.
Click Add User or Group and type your Windows user name.
Restart your computer (logging off and on might work as well)

Good day! newbie on cryptomining pls be gentle :). I just observe that my shares went down from 1.5M to 400K on dash pool . Miner been running 24/7 and never been OFF. Is this normal?

Seems only about 20% of expected return.

I doubt that after 11 hours of not finding anything, a new block was found with a 2% effort:

Hello,

First of all @Poolmining Support, i want to say that i really appreciate all the hard work, the fact you chose to create your own pool and SW and the fact that you try to respond personally to as much of the questions possible. I feel like you are up to creating a nice loyal communuty here. Keep up the good work.

I am new to mining. Currently i am mining on the Monero pool.

Now to my PPLNS uncertainties. First i will state what and how i understand PPLNS works (please correct me if i got anything wrong) and then i will have some questions that i would like to get clarified.

What i know so far (hopefully correct):

PPLNS = Pay Per Last N Shares

-so when a block is found it pays for the last N shares submitted (and also takes into account the difficulty of those shares)

- N shares window is calculated as being X * difficulty

- share count is not resetted when a block is found

My questions:

1. What is the value of X in calculating the number of shares to reward? Is it according to FAQ (ie. value of 2?), or that is just an generic explanation?

2. What is the value of difficulty taken into consideration. Difficulty of the block that was found, or the difficulty that the pool assigned to the miner by VarDiff at the moment the block was found?

And a concern:

If the case is that X = 2 and difficulty = difficulty that the pool assigned to the miner by VarDiff at the moment the block was found, considering a pool that has a hard time finding any blocks, the Monero pool for example, won't this mean that miners are loosing shares that will never get rewarded?

To be more specific: I mine at an avg. rate of 475 H/s on port 3033 now. The pool dinamically assigs me an average difficulty of around 6500-7000. Let's supose 7000. And my total number of shares is 22402 right now.

If a block were to be found now, if the case is as stated above, then N = 2 * 7000 = 14000.

So theoretically i will be rewarded for the last 14000 shares and 22402 - 14000 = 8402 shares are lost. Am i right?

If yes, is there any way this can be prevented, like allowing miners to ask for a certain difficulty and prevent VarDiff? Or increase value of X?

I mean 8402 shares lost is...kind of a big waste, about a day worth of mining and electricity in vain.

I am eagerly awaiting your answers.

Thank you!

The good news first: The infrastructure and configuration changes performed yesterday greatly increased the efficiency of the pool. As a result the pool found 4 blocks yesterday alone. One of the blocks (783247) went missing due to a configuration change related to a pool restart just in the moment the block was found. I've manually added the block to the database for payment processing.

Now to the bad news: The other 3 blocks we've found where rejected by the dash daemon because in all that chaos a configuration switch was removed that enabled the correct handling of Dash Masternode Payments. As a result of this, the effort for those 3 blocks was wasted. I'm deeply sorry about this. The error has since been corrected.

The Dash pool found a block - and most likely will find more throughout night - that is currently not shown on the website. I'm aware of the issue and will resolve it tommorow morning. I have to get some sleep after 19 hours of work. Thanks for your patience.