You get money onto Hyperliquid by depositing through the official-app route for that asset, then waiting for a HyperCore credit. HyperCore is the onchain trading environment that holds the perps and spot books. USDC usually arrives from Arbitrum, Circle CCTP, or an email Across address. A CEX Send on the wrong chain leaves that HyperCore line empty. On the deprecated Arbitrum USDC contract, any send below 5 USDC is lost with no recovery.
Suppose you have 400 USDC on a centralized exchange and want it tradable on Hyperliquid tonight. You copy a string from a chat that says Hyperliquid, pick Ethereum because that is the network your CEX already lists, and confirm. The CEX books a withdrawal. The HyperCore line you opened the app to watch stays empty.
How Hyperliquid deposits and bridges work
A Hyperliquid deposit is a send to the address the official app shows for one asset on one network, followed by a credit on HyperCore or HyperEVM. HyperEVM is the Ethereum-style contract environment on the same chain, where HYPE pays gas. Official onboarding says a completed native deposit arrives as USDC on HyperCore, and that many exchanges and bridges support withdrawals on Hyperliquid over either HyperCore or HyperEVM (source: Hyperliquid Docs, How to start trading). A CEX row that only says Hyperliquid has not named which environment you are funding.
The last hop is always the window in the official app, and an aggregator that got USDC onto Arbitrum still leaves that paste as the last hop. How Hyperliquid works covers why HyperCore and HyperEVM share one chain. The deposit job is narrower: fund the environment you will actually use, on the asset and network that window named.
A signed session has to exist before that paste is more than busywork. Enable Trading, or the 6-digit email code, is that login. Hyperliquid wallet and account setup is that signed session. A BloFin password opens BloFin. The HyperCore account that receives the credit starts with the first Hyperliquid deposit.
CEX withdrawals and wrong-chain deposits
The common loss is treating a CEX withdrawal, or a chain that CEX already supports, as if it were HyperCore. Pick the asset and network the deposit window named. A Send inside the native app moves coins to another Hyperliquid account on HyperCore. It is a different click from a withdrawal to another chain.
Suppose that 400 USDC is sitting on the exchange, and the chat string you pasted happens to be a HyperEVM address, or an Ethereum address, while you wanted perps margin. The explorer on the source chain can show success. HyperCore still shows zero.
The other version of the same miss starts on Hyperliquid. You open Send because it looks like a cash-out, paste the CEX deposit address, and sign. Official support leaves that send with the CEX. "If you sent it to a CEX, this means that only the CEX address can access the funds you sent." You then wait for that exchange to integrate the Hyperliquid blockchain if you want those coins retrieved (source: Hyperliquid Docs, Withdrawal has not arrived). There is a warning on that click, and BloFin support cannot retrieve it.
How to send and receive HYPE covers Send as a HyperCore-to-HyperCore hop and Withdraw as an off-chain exit. The inbound version of that fork is this deposit: a CEX Send funds the exchange's chain list, and a HyperCore Send stays inside Hyperliquid. How to send and receive crypto is the generic network-match habit. The Hyperliquid-specific check is the deposit window's asset and chain, copied from the official app, not from a CEX autocomplete.
Clipboard hijacking is how a pasted string can be the wrong destination even when the chain label was right. For a first deposit, write the first six and last six characters from the official window on paper, then match them before you sign.
That 400 USDC is still somewhere. It is off the HyperCore line you opened the app to watch.
HyperCore credit vs HyperEVM credit
A deposit can credit HyperCore, where perps and spot books live, or HyperEVM, where the same chain shows as an EVM network with HYPE as gas. Credit on one side stays off the other until you transfer. Name the environment before you paste an address.
Suppose you refresh perps and still see zero, even though the explorer on the source chain shows a success. The inbound can have landed as HyperEVM spot. That is a completed send to the other environment, and you still need a Core-to-EVM transfer, in the other direction, to move it onto the books.
Official transfer docs allow spot assets to move between HyperCore and HyperEVM, and they warn against assuming those two spot balances are accurately fungible (source: Hyperliquid Docs, HyperCore HyperEVM transfers). A number that looks like USDC on HyperEVM is still HyperEVM spot until you move it. Transfer to or from EVM is you moving between those two environments after the inbound already landed, separate from a CEX withdrawal and from a friend Send.
A green explorer on Arbitrum or Ethereum can still be the wrong screen if the credit sat down as EVM spot.
USDC routes: Circle CCTP and the older Arbitrum bridge
USDC onto Hyperliquid has more than one path. Circle's CCTP, Cross-Chain Transfer Protocol, is the preferred mint of USDC onto the Hyperliquid L1. An older Arbitrum bridge still exists, is deprecated, and still takes native USDC with a 5 USDC floor. Email logins and wallet logins use different supported-network lists.
The L1 can mint USDC natively, and the deprecated Arbitrum contract can still take a send. Official developer copy puts the preference first: CCTP is the preferred method for minting USDC natively on the Hyperliquid L1, and the legacy bridge is deprecated. "The minimum deposit amount is 5 USDC. If you send an amount less than this, it will not be credited and be lost forever." Withdrawals from Arbitrum on that path are handled entirely by validators, and the funds arrive in the user wallet in 3-4 minutes (source: Hyperliquid Docs, USDC). The 5 USDC floor is a loss rule on that contract.
The Hyperliquid legacy bridge contract has been audited by Zellic (source: Hyperliquid Docs, Audits). That audit covers the older contract. It is separate from Circle's mint path.
Circle publishes a separate contract set for the mint path, described as the repository for all HyperEVM contracts developed by Circle (source: GitHub, circlefin/hyperevm-circle-contracts).
Circle's howto then places the HyperCore credit after the mint: deposits credit the perps balance on HyperCore (source: Circle, Transfer USDC from Arbitrum to HyperCore). That default is dest-dex 0. Dest-dex is a Circle CoreDepositWallet field that chooses perps versus spot after the mint. Spot is a different dex id on that path, the unsigned 32-bit maximum. If that field stays blank, look at perps first.
| Path | What it does | Below 5 USDC |
|---|---|---|
| Circle CCTP | Mints USDC on the L1. Credits HyperCore perps by default (dest-dex 0). | Circle's HyperCore copy states no minimum deposit amount. This is the CCTP path, not the older Arbitrum contract. |
| Older Arbitrum bridge | Deprecated. Still takes native USDC. Validators handle the Arbitrum withdrawal in 3-4 minutes. | Lost forever. No recovery. |
| Email login + Across | USDC via Arbitrum, Base, Ethereum, and Polygon. | Redirected to the email wallet. Amounts below 1 USDC are lost. |
| Connected wallet | USDC via Arbitrum only. | Lost. No Across redirect and no 10-minute undo. |
Wallet USDC on Arbitrum credits HyperCore USDC through the deprecated bridge validators. Email USDC credits HyperCore USDC through Across plus the email wallet. Circle CCTP credits HyperCore perps by default, trusting Circle's mint plus the Hyperliquid forwarder, and that path skips the 5 USDC legacy floor. Unit ETH or ENA credits those HyperCore assets through Unit, an independent team, and below 0.007 ETH or 120 ENA is lost. That list describes documented routes. Third-party aggregators can still be how you get USDC onto Arbitrum in the first place, and the last hop is still the official window.
Email login vs wallet login for USDC
The same USDC job changes when the login changes. Email can take Arbitrum, Base, Ethereum, and Polygon through Across. A connected wallet only takes Arbitrum. Mixing those two stories is how a deposit that worked last week fails after the login switched.
Official support splits it on the first heading. Connected via email: supports USDC deposits via Arbitrum, Base, Ethereum, and Polygon, and the USDC deposit flow is managed by Across Protocol. Connected via a wallet: supports USDC deposits via Arbitrum only, and deposits below 5 USDC are lost. If you deposited anything other than USDC on supported networks to the Across deposit address, your funds are automatically redirected to your email wallet within 10 minutes (source: Hyperliquid Docs, Deposited USDC). Email amounts below 5 USDC are redirected to that email wallet, and amounts below 1 USDC are lost. Wallet amounts below 5 USDC have no Across redirect and no 10-minute undo.
An email login can take Base, and a connected Rabby session cannot. The Across history page is a transfer log for that email pipe, separate from the HyperCore perps line. Export the email wallet before treating the inbox as the backup, because a connected-wallet miss has no email-wallet export path. Write which login you used on the same paper slip as the first six and last six characters. The supported-network list follows the login, not the asset name.
Unit routes for BTC, ETH, and SOL
BTC, ETH, and SOL use Unit-managed addresses, separate from the USDC bridge. Official onboarding tells a wallet user to send those spot assets to the destination address shown in the deposit window. Unit, an independent team, manages those chains. The wrong token or the wrong network is a failed deposit.
Suppose you see Ethereum on the CEX because you are used to sending ETH there. The Hyperliquid window for ETH is still an ETH window, and that window accepts ETH or ENA only.
Official Ethereum-network copy is specific. The Ethereum address can only receive ETH or ENA on the Ethereum network. Deposits other than ETH or ENA, or on other networks, fail with no credit. Depositing USDC on Ethereum or ETH on Base fails. There are minimum deposits of 0.007 ETH and 120 ENA. Deposits below those amounts result in a loss of funds (source: Hyperliquid Docs, Deposited via Ethereum network). Some mistakes have a Unit revert URL: USDC, USDT, or WETH on Ethereum, or ETH on Arbitrum, can try that revert. An unsupported asset, or ETH or ENA on a chain other than Ethereum, currently has no retrieve path unless Unit later adds one.
Failed deposits that were the right asset, right chain, and above the floor still go to Unit support, not to a chat that claims to be Hyperliquid. Official withdrawal copy already names Unit as independent, so a deposit that shows Failed on a Unit-managed asset is that team's queue.
Bitcoin follows the same pattern on a slower chain. The Bitcoin address can only receive BTC on the Bitcoin network. There is a minimum deposit of 0.0003 BTC. Deposits below 0.0003 BTC result in a loss of funds (source: Hyperliquid Docs, Deposited via Bitcoin network). Sending BTC on another network stays on that other network. The wait is shown in the same pop-up where the address was copied.
Solana is Unit again, with a different asset list. The Solana address can only receive SOL, 2Z, ANSEM, BONK, FARTCOIN, PUMP, or SPX on the Solana network. Depositing USDC on Solana fails with no credit (source: Hyperliquid Docs, Deposited via Solana network). USDC on Solana is a failed Solana send. HyperCore USDC still needs the official USDC window. The window still has to match.
What a cryptocurrency wallet is is the generic tool that still has to match the chain. Here the Hyperliquid-specific address is the one the official window generated for that asset, not a reused Ethereum USDC string.
Withdraw vs Send when leaving Hyperliquid
Leaving Hyperliquid is a Withdraw. Send moves coins to another Hyperliquid account on HyperCore. Withdraw leaves this chain. If you meant a CEX, Withdraw is the click, and that CEX still has to list the network you picked.
Suppose you want the 400 USDC back at the CEX. Keep the CEX deposit string off Send. A friend-to-friend HyperCore hop is a different job. The off-ramp is Withdraw, then the chain the CEX actually lists. Official HyperEVM copy is the same warning in the other direction. Some CEXs support sending and receiving HYPE from spot balances on HyperCore, but not the HyperEVM. Always remember to do a test transaction when you are trying something for the first time (source: Hyperliquid Docs, How to use the HyperEVM). A CEX that lists HYPE can still omit HyperEVM. The same onboarding page also names third-party bridges onto HyperEVM. Those landings are separate from the official USDC window for HyperCore.
Withdrawals that use the older Arbitrum bridge still need only a Hyperliquid signature. Validators handle the Arbitrum side, which is a trust assumption, not a promise that every CEX will book the resulting USDC. Size a test Withdraw before you move the 400.
Centralized versus decentralized exchanges is the category fork. Here the operational fact is the Action column: Withdrawal versus Send. If Status says Completed, the explorer link next to the timestamp is the destination check. If it says Failed on a Unit-managed asset, that is Unit again.
The 1 quote token activation fee
A new HyperCore destination still pays 1 quote token on the first inbound that treats that address as the destination, for example 1 USDC or 1 USDT. That bill is separate from Enable Trading and from HyperEVM gas. Later inbounds to an already activated address skip that fee.
Enable Trading is the gas-less signature. The 6-digit email code is the other login. Neither one is this fee. Activation is the first credit. New HyperCore accounts require 1 quote token, for example 1 USDC or 1 USDT, of fees for the first transaction which has the new account as destination address (source: Hyperliquid Docs, Activation gas fee). Circle describes the same 1 USDC as an earmark that is charged on the first outbound. The 1 USDC activation fee is earmarked at the account level and charged on the user's first outbound action, such as a withdrawal or SendAsset transfer. Circle's HyperCore copy also states there is no minimum deposit amount, and that native USDC remains in the CoreDepositWallet contract on HyperEVM (source: Circle, CCTP-enabled HyperCore transfers). Official copy bills the first destination transaction. Circle copy bills the first outbound. The account can show a credit and still be unable to act until that quote token is actually taken. Keep Enable Trading separate from that quote-token bill.
If you are new, size the first inbound so a 1 USDC or 1 USDT take still leaves a balance you can use. A 5 USDC wallet deposit that also hits activation is a different floor from a 4 USDC send that the older Arbitrum bridge drops. Circle's no-minimum line is the CCTP path.
A deposit checklist
Before you size a deposit, confirm five things: official URL, which login you used, which environment you will fund, which asset and chain the window named, and whether you actually wanted a CEX ledger instead.
- Type the official app and bookmark it. Skip a sponsored result.
- Wallet login or email login. Those USDC networks are different lists.
- HyperCore perps, HyperCore spot, or HyperEVM.
- Asset and chain in the official window, matched on paper, not a CEX autocomplete.
- If the job is actually a BloFin ledger credit, stop here. That is a different product.
The public instruments API on August 22, 2026 still returns a live SWAP row whose instrument ID is HYPE-USDT, 75x, listed December 19, 2024 11:30 UTC (source: BloFin, SWAP instruments). That hyphenated ID is the API key. Reader copy for the same BloFin perpetual is HYPEUSDT, and that pair sits off the Hyperliquid deposit window. HYPERUSDT on the same venue is Hyperlane, a different listing. If the chart header says Hyperlane, you are off a Hyperliquid deposit. Withdrawing USDC from BloFin onto Arbitrum is still a CEX off-ramp. The Hyperliquid last hop is a separate paste in the official window.
How CEX wallets actually hold coins is why a BloFin password reset can still reach a venue balance and stop short of HyperCore. Ethereum deposits and withdrawals on BloFin is that CEX click path. A BloFin deposit form is a product boundary. Size the Hyperliquid hop after the CEX hop, not instead of it.
After the deposit credits
Once HyperCore shows the credit, the next job is whatever you funded it for: a spot buy, perps margin, or a later transfer into HyperEVM. A deposit leaves HIP-3 deployer lockup untouched, and a BloFin SWAP fill stays a CEX fill.
How to buy HYPE is the venue-aware purchase if the token you wanted sits on a book you can leave. A card or bank on-ramp is that purchase, not a bridge. Native Hyperliquid spot is a real market on HyperCore after USDC is there, and it is separate from BloFin. HIP-3 builder-deployed perps is a later product on that same book, with a deployer stake that sits outside this deposit. Funding the account leaves HIP-3 listing for later.
A later inbound is a new paste from the window that day, separate from a top-up of yesterday's Across transfer id. If the original job was a BloFin fill, you already had a CEX credit, and this hop was optional until you actually wanted HyperCore. Native spot after USDC sits on HyperCore is still a book buy, separate from a card on-ramp. The credit leaves HIP-3 listing for later.
Once the line you meant actually moved, size the next action on that environment. A second deposit is a second window. A BloFin SWAP fill stays a CEX instrument until you withdraw it and complete this hop. The deposit job ends at the HyperCore line you funded.
Frequently asked questions
If email USDC already redirected below 5 USDC, do I Across it again from the inbox?
No. Official support already parked that send in the email wallet. The inbox is a first-hop holding place, and a Complete row on the Across history page is still an Across log. Export the email wallet, then, if you still want HyperCore USDC, deposit as a connected wallet on Arbitrum. That rail is Arbitrum only, and amounts below 5 USDC are lost with no undo. A mail-client retry leaves the floor in place and leaves perps empty.
Do email Across and the older Arbitrum window take dest-dex the way CCTP does?
No. dest-dex is a Circle CoreDepositWallet field on the CCTP hop. Official email Across and the older Arbitrum USDC window credit HyperCore USDC as the app's USDC line, and those windows omit dest-dex. A blank CCTP UI is a CCTP screen, so keep the Across address off it. If you used Across or the older contract, watch HyperCore USDC. If you used CCTP with dest-dex blank, that is a different screen. A second Across transfer will not move a CCTP perps credit.
If Unit revert works for USDC I sent to the official Ethereum address, is that HyperCore USDC?
No. Official Ethereum-network copy says that address can receive ETH or ENA only, so a USDC send there fails with no credit. Revert is a retrieve path for a short named list of misses, after which you still use the official USDC window. A successful revert returns coins you can reach again. It leaves you off HyperCore USDC until wallet Arbitrum, email Across, or CCTP actually credits it. Treat Unit revert as a retrieve, then run the official USDC window.
Can I paste a contract from Circle's GitHub instead of the official deposit window?
No. Circle's HyperEVM repo is the contract set for the mint path, including CoreDepositWallet. Addresses the official app generated for your login sit in the app window, not in that repo tree. Paste the window the app showed, or follow Circle's Arbitrum-to-HyperCore howto for that hop. A repo tree, a README proxy note, or a forwarded explorer link is a contract reference. If you skipped that howto, you are off that mint path.
Does BloFin Convert turn USDT into HyperCore USDC?
No. Convert is a centralized-exchange product. It can change a venue balance from one listed asset into another listed asset. Convert leaves USDC as a BloFin ledger line: it skips a HyperCore mint, the older Arbitrum floor, and Circle CCTP. After Convert you still hold a BloFin ledger line. The Hyperliquid last hop is the official window: wallet USDC on Arbitrum, email Across, or CCTP. HYPEUSDT SWAP at 75x is a USDT-margined perpetual on that same venue, separate from that last hop.
Can I skip the 1 quote token by depositing to HyperEVM first?
No. A HyperEVM inbound from another chain is credit on that EVM environment. Official activation bills the first HyperCore destination transaction, so a HyperEVM inbound leaves that bill unpaid. Unactivated accounts cannot send CoreWriter actions until that 1 quote token (1 USDC or 1 USDT in the examples) is taken. Circle still earmarks 1 USDC until the first outbound. Enable Trading leaves both bills unpaid. Fund HyperCore, then transfer to HyperEVM if that is the environment you actually wanted.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated August 2026. Primary sources include Hyperliquid Docs (onboarding, USDC, deposit FAQs, audits, HyperEVM), Circle CCTP HyperCore copy, and BloFin's public SWAP instrument API. Protocol facts independently verified against cited documentation current as of August 2026.
This article is educational and general in nature, not financial or investment advice. Cryptocurrencies and cross-chain deposits carry real risks, including wrong-network sends, bridge-contract risk, unrecoverable sub-minimum deposits, phishing, and the chance of losing funds. Nothing here is a recommendation to deposit, withdraw, bridge, buy, sell, or hold any asset, or to use any venue or wallet. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.