Author: Eric Voskuil 2016-11-17 00:53:45
Published on: 2016-11-17T00:53:45+00:00
In a discussion on the bitcoin-dev mailing list, Eric Voskuil explains why banning duplicate transaction hashes outright is not feasible. Doing so would require spent transaction hashes to be retained forever, which goes against the concept of pruning nodes. Additionally, implementing such a ban would result in a chain split and a hard fork. It is noted that while BIP34 precludes exact duplicate transactions, different transactions can still have the same hash if their parents are identical. However, as long as the hash function remains secure, future transactions are guaranteed to have unique transaction IDs.
Updated on: 2023-06-11T20:36:33.410507+00:00