Quote from: Astrali on November 29, 2017, 03:08:33 PM

Quote from: aarons6 on November 29, 2017, 03:38:00 AM

Quote from: VersiJinx on November 29, 2017, 03:07:29 AM

Can these mine on prohashing? I cant seem to connect it properly

it works but not very well. you must add #skipcbcheck to the url...
so stratum+tcp://prohashing.com:3333#skipcbcheck

also diff 512 is the lowest it goes, which is worker diff 2 in bfgminer..
this means it could be an hour or more between shares.. probably not ideal.. :/

my 0.333 mh/s gridseed miner works ultra smooth at 64 diff.
a device 10x faster than that should be able to handle a diff at 512 .. or not?

im a bit confused now

pool diff 512 should be one every 30 seconds or so at stock ~4mh speeds. Regardless of pool diff with the current driver you should be seeing multiple red led flashes a second. The first hash numbers show whats going on at the device level regardless of whether the device has found a pool diff share or not...that just depends on luck.

Obviously if you want less variance in your pool hashrate just decrease your pool diff if thats an option. There is no reason to set these below 128 diff though.

Edit: nvm I see whats going on. They have a default diff of 128k (bfgminer diff 1 = 64k diff for scrypt), so yea these will take forever to submit a share at that diff. Seems like their diff logic is broken as well (setting d=512 as password does not work). Ill talk to them and see what I can do.