public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Eric Lombrozo <elombrozo@gmail.com>,
	Mark Friedenbach <mark@friedenbach.org>,
	Btc Drak <btcdrak@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)
Date: Fri, 27 Nov 2015 14:32:45 +1030	[thread overview]
Message-ID: <87ziy0qeca.fsf@rustcorp.com.au> (raw)
In-Reply-To: <eme59eddfb-c410-4af4-b496-e3301ac9db85@platinum>

Eric Lombrozo via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> writes:
>>From an app developer's perspective, I think it is pretty blatantly 
> clear that relative timelock is *the* critical exposed functionality 
> intended here.

As someone who actually developed scripts using CSV, I agree with Mark
(and Matt).  The relative locktime stuff isn't in this opcode, it's in
the nSequence calculation.

So, I vote to keep CSV called as it is.

Thanks,
Rusty.


  parent reply	other threads:[~2015-11-27  4:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 10:30 [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112) Btc Drak
2015-11-24 12:20 ` Peter Todd
2015-11-24 12:35   ` Jorge Timón
2015-11-24 12:31 ` Jorge Timón
2015-11-25  1:14   ` Eric Lombrozo
2015-11-26 21:32     ` Eric Lombrozo
2015-11-26 22:25       ` Peter Todd
2015-11-25 23:05 ` Mark Friedenbach
2015-11-25 23:41   ` Eric Lombrozo
2015-11-26 22:23     ` Matt Corallo
2015-11-27  4:02     ` Rusty Russell [this message]
2015-11-27  8:10       ` Eric Lombrozo
2015-11-27  4:08   ` Dave Scotese
2015-11-27 10:14   ` Jorge Timón

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=87ziy0qeca.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=btcdrak@gmail.com \
    --cc=elombrozo@gmail.com \
    --cc=mark@friedenbach.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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