From: Peter Todd <pete@petertodd.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change
Date: Thu, 8 Oct 2015 19:43:29 +0200 [thread overview]
Message-ID: <20151008174329.GB9291@muck> (raw)
In-Reply-To: <20151003143056.GA27942@muck>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Sat, Oct 03, 2015 at 04:30:56PM +0200, Peter Todd via bitcoin-dev wrote:
> BIP68 and BIP112 collectively define the CHECKSEQUENCEVERIFY semantics,
<snip>
Another issue that came to mind re: CSV review is that there isn't
actually any one pull-req with all the code changes together, making it
hard to be sure what the final effect will be once all three BIPs are
merged.
While evaluating stuff separately is often good, I think this is a case
where the overall design needs to be evaluated as a single unit to fully
understand the behavior.
--
'peter'[:-1]@petertodd.org
00000000000000000de60f807a5fd32057510e7715038ecbc888052861b6a5c1
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
prev parent reply other threads:[~2015-10-08 17:43 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
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 [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=20151008174329.GB9291@muck \
--to=pete@petertodd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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