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; 
MIME-Version: 1.0
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
Subject: [Bitcoin-development] BIP - Selector Script
Precedence: list

--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 &quot;Multi-P2SH&quot;.<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--