Chain · Public Ledger
Who can write, who can verify, who can amend.
Conceptual Chain is in Phase 1 — founding state. Governance below describes both what is currently in force and what is on the published roadmap. We tell you which is which.
Writers · current
Who can write to the chain today.
Write access to Conceptual Chain is currently held by Conceptual Healthcare Corporation services: the clinical applications (Provider AI, Clinical, Pharmacy) for axis-event settlement; the HCR/HCC mint authorities for token settlement; the IP-attestation service for SHA3-256 disclosure anchoring. Every writer's public key is recorded on chain at registration. The full writer set is enumerable today and will remain publicly enumerable as it grows. Adding a writer requires an on-chain governance event signed by the operator key.
Validators · current
One validator. Phase 1 — founding state.
Conceptual Chain entered live operation with one internal validator (ch-validator-1, Conceptual Health® HQ — Destin, FL), running Proof-of-Authority consensus (CH-PoA) at a 5-second target block time. Every block since genesis has been signed by this validator and is publicly verifiable in the explorer. The live validator set is read directly from the chain at /api/v1/chain/validators — there is no separate marketing roster.
Validators · roadmap
Phase 2 target: multi-institution BFT.
The architectural target is an N-of-M Byzantine-fault-tolerant set drawn from licensed healthcare institutions, regulated custodians, and at least one sovereign health authority, geographically distributed across multiple jurisdictions. Onboarding criteria, slot count, jurisdiction policy, and the BFT threshold (likely 7-of-11 once the set is fully seated) will be ratified by the CH governing body and recorded as on-chain governance amendments before going live. We will publish prospective validator nominations as they advance through review on the governance log.
Amendment
How chain governance changes.
Changes to chain governance — adding or removing a writer, seating or rotating a validator, changing the BFT threshold, changing the consensus rules — are recorded as on-chain governance events visible to anyone in the explorer. Each amendment names the change, the rationale, the effective block height, and the signing authority. Today, amendments are signed by the operator key; in Phase 2, amendments will require the same supermajority that finalizes blocks. Every historical amendment remains on chain forever; the audit log of how the chain has evolved is itself part of the chain.