Bybit Delists YALAUSDT Perpetual And Pauses Story (IP) Transfers For v1.5.2 Upgrade

Bybit publishes two separate operational notices that matter for derivatives traders and anyone using exchange rails for the Story (IP) network.

• YALAUSDT perpetual delisting: Bybit says it will remove the YALAUSDT perpetual contract on February 7, 2026 at 9:00AM (UTC), per the exchange announcement titled “Delisting of YALAUSDT Perpetual Contract”.
• Story (IP) transfer pause: Bybit says it will suspend deposits and withdrawals via Story (IP) starting February 5, 2026 at 04:00PM (UTC) to support a v1.5.2 network upgrade, which it expects around ~05:00PM (UTC) in the maintenance note “Bybit to Support Story (IP) v1.5.2 Network Upgrade”.

Both items are “exchange-channel” notices. They can move liquidity and settlement behavior even if the broader market stays quiet.

YALAUSDT Perpetual Delisting And What Traders Should Expect

A perpetual delisting is not a routine parameter tweak. It is a hard stop for a specific contract, and it compresses decision-making into a narrow window.

In practice, a delisting event typically affects three things:

• Position lifecycle: Open positions must be closed or settled under the delisting procedure the venue applies.
• Order book continuity: Pending orders and conditional orders linked to the contract usually stop functioning once the venue disables trading.
• Price formation: Liquidity often thins before cutoff. Spreads can widen, and liquidation cascades can occur if market makers step back.

Bybit’s notice sets the core timing, but traders still need the fine print. Before the cutoff, users can check the delisting notice for the operational rules that matter most, including whether positions are auto-settled or must be manually closed, the final settlement reference (mark or index), and whether any last-minute restrictions apply.

Why Delistings Create Fast Liquidity Migration

Perpetual markets rely on continuous two-sided quoting. When a venue removes a contract, the remaining liquidity often migrates to other derivatives venues that still list the pair, or to substitute exposure via related instruments.

That migration can create short-lived dislocations:

• Funding can become noisy.
• Basis can move unpredictably.
• Forced position reductions can amplify volatility.

Even when a token has other listings, a delisted perp can become “one-way” quickly as traders rush to flatten risk.

Bybit’s Story (IP) Deposit And Withdrawal Pause For v1.5.2

Bybit’s Story (IP) notice describes a standard exchange posture during network upgrades: temporarily halt transfers to avoid inconsistent accounting while the chain transitions.

The exchange schedule matters because it controls the rails:

• A user can still trade internal balances while deposits and withdrawals are paused.
• A user cannot rely on on-chain settlement into or out of the venue during the pause window.

Bybit sets the pause start at February 5, 2026 04:00PM (UTC) and frames the network upgrade as occurring around ~05:00PM (UTC) in its Story (IP) v1.5.2 support note.

How This Relates To The Underlying Protocol Upgrade

Story v1.5.2 is described publicly as a mandatory hardfork upgrade of the Story consensus client, with the upgrade tied to a specific on-chain height. A release summary for Horace (Story v1.5.2) references a Story Mainnet hardfork at height 13,780,500, and links to the relevant explorer and governance references.

Some public calendars also publish an approximate time for that height. For example, a network-upgrade listing states that Story’s upgrade occurs at block height 13,780,500, approximately 13:00:00 (UTC) on February 6, 2026, and links back to a GitHub source in its entry for Story(IP) Network Upgrade.

That mismatch in timestamps is not unusual. Exchanges often choose conservative buffers, and third-party calendars can lag edits. The most reliable verification is watching the chain reach the published height on an explorer link referenced from the release notes.

Why Exchanges Pause Transfers During Hard Forks

During a hard fork or major network upgrade, exchanges face a simple risk: deposits credited on an old chain view can become invalid after the network transitions, and withdrawals can fail or route into unstable conditions.

Bybit’s help documentation describes wallet maintenance and network upgrades as common reasons that withdrawals become temporarily unavailable, reflecting the operational goal of preventing inconsistencies and errors during protocol changes in articles like “How to Set Alerts for Deposit/Withdrawal Suspension Due to Wallet Maintenance”.

Practical Risk Management For Traders And Operators

These two notices hit different risk surfaces, but the mitigation mindset is the same: remove time pressure.

• Close or reduce YALAUSDT exposure early: Closing positions before the delisting window reduces dependency on the venue’s final settlement mechanics and avoids last-minute liquidity gaps.
• Review conditional orders and bots: Automated strategies can fail silently when tickers disappear or when an instrument stops accepting orders. Bots should validate symbol availability and risk limits ahead of February 7, 2026 9:00AM (UTC).
• Avoid “in-flight” Story (IP) transfers near the pause: Deposits sent close to the pause start can arrive late or sit uncredited until the venue resumes. Withdrawals initiated close to the cutoff can fail or remain pending.
• Plan settlement windows: Anyone doing arbitrage, hedging, or cross-venue rebalancing should treat the pause as a temporary loss of routing and custody flexibility.

What To Watch During The Cutover Windows

For YALAUSDT, the most important signals are contract availability and the venue’s settlement handling as the cutoff approaches. If the contract remains tradable up to the deadline, liquidity conditions and spreads provide a real-time indicator of how crowded the exit is.

For Story (IP), the meaningful verification is whether the chain reaches the expected upgrade height and stays stable afterward. The Story v1.5.2 release summary points to the upgrade height and relevant references, while Bybit’s notice sets the operational pause window that controls exchange rails.

Conclusion

Bybit’s YALAUSDT perpetual delisting on February 7, 2026 9:00AM (UTC) and its Story (IP) transfer pause starting February 5, 2026 04:00PM (UTC) both compress risk into tight operational windows. Traders and operators who reduce exposure early, avoid last-minute transfers, and monitor chain-level upgrade progress can materially lower settlement and liquidation surprises.

The post Bybit Delists YALAUSDT Perpetual And Pauses Story (IP) Transfers For v1.5.2 Upgrade appeared first on Crypto Adventure.