Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 192E9E36 for ; Thu, 27 Aug 2015 11:04:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.dtrt.org (mail.dtrt.org [207.192.75.234]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B212D115 for ; Thu, 27 Aug 2015 11:04:33 +0000 (UTC) Received: from harding by mail.dtrt.org with local (Exim 4.72) (envelope-from ) id 1ZUuyt-0004Ov-Uk; Thu, 27 Aug 2015 07:04:31 -0400 Date: Thu, 27 Aug 2015 07:03:30 -0400 From: "David A. Harding" To: Rusty Russell Message-ID: <20150827110330.GA2842@localhost.localdomain> References: <55DA6470.9040301@thinlink.com> <85537faedb1e601d243e3edb666fa844@xbt.hk> <87k2shig1x.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <87k2shig1x.fsf@rustcorp.com.au> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime 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: Thu, 27 Aug 2015 11:04:34 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Aug 27, 2015 at 12:38:42PM +0930, Rusty Russell via bitcoin-dev wrote: > So I'd like an IsStandard() rule to say it nLockTime be 0 if an > nSequence != 0xFFFFFFFF. Would that screw anyone currently? That sentence doesn't quite parse ("say it nLockTime"), so please forgive me if I'm misunderstanding you. Are you saying that you want IsStandard() to require a transaction have a locktime of 0 (no confirmation delay) if any of its inputs use a non-final sequence? If so, wouldn't that make locktime useless for delaying confirmation in IsStandard() transactions because the consensus rules require at least one input be non-final in order for locktime to have any effect? Thanks, -Dave --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV3u6CAAoJEEspww/ynsS3VQ8H/1rIFyKlm5e0/5qk5Xzm90pU CinrCp0cySbglxfTPgpBq7YifXyQGn6lZGrhJ199VUZtnbjezCb+fGTClbogn78d 4X5gRIsxTK6QmI/RdcUuBDPb7sVfdauF2OODRh/NM9F/hqDEjLWaWWC8i2W8J2ml iuBFtkObG+uNjAEJ1l4mYMvyAfyi/BBNqq4ci+Zj2CnfYTEATVdYViS5BFc8Pzsj cOMyDqAzGokJCOwKhN7Dovz98AqUCS4MQw6lPVB8TeRlyXok5JeqS4oW4ER6XBd5 e0QgOyXay8vW13XI2beyrz5Zb890ZFvz0sk3wX9UktdSm9j1e7d7i/sUE38/t+A= =y/le -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--