From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id C848CC002D for ; Thu, 4 Aug 2022 12:19:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 90CB741793 for ; Thu, 4 Aug 2022 12:19:07 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 90CB741793 Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=notatether.com header.i=@notatether.com header.a=rsa-sha256 header.s=protonmail header.b=ZrBNzOYH X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhTFQ2vUDBRK for ; Thu, 4 Aug 2022 12:19:04 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org EC67B409EA Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22]) by smtp4.osuosl.org (Postfix) with ESMTPS id EC67B409EA for ; Thu, 4 Aug 2022 12:19:02 +0000 (UTC) Date: Thu, 04 Aug 2022 12:18:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=notatether.com; s=protonmail; t=1659615540; x=1659874740; bh=L8uzgwV1FOWmaulUzbZgMK7o8hg8UucDdm6PbTIFA5k=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=ZrBNzOYHYdn1ID+OpiTA4ndEuNP0Z8nmpC8kIaB4Ifr1StAoAKmFDVpat45ejF02E lvYBXiq3dfWO42CpUAIF9FYpFrUpSZHyC8fv4Qnf6tOtp6PkCoRoQK9ZWWfVT3YUUO UO6qEnugTjYtMIERwEGdQnkI0rBkY4WUbCwgrXIQmgDxzb4h22pReT9swIsKxZrocc RJUyDyOSQYIQVAIWDJBdh4db7ESq+fccmCgNHTw9rlDEBie35xnFpuRKyWnF/JeA9t DYrw69Y1anKawZ0bRdbvRjhcDcyqSCJlotIyScZgDbCOS4NpTBwxBVq29lEZA4eGOW DVB+BJyRb7O7A== To: bitcoin-dev@lists.linuxfoundation.org From: Ali Sherief Reply-To: Ali Sherief Message-ID: <20220804121851.7e4zoqxaaolseazn@artanis> In-Reply-To: <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch> References: <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch> Feedback-ID: 34210769:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 04 Aug 2022 15:49:51 +0000 Cc: luke_bipeditor@dashjr.org Subject: [bitcoin-dev] BIP-notatether-signedmessage X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2022 12:19:07 -0000 Hi, I have created a new BIP, called notatether-signedmessage. It can be viewed= at https://github.com/ZenulAbidin/bips/blob/master/bip-notatether-signedme= ssage.mediawiki. For those who want a quick summary, it defines a step-by-step process for s= igning and verifying messages from legacy, native/nested segwit, and taproo= t addresses. It does not define a new signature format itself, except in th= e case of Taproot. For those addresses, I have defined a signature format t= hat has 1 byte header/recID, 64 bytes signature, and 32 bytes x coordinate = of a public key. This is required to run the BIP340 Schnorr verify algorith= m using only the signature - and the header byte is added for backwards com= patibility. Otherwise, it completely integrates BIP137 signatures. I am planning to move that format to its own BIP as soon as possible, in li= eu that it is unacceptable to define formats in an Informational BIP. Please leave your comments in this mailing list. CC'ing BIP editors. - Ali