1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mperklin@bitcoinsultants.ca>) id 1XwdCP-0004ui-D3
for bitcoin-development@lists.sourceforge.net;
Thu, 04 Dec 2014 20:40:29 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of
bitcoinsultants.ca designates 204.16.202.179 as permitted
sender) client-ip=204.16.202.179;
envelope-from=mperklin@bitcoinsultants.ca;
helo=oool.saucetel.com;
Received: from mail.saucetel.com ([204.16.202.179] helo=oool.saucetel.com)
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1XwdCM-0002dt-Ce
for bitcoin-development@lists.sourceforge.net;
Thu, 04 Dec 2014 20:40:29 +0000
Received: from [192.168.1.206] (unknown [206.223.168.190])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by oool.saucetel.com (Postfix) with ESMTPSA id 57842E81430;
Thu, 4 Dec 2014 15:44:15 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: multipart/signed;
boundary="Apple-Mail=_FB16573C-3BDF-4590-A423-26D6FBB42AF1";
protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b3
From: Michael Perklin <mperklin@bitcoinsultants.ca>
In-Reply-To: <mailman.473107.1417725057.2207.bitcoin-development@lists.sourceforge.net>
Date: Thu, 4 Dec 2014 15:40:12 -0500
Message-Id: <C314D374-FD73-4997-9DCC-0386F807E494@bitcoinsultants.ca>
References: <mailman.473107.1417725057.2207.bitcoin-development@lists.sourceforge.net>
To: bitcoin-development@lists.sourceforge.net
X-Mailer: Apple Mail (2.1993)
X-Spam-Score: 0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.6 URIBL_SBL Contains an URL's NS IP listed in the SBL blocklist
[URIs: dashjr.org]
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-Headers-End: 1XwdCM-0002dt-Ce
Cc: Eric Lombrozo <eric@ciphrex.com>
Subject: Re: [Bitcoin-development] Serialised P2SH HD chains
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 20:40:29 -0000
--Apple-Mail=_FB16573C-3BDF-4590-A423-26D6FBB42AF1
Content-Type: multipart/alternative;
boundary="Apple-Mail=_1766721B-4827-45BE-A919-46C8E51E662C"
--Apple-Mail=_1766721B-4827-45BE-A919-46C8E51E662C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
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.
>=20
> 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?
>=20
> Luke
--Apple-Mail=_1766721B-4827-45BE-A919-46C8E51E662C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div =
class=3D"">Luke,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Eric Lombrozo is doing work similar to that. You may wish to =
connect. </div><div class=3D""><br class=3D""></div><div =
class=3D"">He's building a BIP to standardize a multisig application of =
BIP32. </div><div class=3D"">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)</div><div class=3D""><br class=3D""></div><div class=3D"">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. </div><div class=3D""><br class=3D""></div><div class=3D"">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.</div><br class=3D""><br =
class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: =
auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><font color=3D"#505050" class=3D"">Michael =
Perklin</font></div><div class=3D""><font color=3D"#e88839" =
class=3D"">Bit</font><font color=3D"#505050" class=3D""><b =
class=3D"">coinsultants Inc.</b></font></div></div>
</div>
<br class=3D""><div class=3D"">On Thu, Dec 4, 2014 at 7:42 AM, Luke =
Dashjr <<a href=3D"mailto:luke@dashjr.org" =
class=3D"">luke@dashjr.org</a>> wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">Is anyone working on a serialisation format to =
convey P2SH HD chains? For<br class=3D"">example, to give someone who =
wants to make recurring payments a single token<br class=3D"">that can =
be used to generate many P2SH addresses paying to a multisig script.<br =
class=3D""><br class=3D"">I'm thinking of something along the lines of a =
simple series of tokens, each<br class=3D"">indicating either a HD chain =
or literal script content. For all HD chains in<br class=3D"">the data, =
a child key would be generated based on the payment number, and all<br =
class=3D"">tokens concatenated to form the P2SH serialised script. Eg, =
for a simple 2-<br class=3D"">of-2, you would do something like this:<br =
class=3D""> literal(OP_2) HDChain HDChain literal(OP_2 =
OP_CHECKMULTISIG)<br class=3D"">Does this sufficiently cover all =
reasonable use cases?<br class=3D""><br =
class=3D"">Luke</blockquote></div></body></html>=
--Apple-Mail=_1766721B-4827-45BE-A919-46C8E51E662C--
--Apple-Mail=_FB16573C-3BDF-4590-A423-26D6FBB42AF1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJUgMavAAoJEJbiob6B1HqifVoQAJu4XWN3061e1lwk6dU8aNif
I4oX6i6jtN9oDRIdAbsz8P9oruZetGjzQc8sitS4ZM3uZRh1hByRrKauSp+hPyA8
PkFPctRMImrTrUuFYvhC4VOYH3ABlpR9GJUxHvp+aIdGEm1ELcMmPEtnkBo7HCEw
qzIMf2+LTJ+3YNA8BbX/jCYXebMrUJu7/xcUqu4kb6Am2Hf15HxIvysu+/AOE6X3
60p4xyPEaVrgyC0XNzo2KD1tMU3hLKYVSwe+spGsVrkvmFI7cp+pkPB64p9dVXAi
pRdPAlC36ZXnXiwfUpj+vOzTPAOAKItoZFfZuy7Hqr8Tb2pKQosZ+W+lJTGrfM8n
AWFkG3vIDeEHjiWxoesPIC+MpFqWvl9zcyO9YQ/MJdysVP0Dpe4mea7UkC4qybIf
VqG4U5UyfjtiNHkMQrshNSmSm3B2PiT8QBxMg1kKMnKS8yVhl+2AO/7W29sAcfzi
/aatcMZBtPd5tA0d4Wv3iMF2/40l8qX3cnlHe/qjMqrye4+J3gOpcG5Y/1C274iI
ArHs32/hMo9C3Rtrk/5JRRdtvrSesigSRuEb12kTnYDW6eJa146mQTjnr3iNFuxv
tD17uV3f4bqLr7pXr5ppenCwNcdFet0OxtiKugpf7XDANZVpQdfbaiY0r4fPjvkU
afe6gotWr1j5iSk+ZBTY
=zA1g
-----END PGP SIGNATURE-----
--Apple-Mail=_FB16573C-3BDF-4590-A423-26D6FBB42AF1--
|
