Crypto Signal Provider Country and Language Metadata Audit

What the two labels mean in this audit

Measurement version stored-country-language-source-bias-v1 preserves the exact label strings after trimming outer whitespace. It does not merge English with English / multilingual, split composite labels, detect language from messages, geolocate administrators, or infer nationality from names. One unique CSR slug remains the record denominator.

Country-label distribution

The 11 labels include Global, which is a broad classification rather than a country. The other 10 labels cover 987 rows (30.8%). This table describes the inventory’s stored taxonomy, not the geographic distribution of crypto signal providers, customers, companies, or Telegram users.

Language-label distribution

The 12 exact labels mix broad categories, single languages, and slash-separated combinations. Multilingual accounts for 2,121 rows, while English / multilingual remains a separate exact value on 12 rows. That inconsistency is visible rather than silently normalized. A category label does not show which language dominated the latest month of posts, whether translations were human or automated, or which language governs payment and refund terms.

Only 13 exact country-language pairs occur

The 13 pair rows reconcile to all 3,200 records. The Global / Multilingual pair alone covers 2,121 rows (66.3%). Each of the 10 non-global country labels maps to one language label in this snapshot. That tight pairing is evidence of a classification scheme, not evidence that every row serves one verified national audience or uses the same language consistently.

Source family explains the apparent precision

RealTelegram assigns Global / Multilingual to all 1,870 rows. Cornix does the same for all 85 marketplace rows. Manual seeds use Global / English, the small WhatsApp family uses Global / English / multilingual, and the Discord family uses Global / English. Those five one-pair families account for 2,047 rows (64%).

The two TGStat families supply all 987 non-global rows: 501 from the group-rating source and 486 from the category source. A reader therefore cannot compare country-label counts without carrying the source frame. The result is source coverage, not market prevalence.

Source URL is almost a locale-assignment key

73 of 74 source URLs assign one exact country-language pair, covering 3,114 records. The remaining shared URL carries more than one source family; its modal pair still matches all but one attached row. This near-determinism is stronger evidence about importer and source taxonomy than about provider geography. A source URL can classify hundreds of records without observing any operator address, legal entity, audience location, or current message sample.

The declared registry mostly reproduces the same labels

Country agrees with the declared source registry on all 3,127 matched assignments, while the complete pair agrees on 3,125. That is a useful consistency check inside the frozen manifest. It does not turn the registry into an independent source: provider rows and source definitions can originate from the same collection pipeline.

Apparent non-global completeness is an importer signature

All 987 non-global rows have a direct route, alias, and subscriber observation because those rows come from TGStat importers that populate those fields. Only 21 have explicit keys. The Global rows are dominated by RealTelegram records with explicit keys but no route, alias, or subscriber observation. This contrast must not be described as stronger evidence, larger audiences, better quality, or greater reliability in one geographic group. It is a field-construction difference between collection pipelines.

Six decisions these labels cannot make

A practical locale-verification workflow

1. Record the exact stored country and language labels, source family, source URL, and snapshot date.
2. Open the current official route independently; do not use a catalog label as route proof.
3. Sample dated public messages across more than one day and record the languages actually used, including translated or automated posts.
4. Separate content language from support language, contract language, and payment or refund terms.
5. Identify the legal entity and target market from current records rather than names, flags, phone codes, or administrator claims.
6. Check current service, exchange, payment, and product eligibility for the reader’s own location.
7. Keep unresolved fields unresolved. A mismatch can trigger clarification without becoming an accusation.

A citation-safe aggregate statement is: “In CSR’s frozen 3,200-record inventory, all 987 non-global country labels came from two TGStat source families.” Keep the inventory, snapshot date, exact-label method, and source-bias boundary attached. Do not rewrite that sentence as a market-share estimate, operator-location claim, national-provider ranking, or legal conclusion.

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.

• FCA: cryptoasset firms marketing to UK consumers

  Current social-media promotion, risk-warning, and fair-clear-not-misleading context.

• ESMA: finfluencer factsheet

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

Continue the transparency research

• Where the 3,200 Crypto Provider Records Came From

  Source-family and field-completeness analysis for the 3,200-record CSR provider inventory, including TGStat, RealTelegram, Cornix, manual seeds, and gaps.

• 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.

• 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, verification gaps, quarantine rates, sources, and missing evidence.