public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Rusty Russell <rusty@rustcorp•com.au>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] CLTV opcode allocation; long-term plans?
Date: Thu, 7 May 2015 13:17:32 -0400	[thread overview]
Message-ID: <20150507171732.GA6033@savin.petertodd.org> (raw)
In-Reply-To: <87lhh188zw.fsf@rustcorp.com.au>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On Thu, May 07, 2015 at 11:05:47AM +0930, Rusty Russell wrote:
> Peter Todd <pete@petertodd•org> writes:
> > That said, if people have strong feelings about this, I would be willing
> > to make OP_CLTV work as follows:
> >
> >     <nLockTime> 1 OP_CLTV
> >
> > Where the 1 selects absolute mode, and all others act as OP_NOP's. A
> > future relative CLTV could then be a future soft-fork implemented as
> > follows:
> >
> >     <relative nLockTime> 2 OP_CLTV
> 
> Mildly prefer to put that the other way around.
> 
> ie. the OP_NOP1 becomes OP_EXTENSION_PREFIX, the next op defines which
> extended opcode it is (must be a push).

There's no good way to implement that option - when the OP_NOPx is
executed all that's available to it without a lot of complex work is
what's already been pushed to the stack, not what will be pushed to the
stack in the future.

-- 
'peter'[:-1]@petertodd.org
000000000000000002761482983864328320badf24d137101fab9a5861a59d30

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]

      reply	other threads:[~2015-05-07 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  5:07 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
2015-05-13  0:38             ` Jorge Timón
2015-05-07  1:35 ` Rusty Russell
2015-05-07 17:17   ` Peter Todd [this message]

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=20150507171732.GA6033@savin.petertodd.org \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=rusty@rustcorp$(echo .)com.au \
    /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