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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ruben@blockcorp.com>) id 1YMCEn-0008Io-FW
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Feb 2015 09:08:37 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of blockcorp.com
designates 74.125.82.170 as permitted sender)
client-ip=74.125.82.170; envelope-from=ruben@blockcorp.com;
helo=mail-we0-f170.google.com;
Received: from mail-we0-f170.google.com ([74.125.82.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YMCEm-0005od-72
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Feb 2015 09:08:37 +0000
Received: by mail-we0-f170.google.com with SMTP id q59so15302368wes.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 13 Feb 2015 01:08:30 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=P/iEgINMW34xXhhdttbcmE2Nnq9vKcvtaMvu+Y1XFCQ=;
b=cUDEjYLLseG4gsL2/GxT3t9O6TRYkxCzF18u8crodK0EJodNmWERGaHM1861+u1oQF
exUxV8iSHKPH+UgIXA4sTfQ6cPAC4PxUiZXY78m2VjZgCF6j0LbAbE7BLAUQxAOvUKlP
usCCru6N+YvNvvoSrGcd3UuNqwqI8Csio/Agr83VHWv+wQi1cddthVl8pJY6ApTW6/px
PKuWagcc1HGFT6vheQyL4uq4wz9W7egHoeUCGLijU3FyVSqSxS1KIfaob3/DWUw44uA4
rTAx3H46EvmbaTbSwHCquYiCSeraJ+bnk8VAYeH7AA83lYxQ6tXzGMng3C+MAvYPMWpt
5efg==
X-Gm-Message-State: ALoCoQlJI0FTiEw4sIHT0jPamd64e3nveEnABLAY4o+4Ej/df0T7C502IxjoKpXKNdcAKo3LP/3o
MIME-Version: 1.0
X-Received: by 10.180.208.69 with SMTP id mc5mr4866169wic.75.1423818101659;
Fri, 13 Feb 2015 01:01:41 -0800 (PST)
Received: by 10.27.11.10 with HTTP; Fri, 13 Feb 2015 01:01:41 -0800 (PST)
In-Reply-To: <20150213075314.GA2122@savin.petertodd.org>
References: <54DD1E3F.60006@thomaskerin.io>
<201502122213.34765.luke@dashjr.org>
<20150213075314.GA2122@savin.petertodd.org>
Date: Fri, 13 Feb 2015 10:01:41 +0100
Message-ID: <CABETNRuFUqBmv7QOMWCMyyBBgb2NQoL+0_GeLvKw+v-uY8+ufA@mail.gmail.com>
From: Ruben de Vries <ruben@blocktrail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=001a11c36d782cb439050ef47ca1
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 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: 1YMCEm-0005od-72
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: Fri, 13 Feb 2015 09:08:37 -0000
--001a11c36d782cb439050ef47ca1
Content-Type: text/plain; charset=UTF-8
The idea is more like BIP44/45 to have a 'standard' that software can
comply by and express they do
so that it makes a step towards compatibility between (wallet) software.
On Fri, Feb 13, 2015 at 8:53 AM, Peter Todd <pete@petertodd.org> wrote:
> 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?
>
> 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.
>
> 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.
>
> --
> 'peter'[:-1]@petertodd.org
> 000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1
>
--
BlockTrail B.V.
Barbara Strozzilaan 201
1083HN Amsterdam
The Netherlands
Phone: +31 (0)612227277
E-mail: ruben@blocktrail.com
Web: www.blocktrail.com
Github: www.github.com/rubensayshi
BlockTrail B.V. Is registered with the Dutch Chamber of Commerce in
Amsterdam with registration No.:60262060 and VAT No.:NL853833035B01
--001a11c36d782cb439050ef47ca1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">The idea is more like BIP44/45 to have a 'standard' tha=
t software can comply by and express they do</div><div class=3D"gmail_defau=
lt" style=3D"font-family:verdana,sans-serif">so that it makes a step toward=
s compatibility between (wallet) software.=C2=A0</div></div><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Fri, Feb 13, 2015 at 8:53 AM,=
Peter Todd <span dir=3D"ltr"><<a href=3D"mailto:pete@petertodd.org" tar=
get=3D"_blank">pete@petertodd.org</a>></span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><span class=3D"">On Thu, Feb 12, 2015 at 10:13:33PM +0000, L=
uke Dashjr wrote:<br>
> Where is the Specification section?? Does this support arbitrary scrip=
ts, or<br>
> only the simplest CHECKMULTISIG case?<br>
<br>
</span>It might be enough to rewrite this BIP to basically say "all pu=
bkeys<br>
executed by all CHECKMULTISIG opcodes will be in the following canonical<br=
>
order", followed by some explanatory examples of how to apply this<br>
simple rule.<br>
<br>
OTOH we don't yet have a standard way of even talking about arbitrary<b=
r>
scripts, so it may very well turn out to be the case that the above rule<br=
>
is too restrictive in many cases - I certainly would not want to do a<br>
soft-fork to enforce this, or even make it an IsStandard() rule.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
'peter'[:-1]@<a href=3D"http://petertodd.org" target=3D"_blank">pet=
ertodd.org</a><br>
000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><di=
v><font face=3D"arial, helvetica, sans-serif">BlockTrail B.V.</font></div><=
div><font face=3D"arial, helvetica, sans-serif">Barbara Strozzilaan 201</fo=
nt></div><div><font face=3D"arial, helvetica, sans-serif">1083HN Amsterdam<=
/font></div><div><font face=3D"arial, helvetica, sans-serif">The Netherland=
s</font></div><div><br></div><div><font face=3D"arial, helvetica, sans-seri=
f">Phone:<span style=3D"white-space:pre"> </span>+31 (0)612227277</font></=
div><div><font face=3D"arial, helvetica, sans-serif">E-mail:<span style=3D"=
white-space:pre"> </span><a href=3D"mailto:ruben@blocktrail.com" target=3D=
"_blank">ruben@blocktrail.com</a></font></div><div><font face=3D"arial, hel=
vetica, sans-serif">Web:<span style=3D"white-space:pre"> </span><a href=3D=
"http://www.blocktrail.com/" target=3D"_blank">www.blocktrail.com<br></a></=
font></div><div>Github:<span style=3D"font-family:arial,helvetica,sans-seri=
f;white-space:pre"> </span><span style=3D"font-family:arial,helvetica,sans-=
serif;white-space:pre"> <a href=3D"http://www.github.com/rubensayshi" targe=
t=3D"_blank">www.github.com/rubensayshi</a></span></div><div><font face=3D"=
arial, helvetica, sans-serif"><br></font></div><div><font face=3D"arial, he=
lvetica, sans-serif">BlockTrail B.V. Is registered with the Dutch Chamber o=
f Commerce in Amsterdam with registration No.:60262060 and VAT No.:NL853833=
035B01</font></div></div></div></div></div>
</div>
--001a11c36d782cb439050ef47ca1--
|
