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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 90D81C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 03:36:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 6AC9640158
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 03:36:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 2.098
X-Spam-Level: **
X-Spam-Status: No, score=2.098 tagged_above=-999 required=5
tests=[BAYES_50=0.8, BITCOIN_SPAM_04=1, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id nvv8IQVwuEQc
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 03:36:29 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch
[185.70.40.132])
by smtp2.osuosl.org (Postfix) with ESMTPS id 3087840126
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Feb 2022 03:36:29 +0000 (UTC)
Date: Fri, 18 Feb 2022 03:36:19 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1645155385;
bh=sPbXV2mZPnXuzVkvVipdLe8B46V9qEuJXIavXYUXzFA=;
h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID;
b=Il5DQt5lMaKNtiXxqx7PvcQaSC/xKBPqLphFzuCfnjrIxkrmNX14nO/NfyTju3LEm
OlBH/yUFOuynes7u27JZOLvxpbl/0ZjZ9kE8kWisZggav7T6k4GVgjuBwpFbRfnvqA
JoiR0i+oYzQHxlTv1GwxohRddxBjSYL4lm1BfdLeRB03JPp9A2OQINgddd5MCraep7
LACX3Ft0wXKB17lrTf4e8t7+xXpCnlMoDmMuJ9IyS/8btcSrPvdAIsNY9SSm8tLKdc
Esroi1LOSMTBhtGNHmds+jZHtLov4oEgh4/r9513hjgksIPU3jn3kiLIFWl+T71zDB
DQfLSq+QNyyLA==
To: shymaa arafat <shymaa.arafat@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <TUXPKVrq0LQJ3nSS_t9HeG8iyRTnikkswCFL2onfsDGoxd9spW57jLXUDITsVNR6KjIMoiunF5ZUNqlauXj4qM3UigrigxX6rdtE7NuJCRE=@protonmail.com>
In-Reply-To: <CAM98U8=Skhz8ETxHd+aBZssHDcj3qNikDa_JYuR5dcSMUJP32g@mail.gmail.com>
References: <CAM98U8kJVMJOQ++cyP3WXFRSHUZw0ySp3dVuZ=BzoRj2qE4Dug@mail.gmail.com>
<c7bdbBVd0KmLFPUeYk0QUdni7tbDwJSj4HGLlEOkdPzIYzOyaX147HWJPKE-isTL267nQeJds8-rsKNyzRrBhucsZvwZcg5dZjQxDnbwxAA=@wuille.net>
<382073c28af1ec54827093003cbec2cc@willtech.com.au>
<CAM98U8mJvYcBur01Z32TS4RYW+jMDCVQAUtrg5KXF+50d0zirA@mail.gmail.com>
<CAM98U8=Skhz8ETxHd+aBZssHDcj3qNikDa_JYuR5dcSMUJP32g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: lightning-dev <lightning-dev@lists.linuxfoundation.org>
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: Fri, 18 Feb 2022 03:36:30 -0000
Good morning shymaa,
> I just want to add an alarming info to this thread...
>
> There are at least 5.7m UTXOs=E2=89=A41000 Sat (~7%),=C2=A0
> 8.04 m =E2=89=A41$ (10%),=C2=A0
> 13.5m =E2=89=A4 0.0001BTC (17%)
>
> It seems that bitInfoCharts took my enquiry seriously and added a main li=
nk for dust analysis:
> https://bitinfocharts.com/top-100-dustiest-bitcoin-addresses.html
> Here, you can see just the first address contains more than 1.7m dust UTX=
Os
> (ins-outs =3D1,712,706 with a few real UTXOs holding the bulk of 415 BTC)=
=C2=A0
> https://bitinfocharts.com/bitcoin/address/1HckjUpRGcrrRAtFaaCAUaGjsPx9oYm=
LaZ
>
> =C2=BB=C2=BB=C2=BB=C2=BB=C2=BB
> =C2=A0That's alarming isn't it?, is it due to the lightning networks prot=
ocol or could be some other weird activity going on?
> .
I believe some blockchain tracking analysts will "dust" addresses that were=
spent from (give them 546 sats), in the hope that lousy wallets will use t=
he new 546-sat UTXO from the same address but spending to a different addre=
ss and combining with *other* inputs with new addresses, thus allowing them=
to grow their datasets about fund ownership.
Indeed JoinMarket has a policy to ignore-by-default UTXOs that pay to an ad=
dress it already spent from, precisely due to this (apparently common, sinc=
e my JoinMarket maker got dusted a number of times already) practice.
I am personally unsure of how common this is but it seems likely that you c=
an eliminate this effect by removing outputs of exactly 546 sats to reused =
addresses.
Regards,
ZmnSCPxj
|
