Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Yq7W1-0000De-Uv for bitcoin-development@lists.sourceforge.net; Wed, 06 May 2015 22:10:05 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.44 as permitted sender) client-ip=209.85.192.44; envelope-from=tier.nolan@gmail.com; helo=mail-qg0-f44.google.com; Received: from mail-qg0-f44.google.com ([209.85.192.44]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yq7W0-0001eP-SL for bitcoin-development@lists.sourceforge.net; Wed, 06 May 2015 22:10:05 +0000 Received: by qgeb100 with SMTP id b100so12210588qge.3 for ; Wed, 06 May 2015 15:09:59 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.55.15.15 with SMTP id z15mr2051454qkg.21.1430950199443; Wed, 06 May 2015 15:09:59 -0700 (PDT) Received: by 10.140.85.241 with HTTP; Wed, 6 May 2015 15:09:59 -0700 (PDT) In-Reply-To: References: <20141001130826.GM28710@savin.petertodd.org> <55075795.20904@bluematt.me> <20150421075912.GA25282@savin.petertodd.org> <5546D653.4070404@bluematt.me> Date: Wed, 6 May 2015 23:09:59 +0100 Message-ID: From: Tier Nolan Cc: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11475dda54467a0515710e1a X-Spam-Score: 1.8 (+) 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 (tier.nolan[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header 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 1.2 MALFORMED_FREEMAIL Bad headers on message from free email service X-Headers-End: 1Yq7W0-0001eP-SL Subject: Re: [Bitcoin-development] Relative CHECKLOCKTIMEVERIFY (was CLTV proposal) 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: Wed, 06 May 2015 22:10:06 -0000 --001a11475dda54467a0515710e1a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, May 6, 2015 at 8:37 AM, Jorge Tim=C3=B3n wrote: > > This gives you less flexibility and I don't think it's necessary. > Please let's try to avoid this if it's possible. It is just a switch that turns on and off the new mode. In retrospect, it would be better to just up the transaction version. In transactions from v2 onwards, the sequence field means height. That means legacy transactions would be spendable. This is a pure soft-fork. --001a11475dda54467a0515710e1a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On W= ed, May 6, 2015 at 8:37 AM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote:

This gives you less flexibility and I don't think it's neces= sary.
Please let's try to avoid this if it's possible.
<= br>
It is just a switch that turns on and off the new mode.
In retrospect, it would be better to just up the transaction v= ersion.=C2=A0

In transactions from v2 onwards, the sequence field m= eans height.=C2=A0 That means legacy transactions would be spendable.
This is a pure soft-fork.
--001a11475dda54467a0515710e1a--