USDC missing on Hyperliquid: HyperCore, HyperEVM and perps balances

Record sender and receiver addresses, asset, token contract where relevant, network, net amount and TXID. Then identify your Hyperliquid access method: connected wallet, email account or another app. The active address must match the funded account. Switching browsers or connecting another wallet can display a valid account different from the one you funded.

A transfer to your HyperEVM address does not automatically become spendable HyperCore funds because the wallet identifier matches. Connecting does not import every asset from other networks either. For an ordinary first deposit, use the Hyperliquid walkthrough; here we trace an already submitted transfer and distinguish its possible destinations.

Current Hyperliquid documentation distinguishes Standard and Unified. Standard separates Spot, Perps and individual DEX balances; Unified has a per-asset balance shared with spot and supporting cross-margin positions in that currency. The app defaults to Unified. Do not prescribe a Spot-to-Perps transfer as a universal fix: identify the account’s actual mode first.

For technical queries, Unified reports balances and holds in spot state; reading an individual perpetual DEX state in isolation can mislead. For an interface user, the practical check is asset, main account or subaccount, and committed funds—not experimenting with account modes. Changing margin arrangements while positions are open can change how exposure is backed.

Circle documents transfers from other chains into HyperEVM and then HyperCore through CoreDepositWallet. The source can burn USDC, followed by attestation and destination minting, with forwarding where required. A confirmed burn establishes that stage only. It does not by itself establish completed minting or final trading credit.

In this integration, Circle distinguishes native USDC held in the HyperEVM contract from the protocol-level credit reflected by HyperCore. The selected destination can be perpetuals or spot; a successful EVM transaction alone does not establish which balance was funded. From HyperEVM, the documented route uses specific contract functions rather than an improvised transfer to a system address.

Mainnet and testnet use separate contracts. Developer examples may use test funds and are not instructions to paste addresses into a real withdrawal. For diagnosis, follow the initiating tool’s history and reconcile identifiers for each stage. Do not execute contract calls or pay another bridge simply because the first reference does not yet show the expected balance.

Hyperliquid’s deposit FAQ separately describes Across-managed email funding and connected-wallet funding. It lists Arbitrum, Base, Ethereum and Polygon USDC for email and Arbitrum for the documented wallet route. An interface-specific list neither invalidates Circle’s CCTP integrations nor lets you use any route with an address generated for a different method. Follow the current instructions for the initiated operation.

Minimums and error handling are route-specific too. The FAQ warns that wallet deposits below USDC 5 are lost; described email-wallet returns for certain mistakes or amounts are not a universal recovery guarantee. Do not use a tiny test without checking its threshold. USDC returned to an email wallet is not necessarily perpetual margin, so inspect that wallet’s address and history.

• No source TXID: inspect authorisation, queue or withdrawal status with the sender.
• Failed TXID: retain the error and check the source balance before creating another transfer.
• Confirmed transfer or burn: identify network and receiver, then mint or forwarding status where used.
• HyperEVM balance: inspect USDC and HYPE gas; do not assume it is already spendable on Core.
• HyperCore credit: check Standard/Unified mode, subaccount, margin asset and funds held by orders or positions.

Hypothetical example: 100 USDC leaves a chain and the explorer confirms the burn. A missing destination mint points investigation toward that route and its attestation. If 100 is already on HyperEVM but the trading panel shows zero, identify whether a Core deposit was requested and completed. These are different diagnoses; changing accounts or sending another 100 does not finish the first instruction.

Prepare access method, affected address, asset and contract, networks, amount, time, source TXID and bridge or destination references. State the last verified stage and which panel lacks the balance. Contact help through the tool actually used; a private message from a supposed rescuer establishes neither technical access nor authority to move funds. Reading a TXID requires no backup or private key.

Recovery and a universal timeframe cannot be promised. Once funds are located and their availability understood, the Hyperliquid review and existing access route can support ordinary use. That access is not a rescue service. For another sender-to-receiver workflow, see platform transfers and withdrawal to a personal wallet.