From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 515796C for ; Wed, 28 Nov 2018 06:33:44 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BF72519B for ; Wed, 28 Nov 2018 06:33:43 +0000 (UTC) Received: by mail-qt1-f181.google.com with SMTP id n21so24689028qtl.6 for ; Tue, 27 Nov 2018 22:33:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=H/MfLQT/V50lcTgjj3fq2oxk0qXpUAir42smZ+780eU=; b=ZZO9xWXfxENsZ/gHYDYeq2+IkEDh6RXiFnyMenl+Q/aFMZsPNvJw3eMRlJhxlgd738 UCG+SmH1+cUWSSdriMqZhakBh9GKDSkp/T1tRxHkVb5Bvatp2Sidsl/UX4JMKB9reOxH XZqCoEj59THAGa47G6aFhJUBipxC6MuIUHqD307VK4CaRQYgUVCyWur9O0LPZpJu5a45 0iqE7Mudx/+of9pt/mY/jCIkR1AsIvcbiFzkUBiSJD1VNk0qfsJVRN/GGX8SoScZWnlc 6a7FL65wJHo+gvIM/UpswzX6gwddUoL1d+g/ySSCLKL7PyrFKGiKASagYFIfLJPCcmyG cqrg== X-Gm-Message-State: AA+aEWapS6Sb1IU3UprJmV3ZhZYMNNh+RVBAnDtUS0JdUn1n3xaCyc/9 w1xAHMB0We30PEYaLfYopknhjy7tNkN3TnP69i5bSw== X-Google-Smtp-Source: AFSGD/WPJh4W8e29NG9mln0L6kgG5wq/W3eQye0wh8j6+e/2ZTFWMsyjrdnVuyLSJKj/uJ3GW2fNukamuiwwjUMqEmY= X-Received: by 2002:a0c:d6c4:: with SMTP id l4mr34769087qvi.103.1543386822598; Tue, 27 Nov 2018 22:33:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Devrandom Date: Tue, 27 Nov 2018 22:33:30 -0800 Message-ID: To: omer.shlomovits@gmail.com, Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000004ffaaa057bb3bfc2" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Wed, 28 Nov 2018 06:47:43 +0000 Cc: g.benattar@gmail.com, elichai.turkel@gmail.com, mail@romanzey.de, mortendahlcs@gmail.com Subject: Re: [bitcoin-dev] Multi party Schnorr Rust implementation X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2018 06:33:44 -0000 --0000000000004ffaaa057bb3bfc2 Content-Type: text/plain; charset="UTF-8" Hi Omer, Are there any candidates for non-interactive threshold signatures? Interactive signatures are not very suitable for air-gapped use cases. On Tue, Nov 27, 2018 at 11:18 AM Omer Shlomovits via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --0000000000004ffaaa057bb3bfc2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Omer,

Are there any candidates= for non-interactive threshold signatures?=C2=A0 Interactive signatures are= not very suitable for air-gapped use cases.

On Tue, Nov 27, 2018 at 11:18 AM Omer Shlomovits via b= itcoin-dev <bit= coin-dev@lists.linuxfoundation.org> wrote:
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 aggr= egated signatures, accountable signatures (which for n out of n are multi-s= ignatures) and threshold signatures (wip).=C2=A0
The project can = be found here:=C2=A0https://github.com/KZen-networks/multi-party-sc= hnorr .=C2=A0
We aim that if the protocol is run in a configu= ration of a single party it will be bip-schnorr [2] compliant.=C2=A0
<= div>
Hope you'll find it useful :)
Questions, suggestions a= nd pull requests are welcome!

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--0000000000004ffaaa057bb3bfc2--