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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1WdmH0-0003Vi-CT
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 19:59:02 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.75 as permitted sender)
client-ip=62.13.149.75; envelope-from=pete@petertodd.org;
helo=outmail149075.authsmtp.net;
Received: from outmail149075.authsmtp.net ([62.13.149.75])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WdmGy-0000YK-TE for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 19:59:02 +0000
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt14.authsmtp.com (8.14.2/8.14.2) with ESMTP id s3PJwpNY054616;
Fri, 25 Apr 2014 20:58:51 +0100 (BST)
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3PJwj7k017488
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Fri, 25 Apr 2014 20:58:48 +0100 (BST)
Date: Fri, 25 Apr 2014 15:58:38 -0400
From: Peter Todd <pete@petertodd.org>
To: Luke-Jr <luke@dashjr.org>
Message-ID: <20140425195838.GA3965@savin>
References: <CAE-z3OXe4fG2S274qcgpGsXA=ZhhJQneEDqLYvNWZT8U9y_NLA@mail.gmail.com>
<201404251917.49826.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3"
Content-Disposition: inline
In-Reply-To: <201404251917.49826.luke@dashjr.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 04306e15-ccb4-11e3-94fa-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAcUGUUGAgsB AmIbWVReVVV7XWs7 bAxPbAVDY01GQQRq
WVdMSlVNFUsrAnx7 QUQZCRlzcAFOcDB3 ZUJjEHBfX0R8IEd4
Xx0HR2kbZGY1a30W VBYJagNUcgZDfk5E aVUrVz1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCWwqJnZ5 DysPGTgkAUofDx44 NR0+NjYB
X-Authentic-SMTP: 61633532353630.1024:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/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
X-Headers-End: 1WdmGy-0000YK-TE
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP - Selector Script
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, 25 Apr 2014 19:59:02 -0000
--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Apr 25, 2014 at 07:17:48PM +0000, Luke-Jr wrote:
> I believe you meant to link here instead?
> https://github.com/TierNolan/bips/blob/bip4x/bip-0046.mediawiki
>=20
> This looks reasonable from a brief skim over, but does not define any use=
=20
> cases (it mentions "necessary for atomic cross chain transfers", but does=
not=20
> explain how it is useful for that - perhaps that belongs in another BIP y=
ou=20
> haven't written yet, though). IMO, it should also require P2SH.
Keep in mind that P2SH redeemScripts are limited to just 520 bytes;
there's going to be many cases where more complex transactions just
can't be encoded in P2SH at all.
--=20
'peter'[:-1]@petertodd.org
00000000000000006407c80d5d4506a4253b4b426e0c7702963f8bf91e7971aa
--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQGrBAEBCACVBQJTWr5pXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDA2NDA3YzgwZDVkNDUwNmE0MjUzYjRiNDI2ZTBjNzcwMjk2
M2Y4YmY5MWU3OTcxYWEvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfs8gwgAs9mpAQWv/6Irahr5Zvip1aK5
upOToKqjFzfBbLTp3w6mgC439gHUb3vOyKYKBECbwo3EZWvWkuU63IMBol6OfoM4
K3x+j6VR1fKPCAbnQluWSymQ08zon72xn4ZWhCjNSmlA+VllA5eYV1me6T38zJi9
r/ojfDZY26iAnDlw7PIeVAoXrxDG5oXVY+nN4wW7XTAEhSyxePkzByKqt7VMTOII
yopqRWAGK7IoX4d5yxbEv3/FNNZMYkOJTgv6Z+odq0tIWtk7MbOvRjUFNyzdyvdf
kO2wy5RHsPmrDcNLfkW5eTGVa8RFxllbgF3E7WnF4zeUKY4+RXC1mlD/K+PrSA==
=qfHG
-----END PGP SIGNATURE-----
--r5Pyd7+fXNt84Ff3--
|
