Which Crypto Signal Provider Metadata Fields Appear Together?

Four binary fields and their limits

Comparison version route-alias-subscriber-explicit-key-crosstab-v1 evaluates each field independently on one unique CSR provider slug. Presence means the manifest contains a qualifying value. It does not test freshness, correctness, provenance strength, agreement with another source, or suitability for a user decision.

Seven observed metadata patterns

The mask order is direct route, alias, subscriber observation, explicit key. For example, 1110 means the first three fields are present and the explicit key is blank. The seven rows sum to 3,200. The other 9 logical combinations have zero records and are not silently converted into missing rows.

The bundle pattern follows the collection path

The largest pattern, 0001, contains all 1,870 RealTelegram records: explicit key present, other three fields blank. Pattern 1110 contains 1,132 TGStat rows with direct route, alias, and subscriber metadata but no explicit key. Pattern 1111 contains 106 rows: 85 Cornix and 21 TGStat-category rows.

The smaller patterns are equally diagnostic. All 26 route-plus-alias-only rows are manual seeds. The 6 alias-plus-subscriber rows are the Discord source family. Alias-only rows combine 40 manual and 12 WhatsApp records. The 8 all-blank rows are manual seeds. These exact alignments show importer design, not natural provider classes.

Pairwise and three-field intersections

Intersections answer whether values coexist on one record. They do not answer whether the values agree, whether the route is official, whether the count is current, or whether the key correctly groups an entity. A large intersection can be entirely explained by one importer.

Narrative dossiers sit outside the route and key bundles

This disconnect is another warning against a single completeness score. Narrative research, identity routing, audience metadata, and source keys were collected through different workflows. Adding their presence flags together would reward importer breadth without measuring evidence quality.

Workflow status by pattern

The listed-for-review and quarantined columns sum to each pattern’s record count. Across the entire inventory, CSR-verified records remain 0 and CSR-reviewed result sheets remain 0. Field co-occurrence changes neither status.

How to use the cross-tab without inventing a score

1. Identify the record’s actual pattern; do not impute blanks from its source family.
2. Open the underlying values and preserve their source and snapshot date.
3. Resolve the direct route independently before relying on aliases or payment instructions.
4. Treat the subscriber count as an observed catalog value, not an audience-quality signal.
5. Use the explicit key only as a review join; inspect names, routes, operators, products, and dates before merging.
6. Request the missing identity, archive, execution, and terms evidence required for the decision.

A citation-safe aggregate statement is: “Seven route/alias/subscriber/key presence patterns occur in CSR’s frozen 3,200-record inventory.” Keep the inventory, field order, date, and non-verification boundary attached. Do not turn the 106 all-four rows into a verified-provider count.

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.

• 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

• Where the 3,200 Crypto Provider Records Came From

  Source-family and field-completeness analysis for the 3,200-record CSR provider inventory, including TGStat, RealTelegram, Cornix, manual seeds, and gaps.

• Crypto Signal Provider Subscriber Counts: Distribution and Source Bias

  Original distribution analysis of 1,244 stored subscriber observations across 3,200 CSR provider records, including quantiles, source coverage, skew, and non-claims.

• Crypto Signal Provider Country and Language Metadata Audit

  Audit country and language labels across 3,200 crypto signal provider records, including source defaults, non-global coverage, and jurisdiction limits.

• Cornix Crypto Signal Marketplace Metrics: Review Sample Size Audit

  Original audit of 85 frozen Cornix marketplace records: reviewer denominators, star summaries, derived weekly activity, offer flags, and exchange compatibility limits.

• 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.