From: Matt Corallo <lf-lists@mattcorallo•com>
To: Nicolas Dorier <nicolas.dorier@gmail•com>,
Nicolas Dorier via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>,
bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime (Btc Drak)
Date: Thu, 13 Aug 2015 16:36:07 +0000 [thread overview]
Message-ID: <6938112D-77D2-44FC-8FF8-13967E9673F2@mattcorallo.com> (raw)
In-Reply-To: <CA+1nnrmkEGHY7HwffbQ4sEG_c2EhCbVK64FtGXSERpGdsxoQZA@mail.gmail.com>
On August 13, 2015 7:34:03 PM GMT+03:00, Nicolas Dorier via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>Would be wonderful to have this pushed together with CLTV and BIP68.
>If BIP68 get pushed in the next fork, this CSV is a no brainer.
>
>Was there a competing RCLTV implementation somewhere that did not
>depend on
>BIP68 for information ? I don't manage to find it.
I think all such competing proposals are dropped because this seemed like a better idea. Feel free to revive one/come up with one, though.
Matt
prev parent reply other threads:[~2015-08-13 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 16:34 Nicolas Dorier
2015-08-13 16:36 ` Matt Corallo [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=6938112D-77D2-44FC-8FF8-13967E9673F2@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=nicolas.dorier@gmail$(echo .)com \
/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