No permanent ROCKVALID account
Certification is designed as a separate transaction for a specific document, not as a prerequisite to join another closed platform.
Make trust
independently visible.
ROCKVALID is built around a simple idea: a digital document should be able to carry evidence about its integrity, origin and confirmation process without becoming permanently dependent on a private document silo.
On the fly
One document. One process. One durable proof.
The OTF workflow replaces the earlier account-and-wallet journey with a direct certification process. A person selects a PDF, completes the required provider checks and receives a new document containing a verifiable ROCKVALID record.
No personal blockchain wallet
Users should not need cryptocurrency, test tokens or blockchain expertise to create a public cryptographic proof.
A verified process, not a hidden assertion
The evidence should link the exact document version to the checks, action, issuer and time recorded for that specific certification.
Data minimisation
Document contents should be processed only as required for the workflow, while the public proof remains compact and contains no PDF.
Integrity that travels with the document
The completed PDF is intended to remain useful outside ROCKVALID: it can be shared, stored and checked as the exact certified version.
Publicly inspectable foundations
Verification should rely on reproducible cryptographic rules and public proof data, not on an unexplained “trust us” result.
ROCKVALID does not attempt to own trust. It attempts to make the evidence behind trust independently visible.
The OTF evidence
Certify and verify on the fly
A ROCKVALID proof is intended to connect several facts that are often separated across documents, payment systems and private databases.
The document
The proof relates to one exact PDF version. Any later modification changes its cryptographic fingerprint.
The recorded person
Where the selected provider flow supports it, returned identity or account-holder data can be checked against the name used in the process.
The declared action
The record should state what was done in relation to the document: for example confirmed, signed, issued, approved or certified.
The issuer and time
Verification should confirm that an authorised ROCKVALID issuer created the proof and that the corresponding public record exists.
Privacy by architecture
Store less. Prove what matters.
Many systems collect documents first and then build walls around them. ROCKVALID follows a different direction: data that is not required for the service should not become a permanent central archive.
What belongs in the proof
- cryptographic document fingerprints;
- minimal identifiers and technical proof data;
- the recorded action, issuer and time; and
- only the identity-related data required by the defined process.
What should not become a public archive
- the PDF itself;
- online-banking credentials;
- unnecessary document contents; and
- provider data unrelated to certification.
Clear boundaries
Evidence is not absolute truth
A trustworthy system must be precise about what it can and cannot prove.
ROCKVALID aims to verify
- document integrity;
- consistency with the public proof;
- the authorised issuer process;
- the recorded identity, action and time; and
- whether the certified PDF remained unchanged.
ROCKVALID does not automatically prove
- that every statement in the PDF is factually true;
- that every person had all legally required authority;
- that a document is lawful in every jurisdiction; or
- that a legally prescribed notarised or qualified form is satisfied.
ROCKVALID is not currently a qualified trust service provider and does not provide a qualified electronic signature under eIDAS. The current OTF version is a public demo; workflows and proof formats may change.