summaryrefslogtreecommitdiff
path: root/8d/5462191c65cfcfb68fafcae2bc8c5bcd431973
blob: 0dbb515974bf9e34777461096cdd7a91eda3ecdb (plain)
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
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 2C93F847
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  7 Aug 2015 17:00:14 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from manxnetsf05.manx.net (outbound.manx.net [213.137.31.12])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 94C06137
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  7 Aug 2015 17:00:12 +0000 (UTC)
Received: from 195.10.99.101 (EHLO coldstorage.localnet) ([195.10.99.101])
	by manxnetsf05.manx.net (MOS 4.4.5a-GA FastPath queued)
	with ESMTP id EFT85353; Fri, 07 Aug 2015 18:00:10 +0100 (BST)
From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Date: Fri, 07 Aug 2015 19:00:08 +0200
Message-ID: <3197878.6zmtLAPm4L@coldstorage>
User-Agent: KMail/4.14.1 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; )
In-Reply-To: <CAPg+sBiCH12i6-WEx++zTbovn=2FZqKAKxfnGkruU_Ah-y-_4g@mail.gmail.com>
References: <CAPg+sBj-wA1DMrwkQRWnzQoB5NR-q=2-5=WDAAUYfSpXRZSTqw@mail.gmail.com>
	<1542978.eROxFinZd4@coldstorage>
	<CAPg+sBiCH12i6-WEx++zTbovn=2FZqKAKxfnGkruU_Ah-y-_4g@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Mirapoint-Received-SPF: 195.10.99.101 coldstorage.localnet
	thomas@thomaszander.se 5 none
X-Junkmail-Status: score=10/50, host=manxnetsf05.manx.net
X-Junkmail-Signature-Raw: score=unknown,
	refid=str=0001.0A0B0205.55C4E41A.017F, ss=1, re=0.000, recu=0.000,
	reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0,
	so=2014-07-29 09:23:55, dmn=2013-03-21 17:37:32,
	mode=multiengine
X-Junkmail-IWF: false
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
	refid=str=0001.0A0B0205.55C4E41A.017F, ss=1, re=0.000, recu=0.000,
	reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0,
	so=2014-07-29 09:23:55, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: f02ffc3b2fb7ead4ffeb73bd283e3060
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] Fwd: Block size following technological growth
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: Fri, 07 Aug 2015 17:00:14 -0000

On Friday 7. August 2015 18.30.28 Pieter Wuille wrote:
> On Fri, Aug 7, 2015 at 6:06 PM, Thomas Zander via bitcoin-dev <
> > But your conclusion that low node count is an indication that its hard
> > to run one discards your own point.  You forget the point that running
> > a node is only needed if you don't know anyone you can trust to run it
> > for you.  I'm  pretty darn sure that this will have a bigger effect on
> > nodecount than how hard it is.
> 
> I never said it is the only factor that influences node count.

You wrote;
>  They are an indication of how hard [node count] is (for various 
>  reasons) to run/use a full node, and thus provide feedback.

You clearly indicated that node count is an indicator of how hard it is to run 
a node.
Thats like saying something is too expensive because we don't sell enough. It 
forgets to ask the question of need. Do people want it.

Like in our case the need to run a node in the first place.


> If the incentives for running a node don't weight up against the
> cost/difficulty using a full node yourself for a majority of people in the
> ecosystem, I would argue that there is a problem. As Bitcoin's fundamental
> improvement over other systems is the lack of need for trust, I believe
> that with increased adoption should also come an increased (in absolute
> terms) incentive for people to use a full node. I'm seeing the opposite
> trend, and that is worrying IMHO.

And you do the same thing again; you dismiss the need factor.

Most merchants have no need for a node, most miners don't even want to run one 
anymore. Users don't make a significant amount of payments to care.

Any conclusions with regards to difficulty of running a node based on max-
blocksize is speculation without numbers; the only numbers you have is 
historical node count, and they don't mean shit because the need has not 
grown.
For instance, merchants are told to trust someone like bitpay.


Historical node-count says nothing. Anyone using it for the blocksize debate 
is speculating without basis.
-- 
Thomas Zander