Explore Hub: Futures And Leverage

Binance Futures published a June 25 notice saying IPUSDT and IPUSDC perpetual contracts will be automatically settled and removed on June 28, 2026 at 09:00 UTC.

What Happened

The official notice says the delisting supports the Story (IP) rebranding plan to Data Network. It states new non-reduce-only orders stop at 2026-06-28 08:30 UTC and that a separate announcement will cover the new contract listing.

The article uses the official or strongest available source as the decision anchor and keeps the explicit dates aligned with that source. The dates below are UTC where a time is stated.

Why It Matters

This is a live derivative deadline. Positions, hedges, bots, copy strategies, funding expectations, and settlement assumptions need explicit review before automatic settlement. A ticker migration does not preserve every existing contract route.

This is an execution and risk-control update, not a prediction. The clean decision is whether positions, bots, transfers, claims, routes, or dapp interactions need a verified change before a deadline or protocol state changes.

Separate three records before action: the source timestamp, the event timestamp, and the account or protocol state observed in the live interface. When those records disagree, the article should trigger a manual review rather than a forced trade, transfer, bridge, claim, or contract interaction.

What To Watch Next

Close or reduce positions deliberately, cancel automation, reconcile hedges across venues, export records, and watch for the separate DATA contract announcement. Keep the June 28 08:30 and 09:00 UTC cutoffs distinct.

Recheck the official page before acting, store the retrieval time, and preserve the no-action branch when the live interface does not match the announcement.

For exchange events, verify every subaccount, bot, conditional order, and API route separately. For protocol events, verify the official domain, contract or documentation path, governance status, and user-facing app state before relying on third-party summaries.

Archive the final decision with UTC time.

Sources

Continue this cluster

Continue with related checks from the same cluster so the follow-up decision stays narrow and auditable.