The "x" in the mining.authorize message actually had a carriage return character at the end, that raised a protocol exception.
Topic: Bug in the pool deamon?? (Read 730 times)
Problem solved
The "x" in the mining.authorize message actually had a carriage return character at the end, that raised a protocol exception.
The "x" in the mining.authorize message actually had a carriage return character at the end, that raised a protocol exception.
worker name and pwd are correct , and even if they were not, the pool normally would give me an answer
or it will still start the mining but it just would not know who to send coins to for the payout.
For example a friend of mine used givemecoins pool with a wrong worker name, the pool started mining despite of that but didn't give the coins to anyone.
or it will still start the mining but it just would not know who to send coins to for the payout.
For example a friend of mine used givemecoins pool with a wrong worker name, the pool started mining despite of that but didn't give the coins to anyone.
Hi,
i think i've found a bug in the stratum pool deamon, i'm mining from pooler cpuminer to the pool
stratum+tcp://wdc.vircurpool.com:3333
and the messages my client sends seems to be correct.
At the beginning it connects via TCP to the pool and it sends this stratum message
{"id": 1, "method": "mining.subscribe", "params": ["dummy"]}
the pool replies with :
{"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "f8002589", 4]}
{"params": [16], "id": null, "method": "mining.set_difficulty"}
{"params": ["375", "6dda62201b49f706141b790e713cfd934692410ac80f2a67162c231eed6b0350", "01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff27031aaf0c062f503253482f0430269a5208", "0d2f7374726174756d506f6f6c2f0000000001cf052152010000001976a914be58449edc4ab192a 4ef08eebcaa9121dba74cac88ac00000000", [], "00000001", "1c0c33bd", "529a262f", true], "id": null, "method": "mining.notify"}
Right after that, my client sends this stratum message
{"id": 2, "method": "mining.authorize", "params": ["vegetasayan.lionel1", "x"]}
After which the pool closes the connection without giving a response.
Why is this? Is it a bug or the client is sending wrong messages?
Thank you!!
i think i've found a bug in the stratum pool deamon, i'm mining from pooler cpuminer to the pool
stratum+tcp://wdc.vircurpool.com:3333
and the messages my client sends seems to be correct.
At the beginning it connects via TCP to the pool and it sends this stratum message
{"id": 1, "method": "mining.subscribe", "params": ["dummy"]}
the pool replies with :
{"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "f8002589", 4]}
{"params": [16], "id": null, "method": "mining.set_difficulty"}
{"params": ["375", "6dda62201b49f706141b790e713cfd934692410ac80f2a67162c231eed6b0350", "01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff27031aaf0c062f503253482f0430269a5208", "0d2f7374726174756d506f6f6c2f0000000001cf052152010000001976a914be58449edc4ab192a 4ef08eebcaa9121dba74cac88ac00000000", [], "00000001", "1c0c33bd", "529a262f", true], "id": null, "method": "mining.notify"}
Right after that, my client sends this stratum message
{"id": 2, "method": "mining.authorize", "params": ["vegetasayan.lionel1", "x"]}
After which the pool closes the connection without giving a response.
Why is this? Is it a bug or the client is sending wrong messages?
Thank you!!
Jump to: