You send HyperCore HYPE by copying the receiver's Hyperliquid address, choosing Send not Withdraw, signing, then waiting for one committed block so their spot balance credits. If that address is new, the first inbound takes 1 quote token of activation. A BloFin withdrawal is a different form, not this Send.
You copy a friend's HyperCore address from that friend's official app, not from chat. You sign Send for 25 HYPE. One committed block later, their spot line shows the credit. The friend is new on HyperCore, so that first inbound also takes 1 quote token. You did not press Enable Trading, and you did not wait on a later leader to undo the send.
The click that looks like a cash-out can still be a HyperCore Send. Those two jobs do not share a destination.
How to send HYPE on HyperCore
A HyperCore spot send is a short signed action. HyperCore is Hyperliquid's onchain trading environment. Pick the receiver's Hyperliquid address. Choose Send. Size it. Sign. Wait for one committed block. Then read their spot credit.
- Confirm both sides already have a HyperCore session. Hyperliquid wallet and account setup is that login: Enable Trading as a gas-less sign, or a 6-digit email code. If the friend is still staring at Connect, there is no receive view yet.
- Copy the address from inside the friend's official app. Write the first six and last six characters on paper. Do not take a string from chat.
- On your Trade or Portfolio page, open Send, not Withdraw, and not Transfer to/from EVM.
- Paste. Match the paper. Size 25 HYPE, and leave a sliver if the friend is new and may need a quote token nearby.
- Sign the pop-up. Read the destination. If the origin is a look-alike domain, close it.
- Wait for one committed HyperBFT block. HyperBFT is Hyperliquid's consensus. The send is chain state after that commit.
- Ask the friend to refresh spot. The credit is the payoff. If they are new, the first inbound also bills 1 quote token.
You do not need a builder payload to do this. The signed action behind the button is a spot send to a 42-character destination. That is enough. You do not need the JSON. You do need the Action label to say Send.
One-block here is the wait. A HyperCore send, like a rest or a fill, sits in the same committed list. A later leader does not un-send your 25 HYPE. How to buy HYPE already covered native spot as a real door. A Send is how that HYPE leaves one HyperCore account and lands on another.
Match the paper characters before you sign. A clean Send modal does not fix a poisoned paste.
How Send differs from Withdraw
The Portfolio Action column is the tell after you click. Send Spot is Hyperliquid-to-Hyperliquid. Withdrawal leaves this chain. Read that label before you treat the click as a cash-out. A CEX deposit string will eat a Send the venue cannot book as a withdrawal.
Your 25 HYPE is a Send. The friend's spot balance is the destination. A Withdraw would have asked for a chain and a CEX deposit string. Official support splits those jobs on the Portfolio page. Check the Action column. If it says Send Spot, or Send USDC (Perps Wallet), you did not withdraw. Send moves funds to another account on the Hyperliquid blockchain. There is an explicit warning message reminding users not to use Send to withdraw to a CEX. Send is used to send tokens to another account on the Hyperliquid blockchain. It is not to withdraw to another blockchain (source: Hyperliquid Docs, Withdrawal has not arrived).
A third control sits next to those two. Transfer to/from EVM moves HYPE between your HyperCore spot and your HyperEVM balance. It is still you. It is not a friend. It is not a CEX. A friend's Portfolio will not list that move as Send Spot, because they were not the destination. How to send and receive crypto is the generic network-match habit. Here the Hyperliquid-specific fork is the Action label, not a memo field.
Those three clicks sort like this. A HyperCore Send of spot HYPE moves coins to another Hyperliquid account and lands on their HyperCore spot. An off-chain Withdraw leaves HyperCore for another network and lands at a CEX or other chain. A spot Transfer into HyperEVM stays with you, just on the other half.
The public spot instruments feed on August 21, 2026 still returns a live HYPE-USDT SPOT row, listed May 30, 2025 13:30 UTC (source: BloFin, SPOT instruments). That HYPE/USDT listing leaves through withdrawing from BloFin. It never becomes a HyperCore Send. HYPER/USDT on the same venue is Hyperlane. HYPER is the native token for the Hyperlane protocol (source: Hyperlane Docs, Protocol economics). If the chart header says Hyperlane, stop. You are not in a HyperCore send at all.
How to receive HYPE on a new address
Receiving HYPE is the same Send, viewed from the other side. You publish a HyperCore address you control. You wait. Spot credits after one committed block. If your account is new, the first inbound that treats you as destination still takes 1 quote token.
The friend in the 25 HYPE walk had never been a destination. Official activation is blunt, and it is a different click from Enable Trading. Enable Trading, or the 6-digit email code, is the login the wallet-setup walk already covered. Activation is the first credit. "This applies regardless of the asset being transfered to the new account." (source: Hyperliquid Docs, Activation gas fee). The source keeps that spelling. A first inbound of HYPE still bills 1 USDC or 1 USDT as the quote-token example the page names. The docs do not offer a HYPE-only substitute.
A wallet help page can surface the same fee as a sender-side Transfer Error. Gem Wallet tells users that zero network fees apply only when sending to addresses that are already active or have been used before (source: Gem Wallet, Hyperliquid). That line is a vendor fence, not a second protocol. Official billing sits on the destination. A send can still fail until a quote token is there to pay the one-time fee. Both of those can be true at once. Gem's 10 USDC swap minimum is a swap floor on that app, not the activation.
If you are the receiver, say which half you can actually open. HyperCore spot is one balance. HyperEVM is the other. Publishing a 0x string without naming the half is how a friend Sends to the side you are not watching. What a cryptocurrency wallet is is the generic tool. The receive job here is narrower: one HyperCore address, copied from the official app, after the session exists.
You do not need a public announcement. You need a string the sender can check against your screen.
HyperEVM gas and the HYPE-only address
HyperCore spot and HyperEVM are two balances on one chain. Credit on one side does not appear on the other until you transfer. HyperEVM sends spend HYPE as gas. A HyperCore Send to a friend does not. Name the half before you paste, or you will watch the empty side.
Your 25 HYPE credited the friend's spot. It did not pay an EVM app. If the friend later wants gas on chain ID 999, they move a slice with Transfer to/from EVM, or they send HYPE to the HYPE system address. As the native token on HyperCore, HYPE also links to the native HyperEVM balance rather than an ERC20 contract (source: Hyperliquid Docs, HyperCore HyperEVM transfers). That native landing is why a HyperEVM wallet can show HYPE as the currency and still show zero after a HyperCore Send. You are looking at the other half.
The gas bill sits on the side you leave. Sending from your Spot balances to the HyperEVM costs gas in HYPE on HyperCore (Spot) (source: Hyperliquid Docs, How to use the HyperEVM). The other direction spends HYPE on HyperEVM. Independent onboarding makes the same test habit. Whenever you try a route for the first time, send a tiny test amount before moving size (source: HyperAcademy, HyperEVM onboarding).
The HYPE system address is 0x2222222222222222222222222222222222222222. It is HYPE only. Other spot assets have their own transfer addresses. Send the wrong asset there and the docs say it is lost. If you already tapped Transfer to/from EVM by mistake, the coins are usually still yours. You will need HYPE on the EVM for gas. If you transferred something other than HYPE to the EVM, you can buy HYPE on Spot and use Transfer to/from EVM to move a gas slice (source: Hyperliquid Docs, Accidentally transferred to HyperEVM).
Name HyperCore spot unless you actually meant HyperEVM gas. Deposits from Arbitrum or another chain are a later job.
How to confirm a send landed
Confirmation is a table plus a screen, not a chat screenshot. On Portfolio, open Deposits and Withdrawals. Read the Action. Then ask the receiver to show the same address's spot line. If those two disagree, stop sending size until both views match.
Wait until the friend's spot shows 25 HYPE, or 25 minus the first-inbound quote token if this was their first credit. A helper who texts that it is done is not the table. Official support's first check is that Action column. Send Spot means Hyperliquid-to-Hyperliquid. Withdrawal means off-chain. If Status on a real Withdrawal says Completed, the explorer link next to the timestamp is the destination check. If it says Failed on a Unit-managed asset, that is a different team, not a Send retry.
The receiver should match the first six and last six characters they published. Clipboard hijacking is the paste version of a missed check. Compare paper to screen before you treat the credit as final. One-block finality is fast. It is also one-way. Nobody unwinds a Send because the paste was wrong.
If the friend is watching HyperEVM and you used HyperCore Send, the EVM view stays empty. That is the wrong half, not a missing chain. Flip to spot. If it is still empty after a committed Send, you have the wrong address.
Action label, then receiver spot, then paper characters. You do not need an explorer lesson to pass those three.
Using Send to leave Hyperliquid
The riskiest step is Send aimed at a CEX deposit address, or at the wrong Hyperliquid half. Official support already warns you against aiming Send at a CEX deposit string. After that click, only that venue's address can open the credit, and only if they later integrate this chain.
You do not cash out through Send. If you wanted coins on BloFin, you would use the venue withdrawal form, pick the network that venue credits, and treat that as a CEX job. How CEX wallets actually hold coins is why a password reset reaches BloFin and never reaches HyperCore. A HyperCore Send to a BloFin deposit string is not that form. Support on either side cannot un-send it into a Funding account.
The other loss is a look-alike Send modal. Bookmark the official app. Read the origin. A poisoned paste that swaps the middle characters will still look like your friend's prefix. That is why the paper check exists. Hardware helps later storage. It does not make a fake domain honest.
If the destination published HyperEVM and you Sent on HyperCore, the coins can sit in the half they are not watching. That is recoverable if they control both halves and have gas. It is not recoverable if you Sent to a CEX string. Stop at the warning. A tiny test on a new route is cheaper than a support chat that cannot reverse a committed Send.
What self-custody means is the key job in plain terms. How to store HYPE safely is the longer split between an exchange venue and a key you hold. Seed phrases stay in that custody walk. A Send only needs the fork named so you do not treat a HyperCore credit as already-safe storage.
Send checklist
Before you sign size, check six things: official URL, Send not Withdraw, HyperCore address not a CEX string, paper characters, new-destination quote token, and which half. Skip one and you fund the wrong venue. Run the list out loud, then sign, not the other way around.
- Did you type the official app and bookmark it, or follow a sponsored result?
- Does the control say Send, rather than Withdraw or Transfer to/from EVM?
- Is the destination a Hyperliquid account the receiver can open, or a CEX deposit tag?
- Do the first six and last six characters match the paper copy from their screen?
- If they are new, is 1 quote token available for that first inbound?
- Did you mean HyperCore spot, or HyperEVM gas on chain 999?
Run the list out loud before you sign 25 HYPE. If two answers are fuzzy, send a tiny test first. Independent onboarding already treats a first-time route that way. The checklist is short on purpose. You do not need a system-address formula to pass it.
Suppose the last six characters came from chat, and you could not say whether the friend had ever been a destination. Close the modal. Copy from the friend's screen again. Send 0.2 HYPE first. The six checks are the last chance to catch a clone URL, a Withdraw label, or a CEX tag before one committed block makes the paste permanent.
The URL check is first because every later answer is worthless on a clone. The Action check stops a Withdraw dressed as a Send. The CEX check is the honest exit: if you wanted BloFin, open that withdrawal form instead. None of those six answers require a first trade.
After a send credits
After spot credits, the next jobs are optional and separate. Buying more HYPE, keeping it on an exchange, and holding the key each wait until this Send is actually done. Do not treat a BloFin balance as already-sent HyperCore HYPE.
Session exists. Address copied from the official app. Send, not Withdraw. One committed block. Receiver spot. If they were new, 1 quote token came off that first inbound. Native spot still buys HYPE against USDC after a HyperCore deposit, which is a later purchase job. BloFin still lists the hyphenated pairs you can hold without this Send. Creating a BloFin account is that CEX door.
If the next click is a buy, use the venue-aware purchase path rather than inventing a new one. If the next click is storage, decide who holds the key on purpose. If the next click is HyperEVM gas, move a test slice and leave a buffer. Vaults and builder markets are other jobs. They are not how you Send 25 HYPE.
The friend's spot line after a first inbound will not equal your 25 if the quote token came off that credit. Do not chase the missing 1 quote token on an Arbitrum explorer. It never left HyperCore. If they immediately Transfer the whole balance to HyperEVM, they can strand themselves without gas on the way back. Leave a HYPE sliver on spot until they know they need chain 999.
What matters here is the Action you signed, not the pretty portfolio chart. If you only needed a BloFin withdrawal, you never needed this Send. If you needed a friend's HyperCore spot, a CEX password was never going to write it.
Frequently asked questions
If a Transfer Error fires on a brand-new address, did I pick the wrong chain?
Usually not. A Transfer Error on a first send is the wallet telling you the destination has never been a HyperCore destination. Official activation still bills 1 quote token on that first inbound, whether you sent HYPE or another asset. Gem Wallet also lists a 10 USDC minimum for its own swap, which is not the activation fee. If the Action already said Send, and the 0x string matches the friend's HyperCore screen, stay on this chain and free a quote token. A chain mismatch looks like HyperEVM versus HyperCore, or a CEX tag, not like this error.
If I pasted a Binance HyperCore deposit tag, is a Hyperliquid support chat the recovery path?
No. A Hyperliquid chat cannot rekey a string that venue already controls. Recovery sits with that exchange: they either integrate this chain and book the credit, or they run their own recovery process. Opening a Hyperliquid chat that asks them to move the coins into your Trade account is the wrong counter. Write the venue, keep the tx hash, and treat Hyperliquid support as confirmation of the Action label, not as a clawback.
Is one-block finality the same as a CEX completed badge?
No. One committed HyperBFT block is chain state for a HyperCore Send. A CEX completed badge means that venue finished its own checks and broadcast, which can lag minutes and is not a Hyperliquid height. If Portfolio says Send Spot, do not wait on a BloFin badge. If you used BloFin's withdrawal form, do not wait on a HyperCore spot line. The two waits do not substitute. Read the Action that actually fired.
If I Send 1 USDC to a new address first, then Send HYPE a minute later, does the HYPE Send bill another quote token?
No. Official activation is the first transaction that treats that account as destination, not every inbound. A 1 USDC Send that lands first can be that transaction. The later HYPE Send to the same address is a second destination credit, so it should not bill the one-time fee again. Confirm the friend's spot shows the USDC before you size the HYPE. If both sit in one unconfirmed batch and the friend is still empty, wait for the first credit, then send HYPE.
Can a receiver publish a HyperEVM address to a venue that only credits HyperCore spot?
They can publish it. The venue will not credit it as HyperCore spot. Some venues support HyperCore HYPE and not HyperEVM. A 0x string is not proof of the half. The receiver should copy the address from the half the venue names, then test a tiny amount. If they only wanted a BloFin pair, they never needed a HyperEVM receive string.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated August 2026. Primary sources include Hyperliquid support on Send versus Withdraw, activation-gas docs, HyperCore to HyperEVM transfer pages, HyperAcademy onboarding, Gem Wallet's Hyperliquid send notes, Hyperlane protocol economics, and BloFin's public spot instrument API. Protocol and listing facts checked against those cited pages as of August 2026.
This article is educational and general in nature, not financial or investment advice. Cryptocurrencies like HYPE carry real risks, including price volatility, venue failure, phishing, signature mistakes, and the chance of losing funds. Nothing here is a recommendation to buy, sell, hold, or send HYPE. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.