(xandriel)
<
<
<
I did a test of pointing the blade to a non-existent worker at the pool and things did not appear to work at the proxy. I then created that worker at the pool and the proxy started spitting accepted messages and the blade started showing accepted count. I took that to mean that the blade was talking through the proxy to the pool server.
(DrunkenSailor)
>>I've got a v2 blade working fine with Slush's pool. Could you post some of your proxy log? That might help folks >>point you in the right direction. Also, it does take some time for the worker to show up, and even more time for the >>Mh/s to be shown accurately for the worker. Having said that, 2 hours should have been more than enough for the >>worker to at least show up
It is very encouraging to hear that both you and grim xandriel have blades talking to slush. That means I just have to find the right combination.
I will try to post some proxy log a bit later. I have to get it from across the network.
(grimsparkle)
>>One other thought... make sure the blade's configuration points to the IP address of the computer running >>mining_proxy under Server addresses:
>>Ports: 8332,8332
>>Server Addresses: your Mac's IP address, your Mac's IP address
>>user:pass: username.worker1:password,username.worker1:password
>>Blade port 8332 ---->Proxy(Mac 'server' running mining_proxy.py) port 3333 ----> Slush's Pool
I am pretty sure that is how I had it set up. I will check a bit later after it has run for a while on bitminter.
I also have to eat dinner. I certainly appreciate all the help especially knowing that it will work.
Morris