Learn

Click any topic to learn more.

Demonstration Notice: All interactive demos on this page use simulated data for educational purposes only. No actual health data is processed or transmitted.
What is zero-knowledge (ZK)?

Proving something is true without revealing why.

Example:

Traditional: Show your ID to prove you're 21.
Zero-knowledge: Prove you're 21 without showing ID.

Try it:

The math can't lie. That's why it's trustworthy.

What are zkVMs?

Zero-knowledge Virtual Machines run programs privately.

Think of it as:

A computer inside a black box. You see what goes in and what comes out, but not what happens inside.

Health example:

Lab result   [zkVM processes  → "Tested for STIs
document  →   privately]         within 30 days ✓"

The lab values stay private. Only the answer emerges.

What does trustless mean?

You don't need to trust anyone. The math proves itself.

Traditional system:

  • Trust the company to secure data
  • Trust employees not to peek
  • Trust they'll delete when promised

Trustless system:

  • Math guarantees privacy
  • Can't peek at what doesn't exist
  • Nothing to delete

status.health is first in health because:
We combine zkVMs + on-device processing. Others still touch data.

Interactive Verification Demo:

1. Generate a proof on your device

Key principles:

  • Open source verifier: Anyone can audit the verification code
  • Deterministic proofs: Same input always produces same proof
  • No hidden logic: All verification rules are public
  • Cryptographic guarantees: Math, not trust

Verify proofs yourself:

# Download open source verifier
git clone github.com/status-health/verifier
cd verifier

# Verify any proof
./verify proof.json

# Or use the web tool
open verify.status.health

Why it matters: In traditional systems, you trust the company's API. Here, you can verify everything yourself, offline, forever.

What is a TEE?

Trusted Execution Environment. A secure chip in your device.

You already use TEEs:

  • iPhone: Face ID lives in Secure Enclave
  • Android: Fingerprints stored in TrustZone
  • Laptop: BitLocker keys in TPM chip

Why it matters:

Even if your phone is hacked, the TEE stays secure. We process health data there.

See Privacy in Action

Watch how health verification works without exposing data.

Simulate Health Verification:

How Your Data Flows

Track your health data through our system.

1
Your Device
→
2
TEE Chip
→
3
zkVM
→
4
Proof Only

Key point: Your actual health data never leaves your device.

Compare: Traditional vs Zero-Knowledge

See the difference in real-time.

Traditional System

Name: John Doe
DOB: 01/15/1990
Test: STI Panel
Result: Tested
Date: 03/15/2024
Lab: Quest #12345
Breach Risk: HIGH

status.health System

Proof: 0x7f3a9b...
Valid: ✓
Expires: 24h
Breach Risk: ZERO
How Businesses Read Proofs

Reading vs Verifying

When businesses receive a proof, it already contains the result (yes/no).

Example proof received:

{
  "proof_id": "prf_2024_xK9mN3qR",
  "timestamp": "2024-03-15T14:32:00Z",
  "public_inputs": {
    "verification_type": "sti_panel",
    "criteria": "tested_within_30_days",
    "verified_at": "2024-03-15"
  },
  "result": {
    "verified": true,
    "message": "Meets criteria"
  },
  "signature": "0x8f3a9b2c1d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a"
}

Two options:

  1. Just read it: Extract result directly from JSON. No verification needed.
  2. Verify it: Run proof through verifier to confirm validity.

No callback needed:

Everything needed is in the proof. Never contacts status.health.

Verification tools:

  • CLI: status-verify proof.json
  • JavaScript: statusHealth.verify(proof)
  • Binary: ./verifier --proof proof.json