summaryrefslogtreecommitdiff
path: root/71/d6f7720dc0b9d5dd9d4eedee927e3adb96f030
blob: fb9c4f3bf07ed3412405b00c2e804bbc7d65f7a1 (plain)
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
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <elombrozo@gmail.com>) id 1YwK1n-0002xA-Tg
	for bitcoin-development@lists.sourceforge.net;
	Sun, 24 May 2015 00:44:31 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.51 as permitted sender)
	client-ip=209.85.220.51; envelope-from=elombrozo@gmail.com;
	helo=mail-pa0-f51.google.com; 
Received: from mail-pa0-f51.google.com ([209.85.220.51])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YwK1l-0004HR-Ge
	for bitcoin-development@lists.sourceforge.net;
	Sun, 24 May 2015 00:44:31 +0000
Received: by padbw4 with SMTP id bw4so46422259pad.0
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 23 May 2015 17:44:23 -0700 (PDT)
X-Received: by 10.70.134.133 with SMTP id pk5mr27785565pdb.133.1432428263853; 
	Sat, 23 May 2015 17:44:23 -0700 (PDT)
Received: from [192.168.1.102] (cpe-76-167-237-202.san.res.rr.com.
	[76.167.237.202])
	by mx.google.com with ESMTPSA id ae9sm5979304pac.25.2015.05.23.17.44.21
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sat, 23 May 2015 17:44:22 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_A082DC55-1992-454D-A3FA-607E6C2EB5FF";
	protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <20150213075314.GA2122@savin.petertodd.org>
Date: Sat, 23 May 2015 17:44:20 -0700
Message-Id: <234B9DB2-3FF1-49CA-BBAE-EA4823839C00@gmail.com>
References: <54DD1E3F.60006@thomaskerin.io>
	<201502122213.34765.luke@dashjr.org>
	<20150213075314.GA2122@savin.petertodd.org>
To: Peter Todd <pete@petertodd.org>
X-Mailer: Apple Mail (2.2098)
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(elombrozo[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YwK1l-0004HR-Ge
Cc: bitcoin-development@lists.sourceforge.net, ruben@blocktrail.com
Subject: Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash
	multi-signature addresses
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: Sun, 24 May 2015 00:44:32 -0000


--Apple-Mail=_A082DC55-1992-454D-A3FA-607E6C2EB5FF
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_4E18D945-15DF-49BF-A992-5D42AAB7842F"


--Apple-Mail=_4E18D945-15DF-49BF-A992-5D42AAB7842F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

A few months back, William Swanson and I had worked on a more general =
script template format. Unfortunately, other work has prevented us from =
being able to fully complete it - but here=E2=80=99s the start:

=
https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXvGGHWxoKmDSk=
iIsPI =
<https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXvGGHWxoKmDS=
kiIsPI>/

- Eric Lombrozo

> On Feb 12, 2015, at 11:53 PM, Peter Todd <pete@petertodd.org> wrote:
>=20
> On Thu, Feb 12, 2015 at 10:13:33PM +0000, Luke Dashjr wrote:
>> Where is the Specification section?? Does this support arbitrary =
scripts, or
>> only the simplest CHECKMULTISIG case?
>=20
> It might be enough to rewrite this BIP to basically say "all pubkeys
> executed by all CHECKMULTISIG opcodes will be in the following =
canonical
> order", followed by some explanatory examples of how to apply this
> simple rule.
>=20
> OTOH we don't yet have a standard way of even talking about arbitrary
> scripts, so it may very well turn out to be the case that the above =
rule
> is too restrictive in many cases - I certainly would not want to do a
> soft-fork to enforce this, or even make it an IsStandard() rule.
>=20
> --
> 'peter'[:-1]@petertodd.org
> 000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1
> =
--------------------------------------------------------------------------=
----
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, =
is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. =
Take a
> look and join the conversation now. =
http://goparallel.sourceforge.net/________________________________________=
_______
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--Apple-Mail=_4E18D945-15DF-49BF-A992-5D42AAB7842F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">A few months back, William Swanson and I had worked on a more =
general script template format. Unfortunately, other work has prevented =
us from being able to fully complete it - but here=E2=80=99s the =
start:<div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXvGGH=
WxoKmDSkiIsPI" =
class=3D"">https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXv=
GGHWxoKmDSkiIsPI</a>/</div><div class=3D""><br class=3D""></div><div =
class=3D"">- Eric Lombrozo</div><div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Feb 12, 2015, at 11:53 PM, Peter Todd &lt;<a =
href=3D"mailto:pete@petertodd.org" class=3D"">pete@petertodd.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">On =
Thu, Feb 12, 2015 at 10:13:33PM +0000, Luke Dashjr wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">Where is the =
Specification section?? Does this support arbitrary scripts, or <br =
class=3D"">only the simplest CHECKMULTISIG case?<br =
class=3D""></blockquote><br class=3D"">It might be enough to rewrite =
this BIP to basically say "all pubkeys<br class=3D"">executed by all =
CHECKMULTISIG opcodes will be in the following canonical<br =
class=3D"">order", followed by some explanatory examples of how to apply =
this<br class=3D"">simple rule.<br class=3D""><br class=3D"">OTOH we =
don't yet have a standard way of even talking about arbitrary<br =
class=3D"">scripts, so it may very well turn out to be the case that the =
above rule<br class=3D"">is too restrictive in many cases - I certainly =
would not want to do a<br class=3D"">soft-fork to enforce this, or even =
make it an IsStandard() rule.<br class=3D""><br class=3D"">-- <br =
class=3D"">'peter'[:-1]@<a href=3D"http://petertodd.org" =
class=3D"">petertodd.org</a><br =
class=3D"">000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb=
1<br =
class=3D"">---------------------------------------------------------------=
---------------<br class=3D"">Dive into the World of Parallel =
Programming. The Go Parallel Website,<br class=3D"">sponsored by Intel =
and developed in partnership with Slashdot Media, is your<br =
class=3D"">hub for all things parallel software development, from weekly =
thought<br class=3D"">leadership blogs to news, videos, case studies, =
tutorials and more. Take a<br class=3D"">look and join the conversation =
now. <a =
href=3D"http://goparallel.sourceforge.net/________________________________=
_______________" =
class=3D"">http://goparallel.sourceforge.net/_____________________________=
__________________</a><br class=3D"">Bitcoin-development mailing list<br =
class=3D""><a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" =
class=3D"">Bitcoin-development@lists.sourceforge.net</a><br =
class=3D"">https://lists.sourceforge.net/lists/listinfo/bitcoin-developmen=
t<br class=3D""></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_4E18D945-15DF-49BF-A992-5D42AAB7842F--

--Apple-Mail=_A082DC55-1992-454D-A3FA-607E6C2EB5FF
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

iQIcBAEBCgAGBQJVYR7kAAoJEJNAI64YFENUqaoP/1A6a3DhtOpP8DXhxoQRWndm
JADL3i/n4LMzCuiu/Bt5TPL1KmoETJDoY+dP7JRccbHaxd5KgixMe5dR5ZHR5l2K
NawmDZX3dCfagk9Z+issOUoxpRxKzITgMO3NLFwfB9iJbwfLsJ8mPrUekTTn1ZmH
zNVCHrENQoVxbOJVw0H87J1JybrhxqaJVzZ7+3JSou2NL1KFI+w0ToJ6+yfD3puF
y3iHwfnxZrWPqMFoHkkkCSf+PXqZjyCVl6FTY+BE2FHTj1SKaRGi0ztzNHGf5pwk
6Tu7xcun2PXACnvzfPKGVhyLPsOrC+62SzjsGmJsSewWgvtsI3oRGaB+YCQkaGTG
3OgZtch7xnpWR2ZItabQiUGV3Zc4NcHQAD0vMq1L1qIfWOdlGlS4Qax30owjpbzM
/Ze5DWo3GcOEiaksRDhZC0OHoD+33zQVn7/04Wih2UqVC/uF/EY9UvWCFRjseQ0w
mdXJf1rJCCYZJl95GHYJCKXewInXWYoGNLl+Bg+3ZYGTYKM6wPxe7U03Uf68HtN6
gaAErPB6755aZpuo6LfBz4DjMTVUt36jmJqKeREtgb0hTi3VQIRG1JUx5itanRKW
OxYuQ71q/ikyfvsN4U5oCaBqr43iyvQk5yeCzKRTToF7PTlVVEi3o+kJshHaLKld
2vJWb7sIWjKzwXx1pu8Z
=qdCL
-----END PGP SIGNATURE-----

--Apple-Mail=_A082DC55-1992-454D-A3FA-607E6C2EB5FF--