From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1URGSJ-0001Pq-1o for bitcoin-development@lists.sourceforge.net; Sun, 14 Apr 2013 06:30:27 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.80 as permitted sender) client-ip=62.13.149.80; envelope-from=pete@petertodd.org; helo=outmail149080.authsmtp.com; Received: from outmail149080.authsmtp.com ([62.13.149.80]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1URGSF-0002yo-BV for bitcoin-development@lists.sourceforge.net; Sun, 14 Apr 2013 06:30:27 +0000 Received: from mail-c226.authsmtp.com (mail-c226.authsmtp.com [62.13.128.226]) by punt10.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id r3E6UErg067746; Sun, 14 Apr 2013 07:30:14 +0100 (BST) Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r3E6U9fK022770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 14 Apr 2013 07:30:11 +0100 (BST) Date: Sun, 14 Apr 2013 02:29:39 -0400 From: Peter Todd To: Luke-Jr Message-ID: <20130414062939.GB3310@savin> References: <20130414050958.GA11142@savin> <201304140526.38940.luke@dashjr.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="neYutvxvOLaeuPCA" Content-Disposition: inline In-Reply-To: <201304140526.38940.luke@dashjr.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: c2ceb1e9-a4cc-11e2-98a9-0025907ec6c5 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdwYUGUUGAgsB AmUbW1NeU117WGE7 bAxPbAVDY01GQQRq WVdMSlVNFUsqAmkH YxdIKRlwdQJBeDB3 ZUNkECNZDxEodBN0 Xx9QRj4bZGY1an0W WBFRagNUcgZDfhgQ OVYsUT1vNG8XDQg5 AwQ0PjZ0MThBJSBS WgQAK04nCXwlNWx0 SgAeEDMjVVYESCM2 Igc9I1ERW1gcKEQ8 IF4sQkkRPBJaFgo8 V3kXOw8RIkQFWysw DAwy X-Authentic-SMTP: 61633532353630.1020:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.178.109/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1URGSF-0002yo-BV Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to P2SH multisig X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 06:30:27 -0000 --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 14, 2013 at 05:26:37AM +0000, Luke-Jr wrote: > On Sunday, April 14, 2013 5:09:58 AM Peter Todd wrote: > > Currently signmessage/verifymessage only supports messages signed by a > > single key. We should extend that to messages signed by n-of-m keys, or > > from the users point of view, P2SH multisig addresses. >=20 > I think it would be wise to figure out HD wallet changes before trying to= =20 > extend message signing. For privacy/safety, it would be a good idea to av= oid=20 > signing with the same private key twice under any circumstances, so it mi= ght=20 > make sense to create a new address format the represent a chain of keys= =20 > instead of one key or combination of keys. Sure, which is why I have the header byte so that when we do come up with a chain of keys thing, that in turn can get it's own magic number allocated. FWIW I have an application now where a multisig signmessage would be useful. --=20 'peter'[:-1]@petertodd.org --neYutvxvOLaeuPCA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJRakzSAAoJEH+rEUJn5PoEY1kIAJfrlW2YugiH99JV8VMMDyBO 8mV3eO9OCN4gIvEUk52MFWPR6d5qNnYpBNNvwRjgxC3l4K4yCAViE50+kPQOe3In 0C1PZV6Vk8bacAicA2MvQxK+7gilN7M5SZDComPMYTNYTzC+c28Es4yVLYIJJ3xh /NRZ7Q30wNspUkMhLczTboV3Bmd+krablxSKOflkJzPbX3JgiQctbuxgA4M3iA46 6/gC9zNoLQ7vIatT3xu4IQK4OD1kDYYohai4lVSPZ276mMpnNuKQYJdwiEmXhaVN NT4LcizsHJrHyaAs5j/7ZCaO+rKyLLYd/Moyef+JFmPVX5TugxkmV9q93q6lQQk= =Sl0F -----END PGP SIGNATURE----- --neYutvxvOLaeuPCA--