A 5 November constitutional proposal authored by Binance requests release of 8,425.997 ETH and 74,559,805.2 ARB on Arbitrum One. These are the proposer’s amounts, not balances independently measured by NetNapz. Approval and execution remain unverified.

The freeze and the release are different actions

Arbitrum’s Security Council notice reports a freeze at 08:08 Hong Kong time on 30 October, equivalent to 00:08 UTC that day. It says an emergency Inbox upgrade moved the assets to a designated holding address before restoring the original implementation. The notice rounds the ETH amount to 8,425; it gives the same ARB quantity as the later proposal.

The proposal describes the freeze as occurring on 29 October, while the Council notice supplies the explicit 30 October Hong Kong timestamp. This report retains that source distinction rather than silently treating the dates as identical. The Council says a DAO governance vote is required to move the funds again.

What the new request would authorize

The requested release would use a temporary Inbox function, transfer the immobilized assets and remove the function. The proposal envisages forum discussion, a Snapshot temperature check and the constitutional onchain process. Its roughly 49-day estimate is conditional, not a confirmed payout date.

Binance proposes restrictions where legal process blocks transfer and says returned assets may replenish reserves used to cover customer losses. Those are proposed terms and issuer representations; they do not establish that reimbursement has occurred.

NetNapz assessment: follow the authority and the delivery

Assessment: containment can prevent an identified balance from moving without resolving who should receive it or when. A release proposal adds a decision for tokenholders, but readers still need evidence of each subsequent stage: the ballot, its outcome, the executable payload and actual delivery. Supportive forum replies are not a substitute for a completed governance decision.

Recovery to an exchange and reimbursement of its customers also require separate confirmation. A transfer to a recovery address would demonstrate one movement of assets; it would not, on its own, verify the exchange’s internal customer accounting. Likewise, an estimated process duration should not be converted into a calendar promise before its prerequisites are met.

The relevant follow-up is a documented change in governance or execution status. This report makes no inference about ARB or ETH demand, current dollar values, exchange solvency or a predictable market-price response.

Sources and verification limits

Checked 7 November: the linked Binance-authored proposal, Arbitrum’s Security Council announcement and the featured-logo usage page. Both incident records are first-party accounts, not independent forensic audits. Linked Etherscan and Arbiscan pages returned access errors, so NetNapz did not independently verify the transaction, current balances, asset ownership, legal claims, vote outcome or reimbursement. No wallet was connected and no trading application was opened.