public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andrew C <achow101@gmail.com>
To: "David A. Harding" <dave@dtrt.org>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] nSequence multiple uses
Date: Sat, 23 Jan 2016 04:41:55 +0000	[thread overview]
Message-ID: <CADToNK96HTcz+pjdQgo7XO2wNhaTkCsAHWbO=WZNPKM0_L4MwQ@mail.gmail.com> (raw)
In-Reply-To: <20160123041042.GA5956@localhost.localdomain>

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

Ahh. I see. Thanks, I must have missed that when going through the BIP.
Guess I need to read more carefully next time.

Thanks,
Andrew

On Fri, Jan 22, 2016 at 11:11 PM David A. Harding <dave@dtrt.org> wrote:

> On Fri, Jan 22, 2016 at 04:36:58PM +0000, Andrew C via bitcoin-dev wrote:
> > Spending a time locked output requires setting nSequence to less than
> > MAX_INT but opting into RBF also requires setting nSequence to less than
> > MAX_INT.
>
> Hi Andrew,
>
> Opt-in RBF requires setting nSequence to less than MAX-1 (not merely
> less than MAX), so an nSequence of exactly MAX-1 (which appears in
> hex-encoded serialized transactions as feffffff) enables locktime
> enforcement but doesn't opt in to RBF.
>
> For more information, please see BIP125:
>
>     https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
>
> -Dave
>
>

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

      reply	other threads:[~2016-01-23  4:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 16:36 [bitcoin-dev] nSequence multiple uses Andrew C
2016-01-23  4:10 ` David A. Harding
2016-01-23  4:41   ` Andrew C [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='CADToNK96HTcz+pjdQgo7XO2wNhaTkCsAHWbO=WZNPKM0_L4MwQ@mail.gmail.com' \
    --to=achow101@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dave@dtrt.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