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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
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 <rick.wesson@iidf.org>) id 1QwHRi-0006FG-KO
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Aug 2011 17:40:58 +0000
X-ACL-Warn:
Received: from mail-gy0-f175.google.com ([209.85.160.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QwHRf-0002QY-KX
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Aug 2011 17:40:58 +0000
Received: by gyg4 with SMTP id 4so1321080gyg.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 24 Aug 2011 10:40:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.43.45.68 with SMTP id uj4mr4761678icb.87.1314207649958; Wed,
24 Aug 2011 10:40:49 -0700 (PDT)
Received: by 10.42.244.130 with HTTP; Wed, 24 Aug 2011 10:40:49 -0700 (PDT)
In-Reply-To: <CAAS2fgTARAMqMu79Sp4XS4KxmUBWiXebpavHWr-EdLZbxS=sTw@mail.gmail.com>
References: <CABsx9T1uw43JuvhEmJP0KCyojsDi1r7v6BaLBHz7wWazduE5iw@mail.gmail.com>
<201108241215.36847.luke@dashjr.org>
<CAAS2fgQspsXy1Vw=fNr1FvsDRkEbP6dEcFLgUpK9DrBKXyiWNg@mail.gmail.com>
<CAJ1JLtsxPG9v-Hwdb-pfgY6GU0Z4it+frFzw_tObVbNC6Xgdjw@mail.gmail.com>
<CAAS2fgTARAMqMu79Sp4XS4KxmUBWiXebpavHWr-EdLZbxS=sTw@mail.gmail.com>
Date: Wed, 24 Aug 2011 10:40:49 -0700
Message-ID: <CAJ1JLttqEnCjALadESmpntxSobD8Lj1zcXL4S7ghqdhyBrwVNw@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec51a76ec230cbd04ab43d0da
X-Spam-Score: 1.3 (+)
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.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QwHRf-0002QY-KX
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] New standard transaction types: time to
schedule a blockchain split?
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, 24 Aug 2011 17:40:58 -0000
--bcaec51a76ec230cbd04ab43d0da
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Aug 24, 2011 at 10:19 AM, Gregory Maxwell <gmaxwell@gmail.com>wrote:
> On Wed, Aug 24, 2011 at 1:07 PM, Rick Wesson
> <rick@support-intelligence.com> wrote:
> > On Wed, Aug 24, 2011 at 9:46 AM, Gregory Maxwell <gmaxwell@gmail.com>
> wrote:
> >> On Wed, Aug 24, 2011 at 12:15 PM, Luke-Jr <luke@dashjr.org> wrote:
> >>
> >> > - Replace hard limits (like 1 MB maximum block size) with something
> that
> >> > can
> >> > dynamically adapt with the times. Maybe based on difficulty so it
> can't
> >> > be
> >> > gamed?
> >> Too early for that.
> > Could you provide a reference to why in your estimation it is "to early."
> > Simpy stating this as fact isn't enough to sway demand.
>
> Can you provide a reference to this 'demand' a post by Luke isn't
> enough to support the claim of demand.
>
> how about trend, its a hard limit and as you acknowledged below we are not
there yet; however the trend is for more transactions and we will bump into
the limit. Being good architects we should consider how to scale or
explicitly state why its a good idea not to.
-rick
> We're not at maximum size right now (thankfully).
>
> We don't know what the network dynamics would look like at that
> traffic level. So how could we competently say what the right metrics
> would be to get the right behavior there? Thats what I meant by too
> early.
>
no one ever "knows" what the network dynamics are going to be in developing
infrastructure -- so lets not kid our selves, in being able to estimate this
before the code is even written.
-rick
--bcaec51a76ec230cbd04ab43d0da
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Wed, Aug 24, 2011 at 10:19 AM, Gregor=
y Maxwell <span dir=3D"ltr"><<a href=3D"mailto:gmaxwell@gmail.com">gmaxw=
ell@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Wed, Aug 24, 2011 at 1:07 PM, Rick Wesson<br>
<<a href=3D"mailto:rick@support-intelligence.com">rick@support-intellige=
nce.com</a>> wrote:<br>
> On Wed, Aug 24, 2011 at 9:46 AM, Gregory Maxwell <<a href=3D"mailto=
:gmaxwell@gmail.com">gmaxwell@gmail.com</a>> wrote:<br>
>> On Wed, Aug 24, 2011 at 12:15 PM, Luke-Jr <<a href=3D"mailto:lu=
ke@dashjr.org">luke@dashjr.org</a>> wrote:<br>
>><br>
>> > - Replace hard limits (like 1 MB maximum block size) with som=
ething that<br>
>> > can<br>
>> > dynamically adapt with the times. Maybe based on difficulty s=
o it can't<br>
>> > be<br>
>> > gamed?<br>
>> Too early for that.<br>
> Could you provide a=A0reference=A0to why in your estimation it is &quo=
t;to early."<br>
> =A0Simpy stating this as fact isn't enough to sway demand.<br>
<br>
</div>Can you provide a reference to this 'demand' a post by Luke i=
sn't<br>
enough to support the claim of demand.<br>
<br></blockquote><div>how about trend, its a hard limit and as you=A0acknow=
ledged=A0below we are not there yet; however the trend is for more transact=
ions and we will bump into the limit. Being good architects we should consi=
der how to scale or explicitly state why its a good idea not to.</div>
<div><br></div><div>-rick</div><div><br></div><div>=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex;">
We're not at maximum size right now (thankfully).<br>
<br>
We don't know what the network dynamics would look like at that<br>
traffic level. So how could we competently say what the right metrics<br>
would be to get the right behavior there? =A0Thats what I meant by too<br>
early.<br>
</blockquote></div><br><div>no one ever "knows" what the network =
dynamics are going to be in developing infrastructure -- so lets not kid ou=
r selves, in being able to estimate this before the code is even written.</=
div>
<div><br></div><div>-rick</div><div><br></div>
--bcaec51a76ec230cbd04ab43d0da--
|
