How two transactions with the same hash can cause double-spending

How two transactions with the same hash can cause double-spending

Let's consider following situation:

  1. Vendor owns address X.
  2. Adversary sends transaction T1 to X with hash Y and receives product from vendor.
  3. Adversary sends transaction T2 to address which he owns with the same hash Y to other nodes.
  4. Vendor receives transaction T2 with same hash as T1, so from his point of view this is the same transaction. He ignores it.
  5. Other nodes receives transaction T1 after T2 so they ignores T1.
  6. Transaction T2 was sent to majority, so probability that T2 will be included in next block is higher than probability of inlcuding T1.
  7. According to probabilty, the transaction T2 was included in next block.

Is this scenario of double-spend correct?

https://ift.tt/2GXKika

Comments

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

couldn't connect to server: EOF reached (code 1)