Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to P2SH multisig
On Sun, Apr 14, 2013 at 01:21:21AM -0400, Alan Reiner wrote: If we're going to extend/expand message signing, can we please add a proper ASCII-armored format for it? Really, anything that encodes the signed message next to the signature, so that there's no ambiguities about what was signed. You can keep the bare signatures as an option for backwards compatiblity, but offer this as the primary one. What we really want is to have the user copy an ASCII-armored block of text into the client (or we could have a URI-extension for this), and the app pops up with a window that says The following message has a valid signature from address 1XKjf32kJbf...: message. I already looked into ASCII-armoring PGP style for a different project. (timestamping) Basically you'd want to follow RFC2440, section 7 Cleartext signature framework: -BEGIN BTC SIGNED MESSAGE- Hello world! -BEGIN BTC SIGNATURE- IKBeCbxXHvD1TJh8ZlMySo26w5z6YZQD1xqKgbhsvlhEgcFD+kvKx4LzUz1yxg/8 IdYdBnzez77VDq3odHrVftg= -END BTC SIGNATURE- Pretty simple really and doesn't need to be done prior to other signmessage changes. There may be an issue passing \r's through the RPC interface; the RFC specifies CRLF line endings. -- 'peter'[:-1]@petertodd.org signature.asc Description: Digital signature -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] RFC: extend signmessage/verifymessage to P2SH multisig
On Sun, Apr 14, 2013 at 05:26:37AM +, 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 signature.asc Description: Digital signature -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
