Original CryptoSignalsReview dataset research
Crypto Signal Provider Transparency Report 2026
What does a large crypto signal provider inventory actually prove? This report separates discovery coverage from verified evidence and publishes the aggregate gaps instead of turning directory size into a ranking claim.
Read the seven findingsNo signup, payment, wallet connection, or credentials are required.
Unique CSR slugs in the frozen inventory.
3,150 records mention Telegram in the platform label.
Snapshot value for 2026-07-05. The inventory contains candidates, not verified recommendations. This is a frozen research figure, not a live count — see the <a href="/how-csr-verifies-results/">current verification status</a>.
Direct answer
The strongest finding is not that CryptoSignalsReview found 3,200 trustworthy providers. It is that discovery breadth is much larger than review depth. The binary public status was 3,200 CSR Unverified and 0 CSR Verified, with 0 CSR-reviewed result sheets. Separately, the frozen historical internal workflow split those records into a 2,517-record review queue and a 683-record quality-quarantine cohort. Those archived workflow classes are not additional public verification statuses. A large directory can improve discovery while still leaving identity, service terms, execution history, loss accounting, and provider continuity unresolved.
Seven findings from the frozen inventory
1. Messaging-platform discovery dominates the inventory
3,150 records, or 98.4%, contain Telegram in the platform label. This is a property of the source mix and collection method, not a claim that the same percentage describes the entire provider market. Telegram categories, groups, channels, and Cornix-linked routes were intentionally prominent inputs.
2. A source route is not an official provider route
Every record retains a discovery source URL, but only 1,264 records have at least one populated Telegram, Discord, WhatsApp, or website route field. The remaining source may be a catalog, marketplace, or category page. That distinction matters because a catalog listing can support existence and classification while remaining insufficient for identity or payment verification.
3. Public verification remains unresolved by design
All 3,200 records carry the public status CSR Unverified and 0 carry CSR Verified in this snapshot. The historical internal workflow recorded 2,517 in its review queue and 683 in its quality-quarantine cohort. The result is a research queue, not a leaderboard. Position, subscriber count, source family, or platform label does not move a provider into CSR Verified status.
4. Result-sheet proof is the central evidence gap
The historical internal review queue contains 2,517 records whose raw snapshot fields say that no CSR-reviewed result sheet is available; the historical internal quality-quarantine cohort marks result-sheet review as not applicable until signal relevance is established. A screenshot, selected win, testimonial, or public member count cannot fill this field. Review requires a loss-inclusive archive, rules for edits and open positions, fees, slippage assumptions, and a reproducible calculation basis.
5. The historical internal quality quarantine removes category noise without making accusations
The frozen historical workflow placed 683 records, 21.3% of the inventory, in its internal quality-quarantine cohort. Most were classified as project/community or airdrop/giveaway candidates rather than usable signal-provider records. That internal classification says the record should not be framed as a provider recommendation; it does not declare fraud, misconduct, or illegality and does not replace the public CSR Unverified status.
6. Field depth is uneven
Subscriber counts are present for 1,244 records, aliases for 1,322, and detailed public-footprint, offer-style, proof-focus, and claim-posture fields for only 18. The report therefore publishes coverage rates and does not silently treat blank fields as negative findings.
7. This inventory is useful as a map of questions
The records can help a reader locate a name, preserve aliases, identify a discovery source, and see what CSR has not verified. They cannot answer whether a service is suitable, profitable, legal in a reader’s jurisdiction, or safe to pay. The appropriate output is a next evidence request, not a score invented from incomplete fields.
Core transparency table
| Measure | Count | Share | Interpretation |
|---|---|---|---|
| All candidate records | 3,200 | 100% | Inventory denominator; not a market-size estimate. |
| CSR Unverified | 3,200 | 100% | Public binary status for every unresolved candidate in this frozen snapshot. |
| CSR Verified | 0 | 0% | No record had passed into CSR Verified status as of 2026-07-05. Frozen snapshot value; for live status see the current verification status. |
| CSR-reviewed result sheet | 0 | 0% | No record has a completed CSR result-sheet review. |
| Direct provider-route field | 1,264 | 39.5% | At least one Telegram, Discord, WhatsApp, or website field is populated. |
| Subscriber count present | 1,244 | 38.9% | Catalog metadata only; not evidence of outcomes. |
Historical internal workflow (2026-07-05)
| Archived workflow class | Count | Share | Interpretation |
|---|---|---|---|
| Historical internal review queue | 2,517 | 78.7% | Raw frozen workflow state; maps to CSR Unverified. |
| Historical internal quality quarantine | 683 | 21.3% | Raw frozen relevance-triage state; maps to CSR Unverified. |
What beginners and advanced traders should do differently
Beginners: use the provider name and source route to slow the decision down. Match the exact handle, locate an independently verified route, save the offer and terms before payment, and stop if the seller will not provide a loss-inclusive record. Do not convert group size or repeated testimonials into trust.
Advanced traders: treat the provider record as a join key for a deeper evidence packet. Reconstruct timestamps, entry feasibility, invalidation rules, leverage, moved stops, partial exits, fees, slippage, deleted posts, unresolved positions, and follower-side fills. Separate provider-side signal quality from exchange execution and copier behavior.
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.
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.
- Investor.gov: social media and investment fraud
Identity verification, impersonation, testimonials, urgency, and social-media limitations.
- CFTC: commodity trading systems sold on the internet
Hypothetical results, fees, slippage, loss capacity, and performance-claim limitations.
- CFTC: virtual-currency pump-and-dump advisory
Messaging-app tips, anonymity, urgency, thin liquidity, and market-manipulation risk.
Continue the transparency research
- 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.
- Why 683 Records Entered CSR’s Historical Quality Quarantine
Analyze CSR’s 683-record historical internal quality-quarantine cohort, including project communities, airdrop groups, weak names, and non-signal candidates.
- Crypto Signal Provider Name Collision Report 2026
First-party analysis of repeated provider names across 3,200 records, with exact and Unicode-normalized counts, source context, and identity limits.
- Crypto Signal Provider Alias Coverage and Entity Resolution
Audit alias-field coverage across 3,200 provider records, including importer patterns, shared values, source-family gaps, and display-name matches.