Operational scope ledger · 11 Jul 2026

Every row gets
an evidence state.

The goal is exhaustive provider coverage without fake certainty. CoinMarketCap supplies a dated discovery inventory; CoinCheckup remains behind an authorization gate. Each discovered public channel receives a terminal audit state—even when that state is “inaccessible” or “ownership unresolved.”

01 / PROVIDER SCOPE

Two sources. Two different states.

Inventory access, channel verification and a project verdict are separate stages. A provider row never becomes “silent” merely because a later stage has not run.

CoinMarketCap

Inventory snapshot captured

Observed

The dated map snapshot supplies listing candidates in three market-support states. Those states describe CoinMarketCap tracking—not whether a project team is communicating.

Total rows: 37,294
Active: 8,180
Inactive: 1,756
Untracked: 27,358

01
Provider inventoryCaptured 11 Jul 2026
Complete
02
Chain and contract identityDeduplicate wrappers, aliases and ticker collisions
Not published
03
Official-link discoveryHydrate website and social candidates, then prove ownership
Not published
04
Channel evidenceCollect native IDs, timestamps, access state and counterevidence
Not published
05
Human classificationOnly evidence-reviewed records receive a Dead Tokens assessment
Case files only

Discovery inventory data provided by CoinMarketCap.com. Dead Tokens independently derives channel evidence and assessments.

CoinMarketCap API reference ↗

CoinCheckup

Authorization gate closed

Not approved

CoinCheckup's effective 7 July 2025 terms prohibit automated extraction, scraping, redistribution and commercial reuse without authorization. Import only a customer export, API response or catalog supplied under written permission, and record that permission before publishing provider-derived rows.

Catalog import: Not started
Automated extraction: Blocked by gate
Public provider-derived rows: Withheld
Gate checked: 11 Jul 2026

No workaround: a sitemap, public page or search result does not replace written authorization. The audit can ingest a customer export or API only after the applicable agreement is recorded.

Review current terms ↗Request permission →

02 / DECISION BOUNDARY

No access is not silence.

No access

The history could not be fully examined because of a private group, deleted page, login wall, block, rate limit, unavailable Nitter mirror or unresolved identity.

Result: inaccessible or unresolved. No silence claim.

✓

Checked silence

The channel is official, its applicable public history was examined through a stated UTC time, the newest qualifying event was preserved, and contradiction searches found no newer successor signal.

Result: a scoped channel clock—not proof of private inactivity.

03 / TERMINAL STATES

Every channel check must end explicitly.

A blank field is not allowed to masquerade as silence. These normalized outcomes retain both the channel’s evidence state and the independent ownership assessment.

StateWhat it meansClock treatment

ActiveA recent, meaningful first-party event was verified on this channel.Native event time

SilentOwnership and accessible history were checked; no newer qualifying event was found through the stated check time.Last verified event + checked-at

StaleAn older last event is dated, but this channel alone cannot establish project-wide silence.Last verified event

DeletedThe verified account, page or repository was absent at observation time.Observed-at; historic event if known

SuspendedThe platform reports a suspension; the cause and full history may remain unknown.Observed-at; historic event if known

InaccessibleA login wall, private group, access denial, rate limit or unavailable mirror prevented a complete check.Checked-at only; never a silence clock

MigratedA verified successor channel carries the project’s continuing identity.Migration or successor event

Not exhaustively checkedA candidate channel exists, but ownership or full history has not been established.No silence clock

Ownership is a separate axis: verified, probable, unresolved or disputed. A precise timestamp from the wrong account is not valid project evidence.

04 / CHANNEL CONTRACT

What “each social” means in production.

Each applicable surface gets its own collection method, source-specific timestamp and failure state. Additional official channels discovered during review join the same ledger.

WWW

Website and documentation

Resolve redirects and ownership, preserve response state, monitor content hashes, and use changelogs or archives only at their supported precision.

Last verified content event, reachable-but-unchanged, offline, repurposed, blocked or identity unresolved.

X / Twitter and Nitter

Retain the native account or post ID and UTC timestamp. Nitter is an access aid, not a separate authority, and mirror failure is recorded independently.

Last verified native post, deleted/suspended account, inaccessible timeline, migrated handle or ownership unresolved.

Medium and first-party blogs

Check profile identity, native article pages and RSS where available; separate publication time from later page edits or syndication.

Last qualifying project-authored post, deleted publication, stale feed, migrated blog or inaccessible history.

GitHub and code forges

Inspect verified organizations, meaningful human commits and releases across relevant branches; exclude bots, mirrors and unrelated forks.

Latest meaningful commit/release, archived or deleted repository, private history, successor repository or unresolved ownership.

Use verified public channels or announcement feeds and preserve message IDs, UTC dates and edit state. Private groups and deleted history remain unknown.

Last qualifying public message, migrated channel, inaccessible/private group, deleted feed or ownership unresolved.

Discord and chat communities

Check public announcement surfaces or an authorized export. A login gate, invite failure or unavailable history is an access result—not silence.

Last verifiable announcement, closed server, inaccessible history, migrated community or not exhaustively checked.

Reddit, forums and governance

Separate official project accounts from community discussion, preserve native post IDs and search for successor forums or governance portals.

Last official communication, community-only activity, deleted forum, inaccessible history or identity unresolved.

YouTube and other discovered media

Record native publication timestamps and channel ownership for video, podcast, Facebook, LinkedIn, Instagram and any project-specific surface discovered.

Last verified first-party publication or an explicit deleted, inaccessible, migrated, unverified or not-applicable state.

05 / PUBLICATION RULE

Scale the queue.
Keep the verdict narrow.

Provider-wide discovery can be automated. Identity resolution, inaccessible histories, migrations and project-wide silence require adversarial review. Until those checks finish, the public state is “unreviewed candidate”—never “dead by default.”

Read the verification protocol Inspect provider constraints