Hi All,
I feel a bit of a dead head, usually when I have questions I just go to the code but I am having a bit of a problem with stratum-mining-proxy and my python knowledge is very sub par. I have been aware of the custom-user capabilities of it and want to take advantage of it with;-
./mining_proxy.py -v --host=stratum.bitcoin.cz --port=3333 --custom-user=MinePeon.Donate --custom-password=Donate
The problem is it still uses the authorise credentuals supplied by the miner dispite showing;-
2013-06-19 01:16:25,727 WARNING proxy mining_proxy.on_connect # Authorizing custom user MinePeon.Donate, password Donate
2013-06-19 01:16:25,728 DEBUG protocol protocol.writeJsonRequest # < {"params": ["MinePeon.Donate", "Donate"], "id": 1, "method": "mining.authorize"}
In the startup. Am I missing something? Is this not the intention of those parameters?
Neil
I got it working on the beaglebone, your parameter usage isn't correct.
should be:
./mining_proxy.py -o stratum.bitcoin.cz -p 3333
then you connect your miner to the proxy and provide the pool user/pass there
./cgminer -o 127.0.0.1:3333 -u MinePeon.Donate -p Donate
If you are going to use the custom_user options, then don't specify a user/pass on the miner, or make them null ""; the point is so that miners can remote connect without revealing user/pass to eliminate a potential man-in-the-middle attack. EDIT doesn't seem to work, it connects to the pool but either uses the credentials supplied by the miner or pukes. I'm no python expert either but will take a crack at it.
MOAR edit. I think I've figured out what the feature does finally. It overrides the submission of shares to go to the account you specify, but it looks like you still need to supply valid credentials at the miner. Going to make a few accounts and test.
If you are feeling generous, hit the donation address in my sig. We have similar projects, so I look forward to collaboration (rather than name calling ala kano/luke-jr).
