From: Gregory Maxwell <gmaxwell@gmail•com>
To: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Selector Script
Date: Fri, 25 Apr 2014 13:13:25 -0700 [thread overview]
Message-ID: <CAAS2fgRjtC+v7G6BA2UGtPWWUHQyuViJk24AO5ge6-hKW+H+Ww@mail.gmail.com> (raw)
In-Reply-To: <CAE-z3OX5_POg9kFoz-LsGhuLRA6qFPcNXoECLhewe+o-+Pw2gA@mail.gmail.com>
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]".
next prev parent reply other threads:[~2014-04-25 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:49 Tier Nolan
2014-04-25 19:17 ` Luke-Jr
2014-04-25 19:58 ` Peter Todd
2014-04-25 20:05 ` Tier Nolan
2014-04-25 20:02 ` Tier Nolan
2014-04-25 20:13 ` Gregory Maxwell [this message]
2014-04-25 20:26 ` Luke-Jr
2014-04-25 20:48 ` Tier Nolan
2014-04-26 17:00 ` Mark Friedenbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAS2fgRjtC+v7G6BA2UGtPWWUHQyuViJk24AO5ge6-hKW+H+Ww@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tier.nolan@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox