Context Navigation

Changes between Version 17 and Version 18 of OneHundredYearCryptography

Timestamp:: 2012-02-11T04:50:28Z (13 years ago)
Author:: zooko
Comment:: Julian's implementation meet's Zooko's performance criteria! (now with links)

v17	v18
32	32	Zooko posted [https://tahoe-lafs.org/pipermail/tahoe-dev/2011-February/006133.html "back of the envelope" performance constraints]. Bottom-line: you get 30 million ARM instructions to implement one complete digital signature verification.
33	33
34		Julian Wälde has [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-March/006237.html posted an actual implementation] of (stateful) hash-based digital signatures! Exciting fact: his implementation ~~meets Zooko's performance criterion~~!
	34	Julian Wälde has [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-March/006237.html posted an actual implementation] of (stateful) hash-based digital signatures! Exciting fact: his implementation [//pipermail/tahoe-dev/2011-July/006554.html meets] Zooko's [//pipermail/tahoe-dev/2011-February/006133.html performance criteria]!
35	35
36	36	Brian and David-Sarah wrote [source:trunk/misc/simulators/hashbasedsig.py a simulator] or two to explore performance trade-offs in (stateless) hash-based signature parameters. The output of one run with the following parameters is this (note that the signing times include regeneration of per-message signing keys from a small long-term private key):