4 ms·
Instead of "deliberately", you might as well say "necessarily". As I argue in [1], "in order to keep verification cheap, hash functions in Hashcash must restri
by tromp 10y ago
Instead of "deliberately", you might as well say "necessarily".
As I argue in [1], "in order to keep verification cheap, hash functions in Hashcash must restrict their resource usage as well. That’s why scrypt is configured to use only 128KB of memory."
To achieve ASIC-resistance, one should avoid Hashcash in favor of asymmetric proof of work systems, where proof attempts can take huge amounts of memory even while verification is instant and memory less.
[1] http://cryptorials.io/beyond-hashcash-proof-work-theres-mining-hashing/ http://cryptorials.io/beyond-hashcash-proof-work-theres-mini...
- cperciva 10y agoRight. Cryptocoins' need for cheap verification of proofs-of-work is precisely opposed to KDFs' need for expensive checking of candidate passwords.
- Dylan16807 10y agoI think they overcorrected. They want it to run on a phone, fine, but a phone app can easily dedicate 100MB of ram to verifying blocks.