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.

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

Start the decision checklist

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

Direct routes present1,264

39.5% of candidates.

Subscriber counts1,244

Audience metadata, not result proof.

Reviewed result sheets0

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

StepRecord to saveStop when
1. Resolve the nameExact provider name, aliases, handle, and the independently reached routeThe destination differs by a character or cannot be cross-linked.
2. Identify the serviceWhat is delivered, where, how often, and whether it is education, alerts, copying, software, or account controlThe seller changes the service description between marketing and support.
3. Preserve the offerPrice, currency, trial, renewal, cancellation, refund, payment recipient, and timestampMaterial terms appear only after payment or conflict across channels.
4. Ask for the complete recordA dated, loss-inclusive archive and calculation rulesOnly wins, testimonials, or screenshots are supplied.
5. Check permissionsEvery requested API, wallet, bot, copier, or account permission and how to revoke itWithdrawal access, seed phrases, passwords, or unclear authority are requested.
6. Slow urgencyThe reason for any deadline and whether the same terms remain available after independent checksPressure is used to prevent route, identity, or terms verification.

Advanced checklist: reconstruct execution

Evidence laneAdvanced checkCommon distortion
Alert chronologyOriginal message ID, timestamp, edit state, deletion handling, and every updateA clean final screenshot replaces the path followers actually saw.
Entry feasibilityVenue, contract, price source, order type, available liquidity, spread, and latencyThe posted entry was visible historically but not executable after the alert.
Risk definitionInvalidation, stop, leverage, margin mode, size rule, and portfolio exposureOutcome reporting counts targets without the downside or capital at risk.
Exit accountingPartial exits, moved stops, breakeven rules, unresolved positions, and conflicting updatesA provider selects the most favorable interpretation after the fact.
CostsTrading fee, spread, slippage, funding, subscription, copier, and data costsGross theoretical return is presented as follower profit.
Follower evidenceSubscriber-side orders, fills, errors, settings, and manual overridesProvider alert quality is conflated with exchange or copier execution.
Sample integrityComplete period, all eligible alerts, exclusions with reasons, and reproducible denominatorThe 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

  1. Stop if the official route cannot be resolved independently.
  2. Stop if the service or payment recipient changes during the decision path.
  3. Stop if only selected wins or hypothetical results are offered.
  4. Stop if account permissions exceed the service that was explained.
  5. 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.

Continue the transparency research