Call me crazy, but merged mining should not affect what would be considered calculation of difficulty per node; the difference being is that the merged mining component (node) is mining with varied hash and share rates, causing the calculation of difficulty per node to be more difficult since those two variable would be changing. In other words, the difficulty would be changing for a merged mine node every instance of check-in on the blockchain, share, block find and any other event on the blockchain.
I am approaching this strictly from a mining point of view, specifically p2pool merged mining pools. To that end, I have run a view with the merged mining pool option which was basically making sure that time was optimized per hash.
I am suggesting that the calculation would not change, just the frequency. If I am wrong, please let me know and where to find the calculation.
|