From: "David A. Harding" <dave@dtrt.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime
Date: Thu, 27 Aug 2015 07:03:30 -0400 [thread overview]
Message-ID: <20150827110330.GA2842@localhost.localdomain> (raw)
In-Reply-To: <87k2shig1x.fsf@rustcorp.com.au>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Thu, Aug 27, 2015 at 12:38:42PM +0930, Rusty Russell via bitcoin-dev wrote:
> So I'd like an IsStandard() rule to say it nLockTime be 0 if an
> nSequence != 0xFFFFFFFF. Would that screw anyone currently?
That sentence doesn't quite parse ("say it nLockTime"), so please
forgive me if I'm misunderstanding you. Are you saying that you want
IsStandard() to require a transaction have a locktime of 0 (no
confirmation delay) if any of its inputs use a non-final sequence?
If so, wouldn't that make locktime useless for delaying confirmation in
IsStandard() transactions because the consensus rules require at least
one input be non-final in order for locktime to have any effect?
Thanks,
-Dave
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-08-27 11:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 11:06 [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime Btc Drak
2015-08-13 18:12 ` Mark Friedenbach
2015-08-13 19:20 ` Gregory Maxwell
2015-08-13 23:42 ` Joseph Poon
2015-08-14 0:47 ` Mark Friedenbach
2015-08-14 18:53 ` Matt Corallo
2015-08-14 21:29 ` Mark Friedenbach
2015-08-14 22:24 ` Jorge Timón
2015-08-17 19:58 ` Btc Drak
2015-08-19 10:37 ` Jorge Timón
2015-08-19 16:21 ` Mark Friedenbach
2015-08-19 21:27 ` Joseph Poon
2015-08-19 21:32 ` Jorge Timón
2015-08-20 21:23 ` Peter Todd
2015-08-24 0:25 ` Tom Harding
2015-08-24 1:01 ` Gregory Maxwell
2015-08-24 2:23 ` Jorge Timón
2015-08-24 2:37 ` Mark Friedenbach
2015-08-25 22:08 ` Mark Friedenbach
2015-08-25 22:36 ` Tier Nolan
2015-08-27 23:32 ` Mark Friedenbach
2015-09-16 22:40 ` Btc Drak
2015-09-16 23:23 ` Eric Lombrozo
2015-09-17 4:23 ` Mark Friedenbach
2015-09-18 1:21 ` Rusty Russell
2015-09-17 7:43 ` jl2012
2015-08-24 2:40 ` jl2012
2015-08-24 2:54 ` Mark Friedenbach
2015-08-24 7:00 ` jl2012
2015-08-25 10:15 ` Btc Drak
2015-08-27 3:08 ` Rusty Russell
2015-08-27 11:03 ` David A. Harding [this message]
2015-08-27 12:29 ` jl2012
2015-08-30 21:33 ` Rusty Russell
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=20150827110330.GA2842@localhost.localdomain \
--to=dave@dtrt.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=rusty@rustcorp.com.au \
/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