VeriCell

Proof of Existence, Integrity, Ownership and Time

Your work, fingerprinted.
Anchored on CKB.

AI makes it trivial to alter files, images and code. A SHA-256 hash proves a file is untampered — but not when it existed, who published it, or where to find the current version. VeriCell stores your project's hash manifest in a live cell on the Nervos CKB blockchain: immutable, timestamped, owned by your wallet, and updatable version by version.

Create a proof Verify a file

Try it — hash a file locally

Drop any file here

Hashed in your browser. Nothing is uploaded.

Only fingerprints on-chain

Your files never leave your computer. The cell stores the project title, file paths and their SHA-256 hashes — nothing else. Private by design.

A cell that lives with your version

The proof is a live CKB cell. Release a new version and the old cell is consumed into a new one — an unbroken, verifiable version chain back to the original.

Verifiable by anyone

No account, no login. Anyone can drop a file, recompute its hash and check it against the chain — the block header proves the timestamp, the lock proves the owner.

Create a project proof

Connect your wallet to create proofs. Verifying never requires login.

Files are downloaded from raw.githubusercontent.com into your browser and hashed locally (public repos, up to 200 files).

Works when the server allows cross-origin requests (CORS). Otherwise download the file and use “Local files”.

Search & verify

Open to everyone — no wallet needed.

…or drop a file to hash and verify it

How it works

  1. Select your work. Files, a folder, a GitHub repository or a URL. Every file is hashed with SHA-256 locally in your browser — content never leaves your machine.
  2. Anchor it. VeriCell builds a manifest (title, paths, hashes, source URL, overall hash) and writes it into the data of a new live cell locked to your wallet address. The block header fixes the timestamp; the lock script fixes the owner.
  3. Verify forever. Anyone can recompute a file's hash and check it against the live cell. Ship a new version? Consume the old cell into a new one — the transaction chain is the version history.

On CKB, 1 CKB token = 1 byte of on-chain space. A compact Merkle-root proof needs ~200 CKB; a full manifest scales with the number of files. Capacity is locked, not spent — consume the cell and the CKB returns to you.

Use cases for VeriCell

Software releases

Developers can anchor every release package, installer, source ZIP, checksum file, and changelog.

Useful for

  • Open-source releases
  • GitHub release assets
  • Desktop software installers
  • Mobile app builds
  • Internal enterprise tools
  • SaaS deployment bundles

Proof provided

  • This exact release existed at block time T.
  • The files were not modified after release.
  • The current live cell shows the latest official version.
  • Older versions remain verifiable as consumed cells.

Note: fits especially well since VeriCell already ships CLI, REST API, and GitHub Actions/CI-CD automation paths.

Website and web-app releases

A team can hash and anchor the compiled frontend build folder before deployment.

Useful for

  • Static websites
  • Landing pages
  • Web apps
  • Documentation portals
  • Compliance-sensitive web content

Proof provided

  • This exact website build existed at time T.
  • A user can verify whether a live website matches the official anchored version.
  • If the website changes, the old build becomes a consumed/superseded version.
Legal documents and contracts

A contract, agreement, signed PDF, or negotiation draft can be hashed locally and anchored.

Useful for

  • NDAs
  • Service agreements
  • Employment contracts
  • Partnership agreements
  • Terms and conditions
  • Signed PDFs

Proof provided

  • This exact document existed at time T.
  • The document has not changed.
  • The wallet that anchored it is linked to the submitter.
  • Later versions can be linked as official successors.

Wording note: avoid claiming "legal authorship" — this is proof that the wallet owner knew the hashes at block time, not legal authorship.

Invoices, purchase orders, and business records

Businesses can anchor financial documents without uploading the content.

Useful for

  • Invoices
  • Purchase orders
  • Delivery notes
  • Payment confirmations
  • Audit files
  • Accounting exports

Proof provided

  • A business record existed at time T.
  • The record was not edited after the fact.
  • A later corrected version can be linked while preserving the old version.
Engineering, CAD, and design files

Engineering teams can prove versions of technical files.

Useful for

  • CAD files
  • PCB designs
  • 3D models
  • Architecture drawings
  • Manufacturing specs
  • Product designs

Proof provided

  • This exact design existed at time T.
  • The current approved design can be identified.
  • Old versions remain traceable.
  • Any file hash can be searched backward to find the related project/version.

This is where backward hash search shines — search any SHA-256 to find the related project, version, and path.

Creative work and copyright evidence

Creators can anchor drafts and final versions before publishing.

Useful for

  • Music files
  • Lyrics
  • Manuscripts
  • Artwork
  • Videos
  • Photography
  • Game assets
  • UI/UX designs

Proof provided

  • The creator had this exact work at time T.
  • Earlier drafts and later final versions can be linked.
  • Public publication can happen after anchoring.
Research, academic papers, and datasets

Researchers can anchor papers, datasets, source code, and experiment outputs.

Useful for

  • Preprints
  • Datasets
  • Lab reports
  • Research notebooks
  • Statistical models
  • Reproducibility packages

Proof provided

  • The research material existed at time T.
  • Dataset integrity can be verified later.
  • Updated datasets can be versioned clearly.
AI models, prompts, and datasets

AI teams can anchor model artifacts, training datasets, prompts, and evaluation results.

Useful for

  • Model weights
  • Fine-tuning datasets
  • Prompt libraries
  • Benchmark results
  • Evaluation reports
  • Safety test logs

Proof provided

  • This model/dataset/prompt existed at time T.
  • The current approved version is identifiable.
  • Old versions remain auditable.
Supply-chain documentation

A supplier can anchor certificates and batch documents.

Useful for

  • Certificates of origin
  • Quality-control reports
  • Batch test results
  • Inspection files
  • Compliance declarations
  • Shipping documents

Proof provided

  • The certificate existed before shipment or delivery.
  • The document was not modified.
  • Updated or revoked certificates can be tracked.
Public tenders and procurement

Organizations can anchor bids, tender documents, and submissions.

Useful for

  • Government tenders
  • Supplier proposals
  • Bid submissions
  • Evaluation documents
  • Procurement audit trails

Proof provided

  • A bid existed before the deadline.
  • The submitted document was not altered later.
  • Revised versions are visible as successors.
Bug reports and vulnerability disclosure

Security researchers can privately anchor a vulnerability report before disclosure.

Useful for

  • Bug bounty reports
  • Responsible disclosure
  • Exploit writeups
  • Security audit findings
  • Patch evidence

Proof provided

  • The researcher knew the vulnerability at time T.
  • The report content can later be verified.
  • Updated reports can be versioned.
Journalism and public statements

Journalists, bloggers, and organizations can anchor published material.

Useful for

  • Articles
  • Press releases
  • Public statements
  • Investigative evidence bundles
  • Media archives

Proof provided

  • This version of the article existed at time T.
  • Later edits are separate versions.
  • Readers can verify whether they're seeing the current version.
Policies, procedures, and compliance documents

Companies can anchor internal policies and SOPs.

Useful for

  • HR policies
  • Safety procedures
  • Compliance manuals
  • ISO documents
  • Internal guidelines
  • Training materials

Proof provided

  • This policy version existed at time T.
  • Employees or auditors can check whether it's still current.
  • Old versions remain traceable.
Education and certificates

Schools, trainers, and online course platforms can anchor certificates and course files.

Useful for

  • Diplomas
  • Certificates
  • Course materials
  • Student submissions
  • Exam files
  • Assignment evidence

Proof provided

  • A certificate or submission existed at time T.
  • The document has not changed.
  • Updated or revoked versions can be shown.
Insurance and claims

A claimant can anchor photos, documents, and reports.

Useful for

  • Accident photos
  • Damage reports
  • Claim documents
  • Repair estimates
  • Medical reports

Proof provided

  • Evidence existed at time T.
  • Files were not modified after anchoring.
  • Additional evidence can be added as new versions.
Product documentation and manuals

Manufacturers can anchor manuals and technical documentation.

Useful for

  • User manuals
  • Safety sheets
  • Release notes
  • Firmware documentation
  • Product specifications

Proof provided

  • This manual/spec existed at time T.
  • The latest live version is easy to identify.
  • Old versions remain historically verifiable.
DAO and Web3 governance

Projects can anchor governance proposals, snapshots, and community documents.

Useful for

  • DAO proposals
  • Treasury reports
  • Voting documents
  • Protocol specs
  • Tokenomics documents

Proof provided

  • The proposal existed before voting.
  • The content was not changed after community review.
  • New proposal versions are linked transparently.
API specifications and technical standards

Teams can anchor OpenAPI specs, schemas, and protocol documents.

Useful for

  • API contracts
  • Database schemas
  • Protocol specs
  • Configuration files
  • Interface definitions

Proof provided

  • The technical contract existed at time T.
  • The current live version is known.
  • Breaking changes become visible through version history.