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 BEBFEE8D for ; Wed, 5 Sep 2018 13:06:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.wpsoftware.net (wpsoftware.net [96.53.77.134]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id EB42D7C7 for ; Wed, 5 Sep 2018 13:06:00 +0000 (UTC) Received: from boulet.lan (boulot.lan [192.168.0.193]) by mail.wpsoftware.net (Postfix) with ESMTPSA id EE2ED40102; Wed, 5 Sep 2018 13:05:58 +0000 (UTC) Date: Wed, 5 Sep 2018 13:05:59 +0000 From: Andrew Poelstra To: Erik Aronesty Message-ID: <20180905130559.GH18522@boulet.lan> References: <2e620d305c86f65cbff44b5fba548dc85c118f84.camel@timruffing.de> <20180812163734.GV499@boulet.lan> <20180903000518.GB18522@boulet.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="G44BJl3Aq1QbV/QL" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 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, 05 Sep 2018 13:43:33 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Schnorr signatures BIP 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, 05 Sep 2018 13:06:03 -0000 --G44BJl3Aq1QbV/QL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 05, 2018 at 08:26:14AM -0400, Erik Aronesty wrote: > Why would you call it FUD? All the weird hemming and hawing about it is > really strange to me. The more I look into it and speak to professors > about i, the more it seems "so trivial nobody really talks about it". >=20 > 1. Generate an M of N shared public key (done in advance of signing .... > this gets you the bitcoin address) > 2. Generate signature fragments (this can be done offline, with no > communication between participants) >=20 > Detailed explanation with code snippets: >=20 > https://medium.com/@simulx/an-m-of-n-bitcoin-multisig-scheme-e7860ab34e7f > The hemming and hawing is because you've been repeatedly told that your scheme doesn't work, and to please implement it in some computer algebra system so that you can see that (or so we can see where your mistake is), and you instead continue to post incomplete/incoherent copies of the same thing across multiple mediums - Reddit, this list, Bitcointalk, Medium, etc ad nauseum. It's distracting and offensive to people who have spent a lot of time and energy thinking about this stuff, and more importantly it causes confusion in the public eye. Phrasings like "weird hemming and hawing" suggest that we don't know/don't care about some insight you have, which is not true. This is why your posts are FUD. For example, in your linked post I looked at every single instance of the character 'k' and *not one of them* defined the value 'k' from which 'R' is derived in the signing procedure. Of course there is no possible value, individual signers cannot learn 'R' at signing time without interaction, and your whole scheme is broken. Given the number of times you've been told this, I find it hard to believe that this was an honest mistake. Andrew --=20 Andrew Poelstra Research Director, Mathematics Department, Blockstream Email: apoelstra at wpsoftware.net Web: https://www.wpsoftware.net/andrew "Make it stop, my love; we were wrong to try Never saw what we could unravel in traveling light Nor how the trip debrides like a stack of slides All we saw was that time is taller than space is wide" --Joanna Newsom --G44BJl3Aq1QbV/QL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJbj9S1AAoJEMWI1jzkG5fBmTkH/0vN30widsnIb828T61sbtx/ 1U2cTiI6tDYm7X9EXgusravwqGJ0JxLpsccm/f/M1ssFaQ2invlpZfQin73R3c7I 7Tckz1B6Rghnews/lKQ6VF5AvR1MkF4XHUj55WXy7k0CqhQbB1KYKwiWZDWhNXZW 4rVWNkN0eJ/l1wc4rgB2tH3mTrUuy2CUYV3sgQWA5KjD2BkTWyzmrqFFnO9rWatw sTJ9RWHlcrk4kWfd9Bis8Ne1K4FRlW3xxxW9gpJBBPBGqFPfgzxPsTOTEbMHptt5 y4fAX3dYNsuyRXu8mBSYzTiQZ0HwCwPvvKSwWJdhcCBXjtvl/FJKjvxuuh03YQo= =CEIz -----END PGP SIGNATURE----- --G44BJl3Aq1QbV/QL--