Original CryptoSignalsReview dataset research

What 3,200 Provider Records Reveal About Missing Proof

The inventory is large, but its verification count is zero. That is not a verdict that every candidate is bad; it is a transparent statement that directory discovery has not been upgraded into reviewed proof.

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 evidence ladder

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

CSR Unverified3,200

100% remain unresolved candidates.

CSR Verified0

No record is presented as CSR Verified in the 2026-07-05 snapshot. Frozen value; see the <a href="/how-csr-verifies-results/">current verification status</a>.

Reviewed result sheets0

No loss-inclusive result sheet completed CSR review.

Direct answer

The snapshot contains 3,200 CSR Unverified providers, no CSR Verified providers, and no CSR-reviewed result sheets. The correct interpretation is procedural: the inventory is an intake and discovery surface. A candidate stays unresolved until identity, original alerts, complete outcomes, execution assumptions, terms, and conflicts can be reconciled. Absence of reviewed proof is not proof of fraud, and directory presence is not proof of quality.

Public verification status

Public verification statusRecordsShare
CSR Unverified3,200100%
CSR Verified00%

The immutable downloads also preserve raw historical internal workflow fields for reproducibility. Their 2,517-record review queue and 683-record quality-quarantine cohort both map to CSR Unverified; neither creates another public status.

Result-sheet statusRecordsShare
No CSR-reviewed result sheet2,51778.7%
Not applicable until crypto signal relevance is confirmed68321.3%

The six-level evidence ladder

1. Identity and route

Match the provider name, legal or operating identity where claimed, public handle, official website, app or marketplace route, payment recipient, and support identity. An independently sourced route is stronger than a link forwarded inside an unsolicited chat.

2. Original signal archive

Preserve the original message IDs, timestamps, edit history, symbols, venues, entries, invalidations, stops, targets, leverage or margin assumptions, and every follow-up. A screenshot without archive continuity is an illustration, not a complete sample.

3. Loss-inclusive outcome reconstruction

Include stopped trades, expired setups, never-filled entries, partial exits, moved stops, open positions, deleted calls, and market periods that do not flatter the strategy. Define how ambiguous calls and missing updates are treated.

4. Execution reality

Reconcile alert time with executable liquidity, bid/ask spread, slippage, fees, funding, contract specification, exchange outage, copier delay, and follower settings. Provider-side theoretical returns are not the same as subscriber outcomes.

5. Commercial terms and control

Save the price, renewal, cancellation, refund, trial, affiliate, brokerage, API permission, copy-control, and support boundaries shown before payment or connection. A disclaimer cannot substitute for the actual service path.

6. Independent reconciliation

Document what agrees, what conflicts, and what remains missing. Verification should be reversible when source records change. Paid production or profile work cannot buy a better evidence status.

Why selected wins do not close the gap

A selected result can omit fees, losing calls, unfilled entries, edits, and the period used to choose the sample. Testimonials add another person’s claim but rarely provide the underlying trade record. Member counts describe audience size, not execution quality. The CFTC’s guidance on internet trading systems specifically highlights hypothetical-result limits, market conditions, stop execution, spreads, fees, and the danger of selectively manufactured historical results.

A reviewable result sheet needs an explicit denominator. It should state the full date range, eligible alerts, excluded alerts and reasons, entry rule, fill assumption, exit hierarchy, unresolved positions, costs, drawdown method, and source archive. Another reviewer should be able to reproduce the total from the same records.

What would change the count

Evidence packetMinimum useful contentsWhy it matters
Identity packetOfficial route, operator or entity claim, payment identity, support identity, dated continuityReduces impersonation and route ambiguity.
Signal packetOriginal loss-inclusive archive with edit and deletion handlingCreates a complete review denominator.
Execution packetVenue, contract, fees, funding, slippage, latency, follower fillsTests whether published outcomes were executable.
Terms packetCheckout, pricing, renewal, refund, permissions, disclosuresShows what service and control were actually offered.
Reproduction fileRules, formulas, source references, exceptions, reviewer notesAllows independent recalculation and correction.

Decision boundary

A zero CSR Verified count is a reason to request evidence, not to make a universal accusation. A provider can respond with records; CSR can review them; and the public status can change only through evidence. Until then, the safest statement is limited: the provider is CSR Unverified, no CSR-reviewed result sheet is available, and missing proof remains visible. A raw “listed for review” value in the immutable snapshot is historical internal workflow data, not a public label.

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