What Is .well-known/jwks.json?
How third parties verify TimeProof identity attestations independently without contacting TimeProof.
Identity verification is essential for connecting timestamps to real people. .well-known/jwks.json is part of how TimeProof ensures that timestamps are attributable to verified individuals.
Why .well-known/jwks.json Matters
In the context of digital evidence and file protection, .well-known/jwks.json plays a critical role. Here is why you should understand it:
For Creators and Professionals
When you need to prove that a file existed at a specific time, the underlying technology must be trustworthy. .well-known/jwks.json is part of what makes TimeProof timestamps independently verifiable — anyone can check the proof without trusting any single company or authority.
For Legal and Compliance Teams
Evidence must be reliable, understandable, and verifiable. Understanding .well-known/jwks.json helps legal professionals explain to courts and regulators how blockchain-based evidence works and why it should be trusted.
For Developers and Technical Teams
If you are integrating timestamping into your application or workflow, understanding .well-known/jwks.json helps you make informed architectural decisions and explain the technology to stakeholders.
How TimeProof Uses .well-known/jwks.json
TimeProof integrates .well-known/jwks.json into its identity attestation system. This ensures that timestamps can be attributed to verified individuals, and that third parties can independently verify the identity connection.
How Blockchain Timestamping Works
When you timestamp a file with TimeProof, TimeProof uses client-side file hashing (SHA-256). That 64-character value is the unique fingerprint for the exact version you selected, and if even one byte changes, the hash changes too. Your file never leaves your device.
TimeProof proves file existence by anchoring file hashes to the Polygon blockchain. The blockchain records the hash, timestamp, and transaction ID permanently, so anyone can verify the record independently on Polygonscan.
This is where .well-known/jwks.json stops being theory and becomes a usable proof workflow.
Practical Example
Consider a photographer who timestamps their portfolio images. The .well-known/jwks.json connects the timestamp to the photographer’s verified identity, so anyone verifying the proof knows not just when the image was timestamped, but who timestamped it.
Key Takeaway
.well-known/jwks.json is not something you need to understand to use TimeProof — the platform handles all technical details automatically. But understanding it builds confidence in the technology and helps you explain it to others when your proof is challenged.
Learn More
TimeProof packages this live workflow into one unified credit system, so you can apply the concept above to real files without needing crypto expertise.
- Scheduled timestamps: 1 credit per file - available to everyone, with proof available within 6 hours.
- Instant timestamps: 2 credits per file - available to verified subscribers, anchored in about 2 seconds.
- Legal-Grade: Starter and Pro: 50 credits up to 25 files, then +2/file. Business: 25 credits up to 25 files, then +1/file. Enterprise: included.
One-time packs start at $15 for 100 credits. Verified monthly plans start at $19/month and include identity verification for instant timestamps and Legal-Grade.
Scheduled timestamps handle routine proof, verified instant timestamps handle immediate needs, and Legal-Grade adds the formal evidence package when the matter is higher stakes.
Start creating tamper-proof proof for your files today.