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
|
Return-Path: <thomas@thomaszander.se>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9751A892
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 16:24:29 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from pmx.vmail.no (pmx.vmail.no [193.75.16.11])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 411AC144
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 16:24:27 +0000 (UTC)
Received: from pmx.vmail.no (localhost [127.0.0.1])
by localhost (pmx.isp.as2116.net) with SMTP id 76EA461F41
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 18:24:26 +0200 (CEST)
Received: from smtp.bluecom.no (smtp.bluecom.no [193.75.75.28])
by pmx.vmail.no (pmx.isp.as2116.net) with ESMTP id 41A1E5F165
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 18:24:26 +0200 (CEST)
Received: from pluto.localnet (unknown [81.191.177.169])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.bluecom.no (Postfix) with ESMTPS id 319D892
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 18:24:25 +0200 (CEST)
From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Date: Wed, 12 Aug 2015 18:24:24 +0200
Message-ID: <4999292.m94ooXBn8O@pluto>
User-Agent: KMail/4.14.1 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; )
In-Reply-To: <CABm2gDqhoDrQAVAE4oedHEK2s_iYwPAADVZVj2zb940eG2hGBQ@mail.gmail.com>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
<1963286.x5NhlJ5RfS@pluto>
<CABm2gDqhoDrQAVAE4oedHEK2s_iYwPAADVZVj2zb940eG2hGBQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
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: Wed, 12 Aug 2015 16:24:29 -0000
On Wednesday 12. August 2015 11.45.53 Jorge Tim=F3n wrote:
> This question had been dodged repeatedly (one more time in this last
> response).=20
This "last response" had a very direct answer to your question, why do =
you=20
think it was dodged?
I wrote; "To buy more time, get bigger blocks now." (quoted from parent=
-of-
parent)
But also said here;
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/0101=
29.html
and here;
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/0101=
86.html
> Then we could go one by one and classify them as:
>=20
> 1) Potential indirect consequence of rising fees.
I have not made any arguments that fall within this section.
> 2) Software problem independent of a concrete block size that needs t=
o
> be solved anyway
I'd like to suggest that number two is not described narrowly enough. T=
his=20
includes everything that we need, ever will need and want in the future=
...
2) Testing and architectural improvements related to nodes that get mor=
e=20
transactions than can be handled for a considerable time.
This includes problems we don't know of yet, since we haven't run under=
=20
these conditions before.
> If you think there's more "problem groups", please let me know.
> Otherwise I don't see the point in repeating the question. I have not=
> received a straight answer but you think you've given it.
I quoted one such answer above, would be interested in knowing how you=20=
missed it.
Here is another one from 2 hours before that email;
"All the banks, nasdaq, countries, businesses etc etc
"now contemplating using Bitcoin itself will see this as a risk too bi=
g to
"ignore and the 1Mb Bitcoin will loose 99% of its perceived value."
source; http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-Aug=
ust/010180.html
> Seems like a dead end.
After repeating some answers you said were missing, it would be nice to=
=20
know where the connection drops.
Maybe you don't understand what people answer, if so, please ask to exp=
lain=20
instead of saying people are dodging the question. ;)
--=20
Thomas Zander
|
