Bitcoin Forum
March 28, 2024, 10:06:01 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How to disable the dust limit without recompiling the client?  (Read 95 times)
garlonicon (OP)
Hero Member
*****
Offline Offline

Activity: 789
Merit: 1910


View Profile
March 12, 2022, 11:03:31 AM
Merited by vapourminer (2)
 #1

I know it is possible to lower fees by using this configuration:
Code:
mintxfee=0.00000001
minrelaytxfee=0.00000001
blockmintxfee=0.00000001
But even with those settings, my node still rejects transaction to Segwit outputs below 0.00000294 BTC. Is it possible to use some other configuration option to lower the dust limit? Or is it hard-coded into the client and I have to rebuild it manually to allow that?

Hold your horses before deploying blockchain-related things. You don't want to deploy SHA-1 collision without deploying hardened SHA-1. Once you reveal some code, and make it Open Source, there is no "undo" button. Once you share some idea, there is no way to erase it from reader's memory.
1711663561
Hero Member
*
Offline Offline

Posts: 1711663561

View Profile Personal Message (Offline)

Ignore
1711663561
Reply with quote  #2

1711663561
Report to moderator
1711663561
Hero Member
*
Offline Offline

Posts: 1711663561

View Profile Personal Message (Offline)

Ignore
1711663561
Reply with quote  #2

1711663561
Report to moderator
1711663561
Hero Member
*
Offline Offline

Posts: 1711663561

View Profile Personal Message (Offline)

Ignore
1711663561
Reply with quote  #2

1711663561
Report to moderator
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1711663561
Hero Member
*
Offline Offline

Posts: 1711663561

View Profile Personal Message (Offline)

Ignore
1711663561
Reply with quote  #2

1711663561
Report to moderator
nc50lc
Legendary
*
Offline Offline

Activity: 2366
Merit: 5429


Self-proclaimed Genius


View Profile
March 12, 2022, 11:26:48 AM
Merited by garlonicon (5), vapourminer (2), BlackHatCoiner (1), PawGo (1)
 #2

Use dustrelayfee=n (BTC/kB) instead of the feerate-related configs | the default value is 0.00001 BTC/kB.

Here's the related note for that config:
Quote
# Fee rate (in BTC/kB) used to defined dust, the value of an output such that it will cost about 1/3 of its value in fees at this fee rate to spend it.
dustrelayfee=0.00001

..JAMBLER.io..Create Your Bitcoin Mixing
Business Now for   F R E E 
▄█████████████████████████████
█████████████████████████
████▀████████████████████
███▀█████▄█▀███▀▀▀██████
██▀█████▄█▄██████████████
██▄▄████▀▄▄▄▀▀▀▀▀▄▄██████
█████▄▄▄██████████▀▄████
█████▀▄█▄██████▀█▄█████
███████▀▄█▀█▄██▀█▄███████
█████████▄█▀▄█▀▄█████████
█████████████████████████
█████████████████████████
▀█████████████████████████████
█████████████████████████████████████████████████
.
      OUR      
PARTNERS

.
█████████████████████████████████████████████████
████▄
██
██
██
██
██
██
██
██
██
██
██
████▀
▄█████████████████████████████
████████▀▀█████▀▀████████
█████▀█████████████▀█████
████████████████████████
███████████████▄█████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████▀█████████
████████████████████████
█████▄█████████████▄█████
████████▄▄█████▄▄████████
▀█████████████████████████████
█████████████████████████████████████████████████
.
   INVEST   
BITCOIN

.
█████████████████████████████████████████████████
████▄
██
██
██
██
██
██
██
██
██
██
██
████▀
garlonicon (OP)
Hero Member
*****
Offline Offline

Activity: 789
Merit: 1910


View Profile
March 12, 2022, 11:46:15 AM
 #3

Thank you! It works!

Hold your horses before deploying blockchain-related things. You don't want to deploy SHA-1 collision without deploying hardened SHA-1. Once you reveal some code, and make it Open Source, there is no "undo" button. Once you share some idea, there is no way to erase it from reader's memory.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!