Recherche vérifiée par sources: Crypto SPOT Listing Timeline

Verified source facts

1. Venue listing announcements can separate wallet and market milestones rather than opening every function simultaneously. 2. OKX's VVV notice publishes deposits, pre-open, trading and withdrawals as four distinct UTC events. 3. The notice applies index-based price limits during pre-open and continuous trading. 4. Official announcement indexes are discovery surfaces; live authenticated controls remain necessary for execution.

Comparison at a glance

1. Control test: Announcement

A trading-control disclosure is meaningful only when converted into a testable rule. For announcement, inspect official publication. Use a sandbox, non-production context, or the smallest reversible test available, then capture timestamp. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, page mutation is therefore an explicit audit gap.

The announcement row should end with a concrete monitoring rule tied to official publication. Make the operator capture timestamp, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; page mutation remains a separate production risk until observed.

2. Control test: Token identity

For token identity, inspect name and contract. Use a sandbox, non-production context, or the smallest reversible test available, then match chain.

In this dimension, lookalike is therefore an explicit audit gap.

The token identity row should end with a concrete monitoring rule tied to name and contract. Make the operator match chain, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; lookalike remains a separate production risk until observed.

3. Control test: Deposit

For deposit, inspect opening and crediting. Use a sandbox, non-production context, or the smallest reversible test available, then verify wallet.

In this dimension, delay is therefore an explicit audit gap.

The deposit row should end with a concrete monitoring rule tied to opening and crediting. Make the operator verify wallet, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; delay remains a separate production risk until observed.

4. Control test: Pre-open

For pre-open, inspect auction or order collection. Use a sandbox, non-production context, or the smallest reversible test available, then read rules.

In this dimension, false liquidity is therefore an explicit audit gap.

The pre-open row should end with a concrete monitoring rule tied to auction or order collection. Make the operator read rules, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; false liquidity remains a separate production risk until observed.

5. Control test: Trading

For trading, inspect continuous-market start. Use a sandbox, non-production context, or the smallest reversible test available, then confirm status.

The trading row should end with a concrete monitoring rule tied to continuous-market start. Make the operator confirm status, retain the venue response, and assign an owner for exceptions.

6. Control test: Withdrawal

For withdrawal, inspect network release time. Use a sandbox, non-production context, or the smallest reversible test available, then test small amount.

In this dimension, maintenance is therefore an explicit audit gap.

The withdrawal row should end with a concrete monitoring rule tied to network release time. Make the operator test small amount, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; maintenance remains a separate production risk until observed.

7. Control test: Price controls

For price controls, inspect limit methodology. Use a sandbox, non-production context, or the smallest reversible test available, then inspect bounds.

In this dimension, rejection is therefore an explicit audit gap.

The price controls row should end with a concrete monitoring rule tied to limit methodology. Make the operator inspect bounds, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; rejection remains a separate production risk until observed.

8. Control test: Eligibility

For eligibility, inspect region and account. Use a sandbox, non-production context, or the smallest reversible test available, then check in app.

In this dimension, restriction is therefore an explicit audit gap.

The eligibility row should end with a concrete monitoring rule tied to region and account. Make the operator check in app, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; restriction remains a separate production risk until observed.

9. Control test: Live status

For live status, inspect operational surface. Use a sandbox, non-production context, or the smallest reversible test available, then recheck before action.

In this dimension, stale notice is therefore an explicit audit gap.

The live status row should end with a concrete monitoring rule tied to operational surface. Make the operator recheck before action, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; stale notice remains a separate production risk until observed.

10. Control test: Stop rule

For stop rule, inspect missing identity or route. Use a sandbox, non-production context, or the smallest reversible test available, then do not act.

In this dimension, support evidence is therefore an explicit audit gap.

The stop rule row should end with a concrete monitoring rule tied to missing identity or route. Make the operator do not act, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; support evidence remains a separate production risk until observed.

Decision scenarios

Scenario 1: when announcement becomes decisive

Consider a reader whose main constraint is official publication. The correct response is not to infer a universal platform or product winner. It is to capture timestamp, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when token identity becomes decisive

Consider a reader whose main constraint is name and contract. It is to match chain, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when deposit becomes decisive

Consider a reader whose main constraint is opening and crediting. It is to verify wallet, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when pre-open becomes decisive

Consider a reader whose main constraint is auction or order collection. It is to read rules, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when trading becomes decisive

Consider a reader whose main constraint is continuous-market start. It is to confirm status, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when withdrawal becomes decisive

Consider a reader whose main constraint is network release time. It is to test small amount, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• VVV/USDT spot listing — OKX Europe
• Announcements — OKX
• New cryptocurrency listings — Binance Support