1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
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 <mark@friedenbach.org>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP0QMHp9PwBr=ekkujtA+=LXbgiL4xkXRSmcOGqaLJEp0g@mail.gmail.com>
References: <CAOG=w-sfiUQQGUh=RR55NU-TkAi1+2g3_Z+YP3dGDjp8zXYBGQ@mail.gmail.com>
<CANEZrP0QMHp9PwBr=ekkujtA+=LXbgiL4xkXRSmcOGqaLJEp0g@mail.gmail.com>
From: Mark Friedenbach <mark@friedenbach.org>
Date: Wed, 27 May 2015 08:26:52 -0700
Message-ID: <CAOG=w-s7JkB6SyEE0=KwmrasyH22aB2Zf3jBdKcXvrGoNhN_Nw@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
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 <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <mike@plan99.net> 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
<div dir=3D"ltr">On Wed, May 27, 2015 at 3:11 AM, Mike Hearn <span dir=3D"l=
tr"><<a href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.ne=
t</a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote"><span class=3D""></span><div>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.</div><div><br></div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">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?<br></div></div>
--001a11c2ff1c977833051711e0ee--
|
