From: Pieter Wuille <pieter.wuille@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] CLTV opcode allocation; long-term plans?
Date: Tue, 12 May 2015 12:23:22 -0700 [thread overview]
Message-ID: <CAPg+sBh8GQdTurvEkMB1+oSWhLgO4Oq2Cu7WRkWp32fRJfaCiw@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDqVu9OqNpOgCa6hMw3CXp7ePWTaAGPtMq4T9rG658K=ow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 248 bytes --]
I have no strong opinion, but a slight preference for separate opcodes.
Reason: given the current progress, they'll likely be deployed
independently, and maybe the end result is not something that cleanly fits
the current CLTV argument structure.
[-- Attachment #2: Type: text/html, Size: 285 bytes --]
next prev parent reply other threads:[~2015-05-12 19:23 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 [this message]
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
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=CAPg+sBh8GQdTurvEkMB1+oSWhLgO4Oq2Cu7WRkWp32fRJfaCiw@mail.gmail.com \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jtimon@jtimon$(echo .)cc \
/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