From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YxdEp-0005g2-1A for bitcoin-development@lists.sourceforge.net; Wed, 27 May 2015 15:27:23 +0000 X-ACL-Warn: Received: from mail-ig0-f174.google.com ([209.85.213.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YxdEk-0007DC-QK for bitcoin-development@lists.sourceforge.net; Wed, 27 May 2015 15:27:23 +0000 Received: by igbpi8 with SMTP id pi8so89515046igb.0 for ; Wed, 27 May 2015 08:27:13 -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=CLoEx8svcUkGptdCY2LrPcn+kDz+bKHZeJhzWxBfEVE=; b=GEX36SxuN54YFmw15qSv1WUFdk0g6CI++yURA0NC1T9gZSLuey8vrSOPoClKdQUGJm TCqJXc4ppJPyYFdVX53+mbgDj2I05UCG0JKHjD1AmcxYo32RLi3tKqmBVxxcsjkLnifR 6EKh810YUw3I6KIAKLhHme2+bQlD351yP3/SFcNi5CZK1qIgp1a7jYYqW2aTj8atUVbH 59C+Stvj4WbmigwlTG9aBNUlCvpje3qkk/83LgOFXy+wRdDoRcn3QcwEyTLI+kPlGzFz Sn+mFaX089qEGSKpnerWw4ktlG+ELuoXf5LVGalGfFHB/N/UkVjTLWXuL0e2YEwCJATp wrcA== X-Gm-Message-State: ALoCoQlxyus2/hCFx7ttH/luV9kSkFep5Ny6gZhHxojSFwygf7IcjdtINpjFGP5irxfDJ3uNVB1P X-Received: by 10.50.142.9 with SMTP id rs9mr4915117igb.17.1432740433453; Wed, 27 May 2015 08:27:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.10.197 with HTTP; Wed, 27 May 2015 08:26:52 -0700 (PDT) X-Originating-IP: [172.56.9.144] In-Reply-To: References: From: Mark Friedenbach Date: Wed, 27 May 2015 08:26:52 -0700 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=001a11c2ff1c977833051711e0ee X-Spam-Score: 1.5 (+) 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 0.5 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YxdEk-0007DC-QK Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Consensus-enforced transaction replacement via sequence numbers 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, 27 May 2015 15:27:23 -0000 --001a11c2ff1c977833051711e0ee Content-Type: text/plain; charset=UTF-8 On Wed, May 27, 2015 at 3:11 AM, Mike Hearn wrote: > > As I believe out of all proposed protocols Satoshi's is still the most > powerful, I would suggest that any change to the semantics on nSequence be > gated by a high bit or something, so the original meaning remains available > if/when resource scheduling and update flood damping are implemented. That > way people can try it out and if miners are breaking things too frequently > by ignoring the chronological ordering people can abandon protocols that > rely on it, and if they aren't they can proceed and benefit from the > greater flexibility. > > Mike, this proposal was purposefully constructed to maintain as well as possible the semantics of Satoshi's original construction. Higher sequence numbers -- chronologically later transactions -- are able to hit the chain earlier, and therefore it can be reasonably argued will be selected by miners before the later transactions mature. Did I fail in some way to capture that original intent? --001a11c2ff1c977833051711e0ee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Wed, May 27, 2015 at 3:11 AM, Mike Hearn <mike@plan99.ne= t> wrote:

As I beli= eve out of all proposed protocols Satoshi's is still the most powerful,= I would suggest that any change to the semantics on nSequence be gated by = a high bit or something, so the original meaning remains available if/when = resource scheduling and update flood damping are implemented. That way peop= le can try it out and if miners are breaking things too frequently by ignor= ing the chronological ordering people can abandon protocols that rely on it= , and if they aren't they can proceed and benefit from the greater flex= ibility.


Mike, this proposal= was purposefully constructed to maintain as well as possible the semantics= of Satoshi's original construction. Higher sequence numbers -- chronol= ogically later transactions -- are able to hit the chain earlier, and there= fore it can be reasonably argued will be selected by miners before the late= r transactions mature. Did I fail in some way to capture that original inte= nt?
--001a11c2ff1c977833051711e0ee--