Crypto.com Disclosed a 320,000-ETH Transfer Error

Crypto.com chief executive Kris Marszalek acknowledged on November 13, 2022 that the exchange had mistakenly transferred 320,000 ether to a corporate account at Gate.io instead of moving the assets to a new cold-storage address.

Gate.io separately confirmed the error and said it assisted with returning the assets. The disclosure mattered because it exposed a significant operational-control failure at a centralized exchange only two days after FTX entered bankruptcy. Customers and market participants were scrutinizing whether exchanges controlled the assets represented on their internal ledgers, making an unexplained transfer between two large platforms especially consequential.

The mistake itself occurred on October 21, but the exchanges’ public explanations and the resulting custody debate belong to November 13. No evidence reviewed for this reconstruction establishes that customer balances were lost or that Crypto.com was insolvent.

What the records establish

Gate.io’s dated statement said Crypto.com sent 320,000 ETH at 02:52 UTC on October 21 to a Gate account used by Crypto.com. According to Gate.io, the deposit activated its security-review process, the companies confirmed that the transfer was an operational error, and Gate.io began returning the assets.

Marszalek said the intended destination had been a new cold-storage address. Instead, the transfer went to a previously approved external-exchange address belonging to Crypto.com. He said the funds were returned to Crypto.com’s cold storage and that the company introduced new processes and system features intended to prevent a recurrence.

An Ethereum transaction identified by Gate.io records the 320,000-ETH transfer. The public ledger verifies the quantity, timestamp and destination address, but it cannot independently establish why the transfer occurred, who authorized it or which company controlled an address. Those elements depend on the attributable statements from Crypto.com and Gate.io.

Contemporaneous reporting initially focused on a visible return of approximately 285,000 ETH, creating questions about the remaining amount. Additional transaction tracing identified a separate return of approximately 35,000 ETH to another Crypto.com-labelled address. Crypto.com and Gate.io both maintained that all of the mistakenly transferred ether was recovered. Address labels and company statements support that account, although the reviewed record does not include an independently audited reconciliation of every associated wallet movement.

Why wallet disclosure was not proof of solvency

On November 11, Marszalek had published several Crypto.com wallet addresses and described their contents as only a portion of the company’s reserves. He listed approximately 391,564 ETH alongside bitcoin and other assets and promised a full audited proof-of-reserves report later.

That address disclosure helped outside observers identify the October 21 transfer, demonstrating the value of public-ledger scrutiny. It did not, however, establish Crypto.com’s complete financial position. A wallet list can show assets at specified addresses, but it does not by itself reveal customer liabilities, encumbrances, off-chain obligations, internal controls or whether an exchange has exclusive and continuing control of every listed asset.

The timing also undercut speculation that the transfer had inflated Gate.io’s cited reserve snapshot. Gate.io said Armanino took that snapshot at 00:00 UTC on October 19—more than two days before the 320,000 ETH arrived. That chronology does not validate every aspect of Gate.io’s reserve assessment, but it provides no support for including the later transfer in the October 19 snapshot.

What remained uncertain on November 13

Neither exchange publicly identified the employee or approval sequence responsible for the error, the precise control failure, or the complete transaction-level reconciliation process. Claims that the transfer proved insolvency, secret reserve sharing or deliberate balance-sheet manipulation were therefore unverified on November 13.

No ether or exchange-token price movement is attributed to the disclosure. Crypto assets traded continuously across multiple venues during the broader FTX crisis, and the reviewed sources do not provide a sufficiently controlled event window for separating the effect of this disclosure from concurrent market stress.

The defensible conclusion was narrower: Crypto.com admitted that a cold-storage transfer had been misdirected to another exchange, recovered the assets and said it strengthened its controls. The episode showed that public wallet transparency could expose operational mistakes while remaining an incomplete substitute for liability reporting, custody verification and independent assurance.