Though now I'm curious also about seoincorporation's post... what did they change to get a diff ID? Is it that "clam-speech" bit? What's that?
I don't really know what's "clam-speech".
As I see in the post made by seoincorporation the "time" has been also changed.
It's in the code provided by seoincorporation... but I guess have to wait for him to respond to understand how the ID changed, and what variable changed it.
"clam-speech" : "Expression of Political Freedom: Autocracy",
OK I'm suddenly curious now and want to try this next time I fire up as I actually never noticed. I don't know how it all works but using explanations above... if tx ID is made by hashing tx data, and the data doesn't change (destination, amount fee, locktime, etc), then the hash result will always be the same, correct?
Isn't this related to
not reusing the same k value?
It's easy to test by signing the same message twice: the signature changes.
k value def new to me (bearing in mind I'm always finding out new things from a very basic user perspective). And don't even know what it means to me. Also always thought signature remains same, as that's how people can verify if I give them the message and signature... right?
In any case, tx ID is created at creation of raw tx, not at signature stage (refer above).
P.S. that link you shared, crazy it still holds 59 BTC (7 more than when it was first alerted in 2013!).