Topic: Does a tx contain a timestamp, and/or does a signed tx remain valid forever? (Read 762 times)
July 31, 2015, 09:48:18 AM
Assuming that no protocol changes to transactions happens and no one has spent those inputs yet, then that transaction can be broadcast whenever you want. There is no timestamp and the time is not a part of the transaction unless you include a locktime.
July 31, 2015, 09:15:51 AM
If I were to push the tx in a month or a year from now, would it still be processed normally?
It should be. But how about 10 years? 100 years? This is a tough question as that means every rule change in the future must be backward compatible forever.
Not all rule changes are truly backward compatible. There are changes (IIRC) that affected all blocks after a certain block height, that were not backwards-compatible.
July 31, 2015, 09:09:15 AM
If I were to push the tx in a month or a year from now, would it still be processed normally?
It should be. But how about 10 years? 100 years? This is a tough question as that means every rule change in the future must be backward compatible forever.
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
July 31, 2015, 06:34:13 AM
Bitcoin transaction does not have a timestamp in it. https://en.bitcoin.it/wiki/Protocol_documentation#tx
Assuming inputs are still unspent and transaction is valid, it will be treated normally.
Assuming inputs are still unspent and transaction is valid, it will be treated normally.
July 31, 2015, 06:02:02 AM
Suppose I create a tx now, sign it, so I have the raw tx data, but I do not push (broadcast) it yet.
If I were to push the tx in a month or a year from now, would it still be processed normally? Or does the tx (or its signature) contain a timestamp of sorts, so that nodes might ignore or discard the tx as 'too old' or 'expired' or something.
Obviously assuming that the inputs are still unspent.
If I were to push the tx in a month or a year from now, would it still be processed normally? Or does the tx (or its signature) contain a timestamp of sorts, so that nodes might ignore or discard the tx as 'too old' or 'expired' or something.
Obviously assuming that the inputs are still unspent.
Jump to: