Bitfinex users holding 13 recently delisted cryptocurrencies must withdraw their assets by 10 a.m. UTC on Aug. 31 or become dependent on a restricted, fee-bearing recovery process.
Following the deadline, the crypto exchange will disable standard withdrawals for the affected tokens. Any subsequent retrieval attempts will be handled entirely at Bitfinex’s discretion during a two-month window.
The exchange noted that this manual recovery is not guaranteed to succeed, incurs additional fees deducted from the recovered amount, and lacks a fixed completion timeline.
Affected assets and platform exceptions
The withdrawal mandate applies to Cosmos (ATOM), Bit2Me (B2M), Bitget Token (BGB), EigenLayer ($EIGEN), Vaulta (A), GateToken (GT), Jupiter (JUP), Kava (KAVA), Lido ($LDO), $NEO, Nexo (NEXO), OMNI and Ultra (UOS). Bitfinex's instructions also explicitly require users to clear any NEOGAS balances.
Notably, some of these assets are the native token for major crypto ecosystems. For context, $LDO is the native token of Lido, Ethereum's dominant liquid staking platform, while $EIGEN is the token for the Ethereum restaking platform EigenLayer.

Customers should note that some assets might appear under alternative interface or API codes on the platform, such as ATO for Cosmos or EOS for Vaulta. Tether ($USDT) on Cosmos and Unus Sed LEO on Vaulta remain unaffected by this action.
To execute a normal transfer before the cutoff, users face a $5-equivalent minimum and varying asset-specific network fees, which could make moving smaller balances uneconomical.
A separate liquidation protocol applies to remaining Japanese yen (JPY) and JPY-PERP balances. Bitfinex will automatically convert any lingering JPY to $USDT outside the public order book.
The exchange retains the right to execute this conversion at an undisclosed time and prevailing market rate, while automatically deducting a 5% fee from the user's funds.
Bitfinex previously halted deposits and trading for the impacted digital assets in July, following an initial market notice issued on June 23.