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; 
Date: Sun, 14 Apr 2013 02:29:39 -0400
From: Peter Todd <pete@petertodd.org>
To: Luke-Jr <luke@dashjr.org>
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)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to
 P2SH multisig
Precedence: list


--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--