How VerixID Works

From a file on your device to a verifiable registration record.

The flow

Your File
   │
   ▼
SHA-256
   │
   ▼
Fingerprint (64 hex chars)
   │
   ▼
VerixID Registration
   │
   ├── Timestamp
   └── Cryptographic Signature
   │
   ▼
Signed Registration Record
   │
   ▼
Verification (anytime, by anyone)

Step by step

1. Fingerprinting

The file is hashed locally using SHA-256. The output is a 64-character hexadecimal fingerprint that uniquely represents the file's content.

SHA-256
7f83b1657ff1fc53b92dc18148a1d65dfc2d4b1fa3d677284addd200126d9069

The file does not need to be uploaded for fingerprinting. Only the hash is submitted.

2. Registration

The fingerprint is submitted to VerixID along with a timestamp. The system creates a registration record binding the fingerprint to that moment in time.

3. Signing

The registration record is cryptographically signed. This makes the record tamper-evident: any modification to the record after signing would invalidate the signature.

4. Verification

At any later time, anyone can:

The file stays with you. The proof stays verifiable.

Why no file upload is required

A SHA-256 fingerprint is sufficient to identify file content for verification purposes. Uploading the file itself would introduce:

By design, VerixID avoids all of these. Only the fingerprint and registration metadata are stored.

Frequently Asked Questions

How does VerixID verify a digital file?

VerixID computes a SHA-256 fingerprint of the file, binds it to a timestamp, and signs the resulting registration record. Verification later consists of recomputing the fingerprint from the original file, looking it up in VerixID, and confirming that the registration record is valid and signed. The file itself is never uploaded.

Does VerixID require uploading the file?

No. Only the SHA-256 fingerprint is submitted to VerixID. The file does not need to be uploaded for fingerprinting or for verification. This zero-custody design eliminates privacy risks, storage obligations, and a large portion of the attack surface.

What cryptographic primitives does VerixID use?

VerixID uses SHA-256 for file fingerprinting, cryptographic signatures for tamper-evident registration records, timestamps for time anchoring, and deterministic recomputation for verification. SHA-256 produces a 64-character hexadecimal fingerprint that uniquely represents the file's content.

What happens during VerixID registration?

During registration, the fingerprint is submitted to VerixID along with a timestamp. The system creates a registration record binding the fingerprint to that moment in time, and cryptographically signs the record so that any later modification would invalidate the signature.

How long does verification take?

Verification is deterministic and does not depend on trust in the operator. Once the fingerprint is recomputed from the original file and looked up, the registration record can be checked quickly. The time required depends primarily on the size of the file for hashing, not on any server-side processing.

Can the same file be registered twice?

The same file content produces the same SHA-256 fingerprint, so the first registration establishes the earliest point in time at which that fingerprint is known to VerixID. Subsequent registrations of the same fingerprint do not change the original registration timestamp.

What happens if a file is modified?

Any modification to a file changes its SHA-256 fingerprint. A modified file will not match the fingerprint associated with an existing registration, so verification will fail for that modified version. This is a property of the cryptographic hash function, not a policy choice.

Is the file stored anywhere during the process?

No. The file stays with the user. Only the fingerprint and registration metadata are stored. The zero-custody model means VerixID never has access to the file's content, and therefore cannot leak, retain, or be compelled to disclose it.

Next

What Proof of Origin means → Register a file →