From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqpJS-0007ay-FM for bitcoin-development@lists.sourceforge.net; Fri, 08 May 2015 20:56:02 +0000 X-ACL-Warn: Received: from mail-ie0-f171.google.com ([209.85.223.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YqpJO-0001eF-5D for bitcoin-development@lists.sourceforge.net; Fri, 08 May 2015 20:56:02 +0000 Received: by iecnq11 with SMTP id nq11so73073282iec.3 for ; Fri, 08 May 2015 13:55:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=4GcN9oRRe527xayf+wOyjiroi9Fs4AtfTNxzokKR4g8=; b=brDsTKcGMTlL6QrCbQT/09eiQ7xPaXRc6mv1E7VQfZxhnhH0TrIrxc87AW7kQp3BKq WX/pPUXi91C47ySYcDwrLp4DjUmA7/6ergesG1cMw/RBsKUkp2NvOkVjjG1Wl/hMqnuM AoubJkn+xjd1LSo0cedOF6Wg1VWOFAvWUTYy+ivHeP0fp8aqK2Jn1djRaWOQE/uiGQPN vtg23FxMq3+t/hG86o3fjW0sOwQJn83xq4DncOQ3qc5XiOatGHszgrnyVAId0ftVY7LK nzTqXgaI3ashTpWWnrjeyt2yhKYY8RTH3d+H/4WdqQoPzE8yfakezR6BcBLAuYImQLDO /y2w== X-Gm-Message-State: ALoCoQk4xKkQykIYTXCX6CSCL4AsVVSapcQPbM28wleIFmGib8eFQZWcxyeDsqNsF/LHtIzqoze0 X-Received: by 10.107.131.87 with SMTP id f84mr7696855iod.50.1431118550816; Fri, 08 May 2015 13:55:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.25.203 with HTTP; Fri, 8 May 2015 13:55:30 -0700 (PDT) X-Originating-IP: [173.228.107.141] In-Reply-To: References: From: Mark Friedenbach Date: Fri, 8 May 2015 13:55:30 -0700 Message-ID: To: Raystonn Content-Type: multipart/alternative; boundary=001a113ecdc4da70b805159840c5 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1YqpJO-0001eF-5D Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Block Size Increase 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: Fri, 08 May 2015 20:56:02 -0000 --001a113ecdc4da70b805159840c5 Content-Type: text/plain; charset=UTF-8 The problems with that are larger than time being unreliable. It is no longer reorg-safe as transactions can expire in the course of a reorg and any transaction built on the now expired transaction is invalidated. On Fri, May 8, 2015 at 1:51 PM, Raystonn wrote: > Replace by fee is what I was referencing. End-users interpret the old > transaction as expired. Hence the nomenclature. An alternative is a new > feature that operates in the reverse of time lock, expiring a transaction > after a specific time. But time is a bit unreliable in the blockchain > --001a113ecdc4da70b805159840c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The problems with that are larger than time being unreliab= le. It is no longer reorg-safe as transactions can expire in the course of = a reorg and any transaction built on the now expired transaction is invalid= ated.

On = Fri, May 8, 2015 at 1:51 PM, Raystonn <raystonn@hotmail.com> wrote:
Replace by fee is what I was r= eferencing.=C2=A0 End-users interpret the old transaction as expired.=C2=A0= Hence the nomenclature.=C2=A0 An alternative is a new feature that operate= s in the reverse of time lock, expiring a transaction after a specific time= .=C2=A0 But time is a bit unreliable in the blockchain
--001a113ecdc4da70b805159840c5--