From: "David A. Harding" <dave@dtrt•org>
To: Andrew C <achow101@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] nSequence multiple uses
Date: Fri, 22 Jan 2016 23:10:42 -0500 [thread overview]
Message-ID: <20160123041042.GA5956@localhost.localdomain> (raw)
In-Reply-To: <CADToNK-O-KWZjLzKAcUz9CZB65to=bCgTfRLTVFhLVKcCjO5bA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-23 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 16:36 Andrew C
2016-01-23 4:10 ` David A. Harding [this message]
2016-01-23 4:41 ` Andrew C
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=20160123041042.GA5956@localhost.localdomain \
--to=dave@dtrt$(echo .)org \
--cc=achow101@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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