Binance reports 90% backfilled: what should holders of the remaining tokens check?

Read the remaining gap by token

Odaily reports that Binance identifies BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC as fully reserve-backed. It attributes the remaining gap to other tokens whose lower liquidity may make completing purchases take longer. Keep that explanation attached to Binance: the report does not include an independently reconstructed inventory of the purchases or the outstanding tokens.

That changes the question for someone holding an asset outside the named group. An overall improvement does not identify which smaller-token balances are covered, what remains to buy for each asset, or the order in which those purchases might finish. A reader should look for a later update naming their token rather than applying the ten-token statement to everything in the account.

The same care applies inside the named group. “Full reserve backing” is the claim being reported. It does not, by itself, establish that a particular user's balance is included in a published proof or that their chosen withdrawal network is operating. Token coverage and transaction processing are different checks, even when the exchange reports progress on both.

For your own records, write down the exact asset ticker beside the account balance you are checking. Add the network only if you have a pending transfer, and copy it from that transfer's record. A familiar token name in a headline cannot resolve a network mismatch in an actual withdrawal request.

A ten-percentage-point change needs a stable definition

The move from about 80% to about 90% is a change of about ten percentage points. That arithmetic uses the two percentages reported in the update. It supplies no dollar value for what was added. Multiplying an earlier headline loss estimate by that change would require evidence that the estimates use the same asset perimeter, valuation time and definition of “affected.” The reports opened for this story do not provide that reconciliation.

Read “about” as part of the figure. The source does not present the percentage as a precise audit result with a line for every liability and asset. A rounded progress figure can help identify the direction of a company's reported work while leaving the composition of the balance unresolved.

Nor does the remaining 10% mean every customer has a 10% shortfall. The report describes an aggregate group of assets. It does not allocate that gap among customer accounts. A statement about the pool cannot establish the treatment of any one account without the corresponding account and asset records.

This is why the asset list carries more practical information than a simple subtraction. If your token is named, you have a specific company claim to compare with the next proof. If it is absent, the next useful disclosure is a token-level statement. Neither case supports inventing a recovery percentage for your personal balance.

Replenishment and recovery describe different movements

PANews also reports the 90% figure and the list of ten fully backed assets. Its account attributes the replenishment funding to part of the SAFU fund, part of the futures insurance fund and Binance's own corporate funds. These are reported sources of replacement funding. They do not establish that the same assets involved in the suspected outflow have returned. PANews' report.

For readers following the broader incident, that distinction prevents double counting. An issuer freeze, an investigator following a wallet, a company buying replacement tokens and a customer receiving a completed withdrawal describe different events. Adding their headline values together would not create a meaningful recovered-funds total.

Our reading of the update is therefore narrow: Binance is reporting progress in restoring asset backing. The funding description suggests that replacement resources form part of that work. A claim that investigators recovered 90% of the outflow would go beyond the reports, which discuss replenishment and purchases.

The funding account also leaves questions a later reconciliation could answer. How much came from each named source? Which assets were purchased? What amounts were acquired and at what valuation? The reports do not supply that breakdown. Those missing details matter if a reader wants to compare reserve restoration with the separate investigation, rather than simply track the company's stated percentage.

The snapshot and the complete proof have different dates

Both reports describe a new reserve snapshot taken at 08:00 SGT on October 31, equivalent to 00:00 UTC. PANews says the complete proof is expected on November 3 UTC. That is a schedule attributed to the company, not evidence that the proof has already been generated and made available to customers.

A snapshot selects a measurement time. A complete proof is a further artifact that readers would need to open and examine when published. The fact that a snapshot exists does not let us inspect a proof that the source says is still expected later.

The time separation matters here because the snapshot predates the evening report of the 90% figure. The opened reports do not reconcile the evening progress statement with each balance captured that morning. Do not assume every purchase completed after the snapshot appears in that earlier measurement. A later publication should make its measurement time clear enough for readers to compare like with like.

If you save the update for later checking, preserve both dates beside their descriptions. Label the first “snapshot time” and the second “expected proof date.” When the full proof becomes available, compare its actual measurement time, covered assets and published results with the claim you were trying to verify. A later publication date alone does not make an older snapshot a current balance sheet.

A planned reopening still needs a working withdrawal

PANews reports an expectation that withdrawals will resume on November 1. The wording is prospective. It does not establish an operating time for every token, network or account, and it does not confirm that a pending request has been broadcast or received.

For a pending withdrawal, start with the request you already have. Save its creation time, asset, quantity, selected network and current status from the account interface. If the account supplies a transaction identifier, preserve that identifier and compare it with the receiving wallet's record. Keep the evidence attached to the same request rather than mixing screenshots from different attempts.

If the request remains pending, use the support route inside the application you already use. Identify the asset and request, then ask: has this withdrawal been broadcast, and which transaction identifier belongs to it? Keep the answer with that request's record. The proposed reopening date does not answer those questions. Avoid sending another transfer merely to test a schedule mentioned in a news report.

For an unsubmitted withdrawal, first inspect the available options in your existing account. A proposed reopening date is a reason to check the live status when the time comes. It supplies no reason to choose an unverified network or rush through an address confirmation. We have not checked any reader's account or completed a withdrawal as part of this story.

Keep market observations separate from reserve evidence

Readers with open positions can consult our liquidations board and funding-rates board for the observations those pages display at the time they open them. We do not import a liquidation total or funding quote into this report because neither opened news report establishes one.

The distinction is useful when a reserve update appears alongside a moving market. A price response cannot demonstrate that reserves were replenished, and the reserve percentage cannot establish the cause of a liquidation. Compare observations using their displayed times before drawing a connection. A shared publication day alone is insufficient evidence of a causal relationship.

For a leveraged position, preserve the position details separately from the withdrawal record. Position management concerns the exposure and controls visible in your account; a reserve report concerns the company's reported assets. Treating those records separately helps you ask a precise support question instead of assuming one headline resolves both problems.

Ignore unsolicited compensation instructions

Do not use a direct message or an unsolicited “Binance compensation” link to resolve this incident. Open the application through your established route and read notices there. Never send funds to an address supplied by an alleged support agent to release a withdrawal, and do not give a stranger a wallet recovery phrase or an account verification code.

This is a precaution for readers acting on the coverage, not a claim that the reports document a new compensation programme or a measured wave of scams. Neither report establishes a customer claim portal, a release fee or a recovery form. A message demanding those steps cannot borrow authority from the 90% headline.

If you receive such a message, keep its text and address without interacting with the proposed payment or login. Ask the existing in-app support channel whether any action is required for the request you already recorded. Preserve your original withdrawal evidence so an unsolicited message does not become your only account of what happened.

What the next disclosure must answer

The reports by Odaily and PANews both attribute the core update to Binance. They are two readable accounts of one company statement, not two independent reserve inspections. The underlying token inventory, the complete forthcoming proof and current account-level withdrawals remain outside the evidence opened for this article.

The next useful checks are specific: a token-by-token completion update for assets outside the named ten; the actual published proof with its measurement time; and a completed transfer for the individual withdrawal being checked. Keep each result with its date. An overall percentage can move again before those separate questions receive answers.

Quick answers

Does 90% backfilled mean 90% of outflow funds were recovered?

The reports describe replenishment, including resources from named company funds. They do not establish that investigators recovered that share of the original outflow.

Does the snapshot mean the full proof is already available?

The reported snapshot time is October 31 at 08:00 SGT. PANews describes the complete proof as expected on November 3 UTC, a separate stage that still needs its own publication evidence.

Does the update confirm my token can be withdrawn?

It does not identify the current processing state of your request. Check the exact asset, selected network and status in your existing account, then the receiving wallet if a transaction identifier is available.