Operational methodology

The decision contract behind every provider file.

CryptoSignalsReview classifies what is known, what remains unproven, and what evidence would change the status. No file implies that a provider is safe, profitable, or suitable beyond the exact proof shown.

1Identity & offer

Confirm the official route, operator or identity claim, product, price, terms, and material conflicts.

2Performance proof

Review a dated, loss-inclusive record with original calls, edits, fees, slippage, leverage, and calculation rules.

3Delivery & operational risk

Inspect alerts, access, payments, refunds, support, bots, and exchange permissions in practice.

Every conclusion must be reversible.

New evidence can raise or lower confidence. Missing proof stays beside the affected claim, and payment, popularity, or visitor opinion cannot change a CSR status.

Three evidence gates

A provider passes only what the record can support.

Gate 1

Identity and offer

The gate passes when official route control is confirmed, claimed people or entities are matched where applicable, and the current product, pricing, billing, refund, and access terms are dated. Unresolved ownership or term conflicts fail the gate.

Gate 2

Performance proof

The gate passes only for a named period when every call in that period is reviewable from original records, including losses, open calls, edits, deletes, fees, slippage, leverage, exits, and result math. Selected periods prove only those periods. Apply the crypto signal accuracy evaluation method before relying on a percentage.

Gate 3

Delivery and operational risk

The gate passes when delivery timing, access, payment, cancellation, support, automation, custody, and API permissions are documented or observed where relevant. Material failures or unsafe permissions remain risk notes. For Telegram-led offers, apply the pre-payment red-flags checklist before paying or granting account access.

Binary verification status

Every provider is CSR Verified or CSR Unverified.

CSR Unverified is the default

Used whenever any required gate is missing, incomplete, rejected, withdrawn, or stale. An active review or a documented caution can be shown as a separate research note, but neither creates another verification status.

CSR Verified requires every gate

All three evidence gates, technical checks, current source access, independent calculation, and named human approval must pass. The evidence record separately names the period, sample, source access, assumptions, included products, exclusions, and last-check date.

Failure returns the status to CSR Unverified

If evidence expires, access stops, a material conflict appears, or approval is withdrawn, the public badge changes to CSR Unverified. The dated reason remains visible in the evidence record.

Risk notes remain separate

Confirmed route or identity mismatches, selective records, omitted losses or edits, unsupported result math, unsafe permissions, and payment or refund conflicts remain visible as risk notes. They never become a third verification status.

Freshness and expiry

Current evidence has a 90-day clock.

Identity and offerCurrent for 90 days from Last checked
Delivery and operational riskCurrent for 90 days from Last checked
Performance proofHistorical for its named period; current for 90 days after Reviewed through
Material route, ownership, term, delivery, permission, or result-method changeExpires the affected evidence immediately

On day 91, if current-evidence requirements no longer pass, the public status becomes CSR Unverified. A refresh may continue as a research activity, while the earlier evidence remains visible as dated historical context.

Missing proof and corrections

Unknowns stay visible. Corrections change the record, not the past.

Missing proof is a finding.

CSR names the gap beside the claim and leaves that claim unproven. Member counts, testimonials, screenshots, anonymous comments, provider assurances, and paid production do not fill it.

1. SubmitIdentify the exact page, disputed statement, source, and source date
2. PreserveCompare the request with the published text and prior source record
3. RecheckTest the new evidence against the same three gates
4. UpdateCorrect the fact, date, proof gap, and status when the evidence requires it
5. RespondShow a provider response when useful; disagreement alone does not change status

Material corrections show the correction date and what changed. Losses, old claims, prior limitations, and earlier statuses are not silently erased.

For Dutch-language experience research, use the crypto signals ervaringen evidence workflow to separate attributable observations, provider claims, and unresolved proof before treating an experience report as decision-grade evidence.

Best 21 boundary

Best 21 is a research-priority shortlist, not a league table.

Inclusion meansThe provider file has current reader relevance and decision value worth comparing
Order meansEditorial reading sequence only; it is not a score
Order can change whenEvidence depth, staleness, category coverage, or reader relevance changes
Inclusion and order never meanApproval, verified status, safety, profitability, value, or future results
Commercial influencePaid work, sponsored visibility, profile work, popularity, and visitor reviews cannot buy inclusion or position

Every Best 21 file displays CSR Verified or CSR Unverified. Research activity, missing proof, and caution notes are displayed separately because comparison can be useful before trust is earned. Coverage is not endorsement.

Apply the contract

Check a provider before paying, copying, or connecting access.

Open a provider file, read the current status and missing proof, then decide what must be verified next. CSR research is informational; crypto trading involves risk, and past performance does not guarantee future results.