Does RUNE’s 13% rise show Binance funds are being recovered?

What the reported 13% actually measures

Cointelegraph places the $0.59 local low at 08:20 SGT on October 30, equivalent to 00:20 UTC. Its $0.67 figure is the price at the time the report was written, citing TradingView. The article does not give that second observation an exact time. Keep the endpoint attached to the report, rather than presenting it as a live quote or the day’s closing price. Read the reported price observations.

Using the rounded prices, the difference is $0.08. Dividing $0.08 by $0.59 gives approximately 13.56%. That calculation is consistent with the report’s wording, “more than 13%.” It cannot reconstruct every trade between the two observations, establish the exact high, or tell a reader what price would have been available for an order of a particular size.

The choice of starting point matters. This is a rise from a local low. It should not be relabelled as a gain since the Binance incident began, a full-day return, or a gain from the previous close. Those comparisons require their own starting observations. None follows automatically from the two prices in the report.

If you hold RUNE, compare your own entry price with the quote shown for the actual product you hold. A headline measuring a rebound from $0.59 does not calculate your position’s return. Check the asset, position size and execution record before copying the headline percentage into your own account calculation. This is an account check to perform, not a claim about any venue’s current RUNE market.

Why RUNE appears in the Binance coverage

Cointelegraph describes THORChain as a protocol for swapping assets across blockchains. It also reports investigator ZachXBT’s account that funds associated with the Binance incident and an earlier Bitget incident passed through THORChain before meeting at the same Ethereum address. Those are the outlet’s attributed findings; they do not identify the owner of every RUNE purchase made during the price move. Read Cointelegraph’s account of the routing.

A reported route and a quoted token price answer separate questions. The route concerns where particular assets travelled. The price concerns the value assigned to RUNE in the observations used by the report. To say that the route caused the entire rally would require evidence connecting transactions, timing and buying activity. The opened market report does not provide that complete reconstruction.

Readers should also avoid transferring an allegation about a particular flow to everyone holding the protocol’s token. Holding RUNE, processing a swap and controlling assets linked to an incident are different relationships. The reported rebound does not establish that token holders participated in the Binance incident, approved a particular transaction or received the disputed assets.

For someone deciding whether to trade, this leaves a narrower question than the headline might suggest: is the intended order based on a price observation, a verified transaction finding, or an assumption connecting them? Write down which one is doing the work. If the decision depends on an unverified cause for the rally, the percentage itself cannot fill that gap.

Four records that should stay separate

A useful way to read the developing event is to keep a price record, an asset-movement record, a recovery record and an account record apart. The categories matter because a new entry in one does not automatically update the others. Our analysis concerns that distinction; it does not claim access to Binance’s internal accounting.

The price record starts with the $0.59 and $0.67 observations. It supports a calculation of the reported rebound. A later price can change the return calculation, but it cannot establish who controls a wallet involved in the incident or whether a specific customer transfer has completed.

An asset-movement record needs an identifiable transaction and a meaningful account of the sender and recipient. A transfer reaching another address can be a relevant new fact. Before calling it a return to Binance, look for evidence connecting the destination to Binance and the transfer to the assets under investigation. An address appearing in a widely shared image is a starting point for checking, not proof of its owner.

A recovery record would need evidence that affected assets came back under the relevant party’s control. Freezing assets, replacing missing assets with company resources and recovering the original assets describe different actions. Their amounts can overlap or refer to different times. Adding them without a reconciliation can count the same resources more than once.

An account record concerns the reader’s own balance or transfer. Even a verified recovery at the company level would not, by itself, prove that a particular withdrawal was processed. Check the request identifier, asset, network and status in the Binance app or site you already use. Preserve the earlier record so a later status change can be compared with the same request.

Company replacement funds need their own reading

PANews reported on October 30 that Binance had prepared more than $6.34 billion of company funds to cover stolen-asset losses. The report said corresponding tokens worth more than $5 billion were already in place, with remaining assets being acquired through market and over-the-counter channels. It also said those figures excluded frozen or protected assets. These are attributed statements about replacement resources, not our verification of the company’s balance sheet. PANews’ account of the replacement effort.

That report provides context for the recovery question without explaining RUNE’s price move. It does not say that Binance bought RUNE, give a RUNE purchase size, or connect an identified company order with the $0.59-to-$0.67 rise. Do not convert a statement about acquiring affected tokens into a claim that a named token’s rally was company buying.

It also matters which outcome a reader is trying to confirm. Replacing an asset using company funds could address a shortfall while work to recover the original assets continues. A price increase in an unrelated holding would be another matter. Each proposed connection needs evidence; a larger number in an update cannot supply the missing transaction or account record.

When reading the next company update, note its publication time and the exact noun attached to the amount: prepared resources, tokens in place, frozen assets or recovered assets. Compare like with like. If an update changes categories, keep both descriptions instead of treating the difference as a newly recovered sum.

Check your position without turning the incident into a signal

For an existing RUNE holding, start with the position already on your screen. Record its size and the price being used for the account valuation. If there are pending orders, review their terms against your intended action. A market article’s historical endpoint is insufficient to confirm the conditions for a new order.

For a pending Binance transfer, open Binance through your established app or bookmark. Check that you are looking at the same asset and network as the original request. Retain its reference and any transaction hash shown. Use the current account notice to understand what the service says about that request; a RUNE chart cannot supply its status.

If the status is unclear, ask Binance support about that request identifier before submitting another transfer.

For broader market context, open our liquidations page and funding-rates page. Read the instrument and observation period on the page before comparing it with a token move. Those pages are relevant checks for trading conditions. Their presence does not establish that the RUNE rally came from liquidations or a particular funding position.

Keep account verification separate from messages offering a shortcut. Do not open unsolicited “Binance compensation” links, send a payment to unlock a payout, or provide a wallet seed phrase to a person contacting you privately. Check any claimed instruction through Binance’s existing official channels.

Which new evidence would change the answer?

A documented return transaction with a verified destination could support a recovery finding. A company statement identifying assets returned would need to be read for its scope and timing. A completed account entry could answer a particular user’s transfer question. RUNE’s next quoted price would update the market story while leaving those other questions open.

For the rally itself, evidence linking identifiable buying with the reported interval could support a more specific explanation. The current report supplies price endpoints and relevant incident context. It does not establish a precise cause for the whole move, the identities of all buyers, or a current execution price.

Watch for those specific additions rather than treating a green percentage as a recovery receipt. The next useful check for a pending transfer remains the same request in the existing Binance account, with its current status and any associated transaction record.