From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z6at1-000770-Hu for bitcoin-development@lists.sourceforge.net; Sun, 21 Jun 2015 08:45:55 +0000 Received-SPF: neutral (sog-mx-2.v43.ch3.sourceforge.com: 162.222.225.19 is neither permitted nor denied by domain of sky-ip.org) client-ip=162.222.225.19; envelope-from=s7r@sky-ip.org; helo=outbound.mailhostbox.com; Received: from outbound.mailhostbox.com ([162.222.225.19]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Z6asr-0002p2-3Q for bitcoin-development@lists.sourceforge.net; Sun, 21 Jun 2015 08:45:55 +0000 Received: from [0.0.0.0] (tor27.anonymizer.ccc.de [77.244.254.227]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: s7r@sky-ip.org) by outbound.mailhostbox.com (Postfix) with ESMTPSA id 12C37781EAA; Sun, 21 Jun 2015 08:45:36 +0000 (GMT) Message-ID: <558679AA.9010308@sky-ip.org> Date: Sun, 21 Jun 2015 11:45:30 +0300 From: s7r User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Braun Brelin , Bitcoin Dev References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=I/SYP4Ug c=1 sm=1 tr=0 a=BXGLLuvM07WwAyUGa8zKJg==:117 a=BXGLLuvM07WwAyUGa8zKJg==:17 a=-NIMs_s3AAAA:8 a=QrohdLjRRo4A:10 a=N659UExz7-8A:10 a=bvjBBkZ6AAAA:8 a=FP58Ms26AAAA:8 a=gQLlWfzH2aSrdKnDWvMA:9 a=XBTVs8mnPPYbqt7Q:21 a=8TZ80MGjebXacolH:21 a=pILNOxqGKmIA:10 X-CTCH-RefID: str=0001.0A020203.558679B3.009A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CTCH-SenderID: s7r@sky-ip.org X-CTCH-SenderID-TotalMessages: 1 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalRecipients: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-BlueWhiteFlag: 0 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.8 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [162.222.225.19 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.7 SPF_NEUTRAL SPF: sender does not match SPF record (neutral) 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Headers-End: 1Z6asr-0002p2-3Q Subject: Re: [Bitcoin-development] Question regarding transactions with NLOCKTIME > 0 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: s7r@sky-ip.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 08:45:55 -0000 Hi I don't think that a transaction with nLockTime>0 will be accepted by nodes / relayed in the Bitcoin network, until its time expires (e.g. nLockTime=3D=3Dnow). This means it obviously cannot be stored in a block, before its locktime expires. nLockTime is designed in a way that you, need to keep it offline (not broadcast it to the network because it won't be accepted or relayed by nodes) until the locktime expires, then you can broadcast it and it will be mined and included in a block, like a normal tx. This is exactly why Peter Todd and others are working on CHECKLOCKTIMEVERIFY and RELATIVE CHECKLOCKTIMEVERIFY - this is an enhancement to basic nLockTime which tends to offer to users the guarantee that if you have a transaction with nLockTime, the signer holding the private keys used to sign it cannot sign another one, with nLockTime 0 and broadcast it before the locktime for your tx expires. Cheers! On 6/21/2015 10:10 AM, Braun Brelin wrote: > Hi all,=20 >=20 > When a transaction with N_LOCKTIME>0 is created, does that transaction > get stored in a block on the blockchain or is it stored in the mempool > until the actual time (or block number) exceeds the current value? If > it is stored on the blockchain, how does that affect the concept of > pruning that is supposed to be going in to version 0.11? I.e. if I > create a transaction that doesn't take effect for 10 years, and that > transaction is stored in a block, does that block stay on the active > list for that period of time? >=20 > Thanks, >=20 > Braun Brelin >=20 >=20 >=20 > -----------------------------------------------------------------------= ------- >=20 >=20 >=20 > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >=20