From: Michael Perklin <mperklin@bitcoinsultants•ca>
To: bitcoin-development@lists•sourceforge.net
Cc: Eric Lombrozo <eric@ciphrex•com>
Subject: Re: [Bitcoin-development] Serialised P2SH HD chains
Date: Thu, 4 Dec 2014 15:40:12 -0500 [thread overview]
Message-ID: <C314D374-FD73-4997-9DCC-0386F807E494@bitcoinsultants.ca> (raw)
In-Reply-To: <mailman.473107.1417725057.2207.bitcoin-development@lists.sourceforge.net>
[-- Attachment #1.1: Type: text/plain, Size: 1688 bytes --]
Luke,
Eric Lombrozo is doing work similar to that. You may wish to connect.
He's building a BIP to standardize a multisig application of BIP32.
Like there are xprv and xpubs for single keychains, he is developing a similar construct that would embed all information necessary for a "multisig xpub" (total keychains in system, minimum # of keys required, and which derivation paths on each keychain are to be combined to make the resultant multisig wallet)
The result would be taking an xpub style string and piping it through a BIP32-like algorithm to pop off P2SH addresses in a deterministic order, just like BIP32 pops off standard addresses in deterministic order.
I will ping Eric to connect with you in case the both of you are working on something similar and you can help each other.
Michael Perklin
Bitcoinsultants Inc.
On Thu, Dec 4, 2014 at 7:42 AM, Luke Dashjr <luke@dashjr•org <mailto:luke@dashjr•org>> wrote:
> Is anyone working on a serialisation format to convey P2SH HD chains? For
> example, to give someone who wants to make recurring payments a single token
> that can be used to generate many P2SH addresses paying to a multisig script.
>
> I'm thinking of something along the lines of a simple series of tokens, each
> indicating either a HD chain or literal script content. For all HD chains in
> the data, a child key would be generated based on the payment number, and all
> tokens concatenated to form the P2SH serialised script. Eg, for a simple 2-
> of-2, you would do something like this:
> literal(OP_2) HDChain HDChain literal(OP_2 OP_CHECKMULTISIG)
> Does this sufficiently cover all reasonable use cases?
>
> Luke
[-- Attachment #1.2: Type: text/html, Size: 2840 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next parent reply other threads:[~2014-12-04 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.473107.1417725057.2207.bitcoin-development@lists.sourceforge.net>
2014-12-04 20:40 ` Michael Perklin [this message]
2014-12-04 15:42 Luke Dashjr
2014-12-04 16:46 ` Gavin Andresen
2014-12-04 17:25 ` William Swanson
2014-12-04 18:04 ` Mike Hearn
2014-12-04 20:02 ` Jeffrey Paul
2014-12-04 20:43 ` Peter Todd
2014-12-04 21:10 ` Luke Dashjr
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=C314D374-FD73-4997-9DCC-0386F807E494@bitcoinsultants.ca \
--to=mperklin@bitcoinsultants$(echo .)ca \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=eric@ciphrex$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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