Data Yield Protocol
Your body generates data every second — heartbeats, glucose levels, sleep cycles, medication responses. That data is worth billions to pharmaceutical companies, AI researchers, and health systems. Today, they take it for free. The Data Yield Protocol lets you earn from it while keeping full control.
How It Works
┌─────────────────────────────────────────────────────────────────────┐
│ DATA YIELD PROTOCOL │
│ │
│ Patient Oracle Sponsor │
│ ─────── ────── ─────── │
│ │
│ 1. Browse programs 4. Evaluate blindly 7. Create │
│ 2. Enroll + consent 5. Generate proof program │
│ 3. Submit commitments 6. Award credits 8. Fund │
│ 9. Dashboard │
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Poseidon │───→│ NaCl │───→│ Oracle │───→│ Merkle │ │
│ │Commitment│ │ Box │ │ Verify │ │ Anchor │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ │
│ Patient never Only oracle Pass/fail + Immutable │
│ sees threshold can decrypt ZK proof audit trail │
└─────────────────────────────────────────────────────────────────────┘
Core Principles
1. Patient Sovereignty
You own your data. You choose which programs to join. You can exit at any time. Credits earned before exit are retained. Your encryption keys never leave your device.
2. Anti-Spoofing by Design
Patients never see the exact thresholds that determine compliance. If you knew "walk 8,000 steps", you'd fabricate 8,001. Instead, you see "submit your activity data" — and the Blind Compliance Oracle verifies against hidden criteria.
3. Sponsor Privacy
Sponsors (pharma, CROs, AI companies) never see individual patient data. They see aggregate compliance rates, geographic distribution, and budget metrics. The oracle sits between both parties.
4. Verifiable Compliance
Every compliance evaluation produces a cryptographic proof — HMAC-signed today, Groth16 ZK proofs in the next phase. Proofs are anchored in Merkle trees on-chain for tamper-evidence.
5. Fair Pricing
Dynamic multipliers ensure fair compensation:
- Geographic scarcity: African data is 3x more valuable because it's 30x underrepresented in medical AI
- Rarity: Ultra-rare disease data (CF, Huntington's, ALS) earns premium rates
- Early bird: First contributors earn 1.5x because they take the most risk
- Supply/demand: Pricing adjusts as programs fill up
Program Categories
| Category | Example Programs | Typical Annual Yield | Rarity Range |
|---|---|---|---|
| Rare Disease | Cystic Fibrosis, Huntington's, ALS, EDS, SLE | $300–$840/yr | 3–5 (Rare–Ultra-Rare) |
| Chronic Condition | Type 2 Diabetes, Heart Failure, COPD, Epilepsy | $120–$360/yr | 1–3 (Common–Rare) |
| Genomic | Pharmacogenomics Response | $300/yr | 3 (Rare) |
| AI Training | Medical Imaging, Clinical NLP, Digital Biomarkers | $96–$500/yr | 1–4 (Common–Very Rare) |
| Mental Health | Depression & Anxiety, Mental Health NLP | $180–$300/yr | 2–3 (Uncommon–Rare) |
| Wellness | Steps, Sleep & Stress | $24/yr | 1 (Common) |
Yield Calculation
Monthly Payout = (Annual Promise / 12)
× Early Bird Multiplier (1.0 or 1.5)
× Region Multiplier (1.0–3.0)
× Compliance Tier Multiplier (0–1.1)
× Dynamic Pricing Multiplier (0.85–1.5)
A patient in Nigeria (3.0x region) enrolling early (1.5x) in the Cystic Fibrosis program ($600/yr) with excellent compliance (1.1x):
$600 / 12 × 1.5 × 3.0 × 1.1 = $247.50/month
Compare to a US patient (1.0x) enrolling after funding (1.0x) with good compliance (1.0x):
$600 / 12 × 1.0 × 1.0 × 1.0 = $50.00/month
The Nigerian patient earns 5x more because their data fills a critical gap in medical AI training data.
System Components
| Component | Location | Purpose |
|---|---|---|
| Blind Compliance Oracle | edh-core + backend | ZK-friendly compliance verification |
| Sponsor Marketplace | backend + web | Self-service program creation and funding |
| Dynamic Pricing Engine | backend | Supply/demand-driven yield optimization |
| Data Submission | all clients | Patient-side commitment generation |
Cross-System Dependencies
Data Yield Protocol
├── ← IPFS (encrypted data storage)
├── ← BIA (biological identity for Sybil resistance)
├── ← Merkle Anchoring (proof immutability)
├── ← EDH Core (Poseidon hashing, NaCl encryption)
├── ← Stripe Connect (sponsor escrow)
├── → Notification Service (enrollment, compliance, payout events)
├── → Earnings/Payouts Module (credit → cash conversion)
└── → Gamification (compliance streaks → XP)
What's Next
- Read the Blind Compliance Oracle spec for the cryptographic design
- See the Sponsor Marketplace for program creation
- Understand Dynamic Pricing for yield optimization
- Review Data Submission for client integration