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.

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.

Read the seven findings

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

Candidate records3,200

Unique CSR slugs in the frozen inventory.

Telegram-labeled98.4%

3,150 records mention Telegram in the platform label.

CSR Verified0

Snapshot value for 2026-07-05. The inventory contains candidates, not verified recommendations. This is a frozen research figure, not a live count &#8212; 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

MeasureCountShareInterpretation
All candidate records3,200100%Inventory denominator; not a market-size estimate.
CSR Unverified3,200100%Public binary status for every unresolved candidate in this frozen snapshot.
CSR Verified00%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 sheet00%No record has a completed CSR result-sheet review.
Direct provider-route field1,26439.5%At least one Telegram, Discord, WhatsApp, or website field is populated.
Subscriber count present1,24438.9%Catalog metadata only; not evidence of outcomes.

Historical internal workflow (2026-07-05)

Archived workflow classCountShareInterpretation
Historical internal review queue2,51778.7%Raw frozen workflow state; maps to CSR Unverified.
Historical internal quality quarantine68321.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.

Continue the transparency research