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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1YMB46-0003LU-6m
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Feb 2015 07:53:30 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.115 as permitted sender)
client-ip=62.13.149.115; envelope-from=pete@petertodd.org;
helo=outmail149115.authsmtp.co.uk;
Received: from outmail149115.authsmtp.co.uk ([62.13.149.115])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1YMB44-0003RQ-2R for bitcoin-development@lists.sourceforge.net;
Fri, 13 Feb 2015 07:53:30 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t1D7rIRL007937;
Fri, 13 Feb 2015 07:53:18 GMT
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t1D7rF2b071653
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Fri, 13 Feb 2015 07:53:17 GMT
Date: Fri, 13 Feb 2015 02:53:14 -0500
From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>
Message-ID: <20150213075314.GA2122@savin.petertodd.org>
References: <54DD1E3F.60006@thomaskerin.io>
<201502122213.34765.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF"
Content-Disposition: inline
In-Reply-To: <201502122213.34765.luke@dashjr.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 5f88612b-b355-11e4-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwEUHlAWAgsB AmMbW1NeVV57WGs7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRR11 AVxoUEtycARAfX0+ bENmVj5eCkxyc0d/
EFMGFmgDeGZhPWQC AkNRcR5UcAFPdx8U a1UrBXRDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA4hPwZ0 SRcYVTkiAUAfQiQ1
Lgc6K1VUBE8Ad1k1 dEAqQ1MAL1oSAxZe fQlIHStFJhwaRiUt
BB9HR0NWGTFRWypH GRAzSgDQ
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YMB44-0003RQ-2R
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: Fri, 13 Feb 2015 07:53:30 -0000
--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Feb 12, 2015 at 10:13:33PM +0000, Luke Dashjr wrote:
> Where is the Specification section?? Does this support arbitrary scripts,=
or=20
> 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.
--=20
'peter'[:-1]@petertodd.org
000000000000000013cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1
--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJU3a1lXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxM2NmODI3MDExOGJhMmVmY2U4YjMwNGY4ZGUzNTk1OTlm
ZWY5NWMzYWI0M2RjYjEvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftivwf/QcZirmmICg4vGos7GSfsx7Ck
AXeSpsQekyh+KZ0UixKO8EiwceO/C4pIqQ7GTOOMqbX1WoqM/6ACy2SGbjqPMnbL
ASoScl3ZL5bYezO77QoWcIcJ1NqOeSiIea/Zs9nIK4IKOIeIrtou16UIvD9aK6lk
bA35M/P2WaubgkzdBlXP1AXNHooi1SKT5zqVQ1VlBqQqiLaAo4BGD3btz00wOa5A
iksbql7MkM0u5zL49Loty+CRc0/4pJD6rYsBjPBUpOcucFljtWm84U87212Xqsma
/bRBmdnCqDWRAErWYse8fGb3CySj/sf22O8btR4kKMB0reEBZcttQRcSsuBJ+Q==
=9dXR
-----END PGP SIGNATURE-----
--3MwIy2ne0vdjdPXF--
|
