From: Rusty Russell <rusty@rustcorp.com.au>
To: Btc Drak <btcdrak@gmail.com>, Alex Morcos <morcos@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change
Date: Fri, 16 Oct 2015 09:48:18 +1030 [thread overview]
Message-ID: <87oafzhgat.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CADJgMzsvdG2iE=FhYrgKve_JxtMjFVOS4Gx-0Q8GnqDYF_-qOw@mail.gmail.com>
Btc Drak <btcdrak@gmail.com> writes:
> Alex,
>
> I am sorry for not communicating more clearly. Mark and I discussed your
> concerns from the last meeting and he made the change. The BIP text still
> needs to be updated, but the discussed change was added to the PR, albeit
> squashed making it more non-obvious. BIP68 now explicitly uses 16 bits with
> a bitmask. Please see the use of SEQUENCE_LOCKTIME_MASK
> and SEQUENCE_LOCKTIME_GRANULARITY in the PR
> https://github.com/bitcoin/bitcoin/pull/6312.
I like it from a technical perspective.
From a practical perspective: yuck. There's currently no way to play
with bitcoind's perception of time, so that's a very long sleep to
blackbox test (which is what my lightning test script does).
So consider this YA feature request :)
Cheers,
Rusty.
next prev parent reply other threads:[~2015-10-16 0:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 14:30 [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change Peter Todd
2015-10-03 18:49 ` jl2012
2015-10-04 8:35 ` Anthony Towns
2015-10-04 12:04 ` s7r
2015-10-05 22:03 ` Alex Morcos
2015-10-06 0:19 ` Mark Friedenbach
2015-10-06 11:09 ` Peter Todd
2015-10-06 0:28 ` Btc Drak
2015-10-06 1:58 ` Rusty Russell
2015-10-08 17:41 ` Peter Todd
2015-10-09 1:38 ` Rusty Russell
2015-10-15 13:47 ` Alex Morcos
2015-10-15 16:27 ` Btc Drak
2015-10-15 16:37 ` Adam Back
2015-10-15 16:41 ` Alex Morcos
2015-10-15 18:31 ` Mark Friedenbach
2015-10-15 23:18 ` Rusty Russell [this message]
2015-10-16 1:26 ` Rusty Russell
2015-10-19 10:43 ` Jorge Timón
2015-10-06 20:00 ` Joseph Poon
2015-10-08 17:43 ` 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=87oafzhgat.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=btcdrak@gmail.com \
--cc=morcos@gmail.com \
/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