Original CryptoSignalsReview dataset research

Crypto Signal Provider Transparency Data Table

This page exposes the aggregate measurements in one place so readers and AI systems can cite a precise denominator, field definition, and limitation instead of extracting unsupported conclusions.

Analysis by CryptoSignalsReview Evidence Desk of 3,200 candidate records frozen 2026-07-05. Published 2026-07-10; updated 2026-07-18. Source commit 5dcd30b2b1a0. Dataset release. No provider paid for inclusion or status.

Open the aggregate tables

No signup, payment, wallet connection, or credentials are required.

Rows analyzed3,200

Frozen candidate records.

Source families7

Exact sourceKind values in the snapshot.

Public source entries38

Source definitions retained by the manifest.

Direct answer

The tables below are the publication-ready aggregate layer for the 3,200-record snapshot. Counts use records as the denominator unless a table says otherwise. Percentages are rounded to one decimal place. Platform mentions overlap; sourceKind values do not. Public verification is binary: 3,200 CSR Unverified and 0 CSR Verified. Raw historical internal workflow fields are reported separately and are not additional public statuses.

Public verification status

Public verification status	Records	Share
CSR Unverified	3,200	100%
CSR Verified	0	0%

Result-sheet status	Records	Share
No CSR-reviewed result sheet	2,517	78.7%
Not applicable until crypto signal relevance is confirmed	683	21.3%

Historical internal workflow (2026-07-05)

Archived workflow class	Records	Share	Public mapping
Historical internal review queue	2,517	78.7%	CSR Unverified
Historical internal quality quarantine	683	21.3%	CSR Unverified

The immutable JSON and CSV retain the original raw enum strings so their byte hashes remain reproducible. Those archived values must not be quoted as current or alternative public verification labels.

Source families

Source kind	Records	Share
RealTelegram channel category	1,870	58.4%
TGStat crypto group rating	598	18.7%
TGStat crypto category	555	17.3%
Cornix supported group marketplace	85	2.7%
Manual provider seed	74	2.3%
Public WhatsApp source family	12	0.4%
Public Discord source family	6	0.2%

Exact discovery-source URL concentration

Measure	Value	Denominator	Boundary
Unique exact source URLs	74	Not applicable	Exact trimmed strings; not an independent-source count.
Distinct source hostnames	47	Not applicable	Lowercase hostname with a leading www removed.
Records on largest exact URL	1,870	3,200	58.4% of inventory records; not market share.
Records on top five exact URLs	2,245	3,200	70.2% of inventory records.
Records on top ten exact URLs	2,643	3,200	82.6% of inventory records.
Singleton exact URLs	42	74	URL frequency, not record percentage.
Record-concentration index	0.3502	Exact URL record shares	Sum of squared shares; not an authority score.
Effective source URL count	2.86	Reciprocal of concentration index	Descriptive equivalent count, not real-world source count.

Declared source-registry reconciliation

Measure	Value	Denominator	Boundary
Unique declared source URLs	38	38	Exact trimmed registry strings.
Distinct source URLs used by provider rows	74	Not applicable	Used URLs can be shared across many records.
Matched provider assignments	3,127	3,200	97.7% exact registry agreement.
Unmatched provider assignments	73	3,200	All are manual source-family rows; mismatch is not a provider verdict.
Used undeclared URLs	44	74	Distinct used routes absent from the declared registry.
Unused declared URLs	8	38	Declared registry routes without a provider-row assignment.

Top platform labels

Platform label	Records	Share
Telegram Channel	2,426	75.8%
Telegram Group	598	18.7%
Cornix / Telegram	85	2.7%
WhatsApp	21	0.7%
Telegram / Web	20	0.6%
Discord	10	0.3%
Telegram	7	0.2%
Discord / Web	6	0.2%
Website / Web	3	0.1%
Telegram / Web / Cornix automation	2	0.1%
Telegram / WhatsApp / Web	2	0.1%
WhatsApp / Telegram	2	0.1%
WhatsApp / Web	2	0.1%
Discord / AO Shadow / Bybit automation	1	<0.1%
Discord / business investing forex crypto	1	<0.1%

Country labels

Country label	Records	Share
Global	2,213	69.2%
Ukraine	150	4.7%
India	145	4.5%
Iran	140	4.4%
China	134	4.2%
Ethiopia	131	4.1%
Belarus	93	2.9%
Kazakhstan	64	2%
Russia	58	1.8%
Uzbekistan	55	1.7%
Kyrgyzstan	17	0.5%

Language labels

Language label	Records	Share
Multilingual	2,121	66.3%
Russian	151	4.7%
Ukrainian / Russian	150	4.7%
English / Hindi	145	4.5%
Persian	140	4.4%
Chinese / English	134	4.2%
English / Amharic	131	4.1%
English	80	2.5%
Russian / Kazakh	64	2%
Uzbek	55	1.7%
Russian / Kyrgyz	17	0.5%
English / multilingual	12	0.4%

Country-language label source bias

Measure	Value	Denominator	Boundary
Exact country labels	11	Label values	Includes Global; not a count of verified countries served.
Exact language labels	12	Label values	Composite and broad values remain separate exact strings.
Exact country-language pairs	13	Pair values	Classification pairs, not verified regional provider classes.
Rows labeled Global	2,213	3,200	69.2%; not operator or audience geography.
Rows labeled Multilingual	2,121	3,200	66.3%; not message-level language detection.
Non-global rows	987	3,200	All 987 come from two TGStat source families.
Rows in single-pair source families	2,047	3,200	5 of 7 source families use one fixed pair.
Source URLs with one locale pair	73	74	3,114 records sit on those exact URLs.
Rows matching source-URL modal pair	3,199	3,200	Source-taxonomy agreement, not provider-locale verification.
Registry-matched complete pair	3,125	3,127	Internal manifest agreement; two matched rows differ.

Source family	Records	Country labels	Language labels	Non-global rows	Dominant pair
RealTelegram channel category	1,870	1	1	0	Global / Multilingual (1,870)
TGStat crypto group rating	598	9	9	501	Global / Multilingual (97)
TGStat crypto category	555	11	10	486	Belarus / Russian (73)
Cornix supported group marketplace	85	1	1	0	Global / Multilingual (85)
Manual provider seed	74	1	1	0	Global / English (74)
Public WhatsApp source family	12	1	1	0	Global / English / multilingual (12)
Public Discord source family	6	1	1	0	Global / English (6)

Historical internal quality-workflow classes

Historical internal quality class	Records	Share
Historical internal project/community candidate	426	13.3%
Historical internal airdrop/giveaway candidate	241	7.5%
Historical internal weak-name candidate	11	0.3%
Historical internal non-signal candidate	3	0.1%
Historical internal airdrop/project community candidate	1	<0.1%
Historical internal project/news channel candidate	1	<0.1%

Historical internal quality flag	Records	Share
weak-project-or-miniapp-candidate	427	62.5%
weak-airdrop-or-giveaway-candidate	242	35.4%
weak-provider-name	11	1.6%
likely-non-signal-candidate	3	0.4%
malformed-scraped-name	1	0.1%

These archived workflow classifications all map to CSR Unverified and are not public verification labels.

Field coverage

Field	Records present	Coverage	What presence means
Discovery source URL	3,200	100%	The public route from which the candidate entered the inventory.
Direct route field	1,264	39.5%	At least one provider-specific messaging or website field is populated.
Telegram URL	1,257	39.3%	A stored Telegram route, not automatic ownership proof.
TGStat URL	1,153	36%	A TGStat route is retained.
Catalog URL	1,955	61.1%	A category or directory route is retained.
Subscriber count	1,244	38.9%	A public count is stored.
Aliases	1,322	41.3%	At least one alternative name is stored.
Search-intent terms	161	5%	At least one editorial query term is stored.
Detailed editorial dossier	18	0.6%	Four narrative research fields are all populated.
Quality note	684	21.4%	A correction or historical internal quality-workflow note is populated.
Explicit dedupe key	1,976	61.8%	An opaque source or comparison key is populated; fallback identity logic is separate.

Selected field coverage by source family

Source family	Records	Direct route	Aliases	Subscriber observation	Explicit key
RealTelegram channel category	1,870	0 (0%)	0 (0%)	0 (0%)	1,870 (100%)
TGStat crypto group rating	598	598 (100%)	598 (100%)	598 (100%)	0 (0%)
TGStat crypto category	555	555 (100%)	555 (100%)	555 (100%)	21 (3.8%)
Cornix supported group marketplace	85	85 (100%)	85 (100%)	85 (100%)	85 (100%)
Manual provider seed	74	26 (35.1%)	66 (89.2%)	0 (0%)	0 (0%)
Public WhatsApp source family	12	0 (0%)	12 (100%)	0 (0%)	0 (0%)
Public Discord source family	6	0 (0%)	6 (100%)	6 (100%)	0 (0%)

Subscriber observation distribution

Measure	Value	Denominator	Boundary
Observed rows	1,244	3,200	38.9% have a finite nonnegative integer value.
Missing rows	1,956	3,200	Missing is not zero.
Unique observed values	1,198	1,244	Value uniqueness does not imply unique audiences.
Median	11,210	1,244	Nearest-rank median among observed rows.
90th percentile	393,586	1,244	Nearest-rank value among observed rows.
99th percentile	5,296,032	1,244	Extreme upper-tail value.
Maximum	202,615,473	1,244	Stored metadata; not independently audited reach.
Arithmetic mean	460,460	1,244	Strongly affected by upper-tail values.

Stored count bucket	Rows	Share of observed
1-99	65	5.2%
100-999	180	14.5%
1,000-9,999	357	28.7%
10,000-99,999	360	28.9%
100,000-999,999	197	15.8%
1,000,000+	85	6.8%

Metadata-field intersection patterns

Mask	Direct route	Alias	Subscriber	Explicit key	Records	Share
`0001`	Blank	Blank	Blank	Present	1,870	58.4%
`1110`	Present	Present	Present	Blank	1,132	35.4%
`1111`	Present	Present	Present	Present	106	3.3%
`0100`	Blank	Present	Blank	Blank	52	1.6%
`1100`	Present	Present	Blank	Blank	26	0.8%
`0000`	Blank	Blank	Blank	Blank	8	0.3%
`0110`	Blank	Present	Present	Blank	6	0.2%

7 of 16 logical patterns occur. Masks use route, alias, subscriber, key order and sum to 3,200 records.

Platform-label and direct-route cross-tab

Platform	Label mentions	Route field	Label and route	Label without route
Telegram	3,150	1,257	1,257	1,893
Discord	24	6	6	18
WhatsApp	32	1	1	31
Web	40	1	1	39

Historical internal workflow by source family

Source family	Records	Historical internal review queue	Historical internal quality quarantine	Historical quality-quarantine share	Historically corrected
RealTelegram channel category	1,870	1,476	394	21.1%	0
TGStat crypto group rating	598	475	123	20.6%	0
TGStat crypto category	555	396	159	28.6%	1
Cornix supported group marketplace	85	84	1	1.2%	0
Manual provider seed	74	69	5	6.8%	0
Public WhatsApp source family	12	11	1	8.3%	0
Public Discord source family	6	6	0	0%	0

Cornix marketplace sample-size and activity audit

Measure	Value	Denominator	Boundary
Cornix marketplace records	85	3,200	Exact sourceKind cohort, not the provider market.
Unique / repeated group IDs	83 / 2	85	4 records are in repeated-ID groups; not duplicate proof.
Rated / unrated rows	46 / 39	85	Unrated means zero stored reviewers and no star value.
Rows with fewer than 10 reviewers	76	85	89.4%; reviewer counts are not deduplicated people.
Reviewer-count median / maximum	1 / 39	85	Nearest-rank record distribution.
Unweighted / reviewer-weighted star mean	3.593 / 3.571	46	Marketplace metadata, not CSR rating or provider conclusion.
Last-month signal median / maximum	131 / 3,000	85	Source-supplied activity quantity, not outcomes.
Weekly values matching monthly * 3 / 13	85	85	Within 1e-9; weekly is not an independent observation.
Exchange labels per record	1-18	85	Median 9; compatibility is not safety or execution proof.

Name and alias resolution

Measure	Count	Denominator	Boundary
Exact-name collision groups	57	Not applicable	Group count is not a record percentage.
Records in exact-name groups	124	3,200	Provider slugs requiring another identity key.
Unicode comparison groups	77	Not applicable	Only non-empty versioned keys shared across slugs.
Records in Unicode comparison groups	172	3,200	Case, combining-mark, and separator variants enter the same non-empty review key.
Records with aliases	1,322	3,200	Presence depends heavily on source-family design.
Providers in normalized shared-alias groups	28	1,322	Records requiring source and route reconciliation.

Route and dedupe resolution

Measure	Count	Denominator	Boundary
Records with direct routes	1,264	3,200	At least one direct route field is populated.
Direct-route assignments	1,265	3,200	One record has more than one route field, so assignments can exceed records.
Exact shared-route groups	9	Groups	Raw stored route equality; group count is not a record percentage.
Canonical shared-route records	25	1,264	Provider slugs touched by the primary platform-specific profile.
Records without explicit dedupe keys	1,224	3,200	Explicit-field missingness; generator fallback keys can still exist.
Repeated explicit-key groups	2	Groups	Opaque stored keys requiring record-level inspection.

Cite and download this release

Use the canonical dataset landing page, snapshot date 2026-07-05, source commit 5dcd30b2b1a0da9bacbaeec08244190dae19a49f, and the metric’s stated denominator. The aggregate files below are frozen in public release 91c6a4d3f781fce63acd8b9689a8511b60269370; repository commit 60368e8bdc778678738af1b1534253bdcbd3bd27 preserves the matching internal build.

Historical-field note: the immutable aggregate JSON and CSV retain the original 2026-07-05 raw workflow enum strings solely for byte-for-byte reproducibility. Those archived fields are historical internal workflow data, not current or alternative public verification labels; public verification uses only CSR Verified or CSR Unverified.

Download aggregate JSON
54,745 bytes. SHA-256 0d133d3a394c4c3e4d2f405e8dc6632209e216ea6a73a89360e101335f9375b3.
Download aggregate CSV
7,057 bytes. SHA-256 e64f109cd3379bf514946bb6b038031d97a3fb5257cda2d4dfc405a990db6230.

CryptoSignalsReview Evidence Desk. CryptoSignalsReview Provider Transparency Snapshot 2026-07-05. Published 2026-07-10. https://cryptosignalsreview.com/crypto-signal-provider-transparency-evidence-library/

Aggregate reuse terms: CSR permits quotation and reuse of the aggregate JSON and CSV with attribution to CryptoSignalsReview, the canonical landing page, snapshot date, and frozen source commit. This permission covers CSR’s aggregate analysis only; it does not grant rights in third-party names, marks, routes, or source-catalog content. Reuse must preserve the non-representative, non-verification, and non-performance boundaries.

Dataset boundary

This is a census of records in the CryptoSignalsReview candidate inventory at snapshot 2026-07-05, not a representative survey of every crypto signal provider or every messaging channel. Directory inclusion is discovery evidence only. Missing fields stay missing, platform labels can overlap, and no count proves provider quality, legality, profitability, or safety.

Public verification vocabulary: CSR Verified or CSR Unverified only. In this frozen snapshot, 0 records were CSR Verified and 3,200 were CSR Unverified. “Listed for review” and “quarantined” are retained only as historical internal workflow fields from 2026-07-05; neither is a third public verification status.

Frozen source: 5dcd30b2b1a0da9bacbaeec08244190dae19a49f. Unit: one unique CSR provider slug. Position: coverage is not endorsement.

Continue the transparency research

How the 3,200-Record Transparency Report Was Built
Reproducible methodology, denominators, field definitions, source limits, and non-claims behind the CSR crypto signal provider transparency report.
Crypto Signal Provider Due-Diligence Checklist
A beginner and advanced due-diligence workflow derived from the evidence gaps in 3,200 crypto signal provider candidate records.
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.
Why 98.4% of the Provider Dataset Is Telegram-Labeled
Analyze why 3,150 of 3,200 CryptoSignalsReview candidate records mention Telegram, what that concentration means, and what it cannot prove.
What 3,200 Provider Records Reveal About Missing Proof
Why the 3,200-record CSR inventory contains zero verified providers and zero reviewed result sheets, and what evidence would change those statuses.