The primary keyword for this update is WAVES 1.6.4 transfer pause. Bybit announced on September 13, 2026 that it would support the WAVES 1.6.4 network upgrade, expected around 21:40 UTC at block height 5,400,000. Deposits and withdrawals were scheduled to pause from 21:00 UTC, while trading remained available and Bybit directed users to set a resumption alert.
What Happened
Bybit announced on September 13, 2026 that it would support the WAVES 1.6.4 network upgrade, expected around 21:40 UTC at block height 5,400,000. Deposits and withdrawals were scheduled to pause from 21:00 UTC, while trading remained available and Bybit directed users to set a resumption alert.
The event date comes from the cited announcement or release note. This page was checked against the sources on September 15, 2026 UTC before publishing.
Why It Matters
For CryptoSigy, the event is a route-control problem rather than a price signal. The Waves release notes describe an activation-height change, so a transfer plan must reconcile the node version, block height, exchange status and a small post-upgrade test transfer before moving size.
The owner fit controls the framing. Exchange events stay on CryptoSigy as route, fee, futures or trading-risk context; protocol events stay on Radar when the useful question is node, governance, chain or ecosystem operations.
What To Watch Next
Watch the activation height, node and exchange status, transfer confirmations, and any post-upgrade change to supported routes or wallet maintenance.
If the official source changes a deadline, block height, contract specification or transfer status, rebuild the decision from the updated source rather than from a stale headline.
The editorial filter is network upgrade, transfer pause, chain-height coordination and exchange-route risk.. Treat this as decision context, not as a prediction, recommendation or promotional note.
Date discipline matters: published and updated timestamps are generated at publish time in UTC, while event dates in the body come from the cited source.
Risk reminder: betting and crypto decisions can cause financial loss. Use official sources, keep stakes or position sizes controlled, and avoid treating one update as a complete strategy.
Before acting on the update, compare the official notice with the live product, market or protocol surface. If contract specs, fee terms, route availability, lineup status or governance details differ, the live source should override the older assumption.
The practical output is a watchlist, not a verdict. Readers should know which timestamp, rule, venue field or protocol dependency must be checked next before the update has any operational value.
Continue this cluster
Continue this cluster with related source-backed updates in the same owner lane.