Skip to main content

Professional Oracle Registration

OmegaX supports professional oracle onboarding for labs, hospitals, health apps, and data providers.

Why v2 registration exists​

register_oracle_v2 separates two roles:

  • Admin wallet: creates and maintains organization profile data.
  • Oracle signing key: cryptographically claims the oracle and activates it via claim_oracle_v2.

This avoids impersonation when operators provision profiles on behalf of teams that control dedicated signer keys.

On-chain profile fields​

OracleProfile stores structured data directly on-chain:

  • oracle signer pubkey
  • admin pubkey
  • oracle_type
  • display_name, legal_name
  • website_url, app_url
  • logo_uri, webhook_url
  • supported_schema_key_hashes (bounded list)
  • claimed, created_at_ts, updated_at_ts

Notes:

  • webhook_url is public metadata. Do not store secrets in it.
  • Supported schema capability list is bounded (current max: 16 hashes).
  1. Admin submits register_oracle_v2 with full profile and supported schema hashes.
  2. Oracle signer wallet submits claim_oracle_v2.
  3. Pool operators select claimed/active oracles for quorum policy.
  4. Admin or oracle signer may call update_oracle_profile_v2 as details evolve.

Trust boundary​

  • Profile data and oracle capability declarations are transparent and auditable on-chain.
  • Outcome attestations still require valid signatures from approved oracle signer keys.
Download PDF