0
Why does a TSA first appends the timestamp and hashes the combination of timestamp and data? This product is then signed and send to the client back with the timestamp. Why not signing hash + timestamp?
0
Why does a TSA first appends the timestamp and hashes the combination of timestamp and data? This product is then signed and send to the client back with the timestamp. Why not signing hash + timestamp?
What is a TSA? What protocol or system is this question about? – Pieter Wuille – 2019-09-16T15:05:34.787
@PieterWuille Trusted Time Stamping. TSA is Timestamping Authority. – user674907 – 2019-09-17T15:55:27.747
I don't know about that, but a quick search tells me you're maybe talking about RFC 3161? If so, that seems off topic here. – Pieter Wuille – 2019-09-17T15:56:46.330
@PieterWuille Yeah. this is the protocol. But I do not understand the design choise. – user674907 – 2019-09-17T16:37:35.620
This seems unrelated to Bitcoin. – Pieter Wuille – 2019-09-17T16:38:14.597
I thought this stackexchange is about everything dealing with consensus, byzantine, trusting third parties, etc. ... (everything bitcoin is built on)? – user674907 – 2019-09-17T16:40:02.563
It is about technologies that apply to supporting the bitcoin currency. Timestamping in an abstract sense certainly does, but not the specifics of RFC 3161, which is unrelated to how timestamping services for Bitcoin work. – Pieter Wuille – 2019-09-17T16:41:29.190
If u go to wikipedia page: https://en.wikipedia.org/wiki/Trusted_timestamping It seems like a general concept. I just want to know if I forget something, or about advandatages, such a design choice has. Maybe privacy, scalability, ... I do not know. :/
– user674907 – 2019-09-17T16:43:22.687