From: Btc Drak <btcdrak@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP68: Relative lock-time through consensus-enforced sequence numbers (update)
Date: Sat, 21 Nov 2015 14:13:05 +0000 [thread overview]
Message-ID: <CADJgMzvzfLky3QOGiuUCyjpvQXom3WXUfxuA5_r7jE2itJwGCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
As I am sure you are aware, for the last 5 months work has been on-going to
create a relative lock-time proposal using sequence numbers. The
implementation can be found at https://github.com/bitcoin/bitcoin/pull/6312.
The current implementation is "mempool-only" and the soft-fork would be
deployed at a later stage.
Over these months there has been various discussion back and forth to
refine the details.
I have updated the BIP text now according to the details that were
discussed in mid-October[1][2] and have extensively clarified the text.
To recap, the overall picture for relative lock-time is that BIP68
introduces consensus rules using some of the nSequence field, while BIP112
creates a new opcode OP_CHECKSEQUENCEVERIFY (PR #6564) so relative
lock-time can be verified from the Bitcoin scripting language. Ideally we
would soft-fork BIP68, BIP112 (CSV) and 113 (MTP) together. BIP113 has been
deployed in 0.11.2 as mempool policy so miners should be applying this
policy as they deploy version 4 blocks for the ongoing CLTV soft-fork
(currently at 42% at the time of writing).
I am writing this mail to draw your attention to the BIP68 pull-requests
and to request final review at:
BIP68 text - https://github.com/bitcoin/bips/pull/245
BIP68 implementation - https://github.com/bitcoin/bitcoin/pull/6312
Discussion references:
[1]
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-October/011357.html
[2] http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/10/15#l1444928045.0
[-- Attachment #2: Type: text/html, Size: 2136 bytes --]
reply other threads:[~2015-11-21 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CADJgMzvzfLky3QOGiuUCyjpvQXom3WXUfxuA5_r7jE2itJwGCw@mail.gmail.com \
--to=btcdrak@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