Skip to main content

Protocol Lifecycle

Olymp Network progresses from a foundation-run bootstrap to a governance-operated network. Each phase has explicit operators, controls, and readiness metrics. This section is descriptive, not a promise of timing.

Phases​

Phase 0: Foundation bootstrap​

  • Operators: single or few foundation providers + a foundation gateway.
  • Centralization: score updates and slashing are admin-controlled.
  • Scope: validate data package flows, payment credits, and anchor integrity.
  • Readiness metrics: successful end-to-end verification, stable RPC uptime, basic audits.

Phase 1: Semi-permissionless onboarding​

  • Operators: foundation providers + new external providers (API or full).
  • Centralization: admin still controls scoring and slashing, but onboarding is open with bonds.
  • Scope: introduce API validators and adapter anchoring (trust tiers enforced).
  • Readiness metrics: multiple providers per data type, stable gateway routing, bond/slash tooling.

Phase 2: Permissionless providers + multiple gateways​

  • Operators: permissionless providers, multiple gateway operators.
  • Centralization: admin roles still exist but used sparingly for safety.
  • Scope: gateways enforce Tier A/Tier B policies and minimum scores.
  • Readiness metrics: provider diversity, gateway redundancy, routine monitoring.

Phase 3: Governance-driven control plane​

  • Operators: governance-managed score updates, slashing policies, and schema proposals.
  • Centralization: admin roles are minimized or delegated to governance.
  • Scope: on-chain proposals for scoring policies and slashing rules.
  • Readiness metrics: governance participation, dispute processes, and audit readiness.

Phase 4: Foundation as app-only​

  • Operators: network is autonomous; foundation shifts to application development.
  • Centralization: governance manages all core protocol roles.
  • Scope: open schema proposals, decentralized scoring policies, mature slashing.
  • Readiness metrics: sustained protocol usage, multi-party governance, stable security posture.

Lifecycle timeline​

Control plane transition​

Progression gates (examples)​

  • Provider diversity: multiple independent providers per schema.
  • Redundancy: more than one gateway operator with verified uptime.
  • Security: external reviews of core contracts and gateway verification logic.
  • Stability: sustained fee flows and reliable payment settlement.