Return-Path: <achow101@gmail.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E170C1004 for <bitcoin-dev@lists.linuxfoundation.org>; 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 <bitcoin-dev@lists.linuxfoundation.org>; Sat, 23 Jan 2016 04:42:06 +0000 (UTC) Received: by mail-vk0-f46.google.com with SMTP id e185so51317927vkb.1 for <bitcoin-dev@lists.linuxfoundation.org>; 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: <CADToNK-O-KWZjLzKAcUz9CZB65to=bCgTfRLTVFhLVKcCjO5bA@mail.gmail.com> <20160123041042.GA5956@localhost.localdomain> In-Reply-To: <20160123041042.GA5956@localhost.localdomain> From: Andrew C <achow101@gmail.com> Date: Sat, 23 Jan 2016 04:41:55 +0000 Message-ID: <CADToNK96HTcz+pjdQgo7XO2wNhaTkCsAHWbO=WZNPKM0_L4MwQ@mail.gmail.com> To: "David A. Harding" <dave@dtrt.org> 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 <bitcoin-dev@lists.linuxfoundation.org> 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 <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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 <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 > > --001a1143e54229f60a0529f8f530 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Ahh. I see. Thanks, I must have missed that when going thr= ough the BIP. Guess I need to read more carefully next time.<div><br></div>= <div>Thanks,</div><div>Andrew</div></div><br><div class=3D"gmail_quote"><di= v dir=3D"ltr">On Fri, Jan 22, 2016 at 11:11 PM David A. Harding <<a href= =3D"mailto:dave@dtrt.org">dave@dtrt.org</a>> wrote:<br></div><blockquote= class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli= d;padding-left:1ex">On Fri, Jan 22, 2016 at 04:36:58PM +0000, Andrew C via = bitcoin-dev wrote:<br> > 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<br> > MAX_INT.<br> <br> Hi Andrew,<br> <br> Opt-in RBF requires setting nSequence to less than MAX-1 (not merely<br> less than MAX), so an nSequence of exactly MAX-1 (which appears in<br> hex-encoded serialized transactions as feffffff) enables locktime<br> enforcement but doesn't opt in to RBF.<br> <br> For more information, please see BIP125:<br> <br> =C2=A0 =C2=A0 <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-01= 25.mediawiki" rel=3D"noreferrer" target=3D"_blank">https://github.com/bitco= in/bips/blob/master/bip-0125.mediawiki</a><br> <br> -Dave<br> <br> </blockquote></div> --001a1143e54229f60a0529f8f530--