public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] CLTV opcode allocation; long-term plans?
Date: Tue, 12 May 2015 20:38:27 +0000	[thread overview]
Message-ID: <201505122038.28831.luke@dashjr.org> (raw)
In-Reply-To: <CADJgMzv1NdoXKDScQ1+OycijzME=W2YSut3GMF=EEuKQf6VeUg@mail.gmail.com>

It should actually be straightforward to softfork RCLTV in as a negative CLTV.
All nLockTime are >= any negative number, so a negative number makes CLTV a 
no-op always. Therefore, it is clean to define negative numbers as relative 
later. It's also somewhat obvious to developers, since negative numbers often 
imply an offset (eg, negative list indices in Python).

Luke



  reply	other threads:[~2015-05-12 20:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  5:07 [Bitcoin-development] CLTV opcode allocation; long-term plans? Peter Todd
2015-05-05  0:54 ` Btc Drak
2015-05-09  9:12   ` Peter Todd
2015-05-12 19:16     ` Jorge Timón
2015-05-12 19:23       ` Pieter Wuille
2015-05-12 19:30       ` Btc Drak
2015-05-12 20:38         ` Luke Dashjr [this message]
2015-05-12 21:01           ` Peter Todd
2015-05-13  0:38             ` Jorge Timón
2015-05-07  1:35 ` Rusty Russell
2015-05-07 17:17   ` Peter Todd

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=201505122038.28831.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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