Verify a record

From format version 1.1, a Registration Decision Record prints the hash of the newest event in the project's audit trail when the record was made, under "Audit chain head", where its audit trail verified at that time. The record also lists the SHA-256 of the CSV and of each XML file the export made. The file checksums.sha256 in the export package lists them with the SHA-256 of the record. Enter any of these hashes here. Records of format version 1.0 do not print a chain head.

What the check shows

• For a chain head, whether the hash is an event in an audit trail EUDAMate holds, when that event was recorded and how many events the trail has.
• For a file, whether an export made it and when. The files are the CSV, each XML file, the record in the package and the package itself.
• Whether the audit trail behind the hash verifies against its stored hashes now. A trail whose project data was deleted under the retention policy is answered from the seal kept when it was deleted.
• For a registered fingerprint, when it was first registered.

What it does not show

• It does not identify the project, the devices or the account. It shows no values.
• A match shows an export made this file. It does not show who holds it or that EUDAMED accepted it.
• A match does not show that the copy of the record you hold was made from this audit trail. Compare the number of events and the time with the record.
• The hashes of uploaded files are not answered. A record or package made before this check was added cannot be found by its own hash. Check its audit chain head instead.
• EUDAMate keeps the audit trail and runs this check. It is not an independent attestation or timestamp.
• It does not show that any value in a record is right. The record shows how each value was decided and who decided it.
• A record carries no digital signature. Only the record in an export package has a hash this page knows. A record downloaded later is a new record with its own generation time.

Register a fingerprint

A record made by any tool can be dated here. Pick the record file or paste a SHA-256, such as the audit chain head the record prints. Your browser computes the fingerprint of a file itself. Only the fingerprint is sent to EUDAMate. The file never leaves your browser. EUDAMate does not see the record and does not check it.

• EUDAMate stores the fingerprint and the time it arrived. It stores nothing about who sent it.
• A fingerprint cannot be turned back into the file. Registering it again does not change the first time.
• When someone enters the fingerprint in the check above, the page says when it was first registered. A match shows the file existed unchanged since that time.
• It does not show who made the file or that its content is right. It does not show that EUDAMED accepted anything.

A record's producer can also anchor its chain head with any RFC 3161 timestamp authority. The format does not depend on any one anchor. The page How to check a record says how to check either.

The format of the record is described in the Registration Decision Record specification.