CERBERUS ON CHAINFlare network research
● LIVE VALIDATED DATA
FTSOv2 IMPLEMENTATION RESEARCH · EXAMPLE-PROVIDER DETECTION

Cerberus at the Gates.
The Chain Tells the Tale.

Independent, multi-signal analysis of whether registered Flare providers' submitted values resemble the stock example implementation. This is an implementation-likeness model, not an accuracy ranking.

Flare Foundation Setup FTSO notice titled Implement Your Own Production Provider, stating that the example implementation is only for testing, demonstration, or initial integration and that mainnet operators must maintain their own robust feed value provider.
Flare Foundation provider guidance: the stock example is intended only for testing, demonstration, or initial integration. View source image.

Running an independent production provider is required for reward eligibility and is enforceable by the FTSO Management Group.

active registered providers
detected above 65%
detected share of registered FIP.16 VP
reference rounds

Choose a section below to navigate directly to it, or select Show everything to display the complete page.

Loading active registered weighted-VP cohort…

FIP.16 cohort history

Epoch-by-epoch total WFLR delegated and FLR staked to providers detected as running the stock example implementation, plus their official validator rewards since reward epoch 392.
Loading cohort history…

Detected providers moving together

Compare a detected provider with the detected-cohort median and Flare Network Test 2 across the closed weekly window. The chart is centered on price clustering and shared movement through volatility.
Choose a provider and feed.
selected provider + markersdetected-cohort medianNetwork Test 2

Provider census

Every active registered provider, including insufficient-evidence entries.
Weekly data window. The data displayed is the previous week’s compiled data. The closed weekly window is updated every Sunday.
How results are updated. New reference and on-chain provider observations are captured continuously as voting rounds arrive. Completed rounds are finalized in batches, then the calibrated fingerprint model recalculates provider likelihoods from the accumulated aligned evidence. Validation rejects incomplete or incorrectly calibrated reports, and newly validated results are checked for publication approximately every five minutes. Scores therefore update in validated batches rather than after every individual round. Results supported by fewer comparisons are less reliable than results supported by many comparisons; estimates become more reliable as aligned rounds accumulate. Use each provider's comparison count and the report timestamp when judging freshness and evidence strength.
ProviderLikelihoodClassificationWeighted VP shareEvidence
Loading validated report…

Public data API

Retrieve the complete provider census, scores, evidence components, network summary, and methodology through the versioned read-only JSON API.

API index · Provider data · Cohort history · OpenAPI document

API v1

Collusion detection

The collusion-evidence workspace is in private beta testing. Detector development, event evidence, graphs, provider comparisons, and raw analysis interfaces are not publicly available.

PRIVATE BETA

Scientific methodology

The detector tests whether a provider's submitted-value process resembles the stock implementation. Each candidate is evaluated independently against two anchors—the captured stock provider and the passive on-chain Flare Network Test provider. This is a probabilistic implementation-likeness model, not an accuracy ranking or an inference of intent.

1. Raw two-anchor fingerprint

For candidate value v and anchor value a at the same feed and voting round, the model measures exact equality, proximity, and relative mismatch magnitude.

exact = count(v = a) / n
near5 = count(|v − a| / |a| ≤ 0.0005) / n
mean error (bps) = 10,000 × Σ(|v − a| / |a|) / n

It also measures update-direction agreement, direction during volatility, and whether both values cross a robust population band on the same signed side.

2. Population-relative regimes

Volatility spikes and signed band excursions are binary boundary events. Coincidence matters only when shared events exceed the rate expected from both series' marginal activity.

expected shared = nP × nR / N
precision = n11 / nP
recall = n11 / nR
lift = n11 / expected shared
regime score = √(precision × recall) × clamp((lift − 1) / 3, 0, 1)

This discounts ordinary market-wide movement and sporadic coincidence.

3. Feature construction

Each anchor contributes exact rate, near-5-bps rate, transformed error, movement direction, volatility direction, and signed out-of-band agreement. Two regime families add precision, recall, and transformed lift: 18 model inputs in total.

error feature = −ln(1 + mean error bps)
lift feature = ln(1 + lift)
zi = (xi − μi) / max(0.025, σi)

Cadence and the raw harmonic anchor score remain diagnostics; neither replaces the calibrated final posterior.

4. Regularized posterior

A class-balanced logistic model is fitted using asserted example users as positive controls and known independents plus canonical primary-band performers as negative controls.

class weight = N / (2 × Nclass)
logit = β0 + Σ βi zi
P(example-like) = 1 / (1 + e−logit)

Weighted cross-entropy is constrained by L2 shrinkage. The strongest tested penalty that separates every asserted control at 0.5 is selected; if none succeeds, calibration fails closed.

5. Cadence diagnostic

Update/freeze timing is reported separately using Cohen's κ over feeds and lags −1, 0, and +1. Chance agreement from each series' marginal update rate is removed.

po = (n11 + n00) / N
pe = pP pR + (1 − pP)(1 − pR)
κ = (po − pe) / (1 − pe)
feed weight = N × pR × (1 − pR)

The displayed cadence is a reference-information-weighted diagnostic, not a final logistic input.

6. Decisions and weighted vote power

Detection requires calibrated implementation likelihood strictly above 65%. Coverage is derived from usable evidence at both anchors and is descriptive—not a model weight.

detected cohort: P > 0.65
FIP.16 weighted VP: S = (capped WFLR + 5 × stake)0.75

Vote power is calculated after classification. It describes the detected cohort's network weight and cannot influence a provider's likelihood.