search

Multibit-Legacy / multibit-hd

Deprecated Bitcoin Wallet
https://multibit.org/blog/2017/07/26/multibit-shutdown.html
Other
169 stars 124 forks source link

Low spendable balance detected [..]; Transaction goes through anyways. #776

Open drewshaver opened 8 years ago

drewshaver commented 8 years ago

I think I understand correctly all the cases that should cause this error. But I am confused, because the second transaction went through successfully (I did not resubmit it or anything).

Inspecting the transactions, it does not appear that the second transaction is using the change output from the first. So I don't really understand why this error should be presented.

My guess is that it is a misunderstanding on my part, but this has happened to me numerous times now so I figured best to report it. The transaction goes through every time after receiving the error, so it is very confusing.

The first transaction: aa2b1f6c2a0c974445ae7f9bdbab3d0d60827d530e7b9f4507009842531620f1 The second transaction: 7179ce9c0bb515c3c67b02041815a1496bb045e74e61dc93d3777a8db9353597

I will submit an error report as well so you have the log if needed. I will tag it with the issue number.

jim618 commented 8 years ago

Low spendable balance IS a confusing error message yes. It basically means "I cannot tell from the feedback from other peers whether this transaction has propagated or not through the Bitcoin network".

This does not make much sense to a regular user so we describe the effect - which is some of your bitcoins are 'tied up' with your ongoing transactions. It'll sort itself out when the transactions confirm. There is an article in the help to describe this more (which basically says the same thing).

It is there mainly so that people don't think their bitcoin have "disappeared". This creates alarm rather than temporary confusion until the transactions confirm.

drewshaver commented 8 years ago

Ohh.. interesting. So the propagation thing was probably just caused because of load on the network / small-ish fee, but had nothing to do with chained transactions? And since the typical cause of that sort of status is in fact a long-ish chain of transactions, you make a best guess and report that ... for the sake of simplicity?

gary-rowe commented 8 years ago

Noticed that the submitted log hadn't been added here: c6cfd40