Field-guide appendix

Methodology

How to read marketplace status, evidence, confidence, and stats.

The central questions are: what is gone, what remains, and where did users or assets go? Records keep uncertainty visible instead of smoothing it away.

Placeholder mock evidence must never be presented as verified proof. Current records remain mock layout data.

01

What counts

Included records are named NFT marketplaces, aggregators, CEX-operated marketplace features, chain-specific markets, curated art markets, gaming/metaverse markets, successor/fork markets, and historically meaningful marketplace interfaces when sources support the classification.

02

What does not count

Excluded items include standalone collections, one-off mint pages, galleries, portfolio trackers, price comparison sites, news sites, analytics dashboards, and records where marketplace behavior or source support is too thin.

03

Evidence rules

Prefer official announcements, archived pages, current marketplace pages, reputable news, documentation, and primary social posts. Corrections should include exact URLs and notes about what changed.

Status definitions

Reading the specimen labels

active

Core marketplace behavior appears available.

limited

Some function remains, such as viewing, withdrawal, migration, or partial chain support.

inactive

Activity appears faded but closure is not proven.

dead

Marketplace function is ended or inaccessible.

acquired / merged / rebranded

The record changed identity, ownership, or destination.

unknown

Evidence is insufficient for a clearer status.

Frontend / contract / asset status

NFT marketplaces can disappear unevenly. The frontend may be gone while contracts remain readable, or assets may remain visible through another interface. Detail pages expose all three fields.

Confidence levels

Confidence communicates how strongly the available sources support the classification. Low confidence is acceptable for mock or seed work if the record is clearly marked for review.

Stats methodology

Stats are generated from the same JSON records used by the site. They are coverage and classification summaries, not live market analytics or rankings.

Corrections

Make uncertainty reviewable

Corrections should include source URLs, archive URLs where possible, and precise notes about status, dates, or what remains. Disagreements should be tracked as review work rather than hidden.

Open the correction desk