Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.46 as permitted sender)
	client-ip=209.85.215.46; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f46.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAE-z3OX5_POg9kFoz-LsGhuLRA6qFPcNXoECLhewe+o-+Pw2gA@mail.gmail.com>
References: <CAE-z3OXe4fG2S274qcgpGsXA=ZhhJQneEDqLYvNWZT8U9y_NLA@mail.gmail.com>
	<201404251917.49826.luke@dashjr.org>
	<CAE-z3OX5_POg9kFoz-LsGhuLRA6qFPcNXoECLhewe+o-+Pw2gA@mail.gmail.com>
Date: Fri, 25 Apr 2014 13:13:25 -0700
Message-ID: <CAAS2fgRjtC+v7G6BA2UGtPWWUHQyuViJk24AO5ge6-hKW+H+Ww@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Tier Nolan <tier.nolan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Selector Script
Precedence: list

On Fri, Apr 25, 2014 at 1:02 PM, Tier Nolan <tier.nolan@gmail.com> wrote:
>> 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).
> One use case should be enough.  The atomic cross chain proposal has been
> discussed for a while.  It feels like bitcoin works on an "ask permission
> first" basis.

You're reading that response the wrong way. It isn't in any way
opposed to the specification, it's pointing out that the specification
is _unclear_ about the applications, it mentions one but doesn't
explain it and it wouldn't be apparent to all readers. Thats all.

It could be clarified by saying something like "allows spending to be
controlled by the publication of information, for example in another
transaction so that they can only be completed atomically [citation to
a revision of the contracts page]".