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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1WdlBu-0000Kc-5z
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 18:49:42 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.48 as permitted sender)
client-ip=209.85.192.48; envelope-from=tier.nolan@gmail.com;
helo=mail-qg0-f48.google.com;
Received: from mail-qg0-f48.google.com ([209.85.192.48])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WdlBt-0001Yx-Co
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 18:49:42 +0000
Received: by mail-qg0-f48.google.com with SMTP id q108so4450647qgd.7
for <bitcoin-development@lists.sourceforge.net>;
Fri, 25 Apr 2014 11:49:35 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.140.19.133 with SMTP id 5mr13242543qgh.46.1398451775903;
Fri, 25 Apr 2014 11:49:35 -0700 (PDT)
Received: by 10.140.25.86 with HTTP; Fri, 25 Apr 2014 11:49:35 -0700 (PDT)
Date: Fri, 25 Apr 2014 19:49:35 +0100
Message-ID: <CAE-z3OXe4fG2S274qcgpGsXA=ZhhJQneEDqLYvNWZT8U9y_NLA@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11355746569d3604f7e26d5d
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
(tier.nolan[at]gmail.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.48 listed in list.dnswl.org]
-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: 1WdlBt-0001Yx-Co
Subject: [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 18:49:42 -0000
--001a11355746569d3604f7e26d5d
Content-Type: text/plain; charset=UTF-8
This is a BIP to allow the spender to choose one of multiple standard
scripts to use for spending the output.
https://github.com/TierNolan/bips/blob/bip4x/bip-0045.mediawiki
This is required as part of the atomic cross chain transfer protocol. It
is required so that outputs can be retrieved, if the process ends before
being committed.
https://bitcointalk.org/index.php?topic=193281.msg2224949#msg2224949
The script allows multiple standard scripts to be included in the
scriptPubKey.
When redeeming the script the spender indicates which of the standard
scripts to use.
Only one standard script is actually executed, so the only cost is the
extra storage required.
A more ambitious change would be a soft fork like P2SH, except the spender
is allowed to select from multiple hashes. Effectively, it would be
"Multi-P2SH".
This gets much of the benefits of MAST, but it requires a formal soft fork
to implement.
If there is agreement, I can code up the reference implementation as a PR.
The multi-P2SH might actually be easier.
--001a11355746569d3604f7e26d5d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div>This is a BIP to allow the spender to =
choose one of multiple standard scripts to use for spending the output.<br>=
<br><a href=3D"https://github.com/TierNolan/bips/blob/bip4x/bip-0045.mediaw=
iki">https://github.com/TierNolan/bips/blob/bip4x/bip-0045.mediawiki</a><br=
>
<br></div>This is required as part of the atomic cross chain transfer proto=
col.=C2=A0 It is required so that outputs can be retrieved, if the process =
ends before being committed.<br><br><a href=3D"https://bitcointalk.org/inde=
x.php?topic=3D193281.msg2224949#msg2224949">https://bitcointalk.org/index.p=
hp?topic=3D193281.msg2224949#msg2224949</a><br>
<br></div>The script allows multiple standard scripts to be included in the=
scriptPubKey.<br><br>When redeeming the script the spender indicates which=
of the standard scripts to use.<br><br></div>Only one standard script is a=
ctually executed, so the only cost is the extra storage required.<br>
<br></div><div>A more ambitious change would be a soft fork like P2SH, exce=
pt the spender is allowed to select from multiple hashes.=C2=A0 Effectively=
, it would be "Multi-P2SH".<br><br></div><div>This gets much of t=
he benefits of MAST, but it requires a formal soft fork to implement.<br>
<br>If there is agreement, I can code up the reference implementation as a =
PR.=C2=A0 The multi-P2SH might actually be easier.<br></div></div>
--001a11355746569d3604f7e26d5d--
|
