Timeline for What happens when two txid's collide?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2015 at 21:26 | vote | accept | Nick ODell | ||
| Sep 9, 2015 at 5:48 | history | tweeted | twitter.com/#!/StackBitcoin/status/641488342861893633 | ||
| Sep 9, 2015 at 0:44 | comment | added | Nayuki | Remark: TXID collisions have happened in the past before. This is due to the coinbase transaction being identical, and derived transactions can be made to be identical too. This has been fixed by BIP 34 which forces every coinbase script to be different. | |
| Sep 8, 2015 at 2:52 | answer | added | Nick ODell | timeline score: 5 | |
| Sep 8, 2015 at 2:30 | comment | added | Claris | I don't have the time to research it right now so I'm not going to put it in as an answer, but I guess it would follow the same rules as the two BIP30/34 duplicate TXID, if one is spent the other one is just destroyed. I think they are special cased in the source though so that might only apply to them specifically. | |
| Sep 8, 2015 at 2:26 | comment | added | Nick ODell | @Bitcoin Well, yes, but supposing that you used it to make duplicate transactions, what would happen? | |
| Sep 8, 2015 at 1:16 | comment | added | Nate Eldredge | Another question: if you then create a transaction which spends A, and get it included in a block, will nodes randomly consider this block as valid/invalid depending on whether they resolve the input txid to A or B? | |
| Sep 8, 2015 at 1:15 | comment | added | Claris | If you could generate SHA256 collisions easily I think you would probably want to go for the merkle tree first rather than TXID, being able to produce two blocks that have the same hash but different transactions would be extremely destructive and probably not noticed for a long time. | |
| Sep 7, 2015 at 21:12 | history | asked | Nick ODell | CC BY-SA 3.0 |