Deposit with Hyperunit (cross-chain crypto)

If you hold crypto on its native chain — Bitcoin, Solana, Ethereum, Avalanche, Monad, Plasma, Zcash, and others — Hyperunit bridges it directly into your Hyperliquid account. You send from your wallet on the source chain; Unit's guardian network mints the wrapped asset on HyperCore.

Available for Hyperliquid only.

How it works

1. Open the deposit modal and pick Hyperliquid → Crypto.
2. Pick an asset (e.g. BTC). Aura asks Unit for a deposit address dedicated to you.
3. Before revealing the address, Aura verifies at least 2 of 3 guardian signatures server-side. If verification fails, no address is shown.
4. You must tick two acknowledgement checkboxes before the address appears:
   • Sub-minimum deposits are burned
   • The address is ONLY for the specified network
5. Scan the QR or copy the address into your wallet. Send from the matching chain.
6. After the required confirmations on the source chain, Unit mints the asset on your Hyperliquid account.

The biggest mistake: wrong chain

Every supported asset has a specific network. BTC means Bitcoin mainnet — not Lightning, not Liquid, not WBTC on Ethereum. The network caution banner above the address tells you exactly what is and isn't accepted.

Funds sent on the wrong chain cannot be recovered. The acknowledgement checkboxes exist because this is the most common way users lose money. Read them.

Minimum deposits

Each asset has its own minimum. Sending below the minimum burns the deposit — it's not returned. The minimum and expected ETA are shown next to the address.

A few assets (ZEC, AVAX, VIRTUAL) have no published minimum. The UI skips the minimum banner in that case, but network fees still apply.

Common errors

"Sign in to generate a bridge address"

You're not signed in. Log in first — bridge addresses are tied to your Hyperliquid account.

"Unit address generation failed" / "Guardian signature threshold not met"

Unit's guardian network is down or rotated keys unexpectedly. This is a server-side issue Aura cannot work around. Wait a few minutes and retry; if it persists, contact support so we can update our pinned guardian keys.

"Testnet mode — send testnet coins only"

You're on a QA or dev build. Real BTC/ETH/SOL sent here will be lost because testnet guardians can't mint on mainnet Hyperliquid. Switch to the production app before depositing real funds.

Funds sent but nothing arrived on Hyperliquid

Work through this in order:

1. Confirm the transaction on the source chain. Use a block explorer (mempool.space for BTC, Solscan for SOL, Etherscan for ETH, etc.). Wait for the confirmation count shown in Aura's address panel.
2. Check amount vs. minimum. If you sent below the minimum, the funds are gone.
3. Check the chain. If you sent from the wrong chain (e.g. WBTC on Ethereum instead of native BTC), the funds are on a chain Unit can't see.
4. Wait the ETA shown on the address panel. Some chains take 30+ minutes for enough confirmations.
5. If the source transaction confirmed with a valid amount on the right chain, but the mint never appeared in Hyperliquid: contact Hyperunit support with the source transaction hash. They own the mint leg.

"I regenerated a new address, is my old one still valid?"

Yes, but don't reuse it long-term. Addresses are generated per (asset, your wallet) pair and are stable while Unit's guardians are stable. Treat them as session-scoped and regenerate for each new deposit for safety.

Supported assets

The supported list changes as Hyperunit adds new rails. At time of writing: BTC, ETH, SOL, XPL (Plasma), MON (Monad), ZEC, AVAX, ENA (Ethena), VIRTUAL (Base), PUMP (Solana SPL), FART (Solana SPL), and a few more. The picker in the deposit modal is authoritative.

After the deposit lands

The asset arrives on HyperCore as its Unit wrapper (uBTC, uSOL, etc.). You can trade it on Hyperliquid spot markets or use it as perp collateral in unified account mode. If you want USDC instead, swap on Hyperliquid after the deposit settles.