On October 31, 2026, the FBI said North Korean activity it calls TraderTraitor was responsible for the theft of more than $6 billion in virtual assets from Binance. With the U.S. Secret Service and IRS Criminal Investigation, it urged specified private-sector crypto infrastructure providers to block transactions tied to listed addresses. That does not mean all funds have been frozen or recovered.
The FBI attributed the Binance theft to TraderTraitor and said it occurred on or about October 29, 2026.
In a notice dated October 31, the FBI said North Korea was responsible for stealing more than $6 billion in virtual assets from Binance. The bureau uses the name TraderTraitor for this specific activity. It also said the actors had been converting stolen assets primarily into ETH and that it expected further laundering through DeFi and instant-swap services.
This is the FBI’s official attribution. It should be distinguished from earlier assessments by analytics firms and from a finding by a court. The notice does not provide a final technical account of every step in the intrusion.
The FBI, U.S. Secret Service and IRS Criminal Investigation urged named categories of private-sector crypto infrastructure providers to block transactions with or derived from listed addresses.
The notice names THORNode operators, RPC node operators, instant exchanges, DeFi services, blockchain analytics firms and other virtual-asset service providers. The agencies urged them to block transactions linked to addresses they said TraderTraitor actors were using to launder the stolen assets.
The FBI published addresses across several networks. CoinDesk counted more than 600 Ethereum addresses, just under 20 Bitcoin addresses and one Solana address. So “a call to DeFi” is shorthand: the request targets a broader set of infrastructure providers, not only DeFi users.
Blocking may restrict the use of funds at a particular service, but it does not return them to their owner or stop every possible transfer between addresses and platforms.
The FBI request concerns actions by intermediaries and infrastructure providers that may identify and restrict activity involving known addresses. The notice does not say that one service controls all listed addresses or that every on-chain transfer can be stopped. Nor does it say that all assets in or associated with the list have been frozen or returned to Binance.
For operators, the practical takeaway is to check the addresses against the official notice, assess how existing monitoring and response procedures apply, and avoid treating a match as proof of recovery. Implementation depends on the service; the FBI notice does not prescribe one universal technical method.
The incident highlights the value of quickly sharing verified address information across exchanges, analytics firms and infrastructure operators, but it does not establish that all providers have adopted the same measures.
The FBI notice combines an attribution, a list of addresses and a request directed at several types of service providers. For a crypto trading platform, that underscores the importance of having defined procedures for escalating and verifying notices from law enforcement and analytics organizations.
These are general operational-readiness takeaways, not claims about Binance’s internal measures or a legal interpretation binding on every organization.
No. The FBI, U.S. Secret Service and IRS Criminal Investigation urged named categories of private-sector infrastructure organizations and virtual-asset service providers to act. The notice does not describe this as an order to every DeFi user.
The FBI notice says more than $6 billion in virtual assets. That is the bureau's wording and should not be presented as a final, exact loss calculation.
The FBI published Ethereum, Bitcoin and Solana addresses. CoinDesk counted more than 600 Ethereum addresses, just under 20 Bitcoin addresses and one Solana address.
No. Blocking can restrict funds at a particular point in the infrastructure, but it does not establish that assets were returned or that every related transfer has been stopped.
Binance announced a phased restoration of withdrawals after a security incident. Phase one includes Bitcoin and selected assets on other networks, so the restart is not limited to BTC. The exchange said services would return as stability and security checks are completed.
Binance began restoring withdrawals in phases after suspending them for security checks.
In an official update on November 1, 2026, Binance set a 06:00–09:00 UTC window for phase one. CoinDesk reported that the exchange began the phased restart on Sunday. This is a new development in the incident: it concerns service restoration, rather than a new report about the attack itself.
The phrase “starting with Bitcoin” needs context. BTC is included, but Binance’s official phase-one list also covers selected assets on other networks. The exchange said deposits remained open.
Phase one covers BTC and selected assets across 15 networks, including Ethereum, BNB Smart Chain, Tron, Solana, and XRP.
Binance’s published list includes BTC on Bitcoin; ETH, USDT, and USDC on Ethereum; BNB, USDT, and USDC on BNB Smart Chain; TRX and USDT on Tron; SOL, USDT, and USDC on Solana; and XRP, ZEC, and DOGE on their respective networks. Selected assets are also listed for TON, Polygon, Avalanche C-Chain, Arbitrum, Base, Optimism, and Sui.
This is the phase-one list, not a guarantee that every asset can be withdrawn on every network. Binance said additional networks and assets would be added as they become ready.
Binance said a phased rollout allows it to check the readiness, stability, and security of services for each network and asset pair.
The exchange said it prioritized networks and pairs using user-demand data from the previous week, and would restore access after the required checks. The approach avoids reopening every withdrawal route at once while technical and security checks are underway.
The reopening of some withdrawals does not establish that the incident investigation is finished or that every platform function has been restored. The available announcements describe a gradual service restart.
Check the specific coin and network in Binance’s withdrawal interface, and make sure the sending network matches the receiving address.
Binance directed users to its withdrawal page or network-status page for current availability. The announced phase-one list is not a substitute for checking the live status.
No. BTC is included, but Binance listed selected assets across 15 networks for the first phase.
Not necessarily. The announcements confirm a phased service restoration; they do not establish that the investigation is complete or that every withdrawal route is available.
Check Binance’s withdrawal interface or network-status page. Availability depends on both the asset and the selected network.
On October 31, 2026, Binance said it had covered about 90% of the assets affected by the hack and that users would not bear the financial loss. This describes replenishment of affected customer assets using exchange resources and related funds; it does not, by itself, show that Binance recovered 90% of the stolen tokens.
Binance said it had raised coverage of the affected losses to about 90%, up from roughly 80% in its previous update.
In an update dated October 31, 2026, Binance said it had covered about 90% of the amount affected by the incident. The exchange also said BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC were fully backed at 100%.
These are figures and statements published by Binance. They should be described as the company’s replenishment and backing claims, not as an independent audit of every balance.
No. Replenishing affected balances and recovering tokens taken by attackers are different things.
The coverage claim describes how the exchange is restoring affected assets for customer balances. It does not establish how much of the stolen crypto was seized from the attackers or returned to the platform.
So a headline saying “Binance recovered 90% of the crypto” would go beyond the confirmed information. A more precise description is that Binance said it had replenished or covered about 90% of the affected amount.
Binance named corporate funds, a partial deployment of SAFU and funds from its Futures Insurance Fund.
Binance’s update listed several sources for replenishing assets: corporate funds, a partial deployment of the Secure Asset Fund for Users (SAFU), and funds from the Futures Insurance Fund. The company said it—not users—would bear the financial impact of the loss.
Those disclosures describe the sources Binance says it is using; they are not a complete independent accounting of every asset movement. Public reports put the incident’s estimated impact at about $6.3 billion.
The 90% announcement does not independently verify full restoration of balances or the return of stolen tokens.
The available coverage reports Binance’s statement and the funding sources it named, but does not provide an independent audit of every figure. The 90% figure also cannot be taken to mean that the same share of stolen assets has been seized from the attackers.
It helps to separate three questions: how much was affected, how much Binance says it has covered for customer assets, and how much of the stolen crypto was actually recovered. This update primarily addresses the second question.
In an update published on October 31, 2026.
The available statement concerns replenishing or covering affected assets. It does not confirm that 90% of the tokens were recovered from the attackers.
The exchange cited corporate funds, a partial deployment of SAFU and funds from its Futures Insurance Fund.
Binance said the exchange would bear the financial impact rather than users. This is the company’s stated position.
Published reporting says the Ethereum-side attack on Binance 14 used signed EIP-7702 authorizations that let the wallet delegate code execution. A transaction carried 50 variants with consecutive nonces, and the network applied the one matching the account’s current counter. This highlights the importance of signing controls; it does not, on its own, establish a vulnerability in Ethereum or EIP-7702.
EIP-7702 lets an externally owned account (EOA) sign an authorization for delegated code to execute in the context of that account.
Introduced as part of the Pectra upgrade, EIP-7702 adds a transaction type containing an authorization list. A signed authorization specifies code that may execute on behalf of an EOA. This expands what a conventional wallet can do, while making it especially important to verify what is being signed and to protect the systems that produce signatures.
The distinction matters: EIP-7702 does not mean an account can be switched to delegated code without an authorization signed by its controller.
CoinDesk reported that a transaction contained 50 signed authorizations for consecutive Binance 14 nonces, and Ethereum applied the one matching the account’s current nonce.
A nonce is an account’s transaction counter. Because the counter changes as an account sends transactions, the prepared authorizations covered a sequence of possible values. That allowed the attacker’s transaction to include an authorization that matched when it was processed.
CoinDesk reported that delegated code was then called through Binance 14 and redirected assets. It also said the permission remained active for nearly four hours before it was revoked. This is a published account of the Ethereum portion of the incident, not a final technical report from Binance.
The available reporting describes the use of EIP-7702 delegation, but does not establish a vulnerability in the Ethereum protocol or the specification.
The specification requires an authorization’s signature and parameters—including its nonce—to be checked. The reported transaction therefore points to the use of valid authorizations, but it does not explain how the attacker obtained the ability to use them.
Binance said its investigation was ongoing and that it had identified additional compromise points. It characterized a possible connection to an employee laptop as an initial line of inquiry, not a final conclusion. Until a complete technical reconstruction is published, observed on-chain mechanics should be kept separate from unconfirmed theories about initial access.
Exchanges should review not only private-key protection but also authorization policies, delegated code, nonce monitoring, and how permissions are revoked.
These are general controls to consider when reviewing wallet architecture; they are not claims about which safeguards Binance did or did not have. The incident remains under investigation.
It is an Ethereum feature that lets a key-controlled account sign an authorization for delegated code to execute in the account’s context.
CoinDesk reported that they covered consecutive nonces so one could match the account’s current nonce when the transaction was included.
No. It shows how a signed authorization can be used to delegate execution. The available evidence does not establish a vulnerability in Ethereum or the EIP-7702 specification.
Not from the cited material. Binance said its investigation was ongoing and that it had found additional compromise points; the full path to the authorizations remains unestablished in the available reports.
Binance said it had set aside more than $6.34 billion in company funds and reserves to cover the financial impact of its hack; about $5 billion, the company said, was already held in the affected tokens. That is a commitment to cover losses—not confirmation that stolen assets have been recovered or that the reserve has been independently verified.
On October 30, 2026, Binance said it had set aside more than $6.34 billion to cover the incident’s financial impact, which it preliminarily estimated at about $6.3 billion.
In its official update, Binance said the company would absorb the financial losses rather than pass them on to users. This is the exchange’s statement about funds set aside for coverage, not a final, independently verified loss assessment.
Binance said about $5 billion of the amount was already held in the same tokens affected by the incident. The Block reported that the exchange was buying the remainder. The distinction matters: the total amount committed and the assets reportedly already available in matching tokens are not the same figure.
No. Setting aside funds, recovering stolen assets, and freezing transfers are separate actions.
A commitment to cover losses means Binance says it intends to make up the financial shortfall. By itself, the announcement does not show how much stolen crypto has been recovered or when users will receive compensation.
Frozen assets should not automatically be counted as recovered assets either. Restricting token transfers and restoring assets for affected users are separate steps. The Associated Press separately reported Binance’s statement that it had begun recovering assets for users.
For exchange operators, the incident illustrates why response planning needs to cover both cybersecurity and the financial capacity to absorb losses.
In practical terms, an exchange needs to establish who can authorize compensation, which resources can fund it, and how quickly the required assets can be made available. If restoring customer balances requires matching tokens, a dollar-denominated reserve alone may not be enough; the asset mix and availability also matter.
These are risk-management takeaways, not independent verification of Binance’s stated reserve. The available sources describe its amount and composition based on company statements.
No. Binance said it had set aside more than $6.34 billion overall and that about $5 billion was already held in affected tokens. That is the company’s statement; the sources reviewed do not independently verify the full reserve.
No. A loss-coverage reserve is not the same as recovering stolen assets. Freezing, recovery, and compensation are distinct processes.
The exchange said its reserve exceeded its preliminary estimate of the incident’s impact. The available sources do not independently reconcile the two amounts or establish the final loss.
Freezing can stop some stolen tokens from moving, but it does not by itself establish ownership or return the funds. Recovery may require proof of entitlement and coordination with issuers, exchanges, law enforcement, or courts.
In an update dated October 30, 2026, Binance said it and its partners had frozen about $3 billion in affected assets. CoinDesk separately reported that Tether froze more than $1.56 billion in USDT and Circle froze about $823 million in USDC.
These figures describe the situation reported on October 30, 2026; they are not a final tally of funds returned. They also refer to different scopes: Binance’s overall estimate and amounts attributed to individual issuers.
Binance said it was working with law enforcement, blockchain intelligence firms, token issuers, and other exchanges to trace and recover assets. At the time, the outcome of further recovery efforts was still unknown.
A freeze restricts further movement, but it does not decide who owns the assets or establish the basis for transferring them back.
Experts cited by CoinDesk said that after assets are frozen, ownership and the legal basis for returning them still need to be established. Depending on the circumstances, the process may involve law enforcement, court orders, or issuer procedures. CoinDesk reported that the specific recovery route for Binance’s funds had not yet been determined.
For that reason, the value of frozen assets should not automatically be presented as the amount already returned to the victim.
Centralized stablecoin issuers can have tools to block their tokens, while Bitcoin has no central issuer that can freeze coins at the network level.
For USDT and USDC, the issuers may restrict token transactions using their available controls and applicable procedures. That does not mean any address or asset can be frozen without limits; the grounds and consequences may depend on the circumstances.
Bitcoin works differently: there is no central issuer able to freeze coins across the network. However, if funds reach a centralized exchange or another intermediary, that service may restrict transactions on its own platform.
Experts welcomed the fast response but questioned whether freeze decisions are applied consistently in incidents involving large and smaller victims.
One question raised was whether issuers and other market participants should respond in the same way when the victim is a large exchange or a smaller company. Experts also noted the risk of liability from an incorrect freeze and the need for clear procedures.
This remains a debate, not a settled prediction about how issuers will act in future cases. For trading-platform operators, the practical lesson is limited but important: an incident-response plan should account not only for tracing and blocking assets, but also for working with intermediaries and handling the legal process for recovery.
No. A freeze restricts movement, but it does not automatically establish ownership or complete a return process.
Bitcoin has no central issuer that can freeze coins at the network level. Centralized platforms may restrict transactions involving funds that reach their services.
In its October 30, 2026 update, Binance reported about $3 billion in frozen assets. CoinDesk also reported separate amounts announced by Tether and Circle. These are dated estimates of frozen funds, not confirmation that the assets were fully returned.
CoinDesk reported on October 30, 2026 that the specific process had not yet been determined. Experts said proof of ownership and legal procedures may be required.
As of October 30, 2026, Binance said its investigation had identified additional intrusion points, while withdrawals remained suspended. The exchange set Sunday, November 1, as a target for resuming withdrawals, not a confirmed schedule, as it continued rebuilding and testing related systems. The roughly $6.3 billion impact figure and the investigation’s findings remain preliminary.
Binance said investigators found additional intrusion points beyond the initially suspected compromised laptop; the full sequence of the attack has not yet been published.
Binance’s October 30 preliminary update said the incident may have involved a compromised DevOps engineer’s laptop and access to a service container. CoinDesk later reported that co-CEO Richard Teng said investigators had found additional intrusion points. That broadens the initial picture but does not yet establish the complete attack chain.
Binance estimated the incident’s overall impact at about $6.3 billion and said roughly $3 billion in affected assets had been frozen. These are preliminary company figures, not a final audited loss calculation.
Binance named Sunday, November 1, 2026, as its target, but withdrawals were still suspended in reports published October 30 and no confirmed restart time had been announced.
CoinDesk reported that Binance hoped to resume withdrawals by Sunday while rebuilding and testing the relevant infrastructure. Other reports described approximate time windows. These should not be treated as guarantees: the target could change if security checks are not complete.
For users and integration teams, the practical approach is to check Binance’s official channels for current status rather than rely on a stale estimate or retry against an assumed schedule. At the time of the cited reports, Binance said withdrawals remained suspended.
CoinDesk reported that Binance was reviewing cloud systems, employee devices, private-key management and transaction-signing procedures.
This indicates that recovering trading infrastructure involves more than switching the withdrawal function back on. The exchange said it was reviewing several connected components before testing operations.
This is a list of review areas described in reporting, not a complete technical plan published by Binance. A final post-mortem was not yet available.
The incident highlights the need to examine the full path from employee devices and internal services to permissions and transaction approval—not just wallet security.
This is an operational inference from the reported facts, not a conclusion from a completed root-cause analysis. When an investigation identifies additional intrusion points, platform operators can review trust boundaries between employee devices, service containers, cloud systems and critical asset operations.
Specific controls depend on a platform’s architecture. The available reports do not disclose Binance’s complete internal controls, so this is a general operational checklist, not a description of its configuration.
As of the October 30 reports, the final attack sequence, all contributing causes and the actual withdrawal restart time were not known.
Binance said it would publish a technical post-mortem after completing its investigation and verifying the facts. The final attack mechanism, the full set of affected systems and whether the restart target would be met therefore remained unresolved.
It is also important to distinguish company statements from independent verification. Binance said its preliminary investigation found no evidence of a wallet private-key leak and said it would cover losses, but those statements do not replace a final technical report and subsequent verification.
Reports published on October 30 said withdrawals were still suspended. Sunday, November 1, 2026, was described as a target, not a confirmed restart time.
It is Binance’s preliminary estimate of the incident’s overall impact. It should not automatically be read as the final amount of assets permanently lost.
No. In its preliminary update, Binance said it had found no evidence of a wallet private-key leak. A full technical review had not yet been published.
Use official Binance updates for current status, account for the withdrawal pause in transaction processing and avoid treating the target date as a guaranteed schedule.
As of the October 30 reports, no full post-mortem had been published. Binance said it would share one after the investigation and fact verification were complete.
As of October 30, 2026, Binance estimated the incident’s impact at about $6.3 billion and said approximately $3 billion had been frozen. The exchange said a compromised DevOps engineer’s laptop may have provided a route to a service container, but the investigation is ongoing and no full technical post-mortem has been published. In Binance’s latest update found for this report, deposits were operating while withdrawals remained paused.
Binance is investigating unauthorized withdrawal transactions with a preliminary estimated impact of about $6.3 billion.
In its preliminary account, Binance said a compromised laptop belonging to a DevOps engineer may have given an attacker access to a service container, from which unauthorized withdrawal transactions could be submitted. The exchange said it had found no evidence that wallet private keys were compromised. This remains Binance’s preliminary explanation, not a completed technical report.
Binance also said it intends to cover losses using SAFU and company funds, and to publish a technical post-mortem after the investigation and remediation are complete.
Binance put the estimated total impact at about $6.3 billion and said roughly $3 billion had been frozen; both figures are preliminary and may change.
In its latest update found for this report, Binance said it was working with blockchain partners to trace and freeze assets. The exchange’s reported frozen amount was approximately $3 billion. That figure should not be read as a final recovery total: tracing and investigation are still underway.
It is important to distinguish Binance’s estimate from a completed independent audit. Until the exchange publishes its full post-mortem, the precise attack path and final impact remain unsettled.
In Binance’s latest update found for this report, deposits were operating while withdrawals remained temporarily paused.
Binance said it was carrying out security checks and revamping the withdrawal service and related addresses. This status reflects the exchange’s update on October 30, 2026, and may change; readers should check official Binance communications for current service information.
The company’s statement that user funds are safe should be attributed to Binance. A full technical post-mortem had not yet been published at the time of this report.
Operators should review how access is separated across employee devices, internal services, and withdrawal permissions—and how quickly suspicious transactions can be contained.
Binance’s preliminary account makes the access path for withdrawal operations an important area for platform operators to audit. This is a general engineering takeaway, not a confirmed description of a specific flaw in Binance’s systems.
These controls can reduce operational risk, but they cannot guarantee that an attack will be prevented.
No. Binance said it had found no evidence of a wallet private key compromise. That is the company’s preliminary statement; the investigation is ongoing.
It is Binance’s preliminary estimate of the incident’s total impact. The exchange also reported that about $3 billion had been frozen. A final audit and post-mortem were not available at the time of this report.
Binance said it temporarily paused withdrawals while it conducted security checks and revamped the withdrawal service and related addresses.
Not yet. Binance identified a compromised DevOps engineer’s laptop and access to a service container as a possible route, but it has not published a full technical post-mortem.
On October 29, 2026, Binance reported a security incident and put its preliminary overall impact at about $6.3 billion. The more-than-$5.7-billion figure in reports referred to the value of assets held in wallets linked to the suspected attacker, not a final tally of irrecoverable losses. Binance also said roughly $3 billion in assets had been frozen; the cause was still under investigation.
Binance reported a potential security incident affecting a large volume of crypto assets and began investigating.
Reports published on October 29 cited more than one estimate. Binance later put the incident’s preliminary overall impact at about $6.3 billion. That company estimate does not mean the entire amount was a final, unrecoverable loss.
It is important to distinguish the reported incident, preliminary estimates, and the findings of a completed investigation. Early reports had not established the full attack mechanism or final financial impact.
The figures describe different measures: Binance’s preliminary estimate of about $6.3 billion in overall impact and CoinDesk’s report of more than $5.7 billion in assets held in wallets linked to the suspected attacker.
CoinDesk reported that wallets linked to the suspected attacker held assets worth more than $5.7 billion at one point. The same report discussed other estimates of the assets stolen. The headline claim that Binance “lost $5.7 billion” therefore compresses several different measures: assets tracked in wallets, the exchange’s estimate of overall impact, and any eventual confirmed losses.
When comparing incident figures, check what each number measures: asset movements, the exchange’s own estimate, balances in specific wallets, or confirmed losses.
Binance’s preliminary account pointed to a potentially compromised DevOps engineer’s laptop, but that account is not a final investigative finding.
In its preliminary account, Binance said a compromised device may have enabled access to a service container and the submission of unauthorized withdrawal transactions. The exchange also said it had found no evidence that wallet private keys were leaked.
These are early findings reported by the company, not independent confirmation of the complete technical sequence. While the investigation continues, neither a specific vulnerability nor an attacker’s identity should be presented as conclusively established.
Binance said roughly $3 billion in assets had been frozen and said it would cover incident-related losses using SAFU and company funds.
Binance reported that roughly $3 billion had been frozen on-chain. The exchange also said deposits were no longer affected and that it would cover losses related to the incident using SAFU and company funds. These are the exchange’s statements, not an independent assessment of a completed recovery.
For crypto trading-platform operators and developers, the incident is a reminder to review layered controls. Practical areas include employee access boundaries, endpoint security, approval and monitoring of critical withdrawals, anomaly detection, and incident-response plans. These are general risk-management considerations; they do not establish that any particular missing control caused this incident.
No. CoinDesk used that figure for the value of assets in linked wallets. Binance separately put the preliminary overall impact at about $6.3 billion; neither figure should be treated as a final tally of irrecoverable losses.
Binance reported that about $3 billion in assets had been frozen on-chain. The figure reflects the update available at the time and could change.
Binance said it had found no evidence of a wallet private-key leak. That was a report of preliminary findings, not independent confirmation of every investigative detail.
The sources available for this article do not establish a definitive attribution. Early suggestions about a specific group should not be treated as confirmed.
Binance’s October 1 Proof of Reserves snapshot let CoinDesk match an affected wallet to assets backing customer balances. CoinDesk estimated ETH backing could be around 94% if the withdrawn assets had not been replaced. That is an estimate based on an earlier snapshot, not a confirmed current ratio. Binance said it would cover losses and publish updated reserves after remediation.
On October 30, Binance said its preliminary investigation pointed to a possible compromise of a DevOps engineer’s laptop and access through a service container.
The exchange estimated the total impact at about $6.3 billion and said blockchain partners had frozen about $3 billion in assets at that point. Binance said it had found no evidence that wallet private keys were leaked, temporarily suspended deposits and withdrawals, and would cover losses through its SAFU fund and company funds.
This was Binance’s preliminary account, not a final technical post-mortem. The possible access path should therefore be described as an early investigative finding, not an established final cause.
CoinDesk linked Binance 14 to the October 1 Proof of Reserves snapshot and estimated that ETH backing could be about 94% after the incident if the assets had not been replaced.
CoinDesk’s analysis found Binance 14 in the October 1 reserve snapshot and connected it to wallets later associated with the outflows. The publication reported that customer ETH liabilities were fully covered on the snapshot date and estimated that the withdrawal of roughly 204,500 ETH could reduce ETH backing to around 94% if the exchange had not replenished the asset.
This is a third-party estimate based on a specific snapshot, not Binance’s published post-incident balance. It should not be treated as a confirmed overall reserve ratio or proof that customers cannot access their funds. Binance said it would cover losses and publish updated Proof of Reserves after remediation.
Proof of Reserves helps verify asset and customer-balance data at the time of a snapshot, but it does not provide a continuous, real-time view of reserves.
Binance describes a process that uses a snapshot of customer balances and cryptographic proofs, allowing users to check whether their balances were included in a report. The exchange also notes that a report reflects a particular point in time and may not match current asset holdings.
That makes the October 1 snapshot useful for understanding which wallets and assets were counted then, but it cannot by itself show how much remained after the October 29–30 incident. Updated post-remediation data is needed to assess the later position.
The incident illustrates that reserve verification and wallet-access security address different risks, so platform operators need both kinds of control.
Proof of Reserves can help check reported assets and customer liabilities at a chosen date. Separate access controls and incident response are needed to address unauthorized transactions. Based on the confirmed information in this case, practical considerations include:
These points do not establish which internal security controls Binance did or did not use: the reviewed sources do not include a completed technical report with such findings.
No. It is CoinDesk’s calculation using the October 1 snapshot and estimated ETH outflows, assuming the assets had not been replaced. It is not a final post-incident audit or an overall ratio for all assets.
No. In its October 30 update, Binance said it had found no evidence of a wallet private-key leak. It presented a possible DevOps laptop compromise as a preliminary investigative finding.
Binance said it would publish updated Proof of Reserves after remediation. Its reviewed statement did not give a later specific publication date.
It is a way to report assets held by an exchange and verify that customer balances are included in a report at a particular time. Binance says its report is a snapshot, not a real-time display of assets.