Timeline for Is transaction malleability an issue when receiving payments?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2014 at 13:57 | comment | added | Emre K. | I just figured out from the answer of Pieter to question: bitcoin.stackexchange.com/questions/22663/… that the existing removeConflicts code does not deal with this issue. | |
| Feb 25, 2014 at 21:33 | comment | added | Emre K. | @PieterWullie Thanks. I don't know what memory pool actually does, I'll take a look. But does that mean that they are in the wallet forever? How can I get rid of them? And do you think this is what is going on with the situation I described in this question: bitcoin.stackexchange.com/questions/22663/… | |
| Feb 20, 2014 at 17:41 | comment | added | Pieter Wuille | That method removes conflicting transactions from the memory pool, not from the wallet. | |
| Feb 20, 2014 at 16:08 | comment | added | Emre K. | I have transactions that are stuck on my wallet. What I mean is I have two TXes which have same inputs same outputs. One of them is confirmed. The other one is waiting unconfirmed. I have multiple TXes that are just stuck like this. Any idea why they might have been created? These transactions are mostly received transactions. There is also one sending transaction where I have the same inputs and outputs but different TX ids for 3 transactions. Again one of them is confirmed. The other two are just stuck. I really need help with this. Thanks a lot. | |
| Feb 18, 2014 at 16:18 | vote | accept | Emre K. | ||
| Mar 9, 2014 at 13:55 | |||||
| Feb 18, 2014 at 15:54 | history | edited | John T | CC BY-SA 3.0 |
added 275 characters in body
|
| Feb 18, 2014 at 2:26 | history | answered | John T | CC BY-SA 3.0 |