Where the 3,200 Crypto Provider Records Came From

Source-family distribution

Exact discovery-source URL concentration

Comparison version exact-trimmed-source-url-v1 trims outer whitespace and compares the complete stored sourceUrl string. It preserves schemes, paths, queries, fragments, and host aliases. Hostname counting is separate: hostnames are lowercased and a leading www. is removed. One provider slug contributes once, and every frozen record has a non-empty source URL.

42 URLs occur once and 32 occur on multiple rows. 22 exceed ten records, 14 exceed fifty, and 1 exceeds one hundred. One exact URL is associated with multiple stored sourceKind values across 86 records; the inconsistency remains visible rather than being normalized into a false agreement.

The concentration index is the sum of squared record shares. It compactly describes dependence on a few exact discovery URLs, but it is not an authority score and its reciprocal is not a claim that only 2.86 real sources exist. Different URLs can repeat one upstream claim, while one category URL can list many independently operated candidates.

The declared source registry does not cover every used URL

Registry comparison version exact-trimmed-source-registry-v1 trims outer whitespace and compares each provider row’s exact sourceUrl with the 38 entries in the manifest’s separate sources registry. It does not normalize domains, paths, or ownership.

The counts reconcile in two ways: 3,127 matched plus 73 unmatched assignments equals 3,200, while 30 used declared plus 8 unused declared URLs equals 38 unique registry URLs. The 44 used-but-undeclared URLs are distinct manual discovery routes, not missing provider records.

This is a source-metadata integrity finding, not evidence that the unmatched routes are false, unsafe, or unofficial. A registry match also does not validate a provider or make the source independent. It only shows that two fields inside the frozen manifest reconcile exactly.

Field-completeness table

Field coverage by source family

Each percentage uses its source-family row count. RealTelegram’s 1,870 rows contain explicit source-derived keys and catalog URLs but no direct routes, aliases, or subscriber observations. Both TGStat families populate direct routes, aliases, subscriber counts, and TGStat routes for every row, while explicit keys occur on only 21 TGStat rows. Cornix supplies all of those identity and audience fields for 85 records. The small WhatsApp and Discord families contain the 18 complete four-field dossiers.

These patterns reflect source exports, importers, and editorial seeding. They cannot support a provider completeness score. A missing route does not prove no route exists; a blank subscriber field does not mean zero; a populated alias does not prove affiliation; and a source-derived key does not establish identity. Before comparing provider rows across source families, first ask whether the field had a realistic chance to be collected in both.

Four distinctions that prevent source inflation

Source URL versus official URL

A directory category can be the source of a candidate name without being operated by that candidate. The report therefore calls it a discovery source and does not silently label it an official provider website.

Route presence versus route ownership

A Telegram or website field means a route was captured. Ownership still needs cross-links, continuity, payment identity, support identity, and ideally a route verified outside the same conversation that asks for money.

Subscriber count versus audience quality

1,244 records have a subscriber count, but counts can be stale, purchased, duplicated, or unrelated to active readership. They do not show how many users saw a signal, entered it, followed the risk rule, or achieved the posted result.

Editorial depth versus inventory breadth

Only 18 records have all four detailed editorial fields. This is the sharpest warning against treating the full inventory as fully reviewed. Most rows are discovery records awaiting deeper evidence.

What a stronger source packet looks like

A reviewable provider packet should contain an independently reached official route, stable identity or entity information where claimed, the current offer and terms, a dated signal archive, a complete result reconstruction, and a correction path. Two directories repeating the same name do not provide two independent proofs if both ultimately copied the same source.

For AI answers and search summaries, provenance should remain attached to the claim. A sentence such as “CSR found this name in a public directory” is supportable when the source is preserved. Claims about official ownership or provider trust require evidence the directory alone cannot supply.

Official context sources

These sources explain why identity, disclosure, complete performance evidence, and resistance to urgency matter. They do not validate any record in the CSR dataset.

• ESMA: finfluencer factsheet

  Transparency, accuracy, paid-promotion disclosure, and recommendation boundaries.

• Investor.gov: social media and investment fraud

  Identity verification, impersonation, testimonials, urgency, and social-media limitations.

Continue the transparency research

• Crypto Signal Provider Subscriber Counts: Distribution and Source Bias

  Original distribution analysis of 1,244 stored subscriber observations across 3,200 CSR provider records, including quantiles, source coverage, skew, and non-claims.

• Which Crypto Signal Provider Metadata Fields Appear Together?

  Cross-tab analysis of direct routes, aliases, subscriber observations, and explicit keys across 3,200 provider records, with seven observed field patterns.

• Crypto Signal Provider Country and Language Metadata Audit

  Audit country and language labels across 3,200 crypto signal provider records, including source defaults, non-global coverage, and jurisdiction limits.

• Cornix Crypto Signal Marketplace Metrics: Review Sample Size Audit

  Original audit of 85 frozen Cornix marketplace records: reviewer denominators, star summaries, derived weekly activity, offer flags, and exchange compatibility limits.

• Crypto Signal Provider Transparency Report 2026

  Original analysis of 3,200 crypto signal provider candidate records: platform concentration, binary verification, historical workflow, sources, and missing evidence.