Topic: Transfer status Local (Read 298 times)

I only sent to one address as i normally do in mbtc. Form...51mbtc still stored locally...ive tried over and over to broadcast. But get the same error message....a bug?  Strange..  If it wasent for bad luck id have no luck at all

Thank guys

are you sure it is not "bits"? 51 bits means 5100 satoshi which is lower than the dust limit hence the rejection.
if it doesn't violate your privacy can you post the raw transaction here? you should be able to export the transaction from your android wallet. it will be a long hexadecimal string starting with 01000000 (it can be 02000000 too but Electrum uses version 1 transactions).

if not answer this:
how many new outputs are you creating? (in other words are you paying to 1 address or multiple). and how much you are paying to that 1 or if more to each address?
if it is just one, the only thing that i can think of is that Electrum is making a change address for you and pays the remainder but it is small so it is rejected by the network. which means it is a bug because the wallet doesn't let you create dust output in first place.

I sent 51mbtc.  Its stored locally now apparantly

this error is telling you that the amount you are trying to send is too small.
there is a limit for the amount of bitcoin that you can send, i don't know how much it is now since it has changed multiple times but i believe it is somewhere around 5000 satoshi and when you send an amount smaller than that it will be rejected.

On the history tab right click on the local transaction where it says local and choose remove. Then go to tools > preferences > fiat tab and set the base unit to btc. Now attempt to craft a new transaction via the send tab. This time understand that you are using bitcoin as your unit and not mbtc. Your transaction was previously rejected because you were confusing bitcoin with mbtc. 1 mbtc = 1/1000th of a bitcoin.

This tells you that it got rejected by the network due to your TX being dust.

How much are you trying to send ? It seems like it is just a fraction of 0.01$.

Depending on the specific amount you want to send, you'll either have to wait until the fees are at its lowest (~ 1 sat/B) or you need to use more inputs in order to create a bigger transaction (worth more than fees + minimum amount).

Error message. Says.    rejected by network rules \n\n64:dust\n

Error message. Says.    rejected by network rules \n\n64:dust\n

Aside from "transaction rejected"... Does the error message say anything else?

Usually, it will have an error code/number and a somewhat cryptic message. For example, "66-insufficent priority"

It's been a while since I had issues with the Android version of Electrum, so I'm not 100% that it shows the full error message... However, if it does, knowing this number and message will greatly assist with pinpointing the root cause of your problem.

Screenshot maybe?

If you are using Bitcoin/similar cryptocurrency and use non-centralized wallet, then i think you're not robbed.
Most likely your wallet's default fee is too low which make confirmation takes a while. All you need to do is wait until the transaction is confirmed.

p.s. please give us more information such as wallet that you use and mentioned transaction ID.

Well... If you got a message saying the node rejected your transaction, it probably IS a fee problem (there could be other problems to, but a fee related problem is the most common one).  Without actually seeing the transaction, there is no way to pinpoint the exact problem with the transaction.

Good news, sure there's some good news :
In a non-technical way, it means that the coins never actually left your wallet.

In a technical way, it means that the unspent outputs funding the addresses managed by your wallet were used as input for a new transaction, but since that transaction wasn't succesfully broadcasted, the transaction spending the unspent outputs is not in the mempool of any of the nodes, so as far as the network's concerned: nothing really happened, the transaction sending the funds simply doesn't "exist" (at least from the network's point of view).
This statement only remains true as long as you don't succeed in broadcasting the transaction... If you broadcast it even once, the above statement becomes untrue!




The only "problem" is that electrum actually keeps the unbroadcasted transaction stored in a local file on your computer. As long as electrum has this transaction in this local file, you'll probably not be able to re-spend the funds...

I haven't used electrum in a while, so i don't know if there is a way to make electrum "forget" the transaction that's currently stuck... You can always restore your wallet from seed, but that might be a drastic measure since you'll lose all metadata you added (for example, the comments you added to a transaction or the names you attached to addresses).

what do you mean by respend the funds?   also if its most likely a fee problem does that mean i should just sit and wait it out?  will the locally stored funds ever start moving down the blockchain on there own?  im computer illiterate so if i can avoid any trouble shooting that would be awesome



thanks so much for the replies by the way guys

Well i Pushed the Broadcast button and got an error message telling me that my transaction is rejected by the network..i guess the node rejected me whatever the hell that means...does this mean my coins are stuck...coins wont just dissapear will they?  and finally where and when will my coins final destination be?  i really hope these coins find there way back into my wallet...and again my status still shows as LOCAL


Im fukin  confused..anybody got any good news for me?

Well the funds went from coinbase to electrum to a gaming website.. I did some research and it told me that my transaction is signed and confirmed but not broadcasted...so i went to my wallet and pushed the broadcast button and still nothing is moving it seems...but whats strange is that i sent the coin in the same fashion as i allways do but now for some reason my status is local