summaryrefslogtreecommitdiff
path: root/cb/9cb55fa32cced5c5e38bcf26e9e5afbcbbe8bd
blob: 650f18267411af1ef8ed2c13969f44f1b307bf56 (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
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: <lvella@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id A6F69B14
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Jul 2017 20:00:04 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com
	[209.85.215.50])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 13A4E3D9
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Jul 2017 20:00:04 +0000 (UTC)
Received: by mail-lf0-f50.google.com with SMTP id l200so27116773lfb.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Jul 2017 13:00:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=X32iI9zQRmo62FC5XJUZyhiV2ppqmEhkpQC92zbK7Ts=;
	b=mMNJgz/XR9WQiOMtI+q7XdfHEJCLKWMOElStIBxr+6cP3Vb/vzHLcK2jOIN+4QrOxo
	MejgLz7F/p4r/Kn29iFpYgpWu2V3s8TsXk8ytlJu4eaov0DNyxvM3+m0csKlQwu3jR4e
	0v4KmgCTrh6Coq+kfV/w1z+E0jWBw2TBEWNHeFXAQD9Lvtkc1lte9dBchE+43f20s0Gn
	tWStr5u1jmcS/k17ZeIrlUnPHRWOrmRM7DDdT+i02ytNu2I3J2VoqZ6S+KACQBUvG5Do
	RQeEQMG+vOCyUnEf2Qr3JHw8VGCloG0Q7s+cRR0dtivtpSySIBQBVBHvcWzgIlujT5Y4
	w6Qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=X32iI9zQRmo62FC5XJUZyhiV2ppqmEhkpQC92zbK7Ts=;
	b=cTrjrNuaLQG4AVUWA4jPY6a346U4SVKDpqXvqa+fgKG7cDcQoOZf+HQzYN9dK5xiF9
	Ocr4JaMSG/wO27XKW4bYS8vFyO1q6+671PtnCkJFDud2DmsmqlHRdFp9dS9NQ0zGvgjh
	+HT5W7F4Sqaoxjp5cJDiGh5vEp19tGULjSh0pTg5wshxlFPglceNjYQigzgd82nCmF4X
	5tNHFEtpXCmwO+KcDTN7P0SiHwTwKyo+WM6XxBd5caBDFJH155S4gujxQqjsU8PZonzX
	ghFUjWtJqnAJPJwjRcsEf4GSpumO8MdVxtIjCZukqrHOaiLEkp1S8iUdAXbXF//ht20T
	apjw==
X-Gm-Message-State: AIVw1133lT9+bbosOln5D6G5iHNcWYKnUXpm7TKuY0ReasFzJ09ZKSsU
	Tq7kmXSw4bv+RqRpQsKScjbUjZWmkQ==
X-Received: by 10.46.84.72 with SMTP id y8mr2941511ljd.101.1500667202523; Fri,
	21 Jul 2017 13:00:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.43.208 with HTTP; Fri, 21 Jul 2017 12:59:42 -0700 (PDT)
In-Reply-To: <CAAU88OoR7U3-hg9Mbf6iNB2V-V5Omd1y2UP7hwouc0jbwPPqgg@mail.gmail.com>
References: <CAAU88OoR7U3-hg9Mbf6iNB2V-V5Omd1y2UP7hwouc0jbwPPqgg@mail.gmail.com>
From: Lucas Clemente Vella <lvella@gmail.com>
Date: Fri, 21 Jul 2017 16:59:42 -0300
Message-ID: <CAGCathzWMVsmM1wO8eYAZmytEy1Q--ajdr0ssQHedaJWEPu0PA@mail.gmail.com>
To: Major Kusanagi <majorkusanagibtc@gmail.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="f403045fb62e8857640554d94f5f"
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: Fri, 21 Jul 2017 20:05:35 +0000
Subject: Re: [bitcoin-dev] UTXO growth scaling solution proposal
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: Fri, 21 Jul 2017 20:00:04 -0000

--f403045fb62e8857640554d94f5f
Content-Type: text/plain; charset="UTF-8"

2017-07-21 16:28 GMT-03:00 Major Kusanagi via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org>:

> [...] But the fact is that if we want to make bitcoins last forever, we
> have the accept unbounded UTXO growth, which is unscalable. So the only
> solution is to limit UTXO growth, meaning bitcoins cannot last forever.
> This proposed solution however does not prevent Bitcoin from lasting
> forever.
>

Unless there is a logical contradiction in this phrasing, the proposed
solution does not improves scalability:
 - "Bitcoins lasting forever" implies "unscalable";
 - "not prevent Bitcoin from lasting forever" implies "Bitcoins lasting
forever";
 - Thus: "not prevent Bitcoin from lasting forever" implies "unscalable".

In practice, the only Bitcoin lost would be those whose owners forgot about
or has lost the keys, because everyone with a significant amount of
Bitcoins would always shift them around before it loses any luster (I
wouldn't bother to move my Bitcoins every 10 years). I don't know how to
estimate the percentage of UTXO is actually lost/forgotten, but I have the
opinion it isn't worth the hassle.

As a side note, your estimate talks about block size, which is determines
blockchain size, which can be "safely" pruned (if you are not considering
new nodes might want to join the network, in case the full history is
needed to be stored somewhere). But UTXO size, albeit related to the full
blockchain size, is the part that currently can not be safely pruned, so I
don't see the relevance of the analysis.

-- 
Lucas Clemente Vella
lvella@gmail.com

--f403045fb62e8857640554d94f5f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">2017=
-07-21 16:28 GMT-03:00 Major Kusanagi via bitcoin-dev <span dir=3D"ltr">&lt=
;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank"=
>bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span>:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div><div><div><div>[...] But the fact is =
that if we want to make bitcoins last forever, we have the accept unbounded=
 UTXO growth, which is unscalable. So the only solution is to limit UTXO gr=
owth, meaning bitcoins cannot last forever. This proposed solution however =
does not prevent Bitcoin from lasting forever.<br></div></div></div></div><=
/blockquote><div>=C2=A0</div></div>Unless there is a logical contradiction =
in this phrasing, the proposed solution does not improves scalability:<br>=
=C2=A0- &quot;Bitcoins lasting forever&quot; implies &quot;unscalable&quot;=
;<br>=C2=A0- &quot;not prevent Bitcoin from lasting forever&quot; implies &=
quot;Bitcoins lasting forever&quot;;<br></div><div class=3D"gmail_extra">=
=C2=A0- Thus: &quot;not prevent Bitcoin from lasting forever&quot; implies =
&quot;unscalable&quot;.<br></div><div class=3D"gmail_extra"><br></div><div =
class=3D"gmail_extra">In practice, the only Bitcoin lost would be those who=
se owners forgot about or has lost the keys, because everyone with a signif=
icant amount of Bitcoins would always shift them around before it loses any=
 luster (I wouldn&#39;t bother to move my Bitcoins every 10 years). I don&#=
39;t know how to estimate the percentage of UTXO is actually lost/forgotten=
, but I have the opinion it isn&#39;t worth the hassle.<br></div><div class=
=3D"gmail_extra"><br clear=3D"all"></div><div class=3D"gmail_extra">As a si=
de note, your estimate talks about block size, which is determines blockcha=
in size, which can be &quot;safely&quot; pruned (if you are not considering=
 new nodes might want to join the network, in case the full history is need=
ed to be stored somewhere). But UTXO size, albeit related to the full block=
chain size, is the part that currently can not be safely pruned, so I don&#=
39;t see the relevance of the analysis.<br></div><div class=3D"gmail_extra"=
><br>-- <br><div class=3D"gmail_signature">Lucas Clemente Vella<br><a href=
=3D"mailto:lvella@gmail.com" target=3D"_blank">lvella@gmail.com</a></div>
</div></div>

--f403045fb62e8857640554d94f5f--