![]()
Bithumb suspended deposits and withdrawals of the CYBER token after flagging indicators of a potential safety challenge. The change stated clients might nonetheless commerce CYBER already held of their accounts. Kraken individually warned of potential delays for CYBER deposits despatched over the Optimism community.
Bithumb set the cutoff for two:18 a.m. Korea time on Nov. 22, or 17:18 UTC on Nov. 21. Seven minutes after the scheduled cutoff, the change confirmed that the pause was in impact. It additionally urged clients to take care when buying and selling CYBER, saying the safety concern might result in sharper value swings.
Bithumb stated CYBER deposits acquired through the pause could be credited in sequence after service resumed.
The lanes present service standing based mostly on the dated change notices. Line lengths don’t symbolize the period of a pause or delay.
For customers who had already despatched CYBER to Bithumb, the cutoff mattered as a result of sending a deposit and seeing it credited to an account can occur at totally different occasions. Bithumb stated community congestion or sluggish confirmations might maintain up credit score even for transfers despatched earlier than the cutoff. It stated it will credit score deposits acquired through the suspension in sequence as soon as service resumed.
Prospects who had requested a withdrawal earlier than the cutoff and had been nonetheless ready for it to finish confronted a separate course of. Bithumb stated it will run system checks and course of these requests in sequence, which might delay the account replace. The change’s processing notice utilized to requests already in its system when the suspension took impact. New CYBER withdrawals remained topic to the pause.
Bithumb stated it will reopen transfers as soon as the community was secure and would put up the reopening in the identical discover. It gave no reopening time.
Kraken warns of Optimism deposit delays
Kraken flagged potential CYBER deposit delays on Optimism at 19:59 UTC on Nov. 21 and stated its different funding strategies had been working usually.
The incident web page nonetheless listed the problem as recognized at 18:12 UTC on Nov. 22, with no decision posted. Kraken’s replace left the trigger and timing of a repair open.