What historical failures teach
Exchange failures have involved technical attacks, theft and misuse of customer assets. Size and brand recognition alone do not establish safety. Different cases require different lessons.
Mt. Gox: about 650,000 BTC missing
Mt. Gox first reported about 850,000 BTC missing, then found about 200,000 in an old wallet. The 2014 collapse showed the consequences of leaving assets with a custodian. The ensuing rehabilitation and creditor process took years; account access did not mean customers could withdraw on demand.
Bitfinex: about 120,000 BTC stolen
The August 2016 breach stole about 120,000 BTC. Bitfinex spread losses across users and issued BFX claims; those claims were later redeemed or exchanged for equity. This response does not establish a general right to reimbursement.
FTX: more than $8 billion in customer funds
FTX’s collapse involved misuse of customer money, including transfers to Alameda Research. The US Justice Department described more than $8 billion stolen from customers. Custody risk includes management fraud as well as technical breaches.
Treat trading access and long-term custody as separate decisions. Understand the provider’s risks and whether you can manage self-custody safely.
US availability and provider checks
US availability depends on the service, asset, relevant entity and customer’s state. Licensing does not guarantee solvency or protect every asset. The following 3 providers are included for individual eligibility review:
Kraken
Check state and product eligibility
Kraken does not serve residents of Maine or New York. Additional asset, funding and product restrictions apply. Washington is not among the states Kraken excludes.
eToro
Check state and product eligibility
Crypto trading is unavailable in Nevada, Hawaii, Puerto Rico and the US Virgin Islands. The platform is unavailable in American Samoa and Guam. New York crypto access launched in April 2026; its available assets may differ.
Coinbase
Check state and product eligibility
US access is supported, including Hawaii and New York. Individual assets, staking and other features can have separate state restrictions.
Check the current US service and state restrictions before opening an account. Fees, custody disclosures and review criteria are explained in the Exchange comparison.
Five account-security areas
Review these five areas before depositing where possible. Available controls and setup steps vary by provider.
Enable strong authentication
Enable supported phishing-resistant MFA, such as a security key or passkey, before depositing funds. An authenticator app is preferable to SMS when that is the available alternative. Protect recovery codes and the linked email account.
Anti-phishing code
Some exchanges describe an anti-phishing code in their help pages: a code you set that appears in their genuine messages. If yours offers one, configure it. A code is only one signal: still verify the sender and open the exchange from your own bookmark.
Withdrawal-address restrictions
Where supported, restrict withdrawals to verified addresses and protect changes to that list. The protection depends on the exchange’s confirmation and delay rules; it does not make an account takeover harmless.
Unique password and secured email
Use a unique manager-generated password of at least 16 characters where permitted. Consider a separate exchange email address and secure it with MFA as carefully as the exchange account.
Review account activity regularly
Check active sessions, devices, withdrawal addresses, API keys and MFA settings regularly. Enable activity alerts where supported; reviews can reveal unauthorized changes but may not catch them before a loss.
Configure supported address restrictions
Withdrawal-address restrictions can limit covered transfers to approved destinations. Their scope, activation delays and settings-change protections vary; they are one layer rather than an account-takeover guarantee.
Enable supported address restrictions
Look for address allowlisting or withdrawal-address restrictions in the account’s security settings. When supported and enabled, only approved destinations can receive covered withdrawals. Read which assets and transfer methods the restriction covers.
Add independently verified addresses
Add addresses you control using the correct asset and network. Verify the complete destination against the trusted device display where available, and include any required destination tag or memo.
How to verify a receiving address →Complete the exchange’s required confirmation steps
The process may require MFA, email confirmation or a waiting period, depending on the provider. An unexpected address-confirmation email is a warning: do not approve it; investigate through the official account and support channels.
CautionDo not approve a withdrawal address you did not add. Secure your account and contact support through the independently verified official website.
Understand activation and change delays
Check your exchange’s exact activation and removal delays. Coinbase normally applies a 48-hour hold for a newly allowlisted address; other providers and account types have different rules.
Set API permissions carefully
Integrations can expose sensitive API permissions. Use these four rules to reduce that exposure; they do not remove every risk from an integration or compromised service.
Read-only access
Disable trading and withdrawals
Tax software and portfolio trackers normally need read-only access. Disable trading and withdrawals. A stolen read-only key can still expose private account and transaction information.
IP restrictions
Restrict the permitted IP addresses
Where supported, restrict the key to the verified IP addresses used by your tool. This limits exposure, but it is not a guarantee against compromise of an allowed system.
One key per integration
Issue separate keys
Create a separate key for each integration. If one service is compromised, revoke its key and review its access without disabling every other connection.
Review and replace
Review keys regularly
Delete unused keys and investigate any you cannot identify. Follow the provider’s rotation guidance and replace a key immediately if exposure is suspected.
Never publish an API secret in email, chat or a repository. If exposed, revoke it promptly, review logs and permissions, and create a replacement only after securing the affected systems.
Evaluate the provider’s disclosures
Cold Storage
How much is actually held offline?
Read the provider’s current custody policy and independent disclosures. An offline-storage percentage is not a guarantee that customers can withdraw: if a custodian is hacked, shuts down or goes bankrupt, you may lose access to your assets.
Proof of Reserves
Check the scope of the evidence
Proof of reserves is not a full financial audit. A snapshot of assets may omit liabilities, control of those assets and changes after the snapshot. Independent verification does not by itself establish solvency.
US dollar deposits
Understand the protection before depositing
Crypto assets are not FDIC-insured. Any protection for eligible US dollar deposits depends on the bank arrangement and applicable conditions; it does not insure an exchange against every failure.
Crypto assets are not covered by FDIC deposit insurance. Eligible US dollar deposits may have conditional protection at a bank, which is different from protection against exchange failure. Review the provider-specific disclosures in the comparison.
Checklist for a new account
- Check eligibility: Check the provider’s relevant US entity, service and state availability; an EU authorization alone does not answer those questions.
- Enable strong authentication: Use strong supported authentication and secure its recovery path. Prefer phishing-resistant methods where available.
- Set an anti-phishing code: Where the provider supports one, the code appears in its genuine messages but does not replace independent verification.
- Review address restrictions: Use verified destinations and understand activation and settings-change delays.
- Use a unique strong password: Use at least 16 characters where permitted and store it in a secured manager.
- Dedicated email address: Consider an address used only for sensitive exchange accounts and secure it with strong authentication.
- Limit API permissions: Use read-only access where sufficient, supported IP restrictions and a separate key per integration.
- Evaluate custody needs: Consider self-custody together with secure backup and signing responsibilities.
