4 ms·
So the problem is that they are not tracking inputs and outputs, but relying on the transaction ID. This transaction ID can be changed while keeping the signatu
by mathrawka 13y ago
So the problem is that they are not tracking inputs and outputs, but relying on the transaction ID. This transaction ID can be changed while keeping the signatures valid. The inputs and outputs will _not_ be changed.
It sounds like they need to just watch for duplicate transactions as the protocol is built to prevent those.
- laichzeit0 13y agoSo what's the use of tx id's at all then? I mean practically speaking, since they're mutable? I'm thinking of an analogy here but I can't. It's like a git commit hash, but you're "allowed" to append some whitespace to the end of a file so you can keep mutating the hash but it's the "same" commit. I don't really see a use for tx ids if they keep the spec as-is then or am I missing something?