public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Peter Todd <pete@petertodd.org>,
	bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] CLTV opcode allocation; long-term plans?
Date: Thu, 07 May 2015 11:05:47 +0930	[thread overview]
Message-ID: <87lhh188zw.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20150504050715.GA18856@savin.petertodd.org>

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).

Cheers,
Rusty.



  parent reply	other threads:[~2015-05-07 17:20 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
2015-05-13  0:38             ` Jorge Timón
2015-05-07  1:35 ` Rusty Russell [this message]
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=87lhh188zw.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pete@petertodd.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