Does anyone know how to patch stratum-mining-proxy (LTC) for cgminer 3.7.2?

[fcmatt]

Hey all,

I want to use CryptoManiac / stratum-mining-proxy as a stratum to stratum proxy.

I am testing it with cgminer 3.7.2 and there is a problem. Shares are being rejected with 'target-miss'.
An older version of cgminer works fine (3.1.1) so something changed in newer versions of cgminer.

I am hoping someone can point me in the right direction on patching stratum-mining-proxy to work with cgminer 3.7.2 instead of down grading cgminer itself.

I will gladly provide more info on request or add to this post as I figure things out.

[mikeybit]

Interested in this as well

[fcmatt]

Here is what I am seeing in the proxy logs set to verbose when using cgminer 3.7.2

2014-01-09 16:53:20,991 DEBUG protocol protocol.writeJsonRequest # < {"params": ["user.1", "4c44", "01010000", "52cf447c", "e1922000"], "id": 15, "method": "mining.submit"}
2014-01-09 16:53:21,062 DEBUG protocol protocol.lineReceived # > {u'result': None, u'id': 15, u'error': [23, u'target-miss', None]}
2014-01-09 16:53:21,062 INFO proxy stratum_listener.submit # [71ms] Share from 'user.1' REJECTED: (23, u'target-miss', None)

cgminer 3.1.1 does not have this error.

[grizscom]

Does any one solve it?

I have same problem with cgminer ver 3.7.2

[fcmatt]

Does any one solve it?

I have same problem with cgminer ver 3.7.2

I ended up finding a perl program on github that i modifed a bit so it would not crash under load.... No one is going to fix stratum proxy cause the fault lies with cgminer.

[GodChamber]

Hey all,

I want to use CryptoManiac / stratum-mining-proxy as a stratum to stratum proxy.

I am testing it with cgminer 3.7.2 and there is a problem. Shares are being rejected with 'target-miss'.
An older version of cgminer works fine (3.1.1) so something changed in newer versions of cgminer.

I am hoping someone can point me in the right direction on patching stratum-mining-proxy to work with cgminer 3.7.2 instead of down grading cgminer itself.

I will gladly provide more info on request or add to this post as I figure things out.

Changing "Display" to "Quiet" cleared this problem up for me right away.