If the current block's difficulty on which miners are working changes, this new code in pool.js and jobManager.js ( in NOMP's module " stratum-pool " )
will make the stratum server send a new work request to miners.
Before that, it would send a new job id , but if the difficulty in CURRENT block would change, as some new coins include this possibility, it would not update this information to miners, so miners on the pool would continue to mine with the " old " block's difficulty, and if any miner on the pool would find a block, the block would not be accepted since it is not the correct difficulty.
This is a very good protection against high hash variation for new coins, that sometimes happen ( a big farm mines for a few minutes at a very high hash rate and then stops, which makes the network stales over a very difficult block to mine for a very long period of time, or even forever.... killing this new coin ! ).
Here is the source code with this change :
update coming soon
Here is a live pool that implements this change for the coin LIghtningCash, which includes the DarkGravityWave PoW algorithm ( difficulty change for every block ) with " progressively lower difficulty if there is a long stale tip " variation in it :
