Technical documentation

Measuring FOMO before
the crowd feels it.

This document specifies how the FOMO Score is computed, how the oracle publishes it, and how the protocol rewards participants who detect narrative attention before it saturates. It is the normative reference for all settlement disputes.

Version
1.0.4
Effective
2026-08-01
Audit
Passed · Cantina
Status
NORMATIVE
01

The FOMO Score

Each narrative receives a composite score on a 0–100 scale, recomputed every 15 minutes. The score does not measure price or value — it measures attention compressing relative to the narrative's own 90-day baseline. A reading of 60 means attention is accelerating faster than in 60% of comparable historical windows.

FOMO = 100 · Φ( Σ wᵢ · zᵢ )  where z is winsorized at ±3σ over a 90-day rolling window
ComponentWeight wᵢSignal measured
Market0.30Volume, funding rates, basket price velocity across the narrative's tokens
Social0.20Mention & engagement velocity on X and Farcaster, bot-filtered (§04)
On-chain0.20New interacting wallets, net inflows, contract deployments
Search0.15Query-volume growth for the narrative's canonical terms
Development0.10Commits, new repositories, active contributor count
News0.05Coverage count weighted by outlet reach
Design principle
Weights are fixed per specification version and can only change through governance with a 30-day timelock — a score users cannot audit is a score they cannot trust.

Normalization

Each raw input is converted to a z-score against the narrative's own 90-day rolling baseline, then winsorized at ±3σ so a single viral event cannot pin the composite. Φ is the standard normal CDF, mapping the weighted sum onto 0–100. Because baselines are per-narrative, a small narrative and a majors narrative are comparable: both measure acceleration relative to their own history, not absolute size.

Narrative taxonomy

A narrative is a curated basket: 5–40 tokens, a canonical term set for search/social matching, and a contract set for on-chain telemetry. New narratives enter through governance listing with a 14-day probation during which they carry a PROVISIONAL badge and are ineligible for Discover Mining. Basket membership is versioned; every snapshot references the basket version it was computed against.

Update semantics

  • Cadence. Recomputed every 15 minutes at :00, :15, :30, :45 UTC; publication lag target < 90 seconds.
  • Continuity. Component z-scores are EWMA-smoothed (half-life 45 min) — the score moves in points per interval, never in cliffs, except on verified news events flagged in the snapshot.
  • Determinism. Given the same inputs and basket version, any party can recompute the score bit-for-bit; the pipeline is open-source.
02

Phase model

The score maps deterministically onto five phases. Phase boundaries are part of the oracle contract: markets, mining multipliers, and warnings all settle against them.

020406585  →  100
PhaseScore bandInterpretation
DORMANT0 – 20Nothing to see — unless you know how to look. Sparse mentions, a trickle of new wallets.
IGNITION20 – 40Capital moves before news. The discovery window: multipliers decay from x5 to x2.
ACCELERATION40 – 65Volume expands, KOL coverage begins. Early discoverers start planning exits.
MANIA65 – 85Saturated attention. Mining rewards approach zero; risk reprices hourly.
EXHAUSTION ▲85 – 100Reward ≈ 0. The protocol inverts: it now warns entrants that they are the exit liquidity.
Normative warning behaviour
Above score 85 every surface of the product must display the Saturation Warning with equal or greater prominence than any earning call-to-action. The last three narratives to reach Exhaustion corrected an average of −41% within 30 days. The protocol does not pay for chasing tops.

Boundary hysteresis

To prevent flapping at phase edges, a transition only registers after the score holds across the boundary for 2 consecutive snapshots (30 minutes). Markets referencing "enters phase X" settle on the registered transition, not the first touch. The one staged UI moment — the Ignition flare — fires exactly once per registered upward crossing of 20.

03

The FOMO Oracle

Every 15 minutes the oracle publishes a signed on-chain snapshot containing the six component z-scores, the composite score, the phase, and the Organic Ratio for each tracked narrative.

  • Settlement. All FOMO Markets and mining evaluations settle exclusively against published snapshots — never against live feeds.
  • Disputes. A 2-hour window follows each settlement. Challenges require a 1,000 $FOMO stake, slashed if the snapshot is upheld.
  • Degradation. If an input feed fails, the last good snapshot is served with a staleness badge (◔ 15 min ago). Latency transparency is part of the oracle contract, not an apology.

Pipeline stages

  • Ingest. Exchange APIs, archive-node indexers, social firehoses and search feeds land in a staging lake with source signatures.
  • Filter. The Organic Ratio pass (§04) strips synthetic attention before any component is computed.
  • Compute. Deterministic scoring workers produce component z-scores and the composite; three independent workers must agree within ε = 0.01 or the snapshot is withheld.
  • Publish. The snapshot is Merkleized, signed by the oracle key quorum (3-of-5), and posted on-chain; the UI reads the chain, not the pipeline.

Snapshot schema

{ narrative_id, basket_v, ts,  score, phase, organic,  z: [mkt, soc, chain, srch, dev, news],  sig }

Dispute resolution

  • T+0 → T+2h. Anyone may challenge a settlement by staking 1,000 $FOMO and citing the disputed inputs.
  • T+2h → T+26h. A recomputation committee re-runs the pipeline from archived raw inputs; the result is binding.
  • Outcome. Upheld snapshot → challenger stake is slashed 50% to the insurance pool. Overturned → challenger earns 2× stake and affected settlements are replayed.
04

Organic Ratio

The share of measured attention judged human after bot filtering — account-age clustering, posting-cadence entropy, and funding-graph analysis over the mention set.

ReadingBandEffect
● ≥ 0.75healthyFull Social weight applies; narrative eligible for the Golden Zone filter
● 0.50 – 0.75mixedSocial weight applies with a linear haircut
● < 0.50suspiciousFlagged in all UIs; Social component discounted to zero; discoveries ineligible

Filter methodology

TestWeightWhat it catches
Account-age clustering0.40Mention bursts dominated by accounts created within the same narrow window — the signature of farmed rings
Cadence entropy0.35Posting intervals too regular to be human; low-entropy schedules are down-weighted
Funding-graph analysis0.25Wallets behind engaged accounts funded from a common source within 7 days

The ratio is recomputed per snapshot over the trailing 6-hour mention set. Filter parameters are published one version behind (n−1) to resist adversarial adaptation while remaining auditable.

05

Reward mechanisms

MechanismStakePayout logic
Discover Mining500 $FOMOSnapshot S₀ locks a multiplier: x5 at score 20, decaying linearly to x1 at 45. Pays if Δscore ≥ +15 within 72h with Organic ≥ 0.70. A miss refunds 95%; proven manipulation slashes 100% plus reputation.
Prediction Mining200 $FOMOConfidence-weighted binary predictions (50–99%) scored by Brier — confidently wrong costs more than cautiously wrong. Predictions are hashed until settlement; nobody can copy an open position.
FOMO MarketsvariableBinary markets on score thresholds, settled by the oracle (§03). Liquidity providers earn fees when the crowd arrives late.

Reputation — the Hunter Score

A soulbound composite: Early Detection 35% · Prediction 35% · Signal 20% · Tenure 10%. It cannot be bought, transferred, or delegated; B2B signal subscriptions are priced against it.

Protocol constants

ParameterValueNotes
Discovery multiplierx5 → x1M(S₀) = 5 − 0.16·max(0, S₀−20), floored at 1; zero above S₀ = 45
Evaluation window72 hClock starts at the snapshot that includes the discovery
QualificationΔ ≥ +15AND Organic ≥ 0.70 at every snapshot in the window's final 6 hours
Pool cohorts30 minDiscoveries in the same 30-minute cohort split that cohort's pool share; later cohorts split geometrically smaller shares (r = 0.6)
Miss refund95%25 $FOMO retained as a spam deterrent
Manipulation slash100%Plus permanent reputation mark; adjudicated via the dispute process (§03)
Prediction scoringBrierPayout ∝ stake · (0.25 − (outcome − confidence)²) / 0.25, negative scores burn
Market fee1.0%Per fill: 0.7% to LPs, 0.2% to the insurance pool, 0.1% burned
06

Backtest results

27 completed narrative cycles, October 2024 – April 2026. Full per-cycle data ships quarterly with the oracle snapshots.

Method

Walk-forward evaluation with no lookahead: each cycle is scored using only the specification version live at the time, against baskets frozen at cycle start. "Peak price volume" is the 24-hour window with maximum basket dollar volume within ±60 days of the Ignition crossing.

11.3 days
Median lead-time: score entered Ignition before peak price volume
23 / 27
Narratives crossing score 65 whose basket gained ≥ 40% afterward
−41%
Average 30-day drawdown after entering Exhaustion

Sample cycles

CycleLead-timeOutcome
AI Agents · Q4 202514 daysIgnition at 22 → peak 94; basket +212% to peak, −47% in the 30 days after Exhaustion
RWA · Q1 20269 daysIgnition at 24 → peak 87; basket +96% to peak; still in Mania at report date
DePIN · Q1 202612 daysIgnition at 21 → 63 (current); +41% basket to date, cycle open
Restaking · Q2 20256 daysFalse ignition: crossed 20, stalled at 34, decayed — discovery misses refunded 95%
SocialFi · Q3 2025Filtered: Organic 0.41 at crossing; Social zeroed, no Ignition registered, bot ring confirmed
07

Token economics

$FOMO is the protocol's work token: every earning mechanism requires staking it, and every reward is denominated in it.

AllocationShareSchedule
Mining rewards45%Emitted per epoch, split Discover 60 / Prediction 30 / Curation 10; halves every 24 months
Ecosystem & B2B treasury20%Governance-controlled; funds data-feed redundancy and audits
Team18%4-year vest, 1-year cliff
Investors12%3-year vest, 1-year cliff
Insurance pool5%Backstops overturned settlements; replenished by fees and slashes
  • Sinks. 0.1% of every market fill is burned; negative Brier scores burn; manipulation slashes burn 50% (the rest funds insurance).
  • B2B flywheel. Institutions subscribe to hunter signals in $FOMO; 70% streams to the hunter, 30% to the treasury.
  • No emissions for holding. $FOMO pays for being early and right — never for being idle.
08

Risk disclosures

Read before staking
The FOMO Score measures attention, not value. High scores frequently precede drawdowns. Nothing in this product constitutes investment advice. Staking mechanisms can lose up to 100% of staked tokens. Backtested lead-times do not guarantee future performance.
  • Oracle inputs depend on third-party data feeds; degraded feeds widen settlement uncertainty.
  • Phase boundaries are specification constants — they are not tuned to any individual narrative.
  • Reputation slashing for manipulation is irreversible by design.
09

Changelog

v1.0.4 · 2026-08-01
Organic Ratio — funding-graph analysis added to the bot filter; suspicious threshold formalized at 0.50.
v1.0.3 · 2026-05-19
Security audit passed (Cantina) — oracle signing and dispute flow, no critical findings.
v1.0.2 · 2026-03-02
Search component weight raised 0.10 → 0.15; News reduced accordingly after ablation study.
v1.0.0 · 2025-11-14
Initial normative release — six-component score, five-phase model, 72h discovery evaluation.