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
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
|
Return-Path: <gubatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9AD39414
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Apr 2017 13:47:52 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f182.google.com (mail-io0-f182.google.com
[209.85.223.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7E4FC169
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Apr 2017 13:47:51 +0000 (UTC)
Received: by mail-io0-f182.google.com with SMTP id k87so22010754ioi.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Apr 2017 06:47:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=FVVJV+BzICX1mo+zK9P7F2I8EmKMy3OauolcjzfRa9o=;
b=M029VYuyf5QwI16FET2gCRFCsj/1RN5b42OyTSpr323nfg2aP0/ZaFs8pSwHK/Ib3P
AgVPryPHqvkDX9liblzkxFOsJxsCNizONXHp83GvfCDxIcUQyzBkMZNkLg0XmqyWTZSq
AgkId/LJw1Osfcpvqsx+AjmfmQS0ijcamtLHJ7QczQGT3768OjbIc94DEGsOi4frnv1l
DOoH0lE5fz7qIaZMoksHDnbnGIZrR65FI0HzbK5kGK8WZog8G2ujaW4OILFV4MNClF+Q
RCsdDO34D/ODTvz2Dk0W5/ON7fchd/G1EUV7N2Ri1fFXYkZRiCyiFuxOlohJn3tuUG/j
0itQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=FVVJV+BzICX1mo+zK9P7F2I8EmKMy3OauolcjzfRa9o=;
b=tD7qAH+poa6zNy/Ojgy0Sf3aqI9yuH4lgvdZHzgrH/cemwYB1GUQB+xY+0MPxSPZQw
xViws3liZdmdeVM/WTVGkbBc2OBNV/P4l5rw+B+Olp21xix1aYN9FirpBE/vNZRWR9NV
RvhfIwxDFa/2DC3RvVkZWGkc4fDukesXte3SXFvED0q3scdlYBf5N0hNGP95yQolVFH8
ZZQOaMtEY8bdJnRG1iHhVbChBOY4NJPCfyP9L8mcYeWivHtGSKMDufUFAIP8wDk/aZD7
ovQnEmRAAJBiH5B7sItfW5Y/kCbFE5r35znRos+9ZNG+nOgC7jYxnbMO5wEqxm0znfJ8
KACw==
X-Gm-Message-State: AN3rC/5GK4SEGw1kqR+zK1/g8TXwKwb6Gi4D4fXKFh0wwiJExWHfbbkd
USmmVtjgubf1tqiY/MVQzoHYgDjH4Q==
X-Received: by 10.107.163.140 with SMTP id m134mr3378221ioe.74.1492609670869;
Wed, 19 Apr 2017 06:47:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAFVRnypbQQ-vsSLqv48cYaqTCty4R1DmFRqfAvxe4mAqyQNXxQ@mail.gmail.com>
<2226058.Q8lHjYE4Pt@strawberry>
<CAE-z3OVXLKqyBb3R5yzOYdnRALot4KUhJ53r9y2jXkf6Yt=KnA@mail.gmail.com>
<ccb96920-4387-ed91-e03e-15f4b2772aa3@gmail.com>
<q2ESXdrCKqIkoFBVplGtaRC5yHXvrZHmWW5uixMP0Gw64KHhsH6GaZ_Ap-PouUSze4pf4mFmdyniT2CVKVX0kYUdQ1qJZxYAnBsmsCPuYEQ=@protonmail.ch>
In-Reply-To: <q2ESXdrCKqIkoFBVplGtaRC5yHXvrZHmWW5uixMP0Gw64KHhsH6GaZ_Ap-PouUSze4pf4mFmdyniT2CVKVX0kYUdQ1qJZxYAnBsmsCPuYEQ=@protonmail.ch>
From: Angel Leon <gubatron@gmail.com>
Date: Wed, 19 Apr 2017 13:47:40 +0000
Message-ID: <CADZB0_bgD9BoJVJOK1S-LXZ+Mikabj9CZZoMY7OorxtR6HVhXA@mail.gmail.com>
To: udevNull <udevnull@protonmail.ch>, "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11406f3c387b0a054d8545bc
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 19 Apr 2017 15:01:06 +0000
Subject: Re: [bitcoin-dev] Small Nodes: A Better Alternative to Pruned Nodes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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, 19 Apr 2017 13:47:52 -0000
--001a11406f3c387b0a054d8545bc
Content-Type: text/plain; charset=UTF-8
>Financially incentivising nodes is a really weird area because it would
allow someone to essentially automate the deployment of nodes. i.e. if a
node can pay for itself 100% (even at a lesser value, it just becomes
cheaper overall), you could write an application that uses an AWS API or a
digital ocean API to automatically deploy 100's of nodes. Which sounds
great but not if that person is malicious and wants to prevent the
community adopting proposals.
what other projects have done to avoid such attacks (while incentivizing
economically running full nodes) is to only distribute part of the block
rewards back such nodes if that node has committed/frozen a predetermined
amount of coins that can't be spent. This also leaves less liquidity for
market speculation and a incentives for long term commitments.
On Wed, Apr 19, 2017 at 5:14 AM udevNull via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I'd like to add to this. There is definitely a barrier of entry with
> regards to setting up a full node. Unless you're living in a first world
> country, the bandwidth requirements alone, will outright prevent you from
> even setting up a full node (sync since genesis).
>
> To maintain that also becomes a sunk cost, as there is no financial
> incentive to run a node, only an idealogical one. Most of the people who
> benefit and will benefit from Bitcoin, are the un-banked. Which you will
> find in 3rd world countries, that don't have ISPs that provide the data
> packages, to cater for the requirements of running a full node. I'm sure
> many would like to, but simply cannot afford it.
>
> A user may not want to run a node at home, but rather on a digital ocean
> or AWS server, which they cannot afford to do either considering the
> bandwidth and storage costs associated with it. However, I don't think they
> should be excluded from participating in the network (supporting proposals,
> voicing their opinions, running their own wallets, writing their own
> applications on top of Bitcoin [which I think is extremely important]).
>
> So I would definitely be in favour of a small node of sorts. It will
> present us with some interesting technical challenges along the way but
> it's definitely worth while looking into.
>
> Financially incentivising nodes is a really weird area because it would
> allow someone to essentially automate the deployment of nodes. i.e. if a
> node can pay for itself 100% (even at a lesser value, it just becomes
> cheaper overall), you could write an application that uses an AWS API or a
> digital ocean API to automatically deploy 100's of nodes. Which sounds
> great but not if that person is malicious and wants to prevent the
> community adopting proposals.
> Just my 2 cents worth.
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a11406f3c387b0a054d8545bc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">><span style=3D"color:rgb(33,33,33)">Financially incent=
ivising nodes is a really weird area because it would allow someone to esse=
ntially automate the deployment of nodes. i.e. if a node can pay for itself=
100% (even at a lesser value, it just becomes cheaper overall), you could =
write an application that uses an AWS API or a digital ocean API to automat=
ically deploy 100's of nodes. Which sounds great but not if that person=
is malicious and wants to prevent the community adopting proposals.</span>=
<br><br>what other projects have done to avoid such attacks (while incentiv=
izing economically running full nodes) is to only distribute part of the bl=
ock rewards back such nodes if that node has committed/frozen a predetermin=
ed amount of coins that can't be spent. This also leaves less liquidity=
for market speculation and a incentives for long term commitments.</div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Apr 19, 2017 at 5:14 =
AM udevNull via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfo=
undation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><p>I'd like to add to this. There is de=
finitely a barrier of entry
with regards to setting up a full node. Unless you're living in a
first world country, the bandwidth requirements alone, will
outright prevent you from even setting up a full node (sync since
genesis).<br></p><p>To maintain that also becomes a sunk cost, as the=
re is no
financial incentive to run a node, only an idealogical one. Most
of the people who benefit and will benefit from Bitcoin, are the
un-banked. Which you will find in 3rd world countries, that don't
have ISPs that provide the data packages, to cater for the
requirements of running a full node. I'm sure many would like to,
but simply cannot afford it.<br></p><p>A user may not want to run a n=
ode at home, but rather on a
digital ocean or AWS server, which they cannot afford to do either
considering the bandwidth and storage costs associated with it.
However, I don't think they should be excluded from participating
in the network (supporting proposals, voicing their opinions,
running their own wallets, writing their own applications on top
of Bitcoin [which I think is extremely important]).<br></p><p>So I wo=
uld definitely be in favour of a small node of sorts. It will present us wi=
th some interesting technical challenges
along the way but it's definitely worth while looking into.<br></=
p><p>Financially incentivising nodes is a really weird area because it
would allow someone to essentially automate the deployment of
nodes. i.e. if a node can pay for itself 100% (even at a lesser
value, it just becomes cheaper overall), you could write an
application that uses an AWS API or a digital ocean API to
automatically deploy 100's of nodes. Which sounds great but not i=
f
that person is malicious and wants to prevent the community
adopting proposals.<br></p><div>Just my 2 cents worth.<br></div><div>=
<br></div><div class=3D"m_4346759367992423716protonmail_signature_block"><d=
iv class=3D"m_4346759367992423716protonmail_signature_block-user m_43467593=
67992423716protonmail_signature_block-empty"><br></div><div class=3D"m_4346=
759367992423716protonmail_signature_block-proton">Sent with <a href=3D"http=
s://protonmail.com" target=3D"_blank">ProtonMail</a> Secure Email.<br></div=
></div><div><br></div>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--001a11406f3c387b0a054d8545bc--
|
