Why 683 Records Entered CSR’s Historical Quality Quarantine

Historical internal quality-quarantine composition

The share column uses the full 3,200-record inventory as denominator. Within the historical internal quality-quarantine cohort alone, project/community candidates account for 62.4% and airdrop/giveaway candidates account for 35.3%.

Historical internal quality quarantine by discovery-source family

The denominator for each share is that source family’s row count. TGStat category records have the highest observed historical quality-quarantine share at 28.6%, followed by RealTelegram at 21.1% and TGStat group-rating rows at 20.6%. The historical workflow placed 1 Cornix row in that cohort among 85; the six Discord rows had none.

These percentages describe how the frozen CSR internal workflow rules interacted with each collection path. They are not fraud rates, source-accuracy ratings, provider-quality comparisons, public verification labels, or estimates for the broader market. Source families collect different object types and use different inclusion frames. A higher share can reflect category spillover or a broader intake rule rather than worse conduct by the listed communities.

Historical internal quality flags used in the snapshot

Flags are archived triage labels. A weak project or mini-app candidate may be a legitimate project community that simply does not belong in a signal-provider comparison. A weak provider name may be too generic or malformed to support confident entity resolution. A likely non-signal candidate may be news, wallet, support, or community material rather than an alert service.

Why the historical internal quality workflow improves search quality

Without an internal quality-triage layer, a broad catalog import can turn unrelated project groups, giveaways, wallets, news feeds, and truncated names into pages that look like provider reviews. That would mislead readers and create search pages with a false premise. The historical internal workflow kept the page’s job narrow: identify the record, state why signal relevance is unresolved, and request the proof needed to classify it correctly.

The page should not use words such as best, trusted, verified, or recommended merely because a name appeared in a directory. It should also avoid accusations. A weak source record can result from category spillover, stale metadata, an ambiguous name, or a legitimate community outside CSR’s provider scope.

The four historical internal quality controls

Relevance control

Does the record describe a service that publishes actionable crypto trading alerts, analysis tied to explicit decisions, copy-trading instructions, or another clearly defined signal function? General project chat, airdrops, token news, and broad education do not automatically qualify.

Identity control

Can the candidate name be resolved to a stable public route without guessing? Generic names, truncated scrape artifacts, or aliases that collide with unrelated entities require correction or stronger source evidence.

Offer control

Is there a visible offer, delivery method, audience, payment path, and service boundary? If the record only proves a community exists, it should not be framed as a paid or free signal provider.

Recommendation control

Even a relevant provider remains CSR Unverified until the evidence ladder is completed. The historical internal quality gate stopped clearly weak records from entering the recommendation conversation at all; it did not create a third public status.

Correction remains possible

The snapshot includes 1 record marked corrected after a malformed scraped name was repaired before publication. That example matters because quality auditing should not be a one-way blacklist. A record can move when better identity, relevance, or source evidence appears. The change should be documented, dated, and reproducible.

Provider submissions or paid production can supply missing records, but they cannot purchase removal of a valid risk note, a verified label, a ranking position, or a positive conclusion. Evidence changes status; commercial relationships do not.

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.

Continue the transparency research

• Crypto Signal Provider Transparency Report 2026

  Original analysis of 3,200 crypto signal provider candidate records: platform concentration, binary verification, historical workflow, 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.

• Crypto Signal Provider Name Collision Report 2026

  First-party analysis of repeated provider names across 3,200 records, with exact and Unicode-normalized counts, source context, and identity limits.

• Crypto Signal Provider Alias Coverage and Entity Resolution

  Audit alias-field coverage across 3,200 provider records, including importer patterns, shared values, source-family gaps, and display-name matches.