Make important records independently verifiable.
ProofStamp explores how customers, partners and reviewers could check important records without relying only on the system that holds them.
We explain the methods, build prototypes and explore practical uses with people who know the workflow.
Illustrative workflow. The method and implementation depend on the use case.
Add proof where it matters.
Start with a record someone outside your system may need to check. These are possible checkpoints to explore.
Approvals
Preserve the exact document alongside its approval record, so a later reviewer can check which version was recorded.
Inspections
Add independent time evidence to a report and photos at handoff, so later copies can be compared with that checkpoint.
AI review
Preserve selected inputs, outputs and review notes as a package that can be checked later. The capture still needs to be accurate and complete.
Can I check this copy for myself?
An inspection report arrives with a proof tied to that exact file. Later, the recipient can check whether their copy matches and verify any independent time evidence.
With a portable proof and a documented verification method, that check need not depend on access to the sender’s internal database.
These exact bytes existed no later than the verified timestamp.
Example filename, time and result. This does not establish that the inspection itself happened as described.
Explore one checkpoint in your existing workflow.
Your product or internal system could create a proof when a selected record is finalized. The file stays in its usual workflow, with evidence that can be kept and checked separately.
A proposed integration pattern. Adding it requires implementation in the system that handles the record.
What we would explore together
The record. What needs to be preserved, and at which point in the workflow?
The later check. Who needs to verify it, and what question should the proof answer?
The method. Which evidence, privacy requirements and verification dependencies fit the use case?
A small demonstration. Create a proof, change a copy and check both. See whether the result is useful and understandable.
What the evidence can establish
- A supplied file matches the hash recorded in the proof.
- With valid independent time evidence, those exact bytes existed no later than the verified time.
What needs other evidence
- Whether the contents are true or the record is complete.
- Who created, approved, sent or received it.
- Whether it was altered before the checkpoint, or how a dispute should be decided.
Start with one record.
Tell us what it is, who might need to check it and what is difficult to verify today. A short description is enough to start.