From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to P2SH multisig
Date: Sun, 14 Apr 2013 05:26:37 +0000 [thread overview]
Message-ID: <201304140526.38940.luke@dashjr.org> (raw)
In-Reply-To: <20130414050958.GA11142@savin>
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
next prev parent reply other threads:[~2013-04-14 5:26 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 [this message]
2013-04-14 6:29 ` Peter Todd
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=201304140526.38940.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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