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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1WdldK-0007D7-2W
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 19:18:02 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([192.3.11.21])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WdldI-0002cn-PL for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 19:18:02 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 32BCC10802BC
for <bitcoin-development@lists.sourceforge.net>;
Fri, 25 Apr 2014 19:18:31 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 25 Apr 2014 19:17:48 +0000
User-Agent: KMail/1.13.7 (Linux/3.12.6-gentoo; KDE/4.11.5; x86_64; ; )
References: <CAE-z3OXe4fG2S274qcgpGsXA=ZhhJQneEDqLYvNWZT8U9y_NLA@mail.gmail.com>
In-Reply-To: <CAE-z3OXe4fG2S274qcgpGsXA=ZhhJQneEDqLYvNWZT8U9y_NLA@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201404251917.49826.luke@dashjr.org>
X-Spam-Score: -0.7 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1WdldI-0002cn-PL
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:18:02 -0000
I believe you meant to link here instead?
https://github.com/TierNolan/bips/blob/bip4x/bip-0046.mediawiki
This looks reasonable from a brief skim over, but does not define any use
cases (it mentions "necessary for atomic cross chain transfers", but does not
explain how it is useful for that - perhaps that belongs in another BIP you
haven't written yet, though). IMO, it should also require P2SH.
Luke
On Friday, April 25, 2014 6:49:35 PM Tier Nolan wrote:
> 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.
|
