Binance said it will carry out wallet maintenance for the TRON (TRX) network on July 23, with deposits and withdrawals on the network set to pause shortly before the work begins. According to the exchange’s notice, the maintenance is scheduled for 06:00 UTC on July 23, or 14:00 Beijing time. To support the process, Binance will suspend deposits and withdrawals for the TRON network at 05:55 UTC, equivalent to 13:55 Beijing time.
The exchange said the maintenance is expected to last about one hour. Deposit and withdrawal services will resume once the network is stable, and Binance said it will not issue a separate announcement when that happens. The notice also said spot trading for tokens on the TRON network will remain available during the maintenance window.
Binance added that all technical handling related to the wallet maintenance will be managed by the platform, and users do not need to take any action.
Binance said it will conduct wallet maintenance for the TRON (TRX) network at 06:00 UTC on July 23, which is 14:00 Beijing time.
To support the maintenance, deposits and withdrawals on the TRON network will be suspended starting at 05:55 UTC on July 23, or 13:55 Beijing time. The work is expected to take about one hour. Binance said services will resume after the network is stable, with no separate announcement planned.
The exchange also said the maintenance will not affect spot trading for tokens on the TRON network. All technical processing will be handled by the platform, and users do not need to take any action.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
