From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z6e6Z-0003ve-DH for bitcoin-development@lists.sourceforge.net; Sun, 21 Jun 2015 12:12:07 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=bbrelin@gmail.com; helo=mail-wg0-f53.google.com; Received: from mail-wg0-f53.google.com ([74.125.82.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z6e6U-0003kW-7g for bitcoin-development@lists.sourceforge.net; Sun, 21 Jun 2015 12:12:07 +0000 Received: by wguu7 with SMTP id u7so48667990wgu.3 for ; Sun, 21 Jun 2015 05:11:56 -0700 (PDT) X-Received: by 10.180.104.197 with SMTP id gg5mr23063864wib.27.1434888716215; Sun, 21 Jun 2015 05:11:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.154.137 with HTTP; Sun, 21 Jun 2015 05:11:36 -0700 (PDT) In-Reply-To: <558679AA.9010308@sky-ip.org> References: <558679AA.9010308@sky-ip.org> From: Braun Brelin Date: Sun, 21 Jun 2015 14:11:36 +0200 Message-ID: To: s7r@sky-ip.org Content-Type: multipart/alternative; boundary=f46d041825bc38eb1d05190610d0 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: 1Z6e6U-0003kW-7g Cc: Bitcoin Dev 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 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2015 12:12:07 -0000 --f46d041825bc38eb1d05190610d0 Content-Type: text/plain; charset=UTF-8 So, basically it sounds as though the wallet generating the transaction is what is responsible for holding on to the transaction and then only releasing it to the network when the NLOCKTIME value is less than or equal to the current time. Does that sound right? Braun On Sun, Jun 21, 2015 at 10:45 AM, s7r wrote: > 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==now). 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, > > > > 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 > > > > > > > > > ------------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > Bitcoin-development mailing list > > Bitcoin-development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > > --f46d041825bc38eb1d05190610d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
So, basically it sounds as though the wallet generating th= e transaction is what is responsible for holding on to the transaction and = then
only releasing it to the network when the NLOCKTIME value is less = than or equal to the current time.=C2=A0 Does that sound right? =C2=A0

Braun


On Sun, Jun 21, 2015 at 10:45 AM, s7r <= span dir=3D"ltr"><s7= r@sky-ip.org> wrote:
Hi

I don't think that a transaction with nLockTime>0 will be accepted b= y
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,
>
> When a transaction with N_LOCKTIME>0 is created, does that transact= ion
> 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?=C2= =A0 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?=C2=A0 I.e. if= I
> create a transaction that doesn't take effect for 10 years, and th= at
> transaction is stored in a block, does that block stay on the active > list for that period of time?
>
> Thanks,
>
> Braun Brelin
>
>
>
> ----------------------------------------------------------= --------------------
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-d= evelopment@lists.sourceforge.net
> https://lists.sourceforge.net/l= ists/listinfo/bitcoin-development
>

--f46d041825bc38eb1d05190610d0--