Altcoins
Bithumb schedules XPLA deposits and withdrawals to resume on November 9
The South Korean exchange announced an 11:50 a.m. reopening in Seoul after suspending transfers for a CONX network upgrade. Deposits made during the interruption are to be processed gradually.

Reopening announced for 11:50 a.m. in Seoul
Bithumb updated its XPLA notice on November 9 at 11:10 a.m. Seoul time. The exchange said deposits and withdrawals on the CONX network were due to resume at 11:50 a.m., or 2:50 a.m. UTC and 3:50 a.m. in Paris. The initial notice had scheduled their suspension for noon South Korean time on Saturday, November 7, to accommodate a network upgrade. The new time comes from Bithumb's published schedule. The notice provides no independent measurement of the actual return of operations.
The update concerns transfers of XPLA between the exchange and the CONX network. Confirmation on the chain and the credit to a Bithumb account are two distinct steps. A transaction can be recorded in a block while the balance displayed by the exchange is still awaiting deposit processing. Bithumb says deposits received during the interruption are to be credited gradually after reopening and does not specify when the last outstanding deposit will be processed.
Work on the exchange's nodes
In its initial notice, Bithumb said it needed to upgrade its own nodes to remain compatible with the chain. The exchange then estimated that the network upgrade would take place at about 4 p.m. Seoul time on November 7, four hours after the scheduled start of the suspension. It made reopening conditional on network stability and warned that the pace of block production could affect the schedule. The time announced for Bithumb's service is therefore separate from when the network applies its new rules.
The text of CONX governance proposal No. 135, which Bithumb references through the Mintscan explorer, targets block 22,123,850. It describes release candidate 1.15.0-rc1, with fixes for Cosmos-EVM and for the ICS20 component that lets Ethereum-compatible applications use certain cross-chain transfer functions. The text says version 1.15.0 will be published after the patch code is disclosed. It does not detail the vulnerabilities involved.
Handling transactions that remained pending
For withdrawals requested before the suspension but still incomplete when it began, Bithumb plans to check them in its systems and then process them gradually. The exchange also warns that a transfer started before the interruption may arrive too late to be credited immediately, depending on network congestion and confirmation times. This explains why the reopening time may precede the appearance of a particular transaction in the account history.
The delay concerns the handoff between the blockchain and the exchange's internal ledger. A transaction already visible on the chain may therefore remain pending at Bithumb. The November 9 notice sets a time for transfers to resume, without giving the volume of pending transactions or a processing time for each transaction.
