From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Sun, 14 Apr 2013 05:26:37 +0000
User-Agent: KMail/1.13.7 (Linux/3.7.8-gentoo; KDE/4.10.1; x86_64; ; )
References: <20130414050958.GA11142@savin>
In-Reply-To: <20130414050958.GA11142@savin>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201304140526.38940.luke@dashjr.org>
Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to
	P2SH multisig
Precedence: list

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.

I think it would be wise to figure out HD wallet changes before trying to 
extend message signing. For privacy/safety, it would be a good idea to avoid 
signing with the same private key twice under any circumstances, so it might 
make sense to create a new address format the represent a chain of keys 
instead of one key or combination of keys.

Luke