Skip to main content

Olymp Network

Olymp Network is an Arbitrum Orbit L3 data network where validators produce signed Data Packages and anchor proofs on-chain. Consumers fetch verifiable payloads through public gateways and pay with OLYMP credits.

How the network works (overview)​

  • Providers publish signed Data Packages, store payloads off-chain, and anchor metadata on-chain for verifiability. See Data Packages and Provider roles.
  • Gateways aggregate providers, verify signatures/anchors/hashes, and serve best-scored packages to consumers. See Gateway.
  • The chain stores registries, anchors, scores, and payment credits to act as the source of truth. See Architecture overview.
  • Consumers pay per request using OLYMP credits with replay-protected signatures. See Payments.
  • Scores rank providers by data quality and freshness, and the gateway enforces minimum score policies. See Score model v2.
  • Gateways return a canonical Attested Data Response (ADR) with a signed query receipt. See ADR spec and Query receipt.
  • Founder Participation in Protocol Fees for Network Bootstrapping is a time-limited participation right with no guarantees or governance rights. See Founder Participation.
  • Namespaces keep core data protocol isolated from apps and games. See Namespaces.
  • Protocol control moves from bootstrap roles to governance over time. See Protocol lifecycle.

Core components​

  • Providers (Full vs API): Full providers sign and anchor packages; API providers supply data via adapters with explicit trust tiers. See Validators.
  • Gateways: Public routers that verify and cache packages, enforce payments, and return proof bundles. See Gateway.
  • Chain registries: Provider, schema, anchor, score, and payment registries anchor truth on L3. See Architecture overview.
  • Data Packages: Signed envelopes referencing off-chain payloads with on-chain anchors. See Data Packages.
  • Payments/Credits: Prepaid credits in OLYMP with on-chain consumption for API calls. See Payments.
  • Scores/Ranking: On-chain scores guide routing decisions and risk policies. See Score model v2.
  • ADR + receipts: Canonical response and receipt formats for verification. See ADR spec.
  • Founder module: Founder Participation in Protocol Fees for Network Bootstrapping; variable and time-limited with no guarantees. See Founder Participation.
  • Namespaces (core/app/games): Shared L3 with clear contract boundaries for core, app modules, and games. See Namespaces.
  • Supply policy: Epoch-based burn and bond lockups as treasury tools. See Supply policy.

Choose your path​

Quick start​

pnpm install

Start the local devnet and services:

cd infra/compose
copy provider.env.example provider.env
copy gateway.env.example gateway.env
# Start chain + services

docker-compose up -d

# In another terminal, deploy + configure
pwsh ../../scripts/bootstrap-local.ps1

Bootstrap now deploys founder and rewards modules, seeds mock stablecoins, and registers a sample provider with bond.

MetaMask setup​

Add the local devnet:

{
  "chainId": "0x7A69",
  "chainName": "Olymp Local",
  "rpcUrls": ["http://127.0.0.1:8545"],
  "nativeCurrency": {
    "name": "ETH",
    "symbol": "ETH",
    "decimals": 18
  }
}

Developer entrypoints​

  • Provider node: http://localhost:8081
  • Gateway: http://localhost:8082 (OpenAPI: http://localhost:8082/docs)
  • Postgres: postgres://postgres:postgres@localhost:5432/olymp