What dust mean in bitcoin and why small amount can be a problem?

[Comeacross]

The longer you stay in crypto, the more you continue to learn. I have been stacking some amount of BTC for a while now. I try to send a very small amount (0.000001 approximately) from the wallet to confirm everything works fine but the transaction failed instantly saying the fee is higher than the amount I want to send. The error message says dust limit which I don't really understand.

If Bitcoin can be divided into million sats, why can't I send any amount no matter how small it is? It's my money and I think I have right to send whatever amount I want.

I also heard that small amount can be a problem later. So I'm now confused. Does it mean I can't send small amount or if I received small amounts they may get stucked forever? What exactly is the dust all about and why does it exist in the first place in bitcoin? I thought dust is only associate with altcoins?

[BIT-BENDER]

The longer you stay in crypto, the more you continue to learn. I have been stacking some amount of BTC for a while now. I try to send a very small amount (0.000001 approximately) from the wallet to confirm everything works fine but the transaction failed instantly saying the fee is higher than the amount I want to send. The error message says dust limit which I don't really understand.

If Bitcoin can be divided into million sats, why can't I send any amount no matter how small it is? It's my money and I think I have right to send whatever amount I want.

I also heard that small amount can be a problem later. So I'm now confused. Does it mean I can't send small amount or if I received small amounts they may get stucked forever? What exactly is the dust all about and why does it exist in the first place in bitcoin? I thought dust is only associate with altcoins?

You were told that the amount you are trying to send is lower than you transaction fee, that is simple logic, what sense will it make to send something lower than you transaction fee even if it is your fund there are some things that absolutely doesn't make any sense.
Even with bank transfers the amount you are sending should not be lower than you charges fee.
Just make it higher than your transaction fee which most times are in small amounts.

[Charles-Tim]

The dust is set by the nodes. Most nodes use the default.

546 sat for legacy addresses
294 sat for segwit bech32
330 sat for taproot.

If you want to send below that, you will need to run your own node and set it to the amount that you want. But on Bitcoin Core those are the dust limit. You can not spend lower than those sats.

This is to avoid or reduce spamming the bitcoin mempool.

[Cookdata]

The longer you stay in crypto, the more you continue to learn. I have been stacking some amount of BTC for a while now. I try to send a very small amount (0.000001 approximately) from the wallet to confirm everything works fine but the transaction failed instantly saying the fee is higher than the amount I want to send. The error message says dust limit which I don't really understand.

0.000001 Btc is equivalent to 100 sats and that's below any of the dust limit, the least dust limit is P2wpkh with 294 sats which is 3x the amount you want to spend.

Check this to know more about dust limits for all scripts.

If you are interested to know why these are the limits, you can read the relevant code starting here: https://github.com/bitcoin/bitcoin/blob/e9262ea32a6e1d364fb7974844fadc36f931f8c6/src/policy/policy.cpp#L26

The dust limit is 3000 sat/kvB, or 3 sats/vbyte, of the minimum amount of data required to spend that type of output.
For a legacy P2PKH transaction, then an input is 148 bytes, and an output is 34 bytes, giving (148+34)*3 = 546 sats.
For a segwit v0 P2WPKH transaction, then an input is 67 bytes and an output is 31 bytes, giving (67+31)*3 = 294 sats.*

For any script hash or taproot outputs, however, then the size of the input is not known in advance, since the locking script is not revealed until after the transaction is made. So instead we use the size of a standard input, and the size of the specific output.
So for a taproot P2TR transaction, then an input is assumed to be 67 bytes and an output is 43 bytes, giving (67+43)*3 = 330 sats.

*This should actually be 297 sats in reality, but a rounding error means that 67.75 is rounded down to 67 instead of up to 68.

If Bitcoin can be divided into million sats, why can't I send any amount no matter how small it is? It's my money and I think I have right to send whatever amount I want.

I also heard that small amount can be a problem later. So I'm now confused. Does it mean I can't send small amount or if I received small amounts they may get stucked forever? What exactly is the dust all about and why does it exist in the first place in bitcoin? I thought dust is only associate with altcoins?

You asked the question on the first paragraph and you answered it in the second paragraph. "Problem later"
You can receive small amount of Bitcoin in large quantities on your wallet address but you may not be able to spend it because you will have large amount of inputs, the more input you have the larger your transaction size and it becomes a problem to get it included into the next block for confirmation, you will need to pay for every sats. You will realize that your transaction fee will be bigger than your input. That's a waste.

Bitcoin amount below dust limit are too small to hold value, allowing such will only invite spam on the Bitcoin network.
Just so you know, if you receive small amount of Bitcoin and don't know the sender, don't spend them. It makes trackers or chain surveillance to know about your inputs and outputs.

[SeriouslyGiveaway]

I also heard that small amount can be a problem later. So I'm now confused. Does it mean I can't send small amount or if I received small amounts they may get stucked forever? What exactly is the dust all about and why does it exist in the first place in bitcoin? I thought dust is only associate with altcoins?

Dust Attack, what it is, why it is dangerous and how to prevent falling to it.
A History of Bitcoin Transaction Dust & Spam Storms.

If you receive any dust, you can freeze that address or freeze that UTXO.
The guide from fillippone.

[hosemary]

546 sat for legacy addresses
294 sat for segwit bech32
330 sat for taproot.

Someone correct me if I am wrong.
I am not sure, but I think the dust limit should be lower for nodes that are accepting fee rates below 1 sat/vbyte.

For example, the dust limit for a legacy output is 3 × 182 × min relay fee rate.
As some nodes have lowered their minimum relay fee rate to less than 1 sat/vbyte, their dust limit should be also lower. Can anyone confirm this?

[dansus021]

Think of Bitcoin like physical cash. If you have $0.01 but the post office charges $0.50 for a stamp to mail it, that penny is effectively 'dust.' You own it, but it’s not worth the cost to move it. Do you know about UTXO Consolidation simple term Bitcoin doesn't have a balance like a bank account, it uses Unspent Transaction Outputs (UTXOs). If you receive 100 small payments of 0.0001 BTC, your wallet has 100 piece of Bitcoin, When you finally try to send 0.01 BTC of those 100 small payments, your transaction will be very large in size. This makes your transaction fee much more expensive

[hd49728]

Someone correct me if I am wrong.
I am not sure, but I think the dust limit should be lower for nodes that are accepting fee rates below 1 sat/vbyte.

For example, the dust limit for a legacy output is 3 × 182 × min relay fee rate.
As some nodes have lowered their minimum relay fee rate to less than 1 sat/vbyte, their dust limit should be also lower. Can anyone confirm this?

It is dust relay fee is 3 sat/vbyte, then total size of inputs and outputs for having dust limit.

If you are interested to know why these are the limits, you can read the relevant code starting here: https://github.com/bitcoin/bitcoin/blob/e9262ea32a6e1d364fb7974844fadc36f931f8c6/src/policy/policy.cpp#L26

The dust limit is 3000 sat/kvB, or 3 sats/vbyte, of the minimum amount of data required to spend that type of output.
For a legacy P2PKH transaction, then an input is 148 bytes, and an output is 34 bytes, giving (148+34)*3 = 546 sats.
For a segwit v0 P2WPKH transaction, then an input is 67 bytes and an output is 31 bytes, giving (67+31)*3 = 294 sats.*

For any script hash or taproot outputs, however, then the size of the input is not known in advance, since the locking script is not revealed until after the transaction is made. So instead we use the size of a standard input, and the size of the specific output.
So for a taproot P2TR transaction, then an input is assumed to be 67 bytes and an output is 43 bytes, giving (67+43)*3 = 330 sats.

*This should actually be 297 sats in reality, but a rounding error means that 67.75 is rounded down to 67 instead of up to 68.

Same explanation here.
https://bitcoin.stackexchange.com/questions/10986/what-is-meant-by-bitcoin-dust

Honestly, after reading, I don't know that with lower fee rate to use recent months, is it affected by lowering dust limit.

[Zaguru12]

Someone correct me if I am wrong.
I am not sure, but I think the dust limit should be lower for nodes that are accepting fee rates below 1 sat/vbyte.

For example, the dust limit for a legacy output is 3 × 182 × min relay fee rate.
As some nodes have lowered their minimum relay fee rate to less than 1 sat/vbyte, their dust limit should be also lower. Can anyone confirm this?

It is dust relay fee is 3 sat/vbyte, then total size of inputs and outputs for having dust limit.

Same explanation here.
https://bitcoin.stackexchange.com/questions/10986/what-is-meant-by-bitcoin-dust

Honestly, after reading, I don't know that with lower fee rate to use recent months, is it affected by lowering dust limit.

With this stackexchange link posted, it clearly Stated that the relay fee tied to the dust calculation was actually that of minimum relay transaction fee. But not bitcoin core actually now uses dust relay fee which has a 3 sat/vbyte as default, so i think the dust limit will be changing if the minRelayTxFee = dustRelayFee, this way as the nodes adjust their minRelayTxFee then the dust limit will also adjust, which takes us back to hosemary question. Except if the 3 sat/vbyte is actually fixed as the dust relay then the limit will be standard as it is.

Logical which I could be wrong is that the fee rate definitely must affect the dust limit because from the raw definition it’s self, a dust is when the output is less than the total fee to be spent for such transaction. So in a rare case of when the min fee rate goes as high as 10 sats/vbyte then this listed dust limit might not hold except my calculations are wrong

[Mia Chloe]

~snip

First understand that most wallets have a fee ratio to transaction  rule. If your fee starts getting close to 30% of your transaction it's considered too expensive to broadcast some wallets will force you to reduce the fee and some will only warn you it's too high.

Secondly understand that dust limits are set to prevent spamming and dust attack if those limits were not there, it would be difficult for nodes to organise data effectively and can bloat the blockchain and make fees increase because of congestion.

[PrivacyG]

I also heard that small amount can be a problem later.

Yes.  If you keep receiving small amounts of Bitcoin, you will eventually have to consolidate a lot of UTXOs.  And when the Fees are higher due to demand and a filled up Mempool, you will have to spend a lot more to consolidate them all.  It does become a problem eventually and this is why it is a good idea to prevent this issue when Fees are low.

[Mia Chloe]

Even with bank transfers the amount you are sending should not be lower than you charges fee.
Just make it higher than your transaction fee which most times are in small amounts.

Lol it doesn't work like that there's a minimal limit to what passes as a transaction and not spam and default depends on what the node sets as minimum relay fee and since most of them these days are using 1 sat/vbyte transactions less than 1000 sats may not go through.

On some wallets I can pay $5 in fees for a $1 transaction which makes the fees literally 500% of the transaction itself so it's not about the value in dollar it's about the dust limit and fee rate.

~snip

And yeah I agree it's correct even experienced it first hand.

[coinlary]

I also heard that small amount can be a problem later. So I'm now confused. Does it mean I can't send small amount or if I received small amounts they may get stucked forever? What exactly is the dust all about and why does it exist in the first place in bitcoin? I thought dust is only associate with altcoins?

No it can't  but it will be unreasonable  to  start accumulating a lot of input in  cents or someone sending you dust everytime, you can( if you use something near the min allowed) but you will have to pay higher fees  because more inputs equals bigger transaction size when you need to spend it which is totally  nonsense.

You don't have any reason to send dust and you won't, that unit will be $1 when Bitcoin reaches $1M. If someone send you dust , freeze it, it's useless.

[bitmover]

If Bitcoin can be divided into million sats, why can't I send any amount no matter how small it is? It's my money and I think I have right to send whatever amount I want.

Actually you can do it. But as sending 1 sat has no real practical use, and it is just a mistake or a spam 99.9% of the time, it is reasonable that you need to go deeper technically to complete the transaction.

There is no limitation in the protocol level, just in wallets interface and node preferences.

[BitMaxz]

It is currently not possible to send 1SAT. Here's how it works:

The formula used by nodes is Dust Limit Amount = (Size of the output) × (dustrelayfee).

Even if you own a Bitcoin core node and set dustrelayfee=1, you will still receive a dust limit error because your transaction will still be above 1 sat and the most popular nodes use 3 sats/vByte for dustrelayfee and the transaction size, such as in Segwit, is usually 110 bytes and above.

However, if you use dustrelayfee=0, your node will accept it, but don't expect other nodes to do the same, so your transaction will end up be rejected or die eventually.

Take the Charles-Tim sample amount you can send if you are using SegWit with SegWit inputs, then your transaction shouldn't be below to "294 sat for segwit bech32".

[stwenhao]

I am not sure, but I think the dust limit should be lower for nodes that are accepting fee rates below 1 sat/vbyte.

No, these limits are handled independently: https://github.com/bitcoin/bitcoin/pull/33106

dust feerate: this feerate cannot be changed as flexibly as the minrelay feerate. A much longer record of low feerate transactions being mined is needed to motivate a decrease there.

Which means, that if a lot of miners will start confirming transactions, where single satoshis would be used in outputs, then it could be lowered in the future. But now, it is not the case yet.

Also, if not miners, then we would still use 1 sat/vB, but some of them started confirming transactions with lower fees, so Bitcoin Core decreased it into 0.1 sat/vB, to improve block propagation.

[nc50lc]

Someone correct me if I am wrong.
I am not sure, but I think the dust limit should be lower for nodes that are accepting fee rates below 1 sat/vbyte.

The quote in hd49728's reply is still applicable since the default DUST_RELAY_TX_FEE isn't lowered when they lowered the DEFAULT_MIN_RELAY_TX_FEE.
Here's the reference clients' default policies (standard rules), highlighted the current dust_relay_tx_fee value: github.com/bitcoin/bitcoin/blob/master/src/policy/policy.h#L63-L68
The formula to calculate the dust limit is already included in the quote (policy.cpp#L27)

I have been stacking some amount of BTC for a while now. I try to send a very small amount (0.000001 approximately) from the wallet to confirm everything works fine but the transaction failed instantly saying the fee is higher than the amount I want to send. The error message says dust limit which I don't really understand.

The note about "fee is higher than the amount" is just a client-side note and didn't affect your ability to send, just to prompt the user to do a sanity-check.
It's actually the "dust limit" message in the broadcast error when you tried to send it, your current sever must be using the standard dust limit.

If Bitcoin can be divided into million sats, why can't I send any amount no matter how small it is? It's my money and I think I have right to send whatever amount I want.

Well, it's not impossible since it's only "non-standard" to send dust but still valid to the consensus rules.

For that, you need to either mine a block yourself and include your transaction with dust like 1sat output.
Or change your node's dust relay settings and connect to nodes and miners' nodes that have similar settings.

The latter sounds simple but it's practically hard to pull-off since finding nodes that relay such transaction is hard and most importantly, a solo/pool miner who's willing to include it to their block.
The former (mine a block) isn't an option for most people.

[BitGoba]

The longer you stay in crypto, the more you continue to learn. I have been stacking some amount of BTC for a while now. I try to send a very small amount (0.000001 approximately) from the wallet to confirm everything works fine but the transaction failed instantly saying the fee is higher than the amount I want to send. The error message says dust limit which I don't really understand.

If Bitcoin can be divided into million sats, why can't I send any amount no matter how small it is? It's my money and I think I have right to send whatever amount I want.

I also heard that small amount can be a problem later. So I'm now confused. Does it mean I can't send small amount or if I received small amounts they may get stucked forever? What exactly is the dust all about and why does it exist in the first place in bitcoin? I thought dust is only associate with altcoins?

Bitcoin on-chain is the base layer of money, and it is more suitable for settlement and larger amounts than for small everyday transactions.

Small transactions, like 100 sats, work much better on Lightning. In the Bitcoin monetary system, Lightning plays a similar role to Visa or Mastercard in the fiat system, it is used for smaller, everyday payments.

You should run your own Bitcoin node and have your own Lightning channels.But you can also use a custodial service like Wallet of Satoshi or CoinOS. When you collect a larger amount, you can send it to your own on-chain address.

[Comeacross]

First understand that most wallets have a fee ratio to transaction  rule. If your fee starts getting close to 30% of your transaction it's considered too expensive to broadcast some wallets will force you to reduce the fee and some will only warn you it's too high.

Oh now it makes sense to me. I didn't know that wallets have that checks built in. This is probably why my transaction was blocked instead of just giving a warning. This is basically a protection mechanism to prevent one from burning their coins on transaction fees accidentally.

Actually you can do it. But as sending 1 sat has no real practical use, and it is just a mistake or a spam 99.9% of the time, it is reasonable that you need to go deeper technically to complete the transaction.

There is no limitation in the protocol level, just in wallets interface and node preferences.

So dust is basically a relay policy and not a concensus rule if I am correct. This means the protocol itself doesn't care if I send a little amount (considered dust) but the majority of nodes won't approve it.

Well, it's not impossible since it's only "non-standard" to send dust but still valid to the consensus rules.

For that, you need to either mine a block yourself and include your transaction with dust like 1sat output.
Or change your node's dust relay settings and connect to nodes and miners' nodes that have similar settings.

The latter sounds simple but it's practically hard to pull-off since finding nodes that relay such transaction is hard and most importantly, a solo/pool miner who's willing to include it to their block.
The former (mine a block) isn't an option for most people.

This is the part I was getting wrong before. So in theory, I can run my own node with dust relay fees as 0 and mine my own block to approve it but practically, finding a miner that'll accept it is impossible unless I have a connection.

Now assuming I broadcast a dust transaction to my own node and a miner include it, does that make the UTXO spendable forever? Will other nodes see it as a valid if it appears in a block even if they haven't relay it before?
From everything I have read here I feel like there is no perfect solution. It's either you pay fees now to consolidate or you risk getting stuck in the future.
I'm more concerned now because I read some old posts as far back as 2017 where people were trapped with this dust of a thing after the fee spike and it cost them more than what the coins were worth. Thank you all for interesting feedback.

[hosemary]

Now assuming I broadcast a dust transaction to my own node and a miner include it, does that make the UTXO spendable forever? Will other nodes see it as a valid if it appears in a block even if they haven't relay it before?

Once a node receives a new block, it checks whether the block is valid or not. If the block is valid, it's added to the blockchain. In other words, nodes check whether the block follows consensus rules or not.
It doesn't matter whether the transactions that have been included in the block follow nodes' standard rules or not.