> We should remove the dust limit from Bitcoin. Any node operator can do that. Just put "dustrelayfee=0.00000000" in your bitcoin.conf.
And there is more: you can also conditionally allow free transactions: mintxfee=0.00000001 minrelaytxfee=0.00000000 blockmintxfee=0.00000000 Then, when using getblocktemplate you will get transactions with the highest fees first anyway, and you include cheap or free transactions in the end, if there will be enough room for them. So, all of those settings are in the hands of node operators, there is no need to change the source code, all you need is to convince nodes to change their settings. On 2021-08-08 20:53:28 user Jeremy via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote: We should remove the dust limit from Bitcoin. Five reasons: 1) it's not our business what outputs people want to create 2) dust outputs can be used in various authentication/delegation smart contracts 3) dust sized htlcs in lightning (https://bitcoin.stackexchange.com/questions/46730/can-you-send-amounts-that-would-typically-be-considered-dust-through-the-light) force channels to operate in a semi-trusted mode which has implications (AFAIU) for the regulatory classification of channels in various jurisdictions; agnostic treatment of fund transfers would simplify this (like getting a 0.01 cent dividend check in the mail) 4) thinly divisible colored coin protocols might make use of sats as value markers for transactions. 5) should we ever do confidential transactions we can't prevent it without compromising privacy / allowed transfers The main reasons I'm aware of not allow dust creation is that: 1) dust is spam 2) dust fingerprinting attacks 1 is (IMO) not valid given the 5 reasons above, and 2 is preventable by well behaved wallets to not redeem outputs that cost more in fees than they are worth. cheers, jeremy _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
