Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z6ZOw-0003sN-VB for bitcoin-development@lists.sourceforge.net; Sun, 21 Jun 2015 07:10:46 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.181 as permitted sender) client-ip=209.85.212.181; envelope-from=bbrelin@gmail.com; helo=mail-wi0-f181.google.com; Received: from mail-wi0-f181.google.com ([209.85.212.181]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z6ZOw-0007xX-3W for bitcoin-development@lists.sourceforge.net; Sun, 21 Jun 2015 07:10:46 +0000 Received: by wicgi11 with SMTP id gi11so49344453wic.0 for ; Sun, 21 Jun 2015 00:10:40 -0700 (PDT) X-Received: by 10.194.205.101 with SMTP id lf5mr41299520wjc.37.1434870640106; Sun, 21 Jun 2015 00:10:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.154.137 with HTTP; Sun, 21 Jun 2015 00:10:20 -0700 (PDT) From: Braun Brelin Date: Sun, 21 Jun 2015 09:10:20 +0200 Message-ID: To: Bitcoin Dev Content-Type: multipart/alternative; boundary=047d7bb03db2cd6202051901daae X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (bbrelin[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z6ZOw-0007xX-3W Subject: [Bitcoin-development] Question regarding transactions with NLOCKTIME > 0 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 07:10:47 -0000 --047d7bb03db2cd6202051901daae Content-Type: text/plain; charset=UTF-8 Hi all, 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? Thanks, Braun Brelin --047d7bb03db2cd6202051901daae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,=C2=A0

When a transaction with N= _LOCKTIME>0 is created, does that transaction get stored in a block on t= he blockchain or is it stored in the mempool until the actual time (or bloc= k number) exceeds the current value?=C2=A0 If it is stored on the blockchai= n, how does that affect the concept of pruning that is supposed to be going= in to version 0.11?=C2=A0 I.e. if I create a transaction that doesn't = take effect for 10 years, and that transaction is stored in a block, does t= hat block stay on the active list for that period of time?

Thanks,

Braun Brelin

=
--047d7bb03db2cd6202051901daae--