Original CryptoSignalsReview dataset research
Crypto Signal Provider Due-Diligence Checklist
The dataset’s most useful output is a stopping rule: do not let a name, directory entry, follower count, disclaimer, or selected result stand in for the records needed to make the next decision.
Start the decision checklistNo signup, payment, wallet connection, or credentials are required.
39.5% of candidates.
Audience metadata, not result proof.
The evidence gap this workflow addresses.
Direct answer
Before joining, paying, copying, or connecting an account, verify the route, service, control path, terms, and loss-inclusive record separately. Stop when any required record is missing. The 3,200-record snapshot shows why: a discovery source exists for every candidate, but only 1,264 have a direct route field and none has a CSR-reviewed result sheet.
Beginner checklist: before joining or paying
| Step | Record to save | Stop when |
|---|---|---|
| 1. Resolve the name | Exact provider name, aliases, handle, and the independently reached route | The destination differs by a character or cannot be cross-linked. |
| 2. Identify the service | What is delivered, where, how often, and whether it is education, alerts, copying, software, or account control | The seller changes the service description between marketing and support. |
| 3. Preserve the offer | Price, currency, trial, renewal, cancellation, refund, payment recipient, and timestamp | Material terms appear only after payment or conflict across channels. |
| 4. Ask for the complete record | A dated, loss-inclusive archive and calculation rules | Only wins, testimonials, or screenshots are supplied. |
| 5. Check permissions | Every requested API, wallet, bot, copier, or account permission and how to revoke it | Withdrawal access, seed phrases, passwords, or unclear authority are requested. |
| 6. Slow urgency | The reason for any deadline and whether the same terms remain available after independent checks | Pressure is used to prevent route, identity, or terms verification. |
Advanced checklist: reconstruct execution
| Evidence lane | Advanced check | Common distortion |
|---|---|---|
| Alert chronology | Original message ID, timestamp, edit state, deletion handling, and every update | A clean final screenshot replaces the path followers actually saw. |
| Entry feasibility | Venue, contract, price source, order type, available liquidity, spread, and latency | The posted entry was visible historically but not executable after the alert. |
| Risk definition | Invalidation, stop, leverage, margin mode, size rule, and portfolio exposure | Outcome reporting counts targets without the downside or capital at risk. |
| Exit accounting | Partial exits, moved stops, breakeven rules, unresolved positions, and conflicting updates | A provider selects the most favorable interpretation after the fact. |
| Costs | Trading fee, spread, slippage, funding, subscription, copier, and data costs | Gross theoretical return is presented as follower profit. |
| Follower evidence | Subscriber-side orders, fills, errors, settings, and manual overrides | Provider alert quality is conflated with exchange or copier execution. |
| Sample integrity | Complete period, all eligible alerts, exclusions with reasons, and reproducible denominator | The review window is chosen because it flatters the strategy. |
Evidence packet template
Provider or channel name: Independent official route: Captured at (UTC): Service promised: Price and payment recipient: Renewal, cancellation, and refund terms: Permissions requested and revocation test: Archive start and end date: Complete alert count: Losses, open positions, and deleted calls: Entry and exit assumptions: Fees, spread, slippage, and funding: Follower-side fills available: Conflicts between sources: Missing proof: Safest next action: Private fields redacted:
Five stopping rules
- Stop if the official route cannot be resolved independently.
- Stop if the service or payment recipient changes during the decision path.
- Stop if only selected wins or hypothetical results are offered.
- Stop if account permissions exceed the service that was explained.
- Stop if urgency is used to prevent evidence checks.
Stopping does not label a provider fraudulent. It preserves the unresolved state until the required record appears. That distinction protects both readers and providers from unsupported conclusions.
Why follower count and disclaimers are insufficient
1,244 records have stored subscriber counts, but audience size does not show active users, successful execution, or complete outcomes. A no-advice disclaimer also cannot resolve what the provider actually promotes, sells, controls, or claims. FCA and ESMA materials emphasize clear, accurate, balanced social-media communication and the limits of generic disclaimers; Investor.gov and CFTC materials emphasize identity checks, resistance to urgency, complete research, and skepticism toward high-return or hypothetical-performance claims.
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.
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
- 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 Transparency Data Table
The aggregate counts, percentages, source families, platform labels, field coverage, statuses, and quarantine classes behind the 2026 CSR report.
- 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.
- 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.