The Birthmark Standard Foundation

Hardware-Backed Photo Authentication

A system that proves photos came from real cameras, not AI generators. By creating unforgeable digital signatures at the moment of capture and recording them on a blockchain operated by a coalition of journalism and fact-checking organizations, we're restoring trust in photography.

The Problem We're Solving

Deepfake Proliferation

AI-generated images are increasingly indistinguishable from real photographs, creating a crisis of trust in visual media.

Metadata Stripping

Existing solutions like C2PA rely on metadata that's easily removed through format conversion, cropping, or screenshotting.

Credibility Crisis

Professional photographers' legitimate work is dismissed as fake, undermining journalism, legal evidence, and democratic discourse.

Key Concepts

What is Hashing?

A hash converts data of any size into a fixed-length unique fingerprint. The same input always produces the same hash, but even the tiniest change creates a completely different one. Critically, you cannot convert a hash back into the original data.

Example: An image produces hash "a3f2b8...". Change one pixel, and you get an entirely different hash like "d91e4c...".

What is Key Encryption?

Encryption scrambles data using a secret key so only authorized parties can decrypt and read it.

Example: Your camera encrypts its identity—only the manufacturer with the decryption key can verify it's legitimate.

Why Blockchain?

Blockchain is a permanent, tamper-proof public ledger. Once data is recorded on a blockchain, it cannot be changed or deleted—even if companies go out of business or try to censor records.

Example: When your photo's hash is recorded on the Birthmark blockchain, that record is permanent and publicly verifiable by anyone, forever. The blockchain is operated by trusted institutions like universities and archives.

1. Creating the Image Hash

Camera-Side Authentication

At the moment of image capture, a secure chip in the camera creates an unforgeable digital signature before the image is even processed.

  • Raw image hashing: A hash is created from the raw image data before any processing like white balance or compression
  • Processed image hashing: A second hash is created from the processed image that you actually save
  • Timestamp and metadata: The camera records when the photo was taken and optionally a hash of the GPS coordinates
  • Parallel processing: Authentication happens in the background while your photo is being captured—no delays or extra steps

Result: A bundle containing both image hashes, timestamp, and optional location hash—ready to be sent to the aggregation server for validation and blockchain recording.

Diagram showing parallel hashing workflow: camera captures image, creates raw and processed hashes simultaneously, sends to Birthmark Media Registry for validation and blockchain recording

Click to view full size

2. Validating Camera Authenticity

Diagram showing privacy-preserving camera validation: camera encrypts calibration file with key table, submission server forwards certificate to manufacturer, manufacturer validates and returns PASS/FAIL without seeing image hashes

Click to view full size - Shows separation of concerns: manufacturer validates camera, never sees image content

Privacy-Preserving Validation

The manufacturer confirms that images come from real cameras without being able to see what photographers are capturing or track individual cameras.

  • Encrypted camera identifiers: Each camera's unique sensor identifier is encrypted using randomly assigned keys, so only the manufacturer can verify it
  • Separation of concerns: Manufacturers receive the encrypted camera ID but never see image hashes, timestamps, or locations
  • Anonymity sets: About 12,000 cameras share each encryption key, preventing tracking of individual cameras
  • Binary response: Manufacturer returns only PASS (legitimate camera) or FAIL (unknown/forged)—nothing else

3. Verifying Images on Blockchain

Immutable Public Verification

Anyone can verify an image's authenticity by checking the blockchain record—no corporate gatekeepers or subscription services required.

  • Direct hash storage: Full SHA-256 image hashes are stored directly on-chain on the custom Birthmark blockchain, eliminating the need for complex cryptographic proofs
  • Institutional validators: The blockchain is operated by trusted institutions (universities, archives, journalism organizations) running validator nodes
  • Zero gas fees: No transaction costs—institutions donate hosting as a public service for truth in media
  • Public verification API: Open protocol allows anyone to build verification tools without asking permission
Diagram showing user verification workflow: select image, hash it locally in web browser, send hash to Birthmark Blockchain, receive match result with timestamp and metadata

Click to view full size - User verification happens client-side

Learn More

📐 Technical Architecture

Deep dive into the cryptographic foundations, system components, privacy guarantees, and security model.

Read Technical Details →

⚖️ Governance Model

Coalition membership, node ownership, voting structure, and the legal framework that makes the system censorship-resistant.

Read Governance Charter →

💻 Source Code

All code is open source under Apache License 2.0. Explore the implementation, contribute, or deploy your own node.

View on GitHub →

Why Birthmark Standard?

🔓

Open Source

Fully transparent system—no corporate secrets or proprietary control.

🛡️

Privacy First

Anonymous camera identifiers prevent tracking while maintaining authentication integrity.

⛓️

Blockchain Permanence

Records survive even if companies go bankrupt or images are cropped and reposted.

💰

Zero Cost

No gas fees or transaction costs—institutional validators donate hosting as a public good.

🤝

Complementary to C2PA

C2PA provides rich metadata embedded in files. Birthmark provides independent blockchain verification that survives when metadata gets stripped by social media.

🌐

Federated

Anyone can run servers—no single point of control or censorship.

🛡️

Censorship Resistant

Legal compulsion triggers node removal, not compliance. Governments cannot subvert the network—only remove individual nodes from it.