Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.182 as permitted sender)
	client-ip=209.85.223.182; envelope-from=melvincarvalho@gmail.com;
	helo=mail-ie0-f182.google.com; 
MIME-Version: 1.0
Date: Sun, 15 Dec 2013 19:09:59 +0100
Message-ID: <CAKaEYh+=cFKzwW7J9j6Bz4P6OxTC56k3K1fFG4svg843QRTjVA@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: public-webcrypto-comments@w3.org
Content-Type: multipart/alternative; boundary=089e013c68e27e64e304ed969a89
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Web Crypto -- Named Curve Dictionary (adding
	secp256k1)
Precedence: list

--089e013c68e27e64e304ed969a89
Content-Type: text/plain; charset=ISO-8859-1

Harry and David suggested I send a message to this group.  I was wondering
if the crypto group may consider adding support for *secp256k1* in the
browser Named Curve dictionary.

http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary

enum NamedCurve {
  // NIST recommended curve P-256, also known as secp256r1.
  "P-256",
  // NIST recommended curve P-384, also known as secp384r1.
  "P-384",
  // NIST recommended curve P-521, also known as secp521r1.
  "P-521"
};

Over the last year, there has been a significant increase in deployment for
this curve.  It's used in bitcoin and many other crypto currencies.
Bitcoin deployment now numbers in the millions of users and hundreds of
companies.  There are also free software implementations in most
languages.

For more background on Koblitz curve used by bitcoin see:

https://bitcointalk.org/?topic=2699.0

I'm aware that the API tends to expose what's existing in NSS, but, imho,
if it were possible to add support for this curve would be a great step to
help to many people that already work with crypto currencies in the browser.

--089e013c68e27e64e304ed969a89
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Harry and David suggested I send a message to this gr=
oup.=A0 I was wondering if the crypto group may consider adding support for=
 <b>secp256k1</b>
 in the browser Named Curve dictionary.=A0 <br><br></div><a href=3D"http://=
www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary" target=3D"_blank">ht=
tp://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary</a><br>
<br>enum NamedCurve {<br>=A0 // NIST recommended curve P-256, also known as=
 secp256r1.<br>=A0 &quot;P-256&quot;,<br>=A0 // NIST recommended curve P-38=
4, also known as secp384r1.<br>=A0 &quot;P-384&quot;,<br>
=A0 // NIST recommended curve P-521, also known as secp521r1.<br>=A0 &quot;=
P-521&quot;<br>};<br><br>Over the last year, there has been a significant i=
ncrease in deployment for this curve.=A0 It&#39;s used in bitcoin and many =
other crypto currencies.=A0 Bitcoin deployment now numbers in the millions =
of users and hundreds of companies.=A0 There are also free software impleme=
ntations in most languages.=A0 <br>
<div><div><div><div><div><div><br></div>For more background on <span>Koblit=
z</span> curve used by bitcoin see:<br>
<br><a href=3D"https://bitcointalk.org/?topic=3D2699.0" target=3D"_blank">h=
ttps://bitcointalk.org/?topic=3D2699.0</a><br><br></div>I&#39;m aware that =
the API tends to expose what&#39;s existing in NSS, but, imho, if it were p=
ossible to add support for this curve would be a great step to help to many=
 people that already work with crypto currencies in the browser.</div>
</div></div></div></div>

--089e013c68e27e64e304ed969a89--