Bitcoin
Coinbase details custody controls following the reported Binance incident
In a November 4 post, Coinbase says it was unaffected and keeps more than 99% of customer assets offline. Its account of safeguards is not a guarantee against every loss.

More than 99% reportedly held offline
Coinbase published an explanation of its safeguards on November 4 after questions raised by the reported incident involving Binance’s internet-connected wallets. The U.S. platform says it was unaffected and holds more than 99% of customer assets offline. That figure describes its own arrangements at the time of publication; it is not an independent measurement of all its risks.
According to Coinbase, a small online reserve supports withdrawals, while excess balances return to offline storage. It separately describes its Custody product as entirely offline and segregated onchain. The company also says it holds customer assets one for one, without lending or using them unless instructed. These statements about availability, segregation and use of holdings address different questions.
Transfers are also subject to controls
The arrangement it describes includes distributed keys, transfer limits, anomaly detection and mechanisms capable of halting signing. According to the company, resumption requires a review of systems and the cause of the alert. The controls therefore also cover movements between reserves. The description explains the intended approach, but does not establish that an attack would be impossible or that withdrawals would always be instantaneous.
To understand that distinction, an educational bulletin from the SEC’s investor education office explains that a wallet stores private keys used to authorize transactions, rather than crypto assets themselves. An internet-connected wallet makes transactions convenient and creates exposure to cyberthreats. Offline storage reduces that exposure, with availability tradeoffs. A physical device can nevertheless be lost, damaged or stolen: disconnecting it does not address every vulnerability.
Custody architecture does not capture every risk
The same bulletin, dated December 12, 2025, distinguishes technical architecture from custody responsibility. Both self-custody and custody provided by a service can use online storage, offline storage or a combination. Entrusting keys to a third party leaves access dependent on its operation. Keeping keys personally instead makes the user responsible for safeguarding them. A platform’s stated percentage therefore cannot, by itself, compare those two arrangements.
The November 4 explanation provides information about safeguards Coinbase claims, without replacing a review of service terms. The SEC bulletin notably suggests understanding access to keys, possible asset reuse, segregation, insurance and the consequences of custodian failure. It is an older educational document, rather than a Coinbase certification published today. The new development is the company’s communication; its operational effectiveness cannot be inferred from that description alone.
