(Explanation of terms below the charts.)
Approximate Equihash Minimum VRAM requirements
|Params||Min VRAM||Standard Name?|
|96, 5||2.5 MB||—|
|200, 9||144 MB||Equihash (Classic?)|
|210, 9||288 MB||Equihash 210_9|
|144,5||2.0 GB||Equihash (Zhash?)|
|192,7||2.5 GB||Equihash Zero (Heavy?)|
List of known coins and implementations
|Coin||Coin Name||Params||Pers String||Algo Name Used||Notes|
|MNX||MinexCoin||96, 5||—||Equihash 96/5*|
|BCI||Bitcoin Interest||200, 9||ZcashPoW||Equihash|
|AION||Aion||210, 9||—||Equihash 210_9|
|BTG||Bitcoin Gold||144,5||BgoldPoW||Equihash-BTG||Effective 2018-7-3|
|SAFE||Safecoin||144,5||Safecoin||Equihash 144,5||Effective 2018-6-18|
|ZER||Zero||192, 7||ZERO_PoW||Equihash 192_7|
Grouped by Params in Min VRAM order; groups sorted alphabetically by Coin.
Equihash provides for the following Parameters: (n, k)
For example, the classic Equihash first used by Zcash used n = 200 and k = 9, so it was Equihash (200, 9).
The n and k values create enormous differences in the minimum memory requirement, and create enormous differences in how the actual mining software is coded in order to do the mining.
The minimum amount of memory necessary for efficient mining; having less than this would require laboriously recalculating values that could be otherwise stored and quickly referenced over and over.
Equihash provides for a Personalization String. The classic Equihash first used by Zcash used ZcashPoW as the string.
An attempt to identify a common name for the given Params.
Algo Name Used:
The name used by the coin team.
There’s some confusion and naming concerns due to the growth in adoption of the Equihash algorithm for PoW (Proof of Work) mining with various implementation parameters. These parameters make an enormous difference in the code for the mining software as well as the validation code for pools and wallets.
Many coins adopted the Equihash algorithm after Zcash, and to maintain easy compatibility in the software, many adopted the same Parameters and Pers as Zcash. In the chart above, we refer to this combination of Params and Pers as “Classic.”
Because of concerns over safety and the intrusion of ASICs in the space, many coins have switched to different parameters, and have made unique Personalization Strings.
This page has been created to help track and differentiate among them and to help the community reach some sort of agreement on what “common names” to use for these variants.