Binance and MEXC listing dataset since September 2026

Current source-backed snapshot

A current event calendar answers what is scheduled next; a research dataset answers what was recorded, when it became known and how later announcement changes were preserved. This page is for the second job. It exposes CoinNudge's listing and delisting catalog by named source and normalized status, alongside point-in-time boundaries. That distinction matters for event studies: a later corrected announcement must not silently replace what a model could have known earlier.

Input documentation: Binance announcements · MEXC announcements · CoinNudge data sample · CoinNudge methodology

Observation window: Actual Binance and MEXC announcement observations since September 2026

Calculation cadence: Auto-refresh about every 3600 seconds

Calculation version: coinnudge-listing-history-coverage-2.0

Download current dataset: JSON · CSV Raw values retain the dataset's published precision. Free fair-use limit: 60 requests per minute per IP, shared across all Research JSON and CSV endpoints.

Observation evidence

First 30 of 30 observations. JSON and CSV contain all published evidence. CSV dataset_section distinguishes summary and observation rows.

Collection begins in September 2026 and is not a multi-year announcement archive. One journal envelope is one captured observation, not automatically a new version. Semantic versions are deduplicated by SHA-256 over source,title,url,symbol,market_type,published,trading_at,status,summary,fingerprint; a content revision is an additional semantic hash for the same announcement identity. Ambiguous identities are quarantined and listing announcements do not guarantee liquidity or return.

How to read this page

• Can I obtain auditable listing and delisting events with the time CoinNudge actually observed them?
• Collection before CoinNudge's local start is not complete; announcement records do not prove trading liquidity, market impact or future return.
• Inspect the table before relying on the summary.
• JSON and CSV preserve the published evidence.

What can this page tell you quickly?

Question answered

Can I obtain auditable listing and delisting events with the time CoinNudge actually observed them?

Measured scope

Actual locally observed announcement history

Update schedule

Recalculated about every 1 hours from stored source observations.

Do not infer

Collection before CoinNudge's local start is not complete; announcement records do not prove trading liquidity, market impact or future return.

How is this different from the live events calendar?

The calendar filters verified events into the current and next seven days for planning. The dataset view focuses on stored historical records, normalized status, first local observation and revision semantics for research or audit.

The two may use the same upstream announcements but produce different units: one row is an upcoming event view; the other is an auditable historical record.

Why preserve announcement revisions?

An exchange can change a trading time, market type or status after the first notice. Overwriting the original makes a historical model appear to know the final answer earlier than it did.

CoinNudge retains first-observed evidence and content-linked archive envelopes. A buyer can distinguish the initially available record from a later update.

How are ambiguous tickers handled?

Ticker strings are not unique identities. Tokenized equities, ETFs, stable-value assets and duplicate tickers can contaminate a crypto study if a symbol alone is trusted.

The shared asset classifier and quarantine path exclude uncertain identity from the eligible universe. Exclusions and coverage gaps should accompany any delivered extract.

What identifies and versions one announcement?

The current-catalog primary identity is the source-qualified announcement ID; source_url links the notice, source_published_at is the publisher timestamp, first_observed is local discovery and last_verified_at is the latest verification. Event status and schedule-conflict fields describe the normalized operational state.

The append-only journal records capture envelopes. A semantic version is a unique SHA-256 over source, title, URL, symbol, market type, publication, trading time, status, summary and fingerprint for the same identity. Unchanged recaptures are counted as repeats, not content revisions.

How can I verify and cite this result?

Download the page JSON for the complete snapshot and CSV for tabular evidence. Record the API dataset key `listing-delisting-dataset`, the returned calculation_version, observation interval and named source alongside any quoted number. The visible table rounds values for readability; the downloads retain the published precision.

The stable URL remains unchanged when the data refreshes. A new calculation time does not prove every input changed, so compare source-observed timestamps and the stated actual locally observed announcement history. Missing rows remain missing rather than becoming zero or a favorable estimate.

What is measured, and what is not?

Method and data boundary

Aggregate current announcement IDs by source and status, then audit the append-only revision journal separately. Count observation envelopes, unique announcement identities, unique semantic content hashes, actual content revisions and repeat captures. A content revision means an additional SHA-256 over the published semantic fields for the same announcement identity; a repeated observation without a changed hash is not called a new version. Publish real recent records with source URL, publication, discovery, verification and status fields.

Collection before CoinNudge's local start is not complete; announcement records do not prove trading liquidity, market impact or future return.

Read the complete CoinNudge methodology

Sources and verification

• Binance announcementsListing and delisting source notices.
• MEXC announcementsListing source notices.
• CoinNudge data samplePublished event field and timestamp examples.
• CoinNudge methodologyAsset classification, quarantine and revision rules.

Frequently asked questions