Skip to content
Sebastian Grewe edited this page Jun 5, 2013 · 23 revisions

A quick FAQ of things we have encountered so far.

Q) Why does stratum seem to be off when using mmcfe-ng? A) Long Answer, sorry for that! @pooler was nice enough to explain it to me in detail:

pushpoold uses a target bits terminology and stratum a difficulty setting. These are different. When running pushpoold at a target bit of 20 you will match the default setting of 16 in startum-mining. This will ensure that hashrates on mmcfe-ng match up! If you'd think you could set pushpoold to 16 and match it with stratum you will be off.

He devised a formula that can be used to change startum difficulty and match pushpoold and mmcfe-ng to it:

(stratum diff) ~= 2^((target bits in pushpool) - 16)

So if you change your stratum dWhen running stratum-mining I noticed that stratum and pushpoold use different settings. @pooler was nice enough to explain it to me in detail:

pushpoold uses a target bits terminology and stratum a difficulty setting. These are different. When running pushpoold at a target bit of 20 you will match the default setting of 16 in startum-mining. This will ensure that hashrates on mmcfe-ng match up! If you'd think you could set pushpoold to 16 and match it with stratum you will be off.

He devised a formula that can be used to adjust stratum to match the difficulty used in mmcfe-ng (and pushpoold:

(stratum diff) ~= 2^((target bits in pushpool) - 16)

Example, you are running mmcfe-ng and pushpoold with a setting of 20:

16 ~= 2^(20 - 16)

Clone this wiki locally