Quote from: bitsaber on February 11, 2014, 12:34:21 AM

Quote from: justusranvier on February 11, 2014, 12:18:01 AM

Transactions have always been malleable prior to being included in a block. This wasn't really apparent until 2011.

Maybe they were, but this certainly didn't help:

Quote from: Gavin Andresen on August 13, 2010, 07:28:23 PM

I'm proposing one small change to Bitcoin's JSON-RPC api: return a transaction ID when Bitcoins are successfully sent.

Why? Because I want to keep a complete audit trail for any coins going into or coming out of my application's wallet; I want to keep track of the particular transactions in the bitcoin network that correspond to actions my application takes. The alternative is to call sendtoaddress and then call listtransactions, but that won't work properly if two similar transactions (same amount to same address) occur at about the same time.

Where's the part of that where he says "then, after returning the txid, depend on it as a permanent identification proving a deposit into an exchange?" I'm not seeing that. There's really nothing more fundamental to Bitcoin than the blockchain, and that if something is on it, you can trust it forevermore after whatever number of confirms makes you comfortable. If it isn't, you can't, even if it might have some temporary use in the interim.