From 170352eb5ce60d4157344405a30d7e6d219553d3 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Sun, 17 Jul 2011 04:15:31 +0000
Subject: [PATCH] =?UTF-8?q?add=20link=20to=20Julian=20W=C3=A4lde's=20imple?=
 =?UTF-8?q?mentation?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

[Imported from Trac: page OneHundredYearCryptography, version 12]
---
 OneHundredYearCryptography.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/OneHundredYearCryptography.md b/OneHundredYearCryptography.md
index c902f43..65b2ada 100644
--- a/OneHundredYearCryptography.md
+++ b/OneHundredYearCryptography.md
@@ -29,6 +29,8 @@ David-Sarah has proposed to use hash-based digital signatures.
  * <http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004509.html>
  * <http://tahoe-lafs.org/pipermail/tahoe-dev/2010-July/004587.html>
 
+Julian Wälde has posted an actual implementation of hash-based digital signatures! <http://tahoe-lafs.org/pipermail/tahoe-dev/2011-March/006237.html>
+
 Brian and David-Sarah wrote [a simulator]source:trunk/misc/simulators/hashbasedsig.py or two to explore performance trade-offs in hash-based signature parameters. The output of one run with the following parameters is this:
 ```
 # range of hash output lengths