public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Harding <tomh@thinlink.com>
To: Mark Friedenbach <mark@friedenbach.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 68 (Relative Locktime) bug
Date: Sun, 05 Jul 2015 12:57:00 -0700	[thread overview]
Message-ID: <55998C0C.5050207@thinlink.com> (raw)
In-Reply-To: <55998AA3.4060801@thinlink.com>

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]


Never mind that last bit.  I overlooked that the other inputs can
independently make the tx non-final.

On 7/5/2015 12:50 PM, Tom Harding wrote:
>
> It would also allow an explicit relative locktime of 0, which would
> help applications avoid accidentally finalizing the whole transaction
> when they only meant to not impose a relative locktime on one input.


[-- Attachment #2: Type: text/html, Size: 758 bytes --]

      reply	other threads:[~2015-07-05 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 15:00 [bitcoin-dev] BIP 68 (Relative Locktime) bug Tom Harding
2015-07-05 16:17 ` Mark Friedenbach
2015-07-05 16:21   ` Pieter Wuille
2015-07-05 16:25   ` Tom Harding
2015-07-05 17:07 ` Mark Friedenbach
2015-07-05 19:50   ` Tom Harding
2015-07-05 19:57     ` Tom Harding [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=55998C0C.5050207@thinlink.com \
    --to=tomh@thinlink.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=mark@friedenbach.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