From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E170C1004 for ; Sat, 23 Jan 2016 04:42:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 461A513C for ; Sat, 23 Jan 2016 04:42:06 +0000 (UTC) Received: by mail-vk0-f46.google.com with SMTP id e185so51317927vkb.1 for ; Fri, 22 Jan 2016 20:42:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=Zd4bgPUOiBsNoKFeVA7jqN8nuspoF9CorMhYv4rNT88=; b=p7CaDCr4LOCUE/Cc3SvMz7onbBjyFryZ5OYijUHSavEOR3qWEgvqMjh5wuEK9KDUH1 yMCbXmzmmokH3PTMK6FX6PJU3kWT/h4FIK0Mk9R9p7rObrUrCHuzXt+YkzEhhyGTKgXD cL332b3EvXgazSv3i18BGNikBmzvECE2B3rSmR1qyUVv1wCJEzXCS7RGKYZqYKzrBTZN KvruSgBUxN0Qb4FeIHAQRugg2qoTVCg62T5BZoDfezbXozlHuZ8BmQs/CW/NmJZxiJ7G Wis8GW80yqg8s9FwvKv/2bqjVqN5kUmphmcAwG5R2zIw73R/ACGLOjp3aP0AdQSm9BNG oThg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=Zd4bgPUOiBsNoKFeVA7jqN8nuspoF9CorMhYv4rNT88=; b=WztFoEyio2JriOD2MfZPN9Be+KSD6TbGQz7sKJ39I0bKfhtvnnCgYvPMz1EfubMJdQ IOp6gq5pI+bPtS9H3bKzDkQUmVFE3yTc9hXU447DwK4R8zGhoQq7yzhcqleE7luMbIMW 2C94/owS1vrOGU7Pe2pF8WrcHIPgKq1AW57EdXHEgGlbjcXySfX66gQHhRC18/1ngLcj WUplEY5H0SSONwDxjYH0xJbiRpy7bmNaGbURTiHq5KgPLI3FalcHcl8Mg8daki9HVMRY mLTDf8TTW9dy0TQliz8+34pZY5s33jG1bYrkcyXALGekehmAND0gpCgToNq26fooDPjR NF9Q== X-Gm-Message-State: AG10YORYDLvJ++4hyfMXIeTNMsWhMC6fxEFKrWEas2eiFYSNybnWOC+dvxIG2OzEFgMzf0/N3f/s1qRiQMtaOw== X-Received: by 10.31.52.195 with SMTP id b186mr3936667vka.39.1453524125347; Fri, 22 Jan 2016 20:42:05 -0800 (PST) MIME-Version: 1.0 References: <20160123041042.GA5956@localhost.localdomain> In-Reply-To: <20160123041042.GA5956@localhost.localdomain> From: Andrew C Date: Sat, 23 Jan 2016 04:41:55 +0000 Message-ID: To: "David A. Harding" Content-Type: multipart/alternative; boundary=001a1143e54229f60a0529f8f530 X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sat, 23 Jan 2016 04:49:51 +0000 Cc: Bitcoin development mailing list Subject: Re: [bitcoin-dev] nSequence multiple uses X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2016 04:42:07 -0000 --001a1143e54229f60a0529f8f530 Content-Type: text/plain; charset=UTF-8 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 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 > > --001a1143e54229f60a0529f8f530 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ahh. I see. Thanks, I must have missed that when going thr= ough 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<= br> > MAX_INT but opting into RBF also requires setting nSequence to less th= an
> 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:

=C2=A0 =C2=A0 https://github.com/bitco= in/bips/blob/master/bip-0125.mediawiki

-Dave

--001a1143e54229f60a0529f8f530--