Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 17564C000D; Thu, 7 Oct 2021 08:17:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id DD9F5840F9; Thu, 7 Oct 2021 08:17:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 VaxCHypH9c3z; Thu, 7 Oct 2021 08:17:45 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from KOR01-PS2-obe.outbound.protection.outlook.com (mail-ps2kor01olkn0147.outbound.protection.outlook.com [104.47.109.147]) by smtp1.osuosl.org (Postfix) with ESMTPS id 8059C840F1; Thu, 7 Oct 2021 08:17:45 +0000 (UTC) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Wuj6VZxiQf/UiI96DByK2G5f/UFCQp0dzXrmXoW+KrGdpBTJ9rnJucy6JD4HLb+1n23jfO93xy47SamVEje/hrkkMp9ZLhWwh27ldGeJM+9N7iSZyQi9PdBjmuTxzNTi25eEIQXJp3I8PT/mzwH+Wm+0eucL9HOJlSFqG/c+iN8bb8HBY0/3Ng9dGy9uGEha3RzvtQEivJoxcsau4MpVTwcI6nQaXmAKaSPUEwoHQeouYxBv/xCrvAU05YKvlxpuY1lPGWMfCMVbXlHcc/toL/umFQuaeg4Kj8MMVbb5TY6dMLHfRfOcRD4WkicrUJ3GcWSVvW1aIBw/b4QN4V+2kA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/VRnKtUHfNGO04PxUBrRYFVVbutZNOo6GD/3DkIHdWU=; b=JjR3+vBjATxIHZrVTmfArxf/GMB0a7K3OiI+U2NtZ/XOuocU0bezaSuJ8rOPJHOIDTCDjbpC8/zEb4872RV7kzRF78vRSUbGOiH4bXhowDd4Wj7aTpbXPyIrK0sfTDwLyq5Di9HMcpG6UulZTAO4oiBXwP/iw01LEDUQ5PgHjmPK7IBLHn0MhVzHbap+Y7JCQyvhGj4Csua8igYO4lzc/06XlGENhtfHH26gdQ11+ZmEfaoqiZ9RAVGcEiTNxQQpcpfeHGk0wBfmmGr+xVh13caGp+2DNZByK8hkUhFwikmRF9iCFQubN7jmXvmjTSN6ih4ONEsb6C9t3+7Hk38ULA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none Received: from PS2P216MB1089.KORP216.PROD.OUTLOOK.COM (2603:1096:301:52::11) by PS2P216MB0626.KORP216.PROD.OUTLOOK.COM (2603:1096:300:1c::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4566.17; Thu, 7 Oct 2021 08:17:40 +0000 Received: from PS2P216MB1089.KORP216.PROD.OUTLOOK.COM ([fe80::ccbf:fb52:3f6b:fbda]) by PS2P216MB1089.KORP216.PROD.OUTLOOK.COM ([fe80::ccbf:fb52:3f6b:fbda%8]) with mapi id 15.20.4587.019; Thu, 7 Oct 2021 08:17:40 +0000 From: LORD HIS EXCELLENCY JAMES HRMH To: Erik Aronesty , ZmnSCPxj , Bitcoin Protocol Discussion 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: References: <20210808215101.wuaidu5ww63ajx6h@ganymede> In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-AU X-MS-Has-Attach: X-MS-TNEF-Correlator: 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
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 c= urrent dust limit at the time the transaction is created but it cannot guarantee 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 af= ter fees for automatic utxo selection, however, perhaps consider this is va= lid for manual utxo selection since it is in every example 'my money' an= d 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 build 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 example= s where the inclusion of what is today considered 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_--