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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jim@ergophobia.org>) id 1Yr9E9-00042q-GB
for bitcoin-development@lists.sourceforge.net;
Sat, 09 May 2015 18:11:53 +0000
X-ACL-Warn:
Received: from mail-wi0-f182.google.com ([209.85.212.182])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yr9E7-0001aN-1M
for bitcoin-development@lists.sourceforge.net;
Sat, 09 May 2015 18:11:53 +0000
Received: by wiun10 with SMTP id n10so57871852wiu.1
for <bitcoin-development@lists.sourceforge.net>;
Sat, 09 May 2015 11:11:45 -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:from:date:message-id:subject:to
:content-type;
bh=4yO9UmCKO0aJc6VAtLRmZputtZZ/2B6AKEb21dxUt3g=;
b=Pc2COMR/0K3LkOhAE/djrvXFC8G+Rj7jXTy75TXx3eRTaBIIorColbtLaIybf29gcW
npVBcyWWUjQSrYs7uKUDdGcQG/sGocQrk3YqKBoDSO/67896la0MrTfVzKu4GImwmGRT
JcEtf9p5AmlahVUzCO5kE6F/Iwpj65CazS+ZNYLZK5jVXaYrSTymEu9yJUSNsQOUboS1
w5dmtKrbdXtiKyvKa9er4mTE8WpH650HGcgZL+8XZn5Eg4aG889Rqr9FCbciwS0K9T9D
ZbyDiCpFbjDiUhlRxwDjGYKKRrwaXHVskhWac8urOxbzqfMRSPF1POmcYOLIa1pA369Z
raEw==
X-Gm-Message-State: ALoCoQmACXNGra4AsodFRcKmj3HP3t5TabOLxHgwTerz0tXHPZqcYTBa0mU2h9Bid22jZJ3piuHn
X-Received: by 10.180.37.207 with SMTP id a15mr7317397wik.2.1431191402964;
Sat, 09 May 2015 10:10:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.246.69 with HTTP; Sat, 9 May 2015 10:09:32 -0700 (PDT)
From: Jim Phillips <jim@ergophobia.org>
Date: Sat, 9 May 2015 12:09:32 -0500
Message-ID: <CANe1mWzBy8-C+CWfwaOLxJ2wokjy8ytQUh2TkRY_Ummn1BpPzw@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=e89a8f6473eb2dffab0515a93714
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
0.0 T_REMOTE_IMAGE Message contains an external image
X-Headers-End: 1Yr9E7-0001aN-1M
Subject: [Bitcoin-development] A suggestion for reducing the size of the
UTXO database
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 09 May 2015 18:11:53 -0000
--e89a8f6473eb2dffab0515a93714
Content-Type: text/plain; charset=UTF-8
Forgive me if this idea has been suggested before, but I made this
suggestion on reddit and I got some feedback recommending I also bring it
to this list -- so here goes.
I wonder if there isn't perhaps a simpler way of dealing with UTXO growth.
What if, rather than deal with the issue at the protocol level, we deal
with it at the source of the problem -- the wallets. Right now, the typical
wallet selects only the minimum number of unspent outputs when building a
transaction. The goal is to keep the transaction size to a minimum so that
the fee stays low. Consequently, lots of unspent outputs just don't get
used, and are left lying around until some point in the future.
What if we started designing wallets to consolidate unspent outputs? When
selecting unspent outputs for a transaction, rather than choosing just the
minimum number from a particular address, why not select them ALL? Take all
of the UTXOs from a particular address or wallet, send however much needs
to be spent to the payee, and send the rest back to the same address or a
change address as a single output? Through this method, we should wind up
shrinking the UTXO database over time rather than growing it with each
transaction. Obviously, as Bitcoin gains wider adoption, the UTXO database
will grow, simply because there are 7 billion people in the world, and
eventually a good percentage of them will have one or more wallets with
spendable bitcoin. But this idea could limit the growth at least.
The vast majority of users are running one of a handful of different wallet
apps: Core, Electrum; Armory; Mycelium; Breadwallet; Coinbase; Circle;
Blockchain.info; and maybe a few others. The developers of all these
wallets have a vested interest in the continued usefulness of Bitcoin, and
so should not be opposed to changing their UTXO selection algorithms to one
that reduces the UTXO database instead of growing it.
From the miners perspective, even though these types of transactions would
be larger, the fee could stay low. Miners actually benefit from them in
that it reduces the amount of storage they need to dedicate to holding the
UTXO. So miners are incentivized to mine these types of transactions with a
higher priority despite a low fee.
Relays could also get in on the action and enforce this type of behavior by
refusing to relay or deprioritizing the relay of transactions that don't
use all of the available UTXOs from the addresses used as inputs. Relays
are not only the ones who benefit the most from a reduction of the UTXO
database, they're also in the best position to promote good behavior.
--
*James G. Phillips IV*
<https://plus.google.com/u/0/113107039501292625391/posts>
*"Don't bunt. Aim out of the ball park. Aim for the company of immortals."
-- David Ogilvy*
*This message was created with 100% recycled electrons. Please think twice
before printing.*
--e89a8f6473eb2dffab0515a93714
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Forgive me if this idea has been suggested before, bu=
t I made this suggestion on reddit and I got some feedback recommending I a=
lso bring it to this list -- so here goes.</div><div><br></div><div>I wonde=
r if there isn't perhaps a simpler way of dealing with UTXO growth. Wha=
t if, rather than deal with the issue at the protocol level, we deal with i=
t at the source of the problem -- the wallets. Right now, the typical walle=
t selects only the minimum number of unspent outputs when building a transa=
ction. The goal is to keep the transaction size to a minimum so that the fe=
e stays low. Consequently, lots of unspent outputs just don't get used,=
and are left lying around until some point in the future.</div><div><br></=
div><div>What if we started designing wallets to consolidate unspent output=
s? When selecting unspent outputs for a transaction, rather than choosing j=
ust the minimum number from a particular address, why not select them ALL? =
Take all of the UTXOs from a particular address or wallet, send however muc=
h needs to be spent to the payee, and send the rest back to the same addres=
s or a change address as a single output? Through this method, we should wi=
nd up shrinking the UTXO database over time rather than growing it with eac=
h transaction. Obviously, as Bitcoin gains wider adoption, the UTXO databas=
e will grow, simply because there are 7 billion people in the world, and ev=
entually a good percentage of them will have one or more wallets with spend=
able bitcoin. But this idea could limit the growth at least.</div><div><br>=
</div><div>The vast majority of users are running one of a handful of diffe=
rent wallet apps: Core, Electrum; Armory; Mycelium; Breadwallet; Coinbase; =
Circle; Blockchain.info; and maybe a few others. The developers of all thes=
e wallets have a vested interest in the continued usefulness of Bitcoin, an=
d so should not be opposed to changing their UTXO selection algorithms to o=
ne that reduces the UTXO database instead of growing it.</div><div><br></di=
v><div>From the miners perspective, even though these types of transactions=
would be larger, the fee could stay low. Miners actually benefit from them=
in that it reduces the amount of storage they need to dedicate to holding =
the UTXO. So miners are incentivized to mine these types of transactions wi=
th a higher priority despite a low fee.</div><div><br></div><div>Relays cou=
ld also get in on the action and enforce this type of behavior by refusing =
to relay or deprioritizing the relay of transactions that don't use all=
of the available UTXOs from the addresses used as inputs. Relays are not o=
nly the ones who benefit the most from a reduction of the UTXO database, th=
ey're also in the best position to promote good behavior.</div><div><di=
v class=3D"gmail_signature"><div><br></div><div>--<div><b>James G. Phillips=
IV</b>=C2=A0<a href=3D"https://plus.google.com/u/0/113107039501292625391/p=
osts" style=3D"font-size:x-small" target=3D"_blank"><img src=3D"https://ssl=
.gstatic.com/images/icons/gplus-16.png"></a>=C2=A0</div></div><div><font si=
ze=3D"1"><i>"Don't bunt. Aim out of the ball park. Aim for the com=
pany of immortals." -- David Ogilvy<br></i></font><div><font size=3D"1=
"><br></font></div></div><div><font size=3D"1"><img src=3D"http://findicons=
.com/files/icons/1156/fugue/16/leaf.png">=C2=A0<em style=3D"font-family:ver=
dana,geneva,sans-serif;line-height:16px;color:green;background-color:rgb(25=
5,255,255)">This message was created with 100% recycled electrons. Please t=
hink twice before printing.</em></font></div></div></div>
</div>
--e89a8f6473eb2dffab0515a93714--
|
