MagicBlock gives OmegaX a private review lane for the parts of a health claim that should move quickly, but should not become public raw medical data.
OmegaX is building health protection for people who live and work across borders. The product needs a very plain promise: a member can buy cover, submit a claim, have that claim reviewed, and receive an approved payout. The protocol side needs an equally plain promise: reserves, claim state, attestations, and settlement actions can be inspected without asking everyone to trust a private back office.
Those two promises collide at claim review. Medical evidence is sensitive. Receipts, timestamps, reviewer state, and settlement consequences need to be verifiable. MagicBlock is useful because it lets us separate those concerns instead of pretending one public ledger should hold everything.
The problem: claims need privacy and proof
A health claim contains two very different kinds of information.
One kind is private human context: medical documents, prescriptions, discharge notes, images, invoices, travel details, and support conversation history. That material belongs in private systems with strict access controls. It should not be published to a public chain, even encrypted, as the default product posture.
The other kind is shared operating state: a claim case was opened, an evidence packet was reviewed, a reviewer produced a bounded result, a payment reference exists, and the normal protocol path can use that result as attestation input. That state is not the medical record. It is the audit trail around the review.
OmegaX uses MagicBlock for that second layer.
What MagicBlock adds
MagicBlock Ephemeral Rollups let a Solana program delegate specific account state into a faster execution lane, then commit the final state back. For OmegaX, the useful unit is not the whole insurance protocol. It is a narrow review-session account.
That matters. The main OmegaX protocol remains the settlement and reserve kernel. Claim cases, reserves, vaults, funding lines, obligations, and payout accounts stay on the standard Solana path. MagicBlock handles a private-review adjunct: a small session that can record public-safe hashes and lifecycle state while the raw claim packet remains outside the public program.
In the current devnet implementation, that adjunct program is omegax_private_claim_review at FADqaRcJHERauzMo3BRzXZVY2qvrpPqg1ie2FGqACCVn. The main OmegaX protocol program remains Bn6eixac1QEEVErGBvBjxAd6pgB9e2q4XHvAkinQ5y1B.
How the flow works
The flow is intentionally boring. That is the point.
- OmegaX prepares a private claim packet in the app or operator system.
- The system hashes the evidence bundle and opens a review-session PDA linked to the claim case.
- Only that review-session PDA is delegated to the MagicBlock review lane.
- A private reviewer or TEE-style review adapter checks the packet and writes bounded outputs: result hash, artifact hash, review binary hash, reviewer authority, and lifecycle status.
- A devnet private-payment reference can be recorded as a preview artifact, but it does not replace production settlement.
- The session is committed back, and the normal OmegaX claim attestation path can reference the committed review artifact.
The public output is a receipt, not a file cabinet. A partner or auditor can see that the account is owned by the private-review adjunct, that it decodes as a review-session receipt, and that the expected public hashes and authorities are present. They still do not see the raw medical evidence.
What we deliberately do not delegate
The key design choice is scope.
We are not delegating the main omegax_protocol program to MagicBlock. We are not moving reserves through MagicBlock. We are not asking an ephemeral rollup to be the source of truth for claims-paying capacity. We are not making the private-review program authoritative by itself.
Production settlement still goes through the standard OmegaX protocol path: claim state, oracle attestation, reserve accounting, obligations, and payout movement. MagicBlock helps with the review receipt around private evidence. It does not become the insurance company, the claims operator, or the reserve vault.
This boundary is what makes the integration honest. It lets us use MagicBlock where it is strongest - low-latency delegated state and private review adjuncts - without blurring the part users and partners must be able to verify on the base protocol.
Why this matters for members and partners
For members, the benefit is privacy. They should not have to choose between getting a claim reviewed and publishing sensitive health evidence into a permanent public surface.
For operators, the benefit is speed and structure. Review work can produce a compact receipt that the rest of the protocol understands.
For sponsors, auditors, and capital partners, the benefit is a cleaner boundary. They can inspect the economic and procedural state without being handed raw health records. The chain can show what happened around the claim. The private systems can protect the claim packet itself.
That is the shape we want for OmegaX: public where money, reserves, and attestations need shared truth; private where health evidence needs dignity and control.
MagicBlock is not the whole claims system. It is the privacy-preserving review lane that makes the rest of the system easier to trust.
