Explore Hub: Futures and Leverage

KuCoin said it would adjust funding-fee settlement times for ten USDT perpetual contracts at 08:00 UTC on May 22, making the update a timing and journal-risk check rather than a new listing.

This article keeps the scope narrow on purpose. The event is fresh enough to matter today, but the useful reader action is not to chase the headline. It is to separate the official change from the route, liquidity, timing or protocol surface that can affect execution after the announcement is already visible.

What Happened

The affected contracts are COHRUSDT, CSCOUSDT, DISUSDT, GLWUSDT, HDUSDT, MRVLUSDT, RKLBUSDT, SOXLUSDT, UBERUSDT and WDCUSDT. KuCoin said the interval remains every eight hours, while settlement times move from 04:00, 12:00 and 20:00 UTC to 00:00, 08:00 and 16:00 UTC.

Because the interval is unchanged, the practical change is when funding hits the account and how bots, reports and risk controls align with the new timestamps. The announcement keeps this inside futures operations, not spot liquidity.

Why It Matters

For CryptoSigy, funding-time changes can alter the execution surface even when the stated interval is unchanged. A strategy that assumes a 12:00 UTC funding debit can misread PnL, liquidation buffer or carry cost after the clock moves.

The affected list is also equity-linked and sector-mixed, so traders should not treat all contracts as having the same liquidity profile. A settlement clock change on a thin synthetic route can be more disruptive than on a deeper crypto-native perp.

The owner-fit angle is signal context: update bot schedules, funding snapshots, journals and margin checks before comparing new signals against old funding windows.

The practical test is whether the update changes a decision that has to be made now: deposit path, funding timestamp, bot schedule, first-session spread, protocol integration or user-facing risk. If it only repeats an existing announcement with no new decision point, it belongs in the rejected pile, not in a separate article.

What To Watch Next

Watch whether funding history, API timestamps and account statements reflect the new 00:00, 08:00 and 16:00 UTC cadence cleanly after the first cycle.

If a bot relies on fixed settlement-time assumptions, pause or reduce size until the logs confirm the new schedule. The risk is not the announcement itself; it is stale automation.

Continue this cluster

Continue this cluster with May 22 exchange-route updates focused on funding-time changes, synthetic perps and listing liquidity checks.