Understanding Your Timestamp Certificate
What Is a Timestamp Certificate?
When TimeProof anchors your file’s hash to the blockchain, it generates a PDF certificate that summarizes the proof in a human-readable format. The certificate is your portable record — it contains everything a third party needs to independently verify that your file existed at the recorded time.
The certificate itself is not the proof. The proof lives on the Polygon blockchain, permanent and immutable. The certificate is a convenient reference that tells you (and anyone else) exactly where to find and verify that proof.
Certificate Fields Explained
File Information
| Field | Description |
|---|---|
| File Name | The name of the file you timestamped |
| File Hash (SHA-256) | The 64-character hexadecimal fingerprint of your file |
| File Size | The size of the original file in bytes |
The file hash is the critical field. This is the unique fingerprint that was recorded on the blockchain. To verify the certificate, re-hash the original file and confirm this value matches.
Timestamp Information
| Field | Description |
|---|---|
| Timestamp Date | Human-readable date and time (your local timezone) |
| Timestamp (UTC) | The timestamp in UTC for unambiguous reference |
| Credit Type | IT (Instant) or ST (Scheduled) — the type of credit used |
The timestamp reflects the block time on the Polygon blockchain — the moment the miner confirmed the transaction containing your hash. For IT timestamps, this is seconds after submission. For ST timestamps, this is the time the batch was anchored.
Blockchain Details
| Field | Description |
|---|---|
| Network | The blockchain network (Polygon mainnet or Amoy testnet) |
| Transaction Hash | Unique identifier for the blockchain transaction |
| Block Number | The specific block containing the transaction |
| Merkle Root | The root hash of the Merkle tree (for batched files) |
| Contract Address | The TimeProof smart contract address |
The transaction hash is your direct link to the blockchain record. Enter it on Polygonscan to see the transaction independently — confirming the timestamp without relying on TimeProof.
Verification Section
| Field | Description |
|---|---|
| Verification URL | Direct link to the TimeProof verification page for this file |
| Polygonscan URL | Direct link to the transaction on Polygonscan |
| QR Code | Scannable code linking to the verification page |
Share these links with anyone who needs to verify your proof. Both work without a TimeProof account.
Standard vs. Legal-Grade Certificates
Standard Certificate (IT or ST)
The standard PDF certificate includes all fields listed above. It proves the file hash was recorded on the blockchain at the stated time.
Legal-Grade Certificate
The Legal-Grade package replaces the standard PDF with a more detailed certificate and adds six additional files. The LG certificate also includes:
- TimeProof branded header with Legal-Grade badge
- Verified Identity section — showing that the owner was identity-verified at the time of timestamping
- Organization section — if the timestamp was created under an organization account
See the Legal-Grade Package Guide for a complete breakdown of all seven files in the LG evidence package.
How to Read Your Certificate
Step 1: Confirm the File
Look at the File Name and File Hash fields. The file name should match the file you timestamped. To confirm the hash, re-compute the SHA-256 hash of your original file:
- Online: Use any SHA-256 tool (search “SHA-256 online calculator”)
- macOS/Linux:
shasum -a 256 yourfile.pdf - Windows:
certutil -hashfile yourfile.pdf SHA256
The computed hash must match the hash on the certificate exactly. If it doesn’t, the file has been modified since timestamping.
Step 2: Check the Blockchain
Click the Polygonscan URL on your certificate. This opens the transaction on Polygonscan, the public blockchain explorer. Confirm:
- The transaction exists
- The block timestamp matches your certificate’s timestamp
- The transaction data contains your file’s hash or Merkle root
Step 3: Verify Independently
For the strongest verification, use the Merkle proof (available in the certificate JSON or LG package) to mathematically confirm your file’s hash is part of the anchored Merkle root. This requires no trust in TimeProof — it’s pure cryptographic verification.
Certificate Storage Best Practices
Keep Certificates Paired with Files
Store each certificate alongside its original file. A certificate without the original file can prove a hash existed, but it can’t prove which file that hash represents. A file without its certificate still has the blockchain record, but finding it requires knowing the hash.
Multiple Backup Locations
Store certificates in at least two locations:
- Your local drive or project folder
- A cloud backup (Google Drive, Dropbox, OneDrive)
The blockchain record is permanent, but the certificate is your convenient reference to it. Losing the certificate means you’d need to re-generate it from your TimeProof dashboard or re-compute the hash and verify manually.
Long-Term Archival
For important timestamps (legal, intellectual property, compliance), consider:
- Printing the PDF certificate for physical records
- Including the certificate in your document management system
- Saving the Polygonscan URL in a separate reference file
Related Documentation
- Certificate Guide (Reference) — detailed certificate specifications
- Verifying a Timestamp — complete verification walkthrough
- Polygonscan Verification — using the blockchain explorer
- Legal-Grade Package — the seven-file evidence bundle
Use the live product for timestamping and verification.
The company site owns the technical reference. The app handles runtime workflows.