Skip to main content

How It Works

Flow at a glance
  1. Pool configured in Nexus → 2) Members onboard to OmegaX Health (oracle) → 3) Oracle emits attestations → 4) Protocol verifies and settles on Solana → 5) Rewards paid.

This section walks through a full OmegaX flow, end to end:

  1. An employer creates a reward pool in Nexus.
  2. Employees onboard into the OmegaX Health oracle app.
  3. The app tracks real-world behavior and computes health events.
  4. The protocol receives attestations and settles payouts on-chain.
  5. $OMEGAX captures protocol-level fee flows on Solana.

OmegaX Health is the first oracle in this loop. The protocol is built to accept compatible attestations from future oracles via the SDK (in development).

1. Employer Sets Up a Pool in Nexus​

  1. The employer logs into nexus.omegax.health.
  2. They create a new reward pool, configuring:
    • Target population (for example “full-time employees in Region A”).
    • Health goals (for example “10% weight loss sustained 90 days”, “normal blood pressure 6 months”).
    • Payout rules (for example “up to 400 USDC per person over 1 year”).
    • Budget caps and time windows.
  3. Nexus deploys or connects to a corresponding on-chain pool on Solana and funds it with:
    • USDC or other accepted assets, and
    • Optionally $OMEGAX for boosted incentives.

From the employer perspective, it feels like configuring a benefits program.
Under the hood, they are creating a parametric, on-chain reward structure.

2. Employees Onboard Into OmegaX Health​

  1. The employer shares invite links or coupons that are wired to the specific pool.
  2. Employees:
    • Download the OmegaX Health app.
    • Create an account and connect health data sources (wearables, phone sensors, etc.).
    • Connect or create a wallet for receiving rewards.
  3. The app personalizes:
    • Baseline health assessment and risk scores.
    • A tailored multi-agent daily and weekly plan across movement, nutrition, sleep, and mental health.

At this point:

  • The user has a coach that calls them, plans for them, and adapts in real time.
  • The protocol has a link between a wallet, a user, and a funded reward pool.

3. Health Oracle Observes and Computes Events​

Over time:

  1. OmegaX Health continuously ingests:

    • Activity, sleep, and HR patterns.
    • Weight and blood pressure logs.
    • In-app adherence signals and check-ins.

  2. The multi-agent system:

    • Tracks progress versus personalized plans.
    • Updates risk scores based on actual behavior.
    • Detects when specific conditions are met, such as:
      • “10% weight loss sustained at least 90 days”
      • “Blood pressure in controlled range for 6 months”
      • “Adherence to plan above 80% for 12 weeks”

  3. When a condition tied to an active pool is met, the oracle generates a health attestation:

    • Type of event
    • Magnitude and duration
    • Time bounds
    • Pseudonymous user identifier
    • Pool or program identifier
    • Cryptographic signature

The oracle does not leak raw data. It emits scored, structured, signed events.

4. Relayer Submits Attestations On-Chain​

  1. A relayer service monitors new health attestations produced by the oracle layer.
  2. It bundles or streams these attestations to the OmegaX Protocol on Solana.
  3. The protocol contract:
    • Verifies the signature and integrity of the attestation.
    • Checks that:
      • The user is enrolled in the relevant pool.
      • The event matches the configured criteria.
      • The event has not already been rewarded.
      • The pool still has budget and is within its active period.

If all checks pass, the protocol authorizes a payout.

5. Payout Settlement And Rewards​

When a payout is triggered:

  1. The protocol updates the state of the reward pool:
    • Decrements available budget.
    • Marks the event as settled for that user.
    • Records the payout for analytics.
  2. Funds are transferred from the pool to the user wallet:
    • Typically in USDC or the pool’s reward asset.
    • Optionally supplemented by $OMEGAX if pool-level boosts are enabled.

From the user perspective:

  • They did the hard part: changing their behavior and improving their health.
  • The rest is automatic: the money arrives in their wallet when the system confirms the outcome.

From the employer or sponsor perspective:

  • They see concrete metrics:
    • How many people hit which milestones.
    • Cost per improvement.
    • Aggregate risk movement in the population.

6. Protocol Fees And $OMEGAX​

Every on-chain interaction that uses OmegaX infrastructure contributes to protocol fees.

Examples of fee events:

  • Creating and funding new pools.
  • Settling payouts.
  • Using advanced risk or analytics modules.

On Solana, fees are:

  1. Collected in the asset used (for example USDC).
  2. Periodically routed through $OMEGAX:
    • Swapped into $OMEGAX via Solana DEXs.
    • Distributed between:
      • Protocol treasury
      • Ecosystem incentives
      • Optional burn or long-term locking

This ties real economic throughput:

  • Number of active pools
  • Volume of rewards
  • Breadth of integrations

to a single asset:

  • $OMEGAX at FTBq3w9gCv27E451DV6w8AbUjBQbyVxxj1ZaYEYepump

7. Scaling To Health Capital Markets​

Once this basic loop runs reliably at scale:

  1. Employers and insurers fund bigger and more sophisticated pools.
  2. Providers integrate cohorts and share upside on risk reduction.
  3. External capital can:
    • Co-fund pools.
    • Take structured exposure to prevention performance.
    • Participate in coverage-like instruments built on top of verified health events.

At that point, OmegaX stops being “a rewards app” and becomes:

  • An infrastructure layer where health risk is:
    • Observed and scored,
    • Priced and funded,
    • Settled and analyzed,
      in full view of the chain.

The omega state:

Human health states, not just speculation, drive flows of capital.
The protocol, the oracle, and $OMEGAX are the rails that make that possible.

Download PDF