Ethash mining changes now available

Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Ethash mining changes now available

by Steve Sokolowski · · Post #28068

We're pleased to announce that the ethash mining changes, which we announced last week, have just been released.

The changes were created in response to customers who pointed out that because not all miners can mine all ethash coins anymore, due to vastly differing DAG sizes, miners who owned more capable graphics cards saw their profitability pulled down by miners who own less capable cards. We wanted to create a fairer algorithm so that all miners were compensated commensurate with their cards' computing power.

Now, there are two ethash algorithms: "ethash" and "Ethash-LowMemory." The second algorithm consists of coins that require DAG sizes of 4GB or less. The first algorithm contains coins with DAG sizes greater than 4GB. If you have a GPU with more than 4GB of memory, you can mine either algorithm, but miners with GPUs containing less memory won't be able to mine the "ethash" algorithm.

If you have a GPU with less memory and you started to encounter errors while mining, you can change to the "Ethash-LowMemory" algorithm to continue mining. Miners with more memory can mine the "ethash" algorithm, whose profitability is higher than it was before this change.

Feel free to submit a support ticket if you have any questions!
fjoe
Archived posts: 1
Joined: Mar 21, 2021

Re: Ethash mining changes now available

by fjoe · · Post #28077

Hi Steve,
I have a rig with six 4gb cards. So far I could mine ethash with around 15USD/day income (170mh). But after tha ethash mining change I can mine with ethash-lowmemory just around 4USD/day. Is there any system issues or is that all I can mine really with this method? Because the difference between the two amounts is too big.
gonzochaos
Archived posts: 1
Joined: Apr 13, 2021

Re: Ethash mining changes now available

by gonzochaos · · Post #28260

UPDATE: looks like it is back up and running now

Hello, I see that both algorithms should be active but i have lost connection with Ethash, the original and cannot seem to connect.. when i go to worker configuration page there is not port number listed. When will this be back up?

Thank you in advance
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Ethash mining changes now available

by Steve Sokolowski · · Post #28266

gonzochaos wrote: UPDATE: looks like it is back up and running now

Hello, I see that both algorithms should be active but i have lost connection with Ethash, the original and cannot seem to connect.. when i go to worker configuration page there is not port number listed. When will this be back up?

Thank you in advance
We're not aware of any port changes. The port for ethash is 3339, and the algorithm has an all-time high for hashrate at the moment. On which page are you not seeing a port number listed?
Steven Godshall avatar
Steven Godshall
Archived posts: 94
Joined: Mar 03, 2020

Re: Ethash mining changes now available

by Steven Godshall · · Post #28271

Steve Sokolowski wrote:
gonzochaos wrote: UPDATE: looks like it is back up and running now

Hello, I see that both algorithms should be active but i have lost connection with Ethash, the original and cannot seem to connect.. when i go to worker configuration page there is not port number listed. When will this be back up?

Thank you in advance
We're not aware of any port changes. The port for ethash is 3339, and the algorithm has an all-time high for hashrate at the moment. On which page are you not seeing a port number listed?
This was due to the ~15 minutes that Ethereum was offline for the Berlin Fork update yesterday.
animatenate avatar
animatenate
Archived posts: 1
Joined: Apr 30, 2021

Re: Ethash mining changes now available

by animatenate · · Post #28458

Using gminer2.54 on win10 I'm getting "invalid algorithm: Ethash-LowMemory" when trying to connect. Should I be using different software to mine eth-lowmemory? The standard Ethash algo is working fine for me.

EDIT: I saw another user that entered "ethash-lowmemory" as the algorithm as well as the "a=" password. Changed algo to "ethash" and it's fixed. Description on the site should clarify these are different so people don't get them confused. ;)