Ellectrum Send Issue

[Maverick9123]

When I try to send BTC to my Bitcoin wallet I get this message:

The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.

Transaction could not be broadcast due to dust outputs.

The wallet shows the correct amount of BTC and it has set there for a year verified.

I have verified I have the latest version software. I have tried a dozen other server selections and I get the same result. Anyone know whats going on?

[OmegaStarScream]

If changing servers didn't help then this could be related to the amount you're trying to spend and it being too small.

[buwaytress]

Now that someone's brought this up, what's the lowest output nodes won't reject now? Last I recall it was still at 3 satoshis/byte, so for a typical SW tx from my Electrum it's 141x3 = 423 satoshi.

Considering the price of Bitcoin now, even 423 satoshi is more than 5 cents. Amazing what dust costs, to look at it from that point of view, isn't it?

Your only option now is to keep trying broadcasting it until you find a node that's willing to accept that, my guess is it's as likely as finding one willing to accept 0-fee txs (no likelihood).

[NeuroticFish]

Transaction could not be broadcast due to dust outputs.

Did you try to send some extremely low amount (less than 546 Satoshi)? If so, you'll have to adjust. Or, if you want only to do tests, I suggest you better play on testnet.

[o_e_l_e_o]

Now that someone's brought this up, what's the lowest output nodes won't reject now? Last I recall it was still at 3 satoshis/byte, so for a typical SW tx from my Electrum it's 141x3 = 423 satoshi.

Any transaction in which the value of the transaction is less than the amount you would pay in fees is rejected. The default dustRelayFee is 3,000 sat/kilobyte, so for a 1-input-1-output legacy transaction of 182 bytes, the minimum transaction is 546 satoshi. This number will be smaller for transactions using SegWit inputs or outputs. You can read the relevant parts on github here: https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.cpp (Lines 16 - 29).

[BitMaxz]

Can you try to make a signed transaction and get the raw transaction then broadcast it to the broadcasting sites listed below.

If you can make a signed transaction you can get the raw transaction you can find it in the preview page.

Check these list of broadcasting sites below.

- https://coinb.in/#broadcast
- https://blockchair.com/broadcast
- https://pool.viabtc.com/tools/broadcast

If not work well I think you need to remove the included dust inputs or choose only the higher amount when making a transaction you can find it on your coins tab in Electrum.

[Abdussamad]

This error message usually means that the server you are connected to is malicious in nature and blocking your spending transaction. You should just learn to switch servers properly (hint you have to right click and choose use server). Try one of the bauerj ones.

[pooya87]

This error message usually means that the server you are connected to is malicious in nature and blocking your spending transaction. You should just learn to switch servers properly (hint you have to right click and choose use server). Try one of the bauerj ones.

i don't think that's correct in this case because of the third line of the error message which clearly indicates the reason. the malicious servers return an error message that can not be parsed which then would show a different message to user which has no "reason" in it.
OP's transaction has dust output in it and since 99% of the nodes are enforcing the same rules i don't think changing servers would help him at all.

[HCP]

Transaction could not be broadcast due to dust outputs.
Anyone know whats going on?

The error message tells you... you have dust outputs. If you setup the transaction and then click the "Preview" button, it'll show you the inputs/outputs being used. In the outputs section you will likely see one or more outputs that has a value below 0.00000546 BTC.

Transactions with tiny outputs are effectively banned from the network to prevent "spam" attacks. You'll need to adjust your transaction (either the amount being sent or the fee being used) to try and prevent the tiny dust output from being generated before the network will accept your transaction.

[buwaytress]

Now that someone's brought this up, what's the lowest output nodes won't reject now? Last I recall it was still at 3 satoshis/byte, so for a typical SW tx from my Electrum it's 141x3 = 423 satoshi.

Any transaction in which the value of the transaction is less than the amount you would pay in fees is rejected. The default dustRelayFee is 3,000 sat/kilobyte, so for a 1-input-1-output legacy transaction of 182 bytes, the minimum transaction is 546 satoshi. This number will be smaller for transactions using SegWit inputs or outputs. You can read the relevant parts on github here: https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.cpp (Lines 16 - 29).

Very helpful, thanks! So it is 3 sats/byte anyway (though maybe actually less since 1 kb is > 1000 bytes?). Makes me wonder now how much is stuck out of circulation because of this.

I've never had the "opportunity" to send anything so small to be honest, although I can foresee that by the time I'll have some reason to do so, we'll already be taking these kinds of transactions off chain onto lightning channels.

[HCP]

Makes me wonder now how much is stuck out of circulation because of this.

Theoretically, none. Remember, this is only to prevent dust from being created, it doesn't stop you from spending dust! The difficulty comes in that the fee to use the input could be so big as to consume the entire dust UTXO and/or you need enough other coins in the wallet to be able to send it out without creating a new dust output.

[Abdussamad]

This error message usually means that the server you are connected to is malicious in nature and blocking your spending transaction. You should just learn to switch servers properly (hint you have to right click and choose use server). Try one of the bauerj ones.

i don't think that's correct in this case because of the third line of the error message which clearly indicates the reason. the malicious servers return an error message that can not be parsed which then would show a different message to user which has no "reason" in it.
OP's transaction has dust output in it and since 99% of the nodes are enforcing the same rules i don't think changing servers would help him at all.

Apologies. You are correct. That's a different error message (non standard transaction one)

@OP When this happens it's usually because users are confusing mbtc with btc. So I suggest choosing btc under tools > preferences > general tab > base unit and trying again.