From: LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>
To: Erik Aronesty <erik@q32.com>, ZmnSCPxj <ZmnSCPxj@protonmail.com>, Bitcoin
 Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: [bitcoin-dev] [Lightning-dev]   Removing the Dust Limit
Thread-Index: AQHXuzcgB3XZYzD9l0SU8Sb0t5+l5KvHK44p
Date: Thu, 7 Oct 2021 08:17:40 +0000
Message-ID: <PS2P216MB10896EAD8C2FE35F2A897C4B9DB19@PS2P216MB1089.KORP216.PROD.OUTLOOK.COM>
References: <CAD5xwhjFBjvkMKev_6HFRuRGcZUi7WjO5d963GNXWN4n-06Pqg@mail.gmail.com>
 <20210808215101.wuaidu5ww63ajx6h@ganymede>
 <MkPutJpff5rqUxXFQrEyHZl6Iz0DfrJU_-BQD-y0El65GQFnj7igVfmWU79fPCtiFztUYl4ofzrqeaN0HFMB45YPErY9rYY7_h1XkuTMfvc=@wuille.net>
 <CAJowKgKt=yYdNOYYNsWh7FJ2EH7rz0bd2EjUjmyA=cA6k5cvUQ@mail.gmail.com>
 <BtaljKLqpe75GB6pHEPQMF6_L-hBaE0ZCBGaXrUfnHRYeEbCqFWZ12DaMRm5jEADceL3uPfCiL-WU9MOZJ_m54Zi3Pzu0vSFN3nQvuSKvBM=@protonmail.com>
In-Reply-To: <BtaljKLqpe75GB6pHEPQMF6_L-hBaE0ZCBGaXrUfnHRYeEbCqFWZ12DaMRm5jEADceL3uPfCiL-WU9MOZJ_m54Zi3Pzu0vSFN3nQvuSKvBM=@protonmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-AU
suggested_attachment_session_id: adead998-8754-2ee6-5353-27e7f0a3f213
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [F0WGyFmGOGqegRUQRL2VfXTn+kJledBJ]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ee963481-6f1d-471b-61e1-08d9896aee58
x-ms-traffictypediagnostic: PS2P216MB0626:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: GkruLs9G2q4RzXMUxHbzhNu7eh/bQgrlkm8bHKSUMi1VElZhD68FMSao1wfOA2zNSlnM7Dro839xVTt4/5JFZztDUQ3s5O/8wVRfP0+W8wjDq59XaGUzN17CsMgtuNf/wUmiT8zGj+4E1AfmH2i7r+9HdrVVle5NTvmRqGUHALDgYhq8klHkEpy3Uy6jjLgQgu+KcBgvcgsQALVL1F3pYKur8kKghCsDCsjdW625j8tgW+E7IaDx2/BGq8wgo8CbPiLcSW7BayUxBfQIoUr3VDjC6QiZBZ9b5powr2rezMkrsxGFOkcLJUMfKwPdVi9ZBvwCz5l+Eh7S5zicgDToPHnTBzaro8zblb0nbPpHm791jeCWpR340C6RXxAwJSYqTtVAiCPp3o+OarwCwSedSitS2BJPzzb94uBCr2pqf+LvPhRN9HbAX9L9sK8RGG+Vvg4MsVjAJDDM4Oq6lwygf0hGC50+LVpTZOgPH+Hjooo=
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: mv5NjYW5HdDMzXkn99p974dk7ao3PmSAPOSJ58fYwt4qGC7OHTM0FuH3JQQhVndhkms8KHGew3z2aPB+Uqk3+jQpfqZQeNhPxomKxa193ESzp4Nu+ATFp+Z46F8J8PWkcmTXX06h02GnhrClQSilgA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative;
 boundary="_000_PS2P216MB10896EAD8C2FE35F2A897C4B9DB19PS2P216MB1089KORP_"
MIME-Version: 1.0
X-OriginatorOrg: sct-15-20-3174-20-msonline-outlook-af45a.templateTenant
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PS2P216MB1089.KORP216.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: ee963481-6f1d-471b-61e1-08d9896aee58
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2021 08:17:40.7157 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PS2P216MB0626
X-Mailman-Approved-At: Sat, 09 Oct 2021 12:36:19 +0000
Cc: lightning-dev <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev]   Removing the Dust Limit
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: Thu, 07 Oct 2021 08:17:47 -0000

--_000_PS2P216MB10896EAD8C2FE35F2A897C4B9DB19PS2P216MB1089KORP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Good Afternoon,

Returning to this subject, there should be no restriction to the value of u=
txo's that keep in one's own wallet as change can be created in any value. =
With obvious intent, the wallet should avoid creating utxo's below the curr=
ent dust limit at the time the transaction is created but it cannot guarant=
ee it.

The wallet should avoid including utxo's that by weight sat/KB are more exp=
ensive to include that their value at the time a transaction is created, ie=
. do not include utxo's in a transaction that lower the input value after f=
ees for automatic utxo selection, however, perhaps consider this is valid f=
or manual utxo selection since it is in every example 'my money' and I can =
spend some of it if I decide.

There is no discipline in complaining that the dust set of utxo's slows dow=
n the process of block validation during mining. Every conceivable computer=
ised business bears the expense of the cost of a database transaction. The =
actual answer to this genuine business concern of database speed is to buil=
d a faster database.

It is correct knowledge to know that the Bitcoin protocol cannot speculate =
as to the future but we can. The case exists where it is conceivable for ex=
ample, that the transaction fee is paid only for the first utxo inclusion i=
n a transaction due to changes to the calculation of block-size. There are =
other easily plausible examples where the inclusion of what is today consid=
ered dust may not be ill-considered.

KING JAMES HRMH
Great British Empire

Regards,
The Australian
LORD HIS EXCELLENCY JAMES HRMH (& HMRH)
of Hougun Manor & Glencoe & British Empire
MR. Damian A. James Williamson
Wills

et al.


Willtech
www.willtech.com.au
www.go-overt.com
duigco.org DUIGCO API
and other projects


m. 0487135719
f. +61261470192


This email does not constitute a general advice. Please disregard this emai=
l if misdelivered.



--_000_PS2P216MB10896EAD8C2FE35F2A897C4B9DB19PS2P216MB1089KORP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Good Afternoon,</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
Returning to this subject, there should be no restriction to the value of u=
txo's that keep in one's own wallet as change can be created in any value.
<u>With obvious intent, the wallet should avoid creating utxo's below the c=
urrent dust limit at the time the transaction is created
<b>but it cannot guarantee it</b>.</u></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
The wallet should avoid including utxo's that by weight sat/KB are more exp=
ensive to include that their value at the time a transaction is created,
<u>ie. do not include utxo's in a transaction that lower the input value af=
ter fees for automatic utxo selection, however, perhaps consider this is va=
lid for manual utxo selection since<b> it is in every example 'my money' an=
d I can spend some of it if I decide.</b><br>
</u></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
There is no discipline in complaining that the dust set of utxo's slows dow=
n the process of block validation during mining. Every conceivable computer=
ised business bears the expense of the cost of a database transaction.
<u>The actual answer to this genuine business concern of database speed is =
to <b>
build a faster database.</b></u></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
It is correct knowledge to know that the Bitcoin protocol cannot speculate =
as to the future but we can. The case exists where it is conceivable for ex=
ample, that the transaction fee is paid only for the first utxo inclusion i=
n a transaction due to changes to
 the calculation of block-size. <u>There are other easily plausible example=
s where the inclusion of what is today considered
<b>dust may not be ill-considered.</b></u></div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
KING JAMES HRMH
<div>Great British Empire</div>
<div><br>
</div>
<div>Regards,</div>
<div>The Australian</div>
<div>LORD HIS EXCELLENCY JAMES HRMH (&amp; HMRH)</div>
<div>of Hougun Manor &amp; Glencoe &amp; British Empire</div>
<div>MR. Damian A. James Williamson</div>
<div>Wills</div>
<div><br>
</div>
<div>et al.</div>
<div><br>
</div>
<div>&nbsp;</div>
<div>Willtech</div>
<div>www.willtech.com.au</div>
<div>www.go-overt.com</div>
<div>duigco.org DUIGCO API</div>
<div>and other projects</div>
<div>&nbsp;</div>
<div><br>
</div>
<div>m. 0487135719</div>
<div>f. +61261470192</div>
<div><br>
</div>
<div><br>
</div>
This email does not constitute a general advice. Please disregard this emai=
l if misdelivered.<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
 color: rgb(0, 0, 0);">
<br>
</div>
</body>
</html>

--_000_PS2P216MB10896EAD8C2FE35F2A897C4B9DB19PS2P216MB1089KORP_--