DAORX is designed to run on physical infrastructure owned by MyRxWallet rather than on rented capacity from third-party cloud providers. The sovereignty principle is foundational: critical healthcare infrastructure must not depend on counterparties that can revoke access, change terms, or fail in ways that interrupt continuity of care or rights administration.
Infrastructure assets are organized into three layers:
MyRxWallet’s affiliated infrastructure organization holds approximately five hundred acres of campus land assets across multiple sites, designed to host data center capacity, biobank facilities, and supporting operations. Campus development supports the long-term capacity expansion necessary for nationwide healthcare data rights administration.
MyRxWallet operates owned data center facilities — designed to host validator hardware, sequencer nodes, indexer infrastructure, application hosting, and the permissioned clinical data layer. The data centers are intended to be geographically distributed across multiple regions for redundancy and latency optimization.
Validator nodes for the sovereign chain are intended to operate on dedicated hardware in MyRxWallet-controlled facilities. Independent qualified validators — initially from healthcare entities and infrastructure partners — are intended to be admitted over time per a public roadmap, advancing the system toward full mature blockchain status.
DAORX is anchored on a sovereign blockchain, designed to serve as the native settlement layer for healthcare data rights administration. The chain is intended to use OP Stack technology and operate as a Layer 2 with cryptographic anchoring to the broader Ethereum ecosystem for interoperability.
Patient health information itself is intended to be held on a permissioned clinical data layer — Hyperledger-based, HIPAA-aligned — distinct from the public sovereign chain. This separation means PHI does not transit a public chain. Only consent events, rights administration events, and access provenance records are anchored on the public chain.
DAORX is designed to maintain bridges to other major public chains for interoperability. Bridge representations of the native unit of account are intended to be visible on external block explorers — clearly disclosed as wrapped network tokens, never as fixed-value instruments.
The infrastructure is designed to meet the standards required of regulated healthcare infrastructure: HIPAA, HITECH, FHIR R4 and R5 alignment, USCDI v7 alignment, NIST Zero-Trust security architecture, CMS interoperability rule alignment, and the developing Bank Secrecy Act AML program standards applicable to digital asset infrastructure.
DAORX is built without dependence on third-party wallets, third-party RPC providers, third-party identity systems, or third-party cloud infrastructure for core platform functions. This is a deliberate architectural commitment. Critical healthcare infrastructure that cannot operate without external counterparties is not sovereign infrastructure — it is a vendor relationship dressed in different language. DAORX rejects that pattern.