If I archive a timestamp for 30+ years, how does GuardTime ensure that the calendar hash information is available when I need to verify the timestamp?
The goal of GuardTime is to provide independently verifiable timestamps. This implies that there cannot be any dependence on GuardTime in terms of any information that is necessary to verify the timestamps. There are several ways how GuardTime makes that possible: • The calendar hash database is distributed to the public domain and available to everyone for auditing and archiving purposes; • After a newspaper publication is printed, the necessary information to bind a timestamp with the physical artifact can be computed from the calendar hash database and stored.
Related Questions
- If I archive a timestamp for 30+ years, how does GuardTime ensure that the calendar hash information is available when I need to verify the timestamp?
- Does the UK Data Archive ensure that ethical guidelines were followed by researchers for the collection of data that are archived by the Archive?
- Does OUtlook Calendar auto archive somewhere?