On November 5, Binance formally requested that Arbitrum's decentralized autonomous organization release approximately 8,425.997 ETH and 74,560,000 ARB tokens currently frozen following a hot-wallet exploit, initiating a governance procedure the exchange anticipates will require seven weeks or more to complete. This specific appeal for asset recovery does not involve a request for a new allocation from the DAO treasury.
The release of these funds is contingent upon approval by ARB token holders and delegates through Arbitrum's established constitutional governance framework. Concurrently, Binance has removed API keys linked to SignalPlus after a third-party platform identified a potential security vulnerability, while plans are in place to progressively reopen additional asset withdrawals once necessary security and readiness checks are finalized.
Governance Process Initiated for Frozen Asset Release
Through its Binance_Post_Listing forum account, Binance put forward a proposal asking tokenholders to permit the return of assets currently stuck on Arbitrum One. These funds sit at an intermediary frozen address, while the process moves toward further forum discussion, a Snapshot temperature check, and a binding onchain vote that remains incomplete.
The exchange declared it would make up for affected users' losses using its Secure Asset Fund for Users, known as SAFU, along with company treasury holdings. Recovered assets might cover incident-related expenses and replenish reserves previously spent to compensate customers. Arbitrum's Security Council announced that it froze the assets at 8:08 a.m. Hong Kong time on Oct. 30, which corresponds to the evening of Oct. 29 in the United States.
Arbitrum's Security Council announced the freezing of assets at 8:08 a.m. Hong Kong time on Oct. 30, which marked the evening of Oct. 29 in the United States. The council implemented a temporary upgrade to Arbitrum's Inbox contract on Ethereum, allowing transactions to shift funds from an address linked to the exploit into the frozen location before reverting the contract to its original state. This technical measure ensured that no other users' funds or applications were impacted by the intervention.
Binance plans a recovery process mirroring a prior technical sequence: an approved transaction will temporarily upgrade the Inbox contract, move the immobilized balances to Binance's designated recovery address, and then eliminate the temporary function. This request pertains to assets already locked on the network, with Binance anticipating no direct DAO budget expenditure aside from standard governance execution costs.
Binance projects that the combined phases of deliberation, voting, and implementation will span about 49 days, though delays remain possible. The timeline breaks down into a week for community forum talks, a subsequent week dedicated to assessing sentiment, followed by a two-week period for the onchain ballot. Once ratified, the team estimates an additional 18 days before the final transaction moves the recovered funds back to their original holders.
Under Arbitrum's governing rules, submitting an onchain initiative demands a minimum of 1 million delegated ARB tokens. A mandatory three-day pause occurs before the ballot opens; standard voting runs for 14 days but may lengthen if quorum is not met promptly. To pass, a proposal needs more affirmative votes than negative ones while satisfying participation thresholds that include both backing and abstentions. Constitutional amendments specifically require support from half of all delegated votable tokens, bounded by a floor of 150 million ARB and a ceiling of 450 million.
To be deemed successful, proposals must additionally navigate waiting periods on both Arbitrum and Ethereum, ensuring message finalization occurs through the rollup's challenge period situated between them. The draft would stop onchain submission and delivery as long as a restraining notice, writ, court order, or other legal process that blocks the transfer stays in effect, unless a competent court allows those actions.
Binance has also agreed to maintain delivered assets separately at the recovery address for the duration of any unresolved legal process and to cover all costs associated with defending competing claims. Prior to onchain submission, the exchange is required to sign indemnification agreements that cover the Arbitrum Foundation, Offchain Labs, and members of the Security Council.
Under agreements subject to New York law and jurisdiction in New York County state and federal courts, Binance's eighth recovery update set additional withdrawals to resume at 04:00 UTC on Nov. 5. These terms manage potential liabilities connected to the initial freeze as well as the planned release.
Technical Sequence and Legal Safeguards for Recovery
Deposits stay open while Binance indicated that access would gradually return for specific assets across Ethereum, BSC, Base, Tron, Polygon and Sui once each network combination cleared security checks. The platform ranked tokens according to demand seen during the last week and cautioned that high traffic might lead to short-term delays.
In a separate announcement released on Nov. 5, Binance stated that it removed all API keys associated with SignalPlus following reports of a potential security issue from the third-party platform, while confirming that its own systems remained unaffected and user funds stayed safe; the exchange advised SignalPlus users to review their positions and open orders directly through Binance, wait for confirmation of resolution before reconnecting API keys, and enable IP whitelisting.