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
|
Return-Path: <eric@voskuil.org>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id D36F5C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 6 Feb 2022 19:14:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id BBB37813A3
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 6 Feb 2022 19:14:31 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=voskuil-org.20210112.gappssmtp.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id rglhi1Y0krow
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 6 Feb 2022 19:14:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com
[IPv6:2607:f8b0:4864:20::102f])
by smtp1.osuosl.org (Postfix) with ESMTPS id C6BB881395
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 6 Feb 2022 19:14:30 +0000 (UTC)
Received: by mail-pj1-x102f.google.com with SMTP id
v15-20020a17090a4ecf00b001b82db48754so11364522pjl.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 06 Feb 2022 11:14:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=voskuil-org.20210112.gappssmtp.com; s=20210112;
h=content-transfer-encoding:from:mime-version:subject:date:message-id
:references:cc:in-reply-to:to;
bh=Fjm3fjYmUQ+7aYUCjde5Mem51C8ka+dChJYkuHpVXvE=;
b=TqXnjA2vWdGAKXe3EuaNZLqA/LAXt5YriFmYZ5qGSV+VuYyeBoDKYI6vUWqkfvAgoO
BeIRlaQKifQdkYY1y+JEVyrLD4NkvPFaEdDjK5fAc3fFeLJ+ROBQYkU2cLbx7gRGKu/N
pj7h0954Jl42IcL5T+JBYE6GN71YeOSvUz6s5ENucAH5U1ivPXAbtUsC9Bh/qGwlq2cQ
AoM1cO82DVOqRZq6JyYLHdcY97o5xdaSeTx2HO7wgj/vxrTe/ZKrsGBWwl6yv05OU6k2
kfS1wEUzfzPzNih41pyYsrRmbnsLVAkkTR/NXOXJu+Pfo1OqCTX2u7PteLdkYMQ5iWUb
ZmEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:content-transfer-encoding:from:mime-version
:subject:date:message-id:references:cc:in-reply-to:to;
bh=Fjm3fjYmUQ+7aYUCjde5Mem51C8ka+dChJYkuHpVXvE=;
b=iWkEIoCKk6Tb7WxQ+HVVqPpiMHauZ9h0G+SNVNiq0Jo3tLxi6s2da2qZyJKGsPsYlr
PiM+dzOHcDEDym9A+IxtnMQtJauUQM7yW+pIJAYw2vf7POnoZxR8LJemsL9ZASUL6H13
izByYS2sKwUoNpcLz35hQXc+SP2ZCM5REIdvnRG9PP9AOmwMbimEgOV7UY1bPnP8qOmF
14dhdgReOhxkUkuW4Uo5tLxpZ1fHintciHUwJTbgRT6mmvECa26XUvMxARyyM7jGhL8Z
t9h8VTadzYRxy3FB5GAiQ/Lwd/JEyXE+W1kZptjwvlgOg/6WDmqrAHmL833FjCWCiehd
lyqg==
X-Gm-Message-State: AOAM530pbKYZlQlGs70nmpl1l3hyGFc9MgKSPE5fV7Aiui62Cx2Bh4Tq
L8iukEUdLBPCWtgL9ka3EDXiyg==
X-Google-Smtp-Source: ABdhPJwpk7fhhmdmuLjk9Hu8Ebf7uFRQOlcSbt8+wX1Eb6azAj8qpbDQfvsta9Du/ms+A9kOuVp67Q==
X-Received: by 2002:a17:903:110d:: with SMTP id
n13mr12818402plh.5.1644174870053;
Sun, 06 Feb 2022 11:14:30 -0800 (PST)
Received: from smtpclient.apple ([2601:600:9c00:1d0::ff78])
by smtp.gmail.com with ESMTPSA id z25sm8965804pfg.129.2022.02.06.11.14.29
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Sun, 06 Feb 2022 11:14:29 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Eric Voskuil <eric@voskuil.org>
Mime-Version: 1.0 (1.0)
Date: Sun, 6 Feb 2022 11:14:28 -0800
Message-Id: <86BAFB7B-5ECB-4790-A19B-6E296A063C59@voskuil.org>
References: <c7bdbBVd0KmLFPUeYk0QUdni7tbDwJSj4HGLlEOkdPzIYzOyaX147HWJPKE-isTL267nQeJds8-rsKNyzRrBhucsZvwZcg5dZjQxDnbwxAA=@wuille.net>
In-Reply-To: <c7bdbBVd0KmLFPUeYk0QUdni7tbDwJSj4HGLlEOkdPzIYzOyaX147HWJPKE-isTL267nQeJds8-rsKNyzRrBhucsZvwZcg5dZjQxDnbwxAA=@wuille.net>
To: Pieter Wuille <bitcoin-dev@wuille.net>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (19C63)
Subject: Re: [bitcoin-dev] A suggestion to periodically destroy (or remove
to secondary storage for Archiving reasons) dust,
Non-standard UTXOs, and also detected burn
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 06 Feb 2022 19:14:31 -0000
> On Feb 6, 2022, at 10:52, Pieter Wuille via bitcoin-dev <bitcoin-dev@lists=
.linuxfoundation.org> wrote:
>=20
> =EF=BB=BF
>> Dear Bitcoin Developers,
>=20
>> -When I contacted bitInfoCharts to divide the first interval of addresses=
, they kindly did divided to 3 intervals. =46rom here:
>> https://bitinfocharts.com/top-100-richest-bitcoin-addresses.html
>> -You can see that there are more than 3.1m addresses holding =E2=89=A4 0.=
000001 BTC (1000 Sat) with total value of 14.9BTC; an average of 473 Sat per=
address.
>=20
>> -Therefore, a simple solution would be to follow the difficulty adjustmen=
t idea and just delete all those
>=20
> That would be a soft-fork, and arguably could be considered theft. While c=
ommonly (but non universally) implemented standardness rules may prevent spe=
nding them currently, there is no requirement that such a rule remain in pla=
ce. Depending on how feerate economics work out in the future, such outputs m=
ay not even remain uneconomical to spend. Therefore, dropping them entirely f=
rom the UTXO set is potentially destroying potentially useful funds people o=
wn.
>=20
>> or at least remove them to secondary storage
>=20
> Commonly adopted Bitcoin full nodes already have two levels of storage eff=
ectively (disk and in-RAM cache). It may be useful to investigate using amou=
nt as a heuristic about what to keep and how long. IIRC, not even every full=
node implementation even uses a UTXO model.
You recall correctly. Libbitcoin has never used a UTXO store. A full node ha=
s no logical need for an additional store of outputs, as transactions alread=
y contain them, and a full node requires all of them, spent or otherwise.
The hand-wringing over UTXO set size does not apply to full nodes, it is rel=
evant only to pruning. Given linear worst case growth, even that is ultimate=
ly a non-issue.
>> for Archiving with extra cost to get them back, along with non-standard U=
TXOs and Burned ones (at least for publicly known, published, burn addresses=
).
>=20
> Do you mean this as a standardness rule, or a consensus rule?
>=20
> * As a standardness rule it's feasible, but it makes policy (further) devi=
ate from economically rational behavior. There is no reason for miners to re=
quire a higher price for spending such outputs.
> * As a consensus rule, I expect something like this to be very controversi=
al. There are currently no rules that demand any minimal fee for anything, a=
nd given uncertainly over how fee levels could evolve in the future, it's un=
clear what those rules, if any, should be.
>=20
> Cheers,
>=20
> --
> Pieter
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
