Why HCC exists.
The most expensive thing in clinical research is the data — and historically, none of that money has reached the people whose lives generated it. A research lab pays a vendor; the vendor licensed an extract from a hospital; the hospital sourced it from charts written about patients who never knew. The transaction is real, the patients are absent, and the system has functioned this way for decades.
HCC closes the loop. When a researcher buys access — and only when — HCC is minted and distributed to the wallets of the patients whose data the researcher accessed. The researcher pays in HCR or USD; the chain mints fresh HCC to the contributing wallets in proportion to how their cohort participated. The data never moves. The receipts do.
How HCC is minted.
HCC mint is buy-side. There is no axis-lift trigger and no time-based emission — HCC exists because someone paid to access a dataset, and the chain is recording who made that data possible.
- Researcher contracts for a query against a de-identified cohort sitting in Datavault.
- Patients in the cohort have, by enrollment-time consent, agreed to be eligible for that class of query.
- The query runs inside a sealed enclave; only summary results leave; raw records do not.
- The chain mints HCC to the participating wallets, weighted by data density and recency.
Patients can revoke consent at any time. Revocation cancels future eligibility immediately; past mints stay in the wallet (the transaction has already happened, and the chain is append-only) but no further mint events route to that wallet from that contract.
Imagine a pulmonary-rehab outcomes study at a teaching hospital purchases access to a 14,200-patient cohort — opted-in patients in Datavault who completed a rehab block in the past 24 months. The researcher pays 4,200 HCR for query access. The query returns a summary table; no raw record leaves. The chain mints 4,200 HCC total to the 14,200 wallets, weighted by per-patient data density. Median patient receives 0.31 HCC; the most-data-rich wallet receives 1.4. Numbers and study are illustrative — no contract of this size has been signed yet.
How HCC is priced.
HCC is not pegged. It floats. Once liquidity exists on hc.exchange, the most common counterparty trades will be HCC↔HCR and HCC↔USD. Researchers will typically settle their contracts in HCR (because that's what they hold from prior license payments to the network); patients will hold or convert as they prefer.
HCC's price is a function of researcher demand for cohort access and patient willingness to opt in. When demand is high and opt-in rates are flat, price will rise. When opt-in rates climb (pulling more wallets into mint events), price will moderate. Both metrics will be tracked and published on chain. We do not intervene.
"The coin is not the trade. The coin is the receipt that the trade happened, and that the patient was a party to it."
HCC vs HCR — different lanes, same chain.
| Property | HCR | HCC |
|---|---|---|
| Mint trigger | Verified axis-lift event | Researcher dataset purchase |
| Mint side | Earn-side (clinical) | Buy-side (data) |
| Primary holder | Patients who improved | Patients who shared data |
| Quoted in | USD (and HCC) | HCR (and USD) |
| Settlement | Same chain, mint lane | Same chain, data lane |
| USD-pegged | No | No |
| Site | coin.health | coin.healthcare |
Consent & revocation.
Eligibility is opt-in only. At signup, patients pick from a menu of consent classes — for example, "any de-identified outcomes research," or "non-commercial cardiovascular research only," or "no third-party access of any kind." Each class is a tag on the wallet; the chain only routes mint events to wallets whose tag matches the contract.
Revocation works at the same granularity. A patient can drop a class, narrow it, or pause all participation through their Guardian Orb settings. The change propagates within one block. The chain logs the change; future contracts that would have included the wallet skip it without any other party being told why.
Privacy guarantees.
The architecture is enforced at the protocol layer, not by policy:
- Sealed enclave. Researcher queries run inside a Datavault enclave with no outbound network. Aggregated results leave; raw records do not.
- Cohort floor. Queries with effective n < 200 are rejected by the enclave before any computation runs.
- Differential privacy. Small-cell statistics receive calibrated noise to prevent re-identification through cell-suppression analysis.
- Pseudonymous wallets. Chain transactions reference wallet addresses; wallet-to-identity mapping lives in Datavault and is never published on chain.
- Audit log. Every column touched by every query is logged, with the log hash pinned on chain.
External attestations are scheduled as part of the Phase 2 launch cycle. See attestations for the timeline. We will not claim an attestation has been performed until the signed report is published.
Who governs HCC.
HCC governance follows the same pattern as the rest of the Conceptual Chain: Phase 1 governance is operator-signed (Conceptual Healthcare Corporation), and Phase 2 introduces a multi-party Trust Council drawn from licensed healthcare institutions, regulated custodians, and at least one sovereign health authority. Council seat count, supermajority threshold, and ratification process will be ratified as on-chain governance amendments before Phase 2 begins. See the chain governance page for the broader roadmap, and the HCC governance log for HCC-specific events as they occur.
Legal posture.
HCC is a commodity-class digital asset, the same posture as HCR. It is not registered as a security, is not marketed as an investment, and holding HCC does not confer ownership in Conceptual Healthcare Corporation. The mint is a receipt for participation in a research transaction; the secondary market is for liquidity, not capital formation.