Equihash

From testwiki
Revision as of 19:36, 15 November 2024 by imported>TravellerEntity (Citations in Specification)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:Short description 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.[1] 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.Template: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.Template:Citation needed

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

Specification

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

The problem in Equihash is to find distinct, n-bit values i1,i2,...,i2k to satisfy H(i1)H(i2)...H(i2k)=0 such that H(i1i2...i2k) has d leading zeros, where H is a chosen hash function.[1] 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 2khashes and XORs.[1]

Memory-hardness and time-space tradeoffs

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.[1][3] For every factor of 1q fewer entries per list, computational complexity of the algorithm scales proportional to qk2 for memory-efficient implementations. Alcock and Ren[4] refute Equihash’s security claims, concluding that no tradeoff-resistance bound is in fact known for Equihash.

Usage

Template:Uncited section The cryptocurrency Zcash implements Equihash with n=200 and k=9.

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

See also

References

Template:Reflist

Template:Cryptography navbox Template:Cryptocurrencies Template:Portalbar Template:Authority control