How to Send Bitcoin to Hyperliquid
Rift Research
Last updated
TLDR: Bitcoin does not exist as a native UTXO on Hyperliquid. Every path is a send that lands as a representation or a swapped asset. Rift is an aggregator with best price execution. It includes Unit and the other inbound venues, adds 0 fee, and selects the best live path automatically.
Calling this a “bridge” is fine. The user action is still a send of BTC toward a destination address or deposit flow.
Official inbound rail: Unit
Unit is the purpose-built lock-and-mint path into Hyperliquid spot. Guardians run a 2-of-3 MPC network. App: app.hyperunit.xyz.
Unit’s own table (confirm live before you send):
- Bitcoin minimum has been published at 0.0003 BTC.
- Bitcoin confirmations: 3+, on the order of 30 minutes or more.
- “Transactions below the minimum amounts cannot be processed.”
- “Only send supported assets to your Unit deposit address.”
Sources: Supported assets, API / confirmations.
A “seconds” quote is not describing the Bitcoin confirmation leg.
Other options, then Rift
| Route | What you get | Watch |
|---|---|---|
| Unit direct | 1:1 inbound representation | Minimums, confirmations, guardian model |
| Native venue then inbound | BTC → ETH/USDC on THORChain / Chainflip / Garden, then into HL | Two sends, sometimes a better all-in print |
| Other aggregators | Same job with their fee model | LI.FI / Socket markup |
| Rift | Best live path among included venues, 0 added fee | Extra hop gas vs going direct to a known winner |
Rift supported chains include Bitcoin and Hyperliquid. If Unit is the winner, Rift gives you Unit’s rate with no Rift markup. If a two-step path wins after fees and time, you get that path.
Go direct to Unit only when you already know it is the only viable inbound rail for your size.