Binance Expands Post-Hack Withdrawals on Ethereum and Solana

Binance confirms Ethereum and Solana token access

The confirmation names Ethereum-network ENA, USDE, PENDLE, WLD, ONDO and LINK among the additional enabled assets. It also lists Solana-network USD1, PUMP, RENDER, RAY, TRUMP, JUP, BONK and WIF, alongside other tokens.

Ethereum-network RLUSD, USD1, TUSD, FDUSD and XUSD appear in its already-enabled group. These examples are selected from Binance’s published list, rather than an independent test of each withdrawal route.

The distinction is important for a token supported on several blockchains. An Ethereum withdrawal reopening does not establish that the same token can leave through another network. The operational unit is the combination of the asset and its selected chain.

The sixth recovery announcement scheduled the wider phase to begin at 04:00 UTC November 3. Binance said availability would be restored progressively after security and readiness checks, rather than switching on every listed asset simultaneously.

Its planned table spans nine networks: BSC, Ethereum, Solana, XRP Ledger, Sui, Arbitrum, Optimism, Tron and Base. Examples outside the confirmed Ethereum and Solana batches include XRP Ledger RLUSD, Sui USDC and HAEDAL, Optimism OP and WCT, and Base ZEN, MIRA, HOME and AWE.

Those entries identify intended coverage. They should not be read as independent confirmation that each route was operating at publication. Binance says it is prioritizing demand over the past week and adding assets as they become ready; deposits remain open.

The new confirmation is a practical change from the completed ten-token reserve proof reported Monday. That disclosure concerned verification of an October 31 balance snapshot. Tuesday’s development concerns customers’ ability to move additional assets out.

Binance hack losses remain at billions

The loss-impact review, checked at 11:08 UTC November 3, found observed theft and on-chain tracing evidence. Elliptic’s final incident assessment, updated November 1 at 08:00 UTC, estimates $6.43 billion stolen across eleven blockchains and $2.85 billion frozen or seized.

Elliptic identifies $3.80 billion taken on Ethereum across 186 tokens and 18,270 stolen bitcoin. The totals describe assets removed from exchange wallets, not a count of individually compromised customer accounts. The reviewed sources did not establish a verified unique customer-victim total.

TRM Labs’ earlier investigation put the theft at approximately $6.36 billion across ten chains, using observations through October 30 at 00:30 UTC. Differences in coverage and valuation mean the two estimates cannot be added together.

TRM described validly signed transfers across multiple networks and an Ethereum authorization that allowed attacker-controlled code to sweep a hot wallet. It also identified a second wave around 23:05 UTC October 29 affecting Avalanche and Polygon. That wave belongs to the original incident, rather than proving a new attack during Tuesday’s reopening.

A freeze restricts an attacker’s access but does not by itself mean funds have been returned to Binance. Similarly, company-funded replacement assets and assets recovered from the thief are different sources of backing. Withdrawal restoration should not be treated as proof that investigators have recovered the entire loss.

Binance reiterated in Tuesday’s notice that it would bear the financial impact of the stolen funds. That commitment is the company’s statement; the reviewed materials do not supply a new independently reconciled returned-funds total.

Withdrawal status still depends on each route

The first reopening phase began November 1. Binance’s earlier recovery notice included native bitcoin, Ethereum-network ETH, USDT and USDC, and Solana-network SOL, USDT and USDC. Tuesday therefore expands token access on networks already involved in the initial restoration.

The initial notice also said withdrawal wallets would use newly generated addresses added to the reserve list. That change concerned Binance’s processing infrastructure; it did not make every supported token immediately available. The staged return separates network readiness from the remaining asset checks.

The earlier surge in customer withdrawals showed why access and balance verification answer different questions. A reserve snapshot records a particular point in time, while a transfer requires the relevant route to operate when the customer requests it.

Binance directs customers to the withdrawal page for the chosen asset and chain or its network-status page. It warns that high traffic can cause delays and advises trying again later when a withdrawal is unsuccessful. Daily Crypto Briefs did not conduct authenticated customer withdrawals to test the announced access.

Broader sentiment remained cautious: Alternative.me’s Fear and Greed Index showed 26, or Fear, on November 3, compared with 37 the previous day. The gauge measures market sentiment, not the security of Binance’s infrastructure or the availability of any specific token.

Further official confirmations for the remaining token-network pairs, a reconciled recovery total and a completed technical account of the breach remain the developments to watch. The reviewed reopening notice does not set a completion time for every outstanding route.