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 D38D0415 for ; Mon, 15 Apr 2019 02:59:55 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1BC3C1C0 for ; Mon, 15 Apr 2019 02:59:54 +0000 (UTC) Date: Mon, 15 Apr 2019 02:59:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1555297192; bh=xroD9VpCIC36ccElmT4/dpQ+MhlY+XAOo4CHYhUgRWI=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:Feedback-ID: From; b=aLmosgkt5zI23BUunluA2eJtL7Cf57mDYshTHhdL+G8nyhyNJhOq8U75PEGgQE4h6 8LVDxH9wSMGeTCBnOucSEsgSB63lzqf7bBW9f9C25/jXTw2Z37ru01IqpMIJ8HAFH1 3soF67t2BGef7S4AzU/HE7PLkZ7F1TBRlVcHnE5Q= To: LORD HIS EXCELLENCY JAMES HRMH , Bitcoin Protocol Discussion From: ZmnSCPxj Reply-To: ZmnSCPxj Message-ID: In-Reply-To: References: Feedback-ID: el4j0RWPRERue64lIQeq9Y2FP-mdB86tFqjmrJyEPR9VAtMovPEo9tvgA0CrTsSHJeeyPXqnoAu6DN-R04uJUg==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, FROM_LOCAL_NOVOWEL, RCVD_IN_DNSWL_LOW 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: Mon, 15 Apr 2019 03:06:48 +0000 Subject: Re: [bitcoin-dev] List of proposals for hard fork/soft fork 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: Mon, 15 Apr 2019 02:59:55 -0000 Good morning LORD YOUR EXCELLENCY, May it please you to be informed the below are likely to be included in som= e kind of upcoming softfork for SegWit v1: 1. Schnorr signatures. 2. MuSig. 3. Taproot. 4. `SIGHASH_NOINPUT`. 5. Signature aggregation. May it please you to be informed, that "Schnorr= " enables signature aggregation, but is not signature aggregation itself. 6. MAST. The above may or may not be an exhaustive list, your excellency. Of these, I believe only `SIGHASH_NOINPUT` has a BIP, may it please your ex= cellency to learn that it is BIP 118. However, I am sorry to inform your excellency, as I understand the `SIGHASH= _NOINPUT` that will eventually reach Bitcoin Core will not match the curren= t version of BIP118. To improve on the possibility of incorrect use of `SIGHASH_NOINPUT`, it is = proposed that every input that is signed with a `SIGHASH_NOINPUT` signature= additionally require a signature without `SIGHASH_NOINPUT`. For other details, I am sorry to inform your excellency, I have no reliable= knowledge. Regards, ZmnSCPxj Sent with ProtonMail Secure Email. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Sunday, April 14, 2019 10:44 PM, LORD HIS EXCELLENCY JAMES HRMH via bitc= oin-dev wrote: > Is anybody keeping a list of the solid proposals > BIP's to be included i= n any actual future consensus-driven fork? Perhaps pre-consensus voting of = what to include in the fork packages? > > Surely not every or each proposal ever scouted is on for consideration. > > This may actually help to build momentum for useful and valuable implemen= tations that may otherwise languish. > > Regards, > LORD HIS EXCELLENCY JAMES HRMH