Skip to main content

Validator Roles

Olymp supports two validator personas.

Full Provider​

  • Signs Data Packages.
  • Anchors metadata on-chain.
  • Exposes provider API.
  • Posts an OLYMP bond to activate.

API Provider​

  • Exposes an API endpoint.
  • Adapter anchors on-chain.
  • Posts an OLYMP bond to activate.

Bond lockups (circulating vs total supply)​

  • Bonds are locked in ProviderRegistry and reduce circulating supply without burning.
  • Withdrawals require a cooldown period and are blocked if the remaining bond would fall below minimum while Active.
  • Slashing can reduce locked bonds immediately for provable violations.
  • Cooldown duration is configurable by governance within safe bounds.
  • Bonds are collateral for misbehavior and do not represent yield.

Trust tiers (API validators)​

Tier A: Provider-Signed (Model 1)​

  • Provider signs the DataPackage (EIP-712).
  • Adapter anchors metadata on-chain.
  • Gateway verifies provider signature against the registry.
  • Recommended for high-trust use cases.

Tier B: Adapter-Attributed (Model 2, Bootstrap)​

  • Adapter signs and anchors.
  • Data is attributed to the API provider but not provider-signed.
  • Gateways MUST label responses with the tier (Tier A or Tier B).
  • Recommended to cap scores or enforce stricter minScore policies.

Gateway enforcement rules (MVP)​

  • Gateways MUST verify the signature against the expected signer:
    • Tier A: provider address
    • Tier B: adapter address
  • Gateways MUST read ProviderRegistry for type, signingMode, and adapter.
  • Gateways SHOULD apply stricter routing policies for Tier B.

Slashing MVP (summary)​

  • Slashing is admin/role-based in MVP.
  • Slashable reasons include invalid signatures, anchor mismatches, repeated schema violations, and deliberate hash mismatches.
  • Downtime is not slashable in MVP; it results in routing penalties or score decay.
  • Governance-based slashing and disputes are future upgrades.