From: Nicolas Dorier <nicolas.dorier@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime (Btc Drak)
Date: Fri, 14 Aug 2015 01:34:03 +0900 [thread overview]
Message-ID: <CA+1nnrmkEGHY7HwffbQ4sEG_c2EhCbVK64FtGXSERpGdsxoQZA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 333 bytes --]
next reply other threads:[~2015-08-13 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 16:34 Nicolas Dorier [this message]
2015-08-13 16:36 ` Matt Corallo
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=CA+1nnrmkEGHY7HwffbQ4sEG_c2EhCbVK64FtGXSERpGdsxoQZA@mail.gmail.com \
--to=nicolas.dorier@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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