Validators · HCC Attestation Mining
Stake HCC to do real work. Earn HCC for the work — not the lock.
Validators on the Conceptual Health protocol stake HCC as good-faith collateral to operate attestation nodes — the independent oracles that sign mining-event evidence (engineering merges, compliance attestations, IP filings, research milestones, clinical encounters, and so on per the published mining taxonomy). Validators earn HCC for each verified attestation they perform. The stake exists to be forfeited on malfeasance, not to produce passive yield.
What a validator actually does
The protocol has a published catalogue of mining lanes — clinical encounters, engineering merges, compliance attestations, IP filings, research milestones, patient-research consent, compute contribution, and others. For each lane, an attesting authority must independently confirm that the action happened before HCC is minted to the actor who performed it. Validators run the attestation nodes that do that confirming.
A validator monitors the data sources relevant to its lane (a clinic's EHR for clinical lanes; a Git repository for engineering lanes; a USPTO feed for IP lanes; an IRB attestation for research-consent lanes), produces a signed attestation for each verified action, and commits the attestation to the chain. The protocol pays the validator HCC for each attestation accepted. The work is real, observable, and independently verifiable.
Why the stake exists
A validator can mis-attest — sign an attestation for an action that didn't actually happen, or fail to detect a fraudulent claim. The stake is the validator's good-faith bond against that risk. If the protocol detects an invalid attestation (via probabilistic audit replay, cross-validator dispute, or external evidence), the offending validator's stake is slashed and the validator loses future attestation privileges on that lane.
The stake is not a yield-bearing instrument. It does not generate income while locked. It generates economic risk that disciplines the validator to attest honestly. Validators earn HCC by doing the attestation work, the same way a clinician earns HCC by completing a patient encounter or an engineer earns HCC by shipping a merged pull-request — verified action, paid per event at the published era rate.
Becoming a validator
Validator nodes will be open to credentialed third parties — specialty societies, partner universities, partner audit firms, and similar ecosystem actors — beginning Phase 2 of the protocol roadmap (post-launch, Q4 2026). The reference validator implementation will be open-source under Apache-2.0; anyone meeting the credentialing and stake requirements for a given lane can apply to operate a node.
Conceptual Healthcare Corporation operates an initial set of validator nodes at launch to bootstrap the network. The Corporation earns HCC for the attestation work it performs on the same terms as any other validator; the Corporation does not earn HCC for operating the protocol itself, only for the verified attestations it produces.
Where to read more
- Mining taxonomy — every lane, every attestation source, every anti-gaming control: /legal/cftc (links to the public taxonomy)
- Trust posture — supply, mints, fee flows, governance log, regulator engagement: /trust
- CFTC engagement — classification posture and dual-track stance pending Innovation-office response: /legal/cftc
- HCC supply — hard cap, halving, treasury structure: /supply/hcc
Disclaimer. HCR and HCC are intended to be classified as digital commodities under 7 U.S.C. § 1a(9); CFTC classification has not been confirmed and engagement with the Innovation office is underway. Conceptual Healthcare Corporation maintains a conservative dual-track compliance posture pending the response. Nothing on this page constitutes investment advice, financial advice, or a solicitation to buy or sell any asset. The validator program described here is the actually-implemented attestation-mining mechanism; the previous yield-product framing has been deprecated and removed.