OmegaX Protocol Architecture
Use this page for the public system map before reading object-level protocol details or SDK workflows.
OmegaX Protocol is the shared settlement foundation for health-plan primitives, claims, reserves, oracle attestations, capital positions, and health capital market infrastructure on Solana.
Apps, sponsor consoles, oracle services, and regulated wrappers can sit around the protocol. They may manage private workflow or user experience, but the settlement-critical rights, liabilities, reserve movements, and capital consequences are represented by protocol objects.
If you are an audit firm, sponsor security team, or capital diligence reviewer, start with the Audit Review Brief. It gives the maintained review scope, trust boundaries, source read order, and current public limits before you dive into code.
Three public layers
| Layer | Main job | What stays out |
|---|---|---|
| OmegaX Protocol | Durable rights, liabilities, reserves, capital, and settlement state | Local workflow and raw evidence |
| SDK and integrations | Builders, readers, safe transaction flows, oracle services, wallets, and analytics | Hidden settlement semantics |
| Product surfaces | OmegaX Health, Business Console, Genesis Protect, sponsor apps, and other frontends | Raw records in public protocol state |
OmegaX Protocol
OmegaX Protocol is the public economic layer.
It exposes objects for:
- health plans and policy series
- member positions and eligibility state
- obligations, claim cases, attestations, and settlement
- reserve domains, asset rails, funding lines, and reserve ledgers
- liquidity pools, capital classes, allocations, and redemptions
- governance and scoped safety controls
SDK and integrations
The SDK gives builders unsigned transaction builders, readers, PDA helpers, reserve-aware read models, and safer client flows for the current public devnet beta interface.
External apps, wallets, analytics systems, oracle services, and capital integrations can use the same protocol surface instead of relying on private coordination.
Product surfaces
OmegaX Health is the first health app plus event-production and oracle layer.
This is where user-facing health guidance, evidence normalization, attestations, and privacy-sensitive workflow sit. It produces the commitments and event references that the protocol can settle against.
The business console at business.omegax.health is the sponsor and operator surface.
This is where organizations configure health plans, manage policy series, operate sponsor budgets, monitor claims, and understand outcomes and costs.
One foundation, multiple access models
OmegaX uses one settlement foundation with layered constraints:
- reserve domains for true legal or custody segregation
- health plans for sponsor and operational policy
- policy series for tighter product semantics
- capital classes for investor eligibility and transfer restrictions
That lets the same protocol support open DeFi participation, sponsor-led programs, and wrapper-mediated participation without splitting economic truth across separate systems.
Reserve accounting
The architecture is designed so the protocol can always answer:
- what is funded
- what is allocated
- what is reserved
- what is owed
- what is claimable or payable
- what is impaired
- what remains free
Reserve ledgers exist across domain, plan, series, funding line, capital class, and allocation scopes so those questions can be answered without private interpretation.
Why this matters
OmegaX does not force healthcare workflow onchain.
It keeps economically material state onchain while leaving raw data, local human workflow, and institution-specific operations around the protocol where they belong.