Skip to main content

Score Registry

Purpose​

Publish high-level provider scores used for selection and routing.

Scope​

This contract stores scores and exposes them to integrators. It does not compute scores on-chain.

Actors and Roles​

  • scoreUpdater submits scores.
  • Owner sets the score updater in MVP.

State and Storage Model (High-Level)​

  • Legacy scores are keyed by provider address and dataTypeHash.
  • v2 scores are keyed by provider, dataTypeHash, and modelId.
  • Each score stores score and updatedAtBlock.

Core Flows (State Machine)​

  • Submit or update provider score (legacy or v2).
  • Read latest score for selection.

Protocol Guarantees​

  • Scores are updated only through authorized publishers.
  • The latest score is retrievable and auditable.

Security Invariants​

  • Unauthorized actors cannot overwrite scores.
  • Score updates follow the approved publishing policy.

Events (Optional)​

  • ScoreUpdated(provider, dataTypeHash, score, updatedAtBlock)
  • ScoreUpdatedV2(provider, dataTypeHash, modelId, score, updatedAtBlock)
  • ScoreUpdaterChanged(newUpdater)

Integration Notes​

  • Treat scores as advisory and combine with off-chain checks.
  • The v2 modelId is bytes32("score_v2").

Disclaimers​

Scores are routing signals only and may change. No guarantees. Not investment advice.