VerixID Documentation

Overview

VerixID is a lightweight, web-native digital asset integrity framework. We never ingest or store your actual files — only a deterministic cryptographic fingerprint (hash) is committed to our append-only ledger alongside an immutable UTC timestamp.

The service operates around three primary functions:

• 1. Submit — Record cryptographic proof of existence for a file to obtain a unique Record ID.
• 2. Verify — Confirm whether a Record ID exists and cryptographically authenticate state via an Ownership Key.
• 3. Certificate of Authenticity (COA) — Issue a durable, identity-bound public certificate of ownership.

How It Works

VerixID functions as a digital notary for file existence: it certifies that a specific payload existed at a precise moment in time, in an exact structural state, registered by an entity possessing a cryptographic secret.

The Submission Workflow

1. Select and drop your document into the client interface.
2. Your web browser generates the file's SHA-256 hash locally via native Web Crypto APIs.
3. The payload hash and UTC server timestamp are submitted to the VerixID core.
4. The engine generates a unique Record ID and a corresponding Ownership Key.
5. You receive a digital receipt containing both values. Store these credentials carefully; lost keys cannot be recovered.

The Verification Workflow

1. Enter the Record ID on the Verify page.
2. The engine performs a lookup against the ledger state.
3. Upon match confirmation, registration metadata is displayed.
4. Optionally supply the Ownership Key to complete zero-knowledge proof of record entitlement.

Record Statuses

1. Active

The record exists in the primary ledger; public verification and key validation are active.

2. Not Found

The requested Record ID does not exist in the VerixID index or has exceeded its retention TTL.

Quickstart Guide

Get started with VerixID in three straightforward steps:

1. Register Your Asset
   Navigate to the main dropzone and select your file. Processing completes entirely inside your browser runtime.
2. Store Receipt Credentials
   Safeguard the resulting Record ID and Ownership Key. Ownership Keys are unrecoverable if misplaced.
3. Verify On-Demand
   Anyone can inspect a Record ID on the Verify interface without creating an account.

Record ID

A Record ID is an alphanumeric identifier issued by VerixID upon record commitment.
Example: vx202606cc1f5dd1 (18-character structured string).

Purpose of a Record ID

A Record ID acts as an index pointer to a specific ledger entry — conceptually similar to a tracking manifest number rather than the parcel contents itself.

Ownership Key

An Ownership Key is a cryptographic token generated client-side during document registration. It serves as cryptographic proof that the submitter holds authority over a registered entry.

Format

Entropy-rich cryptographic secret string emitted by the engine.

Security

Saves no plaintext copy on VerixID servers. Only standard key hashes are committed for verification validation.

Recovery Policy

Non-recoverable. Because VerixID operates under zero-custody standards, lost Ownership Keys cannot be reconstructed under any circumstances.

Cryptographic Binding

Upon submission, the client engine binds the Record ID, File Hash, and client parameters to issue the key.

The server computes a salt-hashed digest of the key and signs the composite record using Ed25519 asymmetric cryptography. This tightly couples the timestamp, original digest, and owner token into a tamper-evident structure.

Hashes & Cryptography

A cryptographic hash functions as a unique mathematical fingerprint of digital content. Cryptographic primitives like SHA-256 condense arbitrary-length files into a deterministic 64-character hexadecimal representation.

Core Cryptographic Properties

• Deterministic: Identical input data guarantees an identical hex fingerprint.
• Avalanche Effect: Altering a single bit in the file yields an entirely different hash string.
• Pre-image Resistance (One-Way): Reconstructing original files from hash strings is computationally infeasible.
• Collision Resistance: Finding two distinct files that evaluate to the same digest is virtually impossible.

Example Demonstration

Two payloads differing by a single numeric character:

File A: "Lease Agreement #001"
SHA-256: 3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c

File B: "Lease Agreement #002"
SHA-256: 9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a

Ledger & Immutability

The VerixID core maintains an append-only data architecture. Existing committed entries cannot be mutated, overridden, or selectively erased during their lifecycle.

Ledger Payload Composition

File Hash

SHA-256 digest calculated from the submitted file.

Record ID

System identifier string assigned to the entry.

Timestamp

UTC time certified by edge infrastructure upon request ingress.

Ownership Key Hash

SHA-256 hash derivative of the ownership token.

Ed25519 Signature

Asymmetric signature generated by VerixID signing nodes across the composite payload.

Excluded Data (Zero-Knowledge Guarantee)

• Original binary payloads or file content are never transmitted or retained.
• No personally identifiable information (PII) like names or emails are required or attached to standard records.
• Raw, unhashed Ownership Keys are strictly excluded from state storage.

Data Retention & Time-To-Live (TTL)

Free tier records committed to the VerixID ledger operate under a deterministic 1-Year Time-to-Live (TTL)* lifecycle calculated from the initial timestamp. Upon expiration, record indices are permanently purged.

Retention Details

Lifespan

365 Days (1 Year)* from commit timestamp.

Purge Policy

Irreversible index eviction from active state storage.

Notifications

Unmonitored and automated; tracking expiry rests with the registrant.

VerixID Legal Position

VerixID is a technical proof provider. We issue deterministic, tamper-evident cryptographic receipts. Interpretation and legal admissibility of cryptographic evidence remain subject to jurisdictional rules and local litigation practices.

✅ Technical Guarantees

• · File integrity: Proof that a matching file existed in an identical state at the recorded UTC time.
• · Uniqueness: Proof that the SHA-256 fingerprint was committed to our ledger.
• · Ownership key authorization: Cryptographic verification of record entitlement.

❌ Out-of-Scope (Non-Attested)

• · Physical or legal identity of original file creators (unless bound via COA).
• · Substantive truthfulness, legal validity, or enforceability of contract terms.
• · Underlying copyright, trademark, or intellectual property ownership.

Electronic Signatures & Legal Admissibility

Digital asset proof emitted by VerixID aligns with global frameworks governing electronic records and evidence legalities, such as US ESIGN Act / UETA, EU eIDAS Regulations, and international UNCITRAL Model Laws on Electronic Commerce.

Data Integrity

Mathematical hashes demonstrate that an electronic record has remained unaltered since creation.

Audit Trail

UTC server-stamped signatures establish chronological sequence in dispute proceedings.

Privacy & Data Protection (GDPR Compliance)

VerixID incorporates global data protection regulations — including the EU General Data Protection Regulation (GDPR) — into its architecture via Privacy-by-Design.

Data Minimization

Standard submissions collect no personal data, email addresses, or user identifiers.

Client-Side Hashing

Because file content is never transmitted, sensitive business data cannot be exposed via server breaches.

Certificate of Authenticity (COA)

The VerixID COA is a premium, durable proof artifact. It links document integrity to an identity claim (ID/Passport Hash) with an extended validity lifetime of 10 years*.

COA vs Ledger

Ledgers provide transient temporary indexes (1-year TTL). COAs create standalone, long-term cryptographic evidence snapshots valid independently of active ledger cycles.

Ledger Record

Transient verification pointer with a 1-year default TTL.

COA Document

Autonomous certificate artifact with 10-year standalone validity*.

Identity Claim

Identity claims bind a COA to an official ID (e.g., Passport or National Tax ID) without storing plaintext numbers on our infrastructure:

identity_hash = SHA-256(identity_value + coa_id + salt)

When presenting proof to third parties, entering the raw identifier recomputes the matching hash, validating entitlement in zero-knowledge style.

Ownership Verification

Public observers can view COA metadata, but proving active entitlement requires re-submitting the exact underlying identity credential to trigger hash verification.

View Specimen COA Certificate

Legal & Evidentiary Use

COAs provide robust evidentiary material for legal counsel, forensic investigators, IP audits, and corporate compliance chains.