MIME-Version: 1.0
From: Omer Shlomovits <omer.shlomovits@gmail.com>
Date: Tue, 27 Nov 2018 19:52:51 +0200
Message-ID: <CALhDas2W5QEPmw8JEgak0zf7y3N0UFTiMVk-djR8x9_WYZiyfQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="000000000000f2a6fa057ba91eea"
Cc: Gary Benattar <g.benattar@gmail.com>, elichai.turkel@gmail.com,
	Roman Zeyde <mail@romanzey.de>, Morten Dahl <mortendahlcs@gmail.com>
Subject: [bitcoin-dev] Multi party Schnorr Rust implementation
Precedence: list

--000000000000f2a6fa057ba91eea
Content-Type: text/plain; charset="UTF-8"

Hello all,

I am working for the past few months with collaborators (in cc) on
providing Rust reference implementations to existing multi party schemes
for Schnorr signatures [1]. This includes aggregated signatures,
accountable signatures (which for n out of n are multi-signatures) and
threshold signatures (wip).
The project can be found here:
https://github.com/KZen-networks/multi-party-schnorr .
We aim that if the protocol is run in a configuration of a single party it
will be bip-schnorr [2] compliant.

Hope you'll find it useful :)
Questions, suggestions and pull requests are welcome!


[1] https://github.com/KZen-networks/multi-party-schnorr/tree/master/papers
[2] https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki

--000000000000f2a6fa057ba91eea
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hello a=
ll,<div><br></div><div>I am working for the past few months with collaborat=
ors (in cc) on providing Rust reference implementations to existing multi p=
arty schemes for Schnorr signatures [1]. This includes aggregated signature=
s, accountable signatures (which for n out of n are multi-signatures) and t=
hreshold signatures (wip).=C2=A0</div><div>The project can be found here:=
=C2=A0<a href=3D"https://github.com/KZen-networks/multi-party-schnorr">http=
s://github.com/KZen-networks/multi-party-schnorr</a> .=C2=A0</div><div>We a=
im that if the protocol is run in a configuration of a single party it will=
 be bip-schnorr [2] compliant.=C2=A0</div><div><br></div><div><font face=3D=
"arial, helvetica, sans-serif"><span style=3D"color:rgb(0,0,0)">Hope you=
9;ll find it useful :)</span><br style=3D"color:rgb(0,0,0)"><span style=3D"=
color:rgb(0,0,0)">Questions, suggestions and pull requests are welcome!</sp=
an></font><br></div><div><br></div><div><br></div><div>[1]=C2=A0<a href=3D"=
https://github.com/KZen-networks/multi-party-schnorr/tree/master/papers">ht=
tps://github.com/KZen-networks/multi-party-schnorr/tree/master/papers</a></=
div><div>[2]=C2=A0<a href=3D"https://github.com/sipa/bips/blob/bip-schnorr/=
bip-schnorr.mediawiki">https://github.com/sipa/bips/blob/bip-schnorr/bip-sc=
hnorr.mediawiki</a></div></div></div></div></div>

--000000000000f2a6fa057ba91eea--