Timeline for Is transaction malleability an issue when receiving payments?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2014 at 16:18 | vote | accept | Emre K. | ||
| Mar 9, 2014 at 13:55 | |||||
| Feb 18, 2014 at 15:54 | comment | added | John T | @AntonAnsgar you got it. | |
| Feb 18, 2014 at 7:06 | comment | added | Emre K. | @JacobTorba Can you write an answer so I can mark as valid? Thank you. | |
| Feb 18, 2014 at 2:26 | answer | added | John T | timeline score: 2 | |
| Feb 17, 2014 at 21:33 | comment | added | John T |
@AntonAnsgar Here is where stale transaction removal happens. removeConflicts checks memory pool for conflicting inputs here.
|
|
| Feb 17, 2014 at 19:54 | comment | added | Emre K. | Thanks. Can you point me to a certain part of the source code where I can check to make sure? | |
| Feb 17, 2014 at 19:11 | comment | added | Murch♦ | I think your Bitcoin-Qt would discard its knowledge of t12 as soon as t13 gets confirmed as they are doublespends of each other. | |
| Feb 17, 2014 at 18:51 | answer | added | T9b | timeline score: -1 | |
| Feb 17, 2014 at 16:35 | history | tweeted | twitter.com/#!/StackBitcoin/status/435452546870951937 | ||
| Feb 17, 2014 at 15:19 | history | asked | Emre K. | CC BY-SA 3.0 |