Binance hot-wallet exploit: return request covers 8,426 ETH and 74.6 million ARB

What changed on November 5

The new development is a formal request to return a defined pool of assets. Binance's proposal identifies the amounts, a recovery destination, the proposed use of the returned funds and the approvals needed before the transfer. It says the Security Council froze these assets on October 29 and moved them to an intermediate address on Arbitrum One. These are statements in the proposal; we have not independently reconstructed the transfers from chain records.

Odaily's report separately describes the assets as still held at the intermediate frozen address. It reports that the proposal needs forum discussion, a Snapshot temperature check and a binding on-chain vote. ChainCatcher also reports that the assets have not yet been returned, attributing its coverage to The Defiant. Read ChainCatcher's report.

This is a distinct recovery update to the incident. It gives users something specific to follow: the progress of this proposal and evidence of its eventual execution. It supplies no basis for treating a headline about “returning funds” as confirmation that the return has already happened.

Read the ETH and ARB balances separately

The precise request is for 8,425.997 ETH and 74,559,805.2 ARB. Rounded to make the headline readable, those are about 8,426 ETH and 74.6 million ARB. They are amounts of two different assets. Adding their token counts would produce a number with no useful financial meaning.

The proposal concerns the full frozen balance described in its specifications. It does not ask ArbitrumDAO to create a new compensation allocation from the DAO treasury. That distinction matters when reading claims about who would fund the recovery: the stated action is to release identified assets already immobilized on Arbitrum One. Source: proposal specifications and overall cost.

Odaily gives dollar estimates using November 5 CoinGecko prices. Those valuations describe the report's price basis, rather than a fixed amount that every customer can claim. We keep the token quantities at the centre of this analysis because the proposed transfer is specified in ETH and ARB. No live dollar quote or current exchange price is established here.

Nor does this request measure the total incident loss or all funds recovered elsewhere. A reader comparing recovery headlines should keep the scope attached to every number: these particular ETH and ARB balances, on this network, subject to this proposal.

Why around 49 days is an estimate

Binance's proposed timeline allows one week for forum discussion, one week for the temperature-check vote, two weeks for the on-chain vote and around 18 days after that vote concludes for the final transaction payload to execute. The proposal describes the full process as around 49 days and elsewhere says approximately seven weeks or longer.

Those intervals describe an anticipated governance path. They do not establish an approved vote schedule, a confirmed execution date or a customer-payment deadline. Starting a personal countdown from a news report would give the estimate more certainty than its author gives it. Source: proposal timeline.

The text also names conditions that can change the sequence. Before on-chain submission, Binance must complete the specified updates and enter into indemnification agreements. Legal process restricting the assets can prevent submission or delivery unless the relevant restriction is changed or lifted as described in the proposal.

For a user, this means a quiet period between milestones need not supply evidence about their individual withdrawal. Follow the dated proposal updates for the recovery process, and follow account records for the transfer you actually initiated. The two records answer different questions.

Who would receive the recovered assets

The proposed destination is a Binance recovery address. The draft says returned assets would be applied to losses and costs arising from the incident, including replenishing SAFU Fund or treasury reserves already used for that purpose. Binance states that it is committed to covering affected users' losses through SAFU and its treasury.

That is the company's stated commitment and proposed accounting treatment. The source does not show that every affected person has already received a payment. It also does not describe an open public claim in which readers send tokens to an address to become eligible. Source: proposal use-of-funds section.

Three events therefore need separate evidence: a DAO decision authorizing release, execution of the transfer to the recovery destination, and any change to a particular customer's balance or claim. A report about one stage cannot confirm the next. An approved vote, if one occurs, would still need to be read alongside execution information before calling the assets returned.

When checking a personal case, retain the original transaction reference and the platform's response. Ask support about that transaction and its status. The proposal's aggregate ETH and ARB balances cannot identify your deposit, establish your entitlement or tell you which support action applies to your account.

What the legal conditions change

The draft explicitly addresses third-party claims to immobilized assets. It says the proposal will not be submitted on-chain, and delivery will not occur, while a restraining notice, order or other legal process prohibiting transfer remains in effect, unless a competent court modifies or vacates it to permit the relevant action.

This clause makes the timeline conditional. The proposal also describes obligations around holding delivered assets at the recovery address and responding to claims. Our reading is that a technical ability to move the tokens would not, by itself, settle every condition described in the draft. This is an interpretation of the proposal's stated sequence, rather than a finding about an existing court order.

We have not verified a current legal restriction on these specific assets. Readers should therefore avoid both assumptions: that litigation has already blocked the request, or that legal questions have already been cleared. A later update would need to identify the actual restriction or its resolution before either becomes a supported claim. Source: third-party claims and legal process.

If you have a pending ETH or ARB transfer

Open your existing account through the app or address you normally use. Locate the original deposit or withdrawal record. Save the asset name, selected network, amount, status and transaction reference if one is available. Record the time in SGT so a later support response can be compared with the same request.

If the sending service says a transfer is complete, compare its transaction reference with the receiving service's record. If it is still pending inside the sender, ask about that pending request before submitting a replacement. These are practical checks; this article has not verified current deposit or withdrawal availability for any individual account.

Avoid sending a second transfer simply to test whether the first has arrived. A duplicate send would create another transaction to reconcile. If you need help, use the support route inside your existing account and ask what evidence is needed for the original transfer. Keep the response attached to that record.

Treat unsolicited “Binance compensation” messages as a reason to stop and verify the contact. Do not disclose a recovery phrase or send an advance payment in response to a private message. The proposal describes a DAO-to-recovery-address process; it gives readers no instruction to pay a fee through a message to unlock compensation.

What evidence to watch next

The next useful development would identify a concrete stage: a published temperature-check vote, an on-chain proposal, a result, or an executed transfer. Check which stage an update actually documents and whether it refers to the same ETH and ARB balances. Retain the source date instead of treating a fresh repost as a new recovery event.

For trading decisions, this recovery request supplies no measured ETH or ARB price response. It also establishes no funding-rate change or liquidation total. Readers checking derivatives conditions can inspect the funding-rate board separately; the proposal itself cannot explain a market move without additional evidence.

Quick answers

Have the frozen assets already been returned?

The opened reports say they remain frozen. The proposal requests their release and describes the process required. It is not an execution receipt.

Is 49 days a promised reimbursement date?

No. It is the proposed governance estimate, subject to the steps and legal conditions in the draft. It does not set a payment date for an individual customer.

Is ArbitrumDAO being asked for a new treasury grant?

The draft requests no new treasury allocation. It concerns the release of the specified frozen ETH and ARB.

Does this prove my pending transfer is resolved?

Your own transaction record and the receiving account's status need to establish that. Save those records and ask support about the specific request rather than using the aggregate recovery balance as proof.