public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to P2SH multisig
Date: Sun, 14 Apr 2013 02:29:39 -0400	[thread overview]
Message-ID: <20130414062939.GB3310@savin> (raw)
In-Reply-To: <201304140526.38940.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

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

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.

-- 
'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2013-04-14  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14  5:09 [Bitcoin-development] RFC: extend signmessage/verifymessage to P2SH multisig Peter Todd
2013-04-14  5:21 ` Alan Reiner
2013-04-14  6:25   ` Peter Todd
2013-04-14 18:24     ` Alan Reiner
2013-04-14  5:26 ` Luke-Jr
2013-04-14  6:29   ` Peter Todd [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130414062939.GB3310@savin \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox