Releasing Ethash and Neoscrypt today

sirslayerjr wrote:what ate the address and port on the neoscrypt mining ??

https://prohashing.com/help.html

Hi Guys,

I tried an Antminer E3 and it seems it can't authenticate itself on the server. Likely due to Bitmain adding their worker name.
Below line from the bmminer.log (which repeats every 5 seconds until I pull the plug).

[2018-09-05 09:36:32] (02709)->[auth_stratum_eth]: Will Use Worker Name!->'003FCAE3ABA1'

I doubt we'll get that one running giving Bitmains funny implementation of things, but just for info as somebody else may try and there ain't much wisdom about the E3 out there.

JJ

jaegersb wrote:Hi Guys,

I tried an Antminer E3 and it seems it can't authenticate itself on the server. Likely due to Bitmain adding their worker name.
Below line from the bmminer.log (which repeats every 5 seconds until I pull the plug).

[2018-09-05 09:36:32] (02709)->[auth_stratum_eth]: Will Use Worker Name!->'003FCAE3ABA1'

I doubt we'll get that one running giving Bitmains funny implementation of things, but just for info as somebody else may try and there ain't much wisdom about the E3 out there.

JJ

have you tried ssh'ing on to the unit and editing the .conf for bmminer?

jaegersb wrote:Hi Guys,

I tried an Antminer E3 and it seems it can't authenticate itself on the server. Likely due to Bitmain adding their worker name.
Below line from the bmminer.log (which repeats every 5 seconds until I pull the plug).

[2018-09-05 09:36:32] (02709)->[auth_stratum_eth]: Will Use Worker Name!->'003FCAE3ABA1'

I doubt we'll get that one running giving Bitmains funny implementation of things, but just for info as somebody else may try and there ain't much wisdom about the E3 out there.

JJ

A few tickets have come in about this, but I'm having trouble figuring out exactly what these miners are doing to the username without owning one myself. As far as I can tell, the miners themselves are fully supported if the correct username can be entered.

How do these work at other pools? Don't they require usernames too, so they know who the money should be paid to?

djliss wrote:

jaegersb wrote:Hi Guys,

I tried an Antminer E3 and it seems it can't authenticate itself on the server. Likely due to Bitmain adding their worker name.
Below line from the bmminer.log (which repeats every 5 seconds until I pull the plug).

[2018-09-05 09:36:32] (02709)->[auth_stratum_eth]: Will Use Worker Name!->'003FCAE3ABA1'

I doubt we'll get that one running giving Bitmains funny implementation of things, but just for info as somebody else may try and there ain't much wisdom about the E3 out there.

JJ

have you tried ssh'ing on to the unit and editing the .conf for bmminer?

Hi,

I did, but the bmminer.conf does not have the '003FCAE3ABA1' in it, so I can't delete it.
"url" : "prohashing.com:3339",
"user" : "jaegersb",
"pass" : "w=800 p=0.26"

In the GUI it shows it as one string "w=800 p=0.26#jaegersb.003FCAE3ABA1" adding that identifier and claims the pool to be dead.
I'll google around to see if there is a way to chop that part, but as said, there is little useful written about E3s on the web.

Steve Sokolowski wrote:

jaegersb wrote:Hi Guys,

I tried an Antminer E3 and it seems it can't authenticate itself on the server. Likely due to Bitmain adding their worker name.
Below line from the bmminer.log (which repeats every 5 seconds until I pull the plug).

[2018-09-05 09:36:32] (02709)->[auth_stratum_eth]: Will Use Worker Name!->'003FCAE3ABA1'

I doubt we'll get that one running giving Bitmains funny implementation of things, but just for info as somebody else may try and there ain't much wisdom about the E3 out there.

JJ

A few tickets have come in about this, but I'm having trouble figuring out exactly what these miners are doing to the username without owning one myself. As far as I can tell, the miners themselves are fully supported if the correct username can be entered.

How do these work at other pools? Don't they require usernames too, so they know who the money should be paid to?

Ethermine (with wallet address) work without issue (it makes the 003... the worker-id, but payout in the wallet is unaffected).
Miningpoolhub (with username) has a different port for the E3 on which it runs without issues.
Nicehash stratum can't be resolved, I assume some issue there as over here.

I'll see if I can find something on the interweb and let you know.

could we create another account just for the our e3s and add 003FCAE3ABA1 or whatever our own e3 is adding to our user name to make a connection?

Will the E3 asic connect for ethash? I tried but it states connection refused.. Thanks

Critters wrote:Will the E3 asic connect for ethash? I tried but it states connection refused.. Thanks

No. There is a problem with that miner where some random characters get added to the username field. We're still not sure how that miner works with any pool, not just ours, because how can a miner be credited if a pool doesn't know the username?

If you come across a solution for this issue, please share it with everyone!

hello, i have checked my miners as they report lower hash rate as they currently have and found it could be cause by switching coins too often. my rig found two shares and then switch other coin, then find another one share and again switch. let me explain. for example i have 9 GPU rig hashing 268Mhs howewer it shows on web page only 229Mhs, which is 14-15% less,which leads to less revenue. i understand there could be some stale share or orphaned,etc, so i understand 5% less,so is possible to switch coins in longer periods?
curently i havepointed here 790Mhs and it is showing only 612Mhs on webpage, thats like 1 whole rig.