Re: [Cfrg] Interest in an "Ed25519-HD" standard?

Aaron Zauner <> Wed, 22 March 2017 00:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1B68D13010D for <>; Tue, 21 Mar 2017 17:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cXtV1aFp6Sei for <>; Tue, 21 Mar 2017 17:25:06 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C15B5129412 for <>; Tue, 21 Mar 2017 17:25:05 -0700 (PDT)
Received: by with SMTP id n11so24135915wma.0 for <>; Tue, 21 Mar 2017 17:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gmail; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=V38Eo0HJqI9i3bQJJfOUxlAJmKys0ZItnBTLX3k/ZQc=; b=Ozw6RcIDlImxq7ZanQzEKijXDZsBx27t8vOO/b9fXTsFQxBwUevbSUXZ+AWKilRo8L v5v67GPnWzE8l7TpRTOFgMxgAyGAk7eTIM0QxrBWvr212s4r1b80+NprglfOoBF34mkJ IxP23WS8jlMk8jNKMyHOgq96jaoiKVxQWeZCg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=V38Eo0HJqI9i3bQJJfOUxlAJmKys0ZItnBTLX3k/ZQc=; b=hCnyLXWdJjxbulyA8tp5KCdEmULvQCJfed3czoNmYdxKgttSd0J5GadsLVW5uxQqNV zyQo35REqBPJNSvuN+B0HVRUPrTJDGROXQ7SAkMGvCKNhocvyojzSQgSReY5otuVAkf3 88H5t6dFB5euAyrD3xS4+oau/SLJimlkubLzGWoJS8x3tZM+QUYUgRyV9EBvGHnogsS+ IOQAKg3L/3dNWFfvfzuDyeZLuOPoHSM9G0QfpZJMxK6hV5qOKPohm37J+/gHdC1i04kJ BxSn9qmtAWZ9JrkT5kyowqiFKmi5XMzqW6FxDgf8BEe4KTsWcwCN4Du+mnkyktleKBf6 hVNw==
X-Gm-Message-State: AFeK/H0iMRe2lY3up06YgUi5KHXoSvYvppuKvwuOy0EKoCBr1d7vuRVoEJRfwFOf82cL1w==
X-Received: by with SMTP id z134mr5409316wmz.55.1490142304296; Tue, 21 Mar 2017 17:25:04 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id g5sm26698700wrb.48.2017. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 21 Mar 2017 17:25:03 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A4FBA875-381F-449E-9CCE-C0E43D51A686"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Aaron Zauner <>
In-Reply-To: <>
Date: Wed, 22 Mar 2017 01:24:27 +0100
Cc: "" <>
Message-Id: <>
References: <>
To: Tony Arcieri <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Subject: Re: [Cfrg] Interest in an "Ed25519-HD" standard?
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Crypto Forum Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Mar 2017 00:25:08 -0000


> On 21 Mar 2017, at 20:42, Tony Arcieri <> wrote:
> Hierarchical key derivation (also sometimes described as "semiprivate keys" or "key blinding") is an increasingly popular technique for generating unlinkable child keys from master public and private keys.
> The Tor Project has been exploring such an approach as the basis for their next-generation hidden services design for several years now[1], during which time it has received security proofs[2]. Their latest design[3] allegedly includes feedback from Dan Bernstein.
> Application of hierarchical key derivation is perhaps most notable in the cryptocurrency space, where Bitcoin's BIP32[4] provided a means for unlinkable single-use signature keys for the secp256k1 elliptic curve. There are several designs for applying the ideas from BIP32 to Ed25519, including ones from Evernym[5] and Chain[6] (where I am an employee).
> The designs in [3], [5], and [6] are all highly similar and accomplish the same goals. Personally I would love to see a single standard design for producing Ed25519 signatures from hierarchically derived keys, notably one which produces signatures that can be verified by any off-the-shelf RFC 8032-compatible Ed25519 implementation.
> There's already been some discussion of this on the curves list:
> I'd be curious to know if anyone else would be interested in collaborating on a draft for such a standard, which can be a synthesis of the existing work in this space.

I feel this is a useful input to CFRG and would be willing to review such a document. I think it's also a good idea if you talk to the original authors of the design documents you've linked to for collaboration.