Q markQUADUsage Evidence

Usage Evidence

This page separates visible testnet surfaces, private readiness inventory, and public evidence of real use. Product use is counted only when the owning surface publishes receipts, summaries, or approved disclosures.

Network UseCommunicationsReceiptsArchitectureReadiness

Current Evidence Labels

These labels are public posture, not sales language or traction claims.

Storage usageOwner receipts required

Count only Infra-published storage, retrieval, retention, or proof summaries.

Compute usageOwner receipts required

Count only accepted provider-work or task-execution summaries from the owning surface.

Liquidity movementOwner route evidence required

Count only Bridge/Liquid/Core route records that are published with their local meaning.

Provider countNot publicly reported

Provider count is not inferred from wallets, endpoints, relayers, or private infrastructure.

Public partnersNo public partner disclosures yet

Partners are named only after approved public disclosure.

Public tractionNot yet published

No stack-wide adoption, revenue, production volume, or partner-usage claim is published here.

Disclosure States

Use these labels before describing use, pilots, or production traffic.

No public partner disclosures yet

No named partner, pilot, or stack-wide adoption claim has been approved for public use.

Pilot announced

Reserved for a dated, approved pilot disclosure that names what is being tested and which surface owns the evidence.

Production usage

Reserved for public product use backed by owner-published receipts, summaries, or route totals.

Mainnet usage

Reserved for post-mainnet use. Testnet traffic, rehearsals, faucet activity, and endpoint readiness do not qualify.

What Does Not Count

These can be useful operations signals, but they are not adoption evidence.

  • Private endpoint inventory. A mainnet endpoint box, multi-chain host, relayer machine, or internal route map is readiness infrastructure, not public usage.
  • Testnet activity alone. Faucet claims, test transactions, testnet delegation, Discord activity, bug reports, and docs feedback do not prove production use.
  • Airdrop-style traffic. Referral farming, prize campaigns, or speculative claim traffic cannot be presented as product-market fit.
  • Unapproved names. Private conversations, screenshots, rumors, crawler summaries, and third-party posts do not become partner disclosures.
  • Adjacent movement. Bridge passage, Liquid motion, Infra receipts, or public attention do not force Core admission or Core value.

Evidence Owners

Each usage claim belongs to the surface that can prove it.

InfraStorage, retrieval, retained memory, compute/work receipts, and BIGHT-priced service paths. BridgePassage, source pools, owner vaults, acquisition evidence, refunds, and route-output labels. LiquidMotion, wrapper posture, settlement requests, risk labels, and liquidity-surface summaries. CoreCore receipt, route, quarantine, payables, balance, and public economic-posture evidence. Main siteStack-level Network Use page for adoption evidence rules and public disclosure labels.