Timeline for Bitcoin transactions reserve more coins than needed
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2015 at 14:50 | comment | added | David Schwartz | @NafetzD You just have to do something sane when the job breaks, like try it again later. | |
| Oct 30, 2015 at 14:38 | vote | accept | NafetzD | ||
| Oct 30, 2015 at 14:37 | comment | added | NafetzD | Hello, David! I realized that this behavior is normal because when transaction get confirmed, tx history in the wallet is correct. I think the problem is that a minute is not enough for transaction to enter into the blockchain because I tried to send coins with sendCoinsWaitBroadcast method and realize that time for the transaction to enter block chain vary. Sometimes enter immediately, sometimes for like 10-20-30 sec, and sometimes exceeds the minute limit and job breaks and when it's in waiting state wallet balance is 0. I guess i must think about providing more time or something. | |
| Oct 27, 2015 at 20:45 | history | edited | David Schwartz | CC BY-SA 3.0 |
added 280 characters in body
|
| Oct 27, 2015 at 17:17 | comment | added | David Schwartz | That's caused by the particular pattern of unspent outputs you happen to start with. | |
| Oct 27, 2015 at 13:24 | comment | added | NafetzD | Thank you for the answer @David Schwartz ! I understand your point but on a successful sessions that I mentioned in the question, everything is normal - in both wallets, transactions are on the history list, even if they have 0 confirmations and balance is correct (exactly balance - (amount + fee)). I observed the wallets history and i noticed other thing. I will edit the question with the additional information. | |
| Oct 26, 2015 at 23:11 | history | answered | David Schwartz | CC BY-SA 3.0 |