Prohashing Mining Pool Forums

Eyedol-X wrote:I can't get either Claymore Zcash or Optiminer Zcash Windows versions to work on a rig with 1 AMD GPU. Both of them throw errors indicating that pool is sending invalid or wrong data.

Anyone have any command line suggestions for AMD cards that work?

Steve Sokolowski wrote:Chris is issuing a restart now to fix more Equihash bugs that were identified last night. Once we're back online, then we're hoping to enable equihash mining in an hour or two.

Eyedol-X wrote:

Steve Sokolowski wrote:Chris is issuing a restart now to fix more Equihash bugs that were identified last night. Once we're back online, then we're hoping to enable equihash mining in an hour or two.

Same issue with a 1gpu amd rig -- any update? Should I assume it's still offline?

Steve Sokolowski wrote:

Eyedol-X wrote:

Steve Sokolowski wrote:Chris is issuing a restart now to fix more Equihash bugs that were identified last night. Once we're back online, then we're hoping to enable equihash mining in an hour or two.

Same issue with a 1gpu amd rig -- any update? Should I assume it's still offline?

We identified another issue now with block headers not being constructed properly. Since hashes, when wrong, are simply wrong, rather than giving any indication of which bytes are out of order, this is probably going to take a day to investigate.

Eyedol-X wrote:

Steve Sokolowski wrote:

Eyedol-X wrote:
Same issue with a 1gpu amd rig -- any update? Should I assume it's still offline?

We identified another issue now with block headers not being constructed properly. Since hashes, when wrong, are simply wrong, rather than giving any indication of which bytes are out of order, this is probably going to take a day to investigate.

Still experiencing same issue here after it was announced in chat that it's back online.

Errors from both claymore and optiminer indicate issues detecting difficulty or work

EWBF Nvidia Miner works but upon first connecting it throws an error about detecting work as well.

Might I suggest a dedicated equihash port? I think that may be the issue here

Steve Sokolowski wrote:

Eyedol-X wrote:

Steve Sokolowski wrote:
We identified another issue now with block headers not being constructed properly. Since hashes, when wrong, are simply wrong, rather than giving any indication of which bytes are out of order, this is probably going to take a day to investigate.

Still experiencing same issue here after it was announced in chat that it's back online.

Errors from both claymore and optiminer indicate issues detecting difficulty or work

EWBF Nvidia Miner works but upon first connecting it throws an error about detecting work as well.

Might I suggest a dedicated equihash port? I think that may be the issue here

The system's architecture wouldn't allow a different port without a large amount of additional work.

I haven't had any issues with the Claymore ZCash miner. Have you tried that? I want to know whether there's something wrong with my test environment, or whether every other miner than the Claymore doesn't work.

Steve Sokolowski wrote:

Code: Select all

ZecMiner64.exe -zpool prohashing.com:3333 -zwal chris -zpsw "a=test23 d=2048" -allpools 1

What is the text of the errors you're seeing?

16:37:51:520	c6c	ZEC: Stratum - connecting to 'prohashing.com' <167.88.15.87> port 3333 (unsecure)
16:37:51:588	1b78	Watchdog enabled
16:37:51:591	1b78	Remote management (READ-ONLY MODE) is enabled on port 3333
16:37:51:594	1b78	

16:37:51:612	c6c	send: {"id": 1, "method": "mining.subscribe", "params": ["equihashminer", null, "prohashing.com", "3333"]}

16:37:51:614	c6c	send: {"id": 2, "method": "mining.authorize", "params": ["(redactedusername)",""a=equihash n=MSI480""]}

16:37:51:617	c6c	send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

16:37:51:620	c6c	ZEC: Stratum - Connected (prohashing.com:3333) (unsecure)
16:37:51:718	c6c	got 1029 bytes
16:37:51:719	c6c	buf: {"id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "401d4320", 4], "error": null}
{"id": null, "method": "mining.set_difficulty", "params": [65536.0]}
{"id": null, "method": "mining.notify", "params": ["1200e1e", "3475c98fe7ee85adac6c2d86175c8cc871c64cd7494f6ab65285f9b25410af6b", "01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4b03d015150425d8a15afabe6d6d5e9f0b69c28b83d597fa856db96e2e2d281b778c99c438e246595eee4ed2a06d080000000000000008", "0c2f4247374c51435055394f2f0000000002e4973095000000001976a91481308472f5a29a68cec40cbb4cd3f4be7209445688ac0000000000000000266a24aa21a9ede68528d2ad2194d9cd2714830b5d32cf6fec8d9f2b0efb1b07aa4907bec2a44100000000", ["9d7a5a9dd0f301100f35581d97a5b305d9640da2d1e7f39f49059210938c4608", "d50717f64f2fbc9fbdf1a9c8a2128f6c1cba311c7a99f0a16cff96ffff00954e", "e50a43bfc5b9655da642d992144ef90e33b323756f7d55d9a969e35721c665e7", "1defbf100635b0cd5223d1bdeb582e0bf2af24f8a68a3edad30c7118a5accc9f"], "20000000", "1a0314ad", "5aa1d720", true]}

16:37:51:720	c6c	parse packet: 98
16:37:51:721	c6c	remove first packet 901
16:37:51:722	c6c	new buf size: 901
16:37:51:723	c6c	parse packet: 63
16:37:51:723	c6c	ZEC: Received unknown response: {"id":null,"method":"mining.set_difficulty","params":[65536.0]}

16:37:51:724	c6c	remove first packet 837
16:37:51:725	c6c	new buf size: 837
16:37:51:726	c6c	parse packet: 836
16:37:51:727	c6c	new buf size: 0
16:37:51:801	c6c	socket was closed remotely
16:37:51:803	c6c	ZEC: Job timeout, disconnect, retry in 20 sec...
16:37:54:270	13bc	Quit...