summaryrefslogtreecommitdiff
path: root/cc/10c1cbaf0a8500c3dad48b1983512741bad9c1
blob: 3b9bd588df8e6a993b4f48be65b3a7f2d6591391 (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
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
Return-Path: <user@petertodd.org>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id CD022C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 26 Jul 2022 12:45:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 60E6B41932
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 26 Jul 2022 12:45:21 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 60E6B41932
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (2048-bit key, unprotected) header.d=petertodd.org
 header.i=@petertodd.org header.a=rsa-sha256 header.s=fm1 header.b=qjZCMDyP; 
 dkim=pass (2048-bit key,
 unprotected) header.d=messagingengine.com header.i=@messagingengine.com
 header.a=rsa-sha256 header.s=fm3 header.b=Ogiml1C7
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level: 
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7,
 SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id cb6HXn98KfvS
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 26 Jul 2022 12:45:20 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org ED2D941920
Received: from wnew1-smtp.messagingengine.com (wnew1-smtp.messagingengine.com
 [64.147.123.26])
 by smtp4.osuosl.org (Postfix) with ESMTPS id ED2D941920
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 26 Jul 2022 12:45:19 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailnew.west.internal (Postfix) with ESMTP id 2D72C2B05B42;
 Tue, 26 Jul 2022 08:45:17 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute4.internal (MEProxy); Tue, 26 Jul 2022 08:45:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petertodd.org;
 h=cc:content-type:date:date:from:from:in-reply-to:in-reply-to
 :message-id:mime-version:references:reply-to:sender:subject
 :subject:to:to; s=fm1; t=1658839516; x=1658846716; bh=tkm05cpyPl
 vDFWRO6EmH5ejR4D5z/xGiyVRrJghB/RM=; b=qjZCMDyP7bIbMpqtTs9k/4OEKk
 IqN66Dkn9wBThD8smrMkIHj3eegxQJI4+D8Irc/W9UbIzg7AlXIbKi+Ab/9rtt8r
 QweLdCWB+EhMf0EOuv1h7xFEiILeWTNXKBS90ROIvhBf0Y74L+B09KdBxMaXhzUt
 Nd6wDcCE08wRBIyZojwfZVE44STD7iD7Xh7E36s+Ypt3DwiLkvmefgyzIikFMX20
 IAt+LYaycDnhTlMK3xw/GCLnUiHqKo0VKmOWcmO55jTQXS6DEolAIq9gONziAhak
 TCRiYJoHs2MB0ZyXlbxioMaeqQufAqZLvV/c59Qsv3FkOZOuXJuJYkfMLf5w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-type:date:date:feedback-id
 :feedback-id:from:from:in-reply-to:in-reply-to:message-id
 :mime-version:references:reply-to:sender:subject:subject:to:to
 :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=
 fm3; t=1658839516; x=1658846716; bh=tkm05cpyPlvDFWRO6EmH5ejR4D5z
 /xGiyVRrJghB/RM=; b=Ogiml1C7gS/Po01uhQR1vGt6hSg9ijyqdSJECz+52old
 Nokk73FE10easl3bwWqayC1LrW2s7mP2c/34t2uF3nnjzzqjdersZK2NwMYgqNY5
 3iMOVzJBxdmy7k5bMH8L/zDOze2AXOCUS+ow21oHNSqXy+h5lxmtJ8GWUgDsBK+k
 8XKEwDv1nYaxAjVNbzSBhSi55PNrlXHkZfxatfgHZZ41MIb9nVy8Kv3AqtBtaR3O
 Fj3kCTjyLvbeWgYpa09V7WXag4Ld2NOxt14ry1jLh+2YZwkz593ZTGzHXmX7lmOx
 bnyggQhklwQuOoVI7/kyU4t3p6ySGhjhdySiTKMjkg==
X-ME-Sender: <xms:3OHfYrge2tj6v874uBspNwGOLOa8zAJFw8rvmc1PM3ed71FYgzBO6Q>
 <xme:3OHfYoCADnb9l43sZmigAg2ACqfwv46Yg9SDJiHSTUxuB_3YUwf8jqwyWprJFWD44
 2v6Fcf3CELYyRKJaUo>
X-ME-Received: <xmr:3OHfYrEOALmw4Z5dcSFuElNmD5BGH3fVzdhNDmYDyM-5ocIkf116XyDUYJWTZsSwWIsWy5NSacus7w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvddutddgheeiucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
 cujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrvghtvghr
 ucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrthhtvg
 hrnhepiedvvdelieekjeeukefgtdelfeegheehleffueehteeghfelveejfeelgeevffef
 necuffhomhgrihhnpehpvghtvghrthhouggurdhorhhgnecuvehluhhsthgvrhfuihiivg
 eptdenucfrrghrrghmpehmrghilhhfrhhomhepuhhsvghrsehpvghtvghrthhouggurdho
 rhhg
X-ME-Proxy: <xmx:3OHfYoSzSCAQXHWxZaxhCGEkETfkwO5GUeEo-OQLqNMEXp2D-kOt-g>
 <xmx:3OHfYozLMELFOGBxRbtUW_5rVjycR7em7b0CQ6Y1GxlQlxgOvouVug>
 <xmx:3OHfYu4OnZP-updfZNhP22EM0z74MA1scgEj955Dj-_1yxPS7XrPLQ>
 <xmx:3OHfYlorSVqmeKgpus1UX13uDyzspsPaNDMWEMXx6IbSgwvh_Jb0HNKTlpM>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue,
 26 Jul 2022 08:45:16 -0400 (EDT)
Received: by localhost (Postfix, from userid 1000)
 id 738755F883; Tue, 26 Jul 2022 08:45:12 -0400 (EDT)
Date: Tue, 26 Jul 2022 08:45:12 -0400
From: Peter Todd <pete@petertodd.org>
To: aaradhya@technovanti.co.in, Aaradhya Chauhan <chauhanansh.me@gmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <Yt/h2Jv3m8ZsfZ8v@petertodd.org>
References: <CAGHFe1BXdTkPZn4r_KTxYoz0sqcMsV830dm5JTTFURxDezBnDQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="WXrc+RvQX36hNhJs"
Content-Disposition: inline
In-Reply-To: <CAGHFe1BXdTkPZn4r_KTxYoz0sqcMsV830dm5JTTFURxDezBnDQ@mail.gmail.com>
Subject: Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
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: Tue, 26 Jul 2022 12:45:21 -0000


--WXrc+RvQX36hNhJs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 26, 2022 at 01:56:05PM +0530, Aaradhya Chauhan via bitcoin-dev =
wrote:
> I know this might be a sort of repetition for a previous question, but I =
do
> want to know from enthusiasts in this group that while Bitcoin was trading
> at much lower price in its early days, 1 sat/vB was a good dust protection
> measure. But now, I think it's a bit high for merely a dust protection
> measure, and should be lowered slightly. Even if not, it should be lowered
> to half when prices go double than today and keeps oscillating at that
> point. As it's not a consensus rule, I think it can be done easily, just
> needing support from full node operators. I support LN but I think
> transaction affordability should remain constant in the future. If I'm ok=
ay
> to wait in a queue, I should have the option for same affordability for
> minimum fees in the future as it is today. (Like we still have posts today
> while email still exists).

If we're expecting fee revenue to be significant in the future - with const=
ant
backlogs of low-fee txs - lowering the dust limit now is a good way to ensu=
re
the entire ecosystem is ready to deal with those conditions. We're fairly c=
lose
to blocks being full, so you can't argue that the dust limit provides value=
 by
reducing block usage. All it achieves is artificially lowering mempool usag=
e,
putting the Bitcoin system in a no-backlog state that's quite unlike how we=
're
expecting Bitcoin to operate in the future. And indeed, the state Bitcoin c=
an
operate in at any moment if there is a demand spike.

So I'd suggest removing the fixed dust limit entirely and relying purely on=
 the
mempool size limit to determine what is or is not dust.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--WXrc+RvQX36hNhJs
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmLf4dIACgkQLly11TVR
Lze2MRAAidy0AaYtJobnQa/ocqvw1NANJY0ktX04gOxh7ehUNxUo92CCpbcEulhq
C70ibJNTkAuwORjxxCFMb9VUaxOypxEAQjZnh564UHPT12NRFTobF7VY20qUWccb
mPknZbiNAnMhbLEctgED3XY41gw/gZUjDoZyxqbUXE+u299XxdNdIasKmpNEXpln
g9ruOHdalHmEZXSLpctAHvSjAF1zDQJ8nPM2Mi2b+GRYVQc5Qo4IqmU66AF07pq4
ZGeR5cySaYE8YjiUH77PN467B5+g2hRHVjtP641ZxTZsW9N43boKNaQobZkdH0oZ
4uNy1ULezCO9XSfHVNAwZA3SOmBNPpUk6+9l6kmk+qwnLa31XDb8RURIO+HuOQJP
cO8SMVx5xp4PgEO5RMtbvp6G//oyQvNNJEgQXOnt+Fw0IAb6XpzNMDpVIyyCsmEN
c4GY1O6UvSH6yjDoPItIKkjd9df1ek4kopjJPc8wXrQQVOZ6buvHYNQ5ivZrIuIk
xFtWPmDEbGYlR5od+7mGdNq3j42NK5tJR4RUcpczi7J1idQJi7dIm1NcKrAzDqRj
qm3OVy84jO6HXXAr0zlaCOGbOmOvL2uA6Fbtq4E6P+BIh7s3PYLlqR/OvBV1I/xe
/aP/bDbPNBVDJJbog+cGotfwc6XbZA24YkgDa1P2CVML41wg0qk=
=bpJC
-----END PGP SIGNATURE-----

--WXrc+RvQX36hNhJs--