From: Peter Todd <pete@petertodd.org>
To: Luke Dashjr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] CLTV opcode allocation; long-term plans?
Date: Tue, 12 May 2015 17:01:25 -0400 [thread overview]
Message-ID: <20150512210125.GA5902@muck> (raw)
In-Reply-To: <201505122038.28831.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Tue, May 12, 2015 at 08:38:27PM +0000, Luke Dashjr wrote:
> 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).
Doing this makes handling the year 2038 problem a good deal more
complex.
The CLTV codebase specifically fails on negative arguments to avoid any
ambiguity or implementation differences here.
--
'peter'[:-1]@petertodd.org
00000000000000000e7980aab9c096c46e7f34c43a661c5cb2ea71525ebb8af7
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-05-12 21:01 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
2015-05-12 21:01 ` Peter Todd [this message]
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=20150512210125.GA5902@muck \
--to=pete@petertodd.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.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