Equihash is a memory-hard Proof-of-work algorithm introduced by the University of Luxembourg's Interdisciplinary Centre for Security, Reliability and Trust (SnT) at the 2016 Network and Distributed System Security Symposium. The algorithm is based on a generalization of the Birthday problem which finds colliding hash values. It has severe time-space trade-offs but concedes vulnerability to unforeseen parallel optimizations. It was designed such that parallel implementations are bottle-necked by memory bandwidth in an attempt to worsen the cost-performance trade-offs of designing custom ASIC implementations. ASIC resistance in Equihash is based on the assumption that commercially-sold hardware already has quite high memory bandwidth, so improvements made by custom hardware may not be worth the development cost.[citation needed]

## General

Equihash was proposed by Alex Biryukov and Dmitry Khovratovich as part of the University of Luxembourg research group CryptoLUX. It was introduced at the Network and Distributed System Security Symposium 2016 in San Diego. Notable blockchain-based projects such as ZCash, BitcoinZ, Horizen, Aion, Hush, and Pirate Chain have integrated Equihash for reasons such as security, privacy, and ASIC miner resistance.[citation needed]

The manufacturer Bitmain has succeeded in optimizing the processing of Zcash's Equihash-200,9 with an ASIC.

## Specification

Equihash has three parameters – $n$ , $k$ , and $d$ – which determine the algorithm's time and memory requirements. The time complexity is proportional to $2^((\frac {n}{k+1))+d)$ while the memory complexity is proportional to $2^{k+{\frac {n}{k+1)))$ . The algorithm is often implemented with $d=0$ (using an alternative method of controlling the effective difficulty).[citation needed]

The problem in Equihash is to find distinct, $n$ -bit values $i_{1},i_{2},...,i_{2^{k))$ to satisfy $H(i_{1})\oplus H(i_{2})\,\oplus \,...\,\oplus \,H(i_{2^{k)))=0$ such that $H(i_{1}\parallel i_{2}\parallel \,...\,\parallel i_{2^{k)))$ has $d$ leading zeros, where $H$ is a chosen hash function. In addition, there are "algorithm binding conditions" which are intended to reduce the risk of other algorithms developed to solve the underlying birthday problem being applicable. A memory-less verification requires $2^{k)$ hashes and XORs.[citation needed]

It is proposed that the puzzle in Equihash be solved by a variation of Wagner's algorithm for the generalized birthday problem. (Note that the underlying problem is not exactly the Generalized Birthday Problem as defined by Wagner, since it uses a single list rather than multiple lists.) The proposed algorithm makes $k$ iterations over a large list. For every factor of ${\frac {1}{q))$ fewer entries per list, computational complexity of the algorithm scales proportional to $q^{\frac {k}{2))$ for memory-efficient implementations. Alcock and Ren refute Equihash’s security claims, concluding that no tradeoff-resistance bound is in fact known for Equihash.

## Usage

This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (February 2021) (Learn how and when to remove this template message)

The cryptocurrency Zcash implements Equihash with $n=200$ and $k=9$ .

The cryptocurrency BitcoinGold implements Equihash with $n=144$ and $k=5$ .