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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 248F99B
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Aug 2015 17:47:59 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com
[209.85.212.177])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 708A0265
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Aug 2015 17:47:58 +0000 (UTC)
Received: by wicne3 with SMTP id ne3so186994281wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Aug 2015 10:47:57 -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:date
:message-id:subject:from:to:cc:content-type;
bh=GiLqGbK9aEqvirwtdU84zQp/jsqcVki3Hm9DAJtvxSg=;
b=No4XsrIdlKB8igroXXhwpCTf9f274MtPvzBooE1eb+XM4S8un53CsnLoPMbuvLqEi2
iygVUKVdp1GQ2c8uJyvve6Sn89fuk6O/V55DxwrzxwlCsFPRo6OuX+ebJ74qzig8pUw+
LLnr5n1+z+D6/vp1TUeZVo9+jHZILCNh6haHXzTU11hHSgeJz7hJ4nK3bp+G+2xcSy77
b+vmLdw3W0ZSpkwWi5d6pt3h/wqb702aOCOWd9pDFjAQ1pIpeP5wSMEUX4OjylALAC03
WCAW5+HXzP5TrJuUkvTqsGRFoYRMb5adusB8yPB54xoloQi4POjyXHbmdAHXnw9gvtpC
Gjhw==
X-Gm-Message-State: ALoCoQlNTiK9BC1iI1/4FndqtGKZdK4nnXeMgBAapDCL+MkbsLR62NQaKsLNx/Hm4ccy0Dp+HxSW
MIME-Version: 1.0
X-Received: by 10.194.238.39 with SMTP id vh7mr56430041wjc.109.1439315276829;
Tue, 11 Aug 2015 10:47:56 -0700 (PDT)
Received: by 10.194.31.230 with HTTP; Tue, 11 Aug 2015 10:47:56 -0700 (PDT)
Received: by 10.194.31.230 with HTTP; Tue, 11 Aug 2015 10:47:56 -0700 (PDT)
In-Reply-To: <8181630.GdAj0CPZYc@coldstorage>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
<CABm2gDpwMQzju+Gsoe3qMi60MPr7OAiSuigy3RdA1xh-SwFzbw@mail.gmail.com>
<CABm2gDoz4NMEQuQj6UHCYYCwihZrEC4Az8xDvTBwiZDf9eQ7-w@mail.gmail.com>
<8181630.GdAj0CPZYc@coldstorage>
Date: Tue, 11 Aug 2015 19:47:56 +0200
Message-ID: <CABm2gDp2svO2G5bHs5AcjjN8dmP6P5nv0xriWez-pvzs2oBL5w@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Thomas Zander <thomas@thomaszander.se>
Content-Type: multipart/alternative; boundary=089e0141aa1acbad87051d0cb346
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fees and the block-finding process
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2015 17:47:59 -0000
--089e0141aa1acbad87051d0cb346
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Aug 11, 2015 12:14 AM, "Thomas Zander via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> On Monday 10. August 2015 13.55.03 Jorge Tim=C3=B3n via bitcoin-dev wrote=
:
> > Gavin, I interpret the absence of response to these questions as a
> > sign that everybody agrees that there's no other reason to increase
> > the consensus block size other than to avoid minimum market fees from
> > rising (above zero).
> > Feel free to correct that notion at any time by answering the
> > questions yourself.
> > In fact if any other "big block size advocate" thinks there's more
> > reason I would like to hear their reasons too.
>
> See my various emails in the last hour.
I've read them. I have read gavin's blog posts as well, several times.
I still don't see what else can we fear from not increasing the size apart
from fees maybe rising and making some problems that need to be solved
rewardless of the size more visible (like a dumb unbounded mempool design).
This discussion is frustrating for everyone. I could also say "This have
been explained many times" and similar things, but that's not productive.
I'm not trying to be obstinate, please, answer what else is to fear or
admit that all your feas are just potential consequences of rising fees.
With the risk of sounding condescending or aggressive...Really, is not that
hard to answer questions directly and succinctly. We should all be friends
with clarity. Only fear, uncertainty and doubt are enemies of clarity. But
you guys on the "bigger blocks side" don't want to spread fud, do you?
Please, prove paranoid people like me wrong on this point, for the good of
this discussion. I really don't know how else to ask this without getting a
link to something I have already read as a response.
--089e0141aa1acbad87051d0cb346
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr"><br>
On Aug 11, 2015 12:14 AM, "Thomas Zander via bitcoin-dev" <<a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.lin=
uxfoundation.org</a>> wrote:<br>
><br>
> On Monday 10. August 2015 13.55.03 Jorge Tim=C3=B3n via bitcoin-dev wr=
ote:<br>
> > Gavin, I interpret the absence of response to these questions as =
a<br>
> > sign that everybody agrees that=C2=A0 there's no other reason=
to increase<br>
> > the consensus block size other than to avoid minimum market fees =
from<br>
> > rising (above zero).<br>
> > Feel free to correct that notion at any time by answering the<br>
> > questions yourself.<br>
> > In fact if any other "big block size advocate" thinks t=
here's more<br>
> > reason I would like to hear their reasons too.<br>
><br>
> See my various emails in the last hour.</p>
<p dir=3D"ltr">I've read them. I have read gavin's blog posts as we=
ll, several times.<br>
I still don't see what else can we fear from not increasing the size ap=
art from fees maybe rising and making some problems that need to be solved =
rewardless of the size more visible (like a dumb unbounded mempool design).=
</p>
<p dir=3D"ltr">This discussion is frustrating for everyone. I could also sa=
y "This have been explained many times" and similar things, but t=
hat's not productive.<br>
I'm not trying to be obstinate, please, answer what else is to fear or =
admit that all your feas are just potential consequences of rising fees.</p=
>
<p dir=3D"ltr">With the risk of sounding condescending or aggressive...Real=
ly, is not that hard to answer questions directly and succinctly. We should=
all be friends with clarity. Only fear, uncertainty and doubt are enemies =
of clarity. But you guys on the "bigger blocks side" don't wa=
nt to spread fud, do you?<br>
Please, prove paranoid people like me wrong on this point, for the good of =
this discussion. I really don't know how else to ask this without getti=
ng a link to something I have already read as a response.<br>
</p>
--089e0141aa1acbad87051d0cb346--
|
