Hyperunit Questions Answered

Hyperunit is a deposit and bridging protocol built on top of Hyperliquid. It lets you bring assets from external chains — starting with Bitcoin — into the Hyperliquid trading environment without going through a centralised exchange. The protocol handles the conversion and delivery steps automatically once you initiate a deposit.

Think of it this way: Hyperliquid is a high-performance perpetuals exchange, but getting native BTC onto it has historically required manual steps. Hyperunit removes that friction entirely.

At launch, Hyperunit's protocol supports Bitcoin (BTC) as the primary deposit asset. The team has indicated that additional assets will follow as the bridge infrastructure matures. The app interface at the main platform always shows the current list of supported tokens and networks, so that's the most reliable place to check.

Each supported asset has its own minimum deposit amount — for BTC the minimum is 0.0003 BTC. Deposits below this threshold won't be processed.

The estimated time shown in the app is around 31 minutes for a BTC deposit. That window accounts for Bitcoin block confirmations (typically 3–6 blocks depending on the current fee environment) plus the time the Hyperunit platform needs to verify and relay the transaction on the Hyperliquid side.

During periods of high Bitcoin mempool congestion the actual time can be longer. If you set your transaction fee too low, miners may deprioritise your transaction and the deposit will take significantly longer than the estimate. Using the fee recommendation shown at the time of deposit reduces that risk.

The estimated network cost — displayed as roughly $1.89 for a BTC deposit at current rates — reflects the on-chain miner fee you pay on the Bitcoin network to get your transaction included in a block. This is not a Hyperunit fee. The protocol itself charges a separate service fee, which is displayed during the deposit flow before you confirm.

Network costs fluctuate with Bitcoin mempool activity. The app refreshes the estimate regularly, but because Bitcoin fees can spike quickly, the figure you see is always approximate.

Security is central to how the Hyperunit platform is built. The smart contracts and bridge logic have undergone third-party security reviews, and the team publishes audit reports in the documentation at docs.hyperunit.xyz. That said, no protocol is risk-free — bridge infrastructure carries inherent complexity, and you should only deposit amounts you're comfortable with given that context.

The protocol does not hold user funds in a custodial way beyond the time needed to process a transaction. Once a deposit completes, assets move into your connected Hyperliquid account.

You need a wallet that can connect to the Hyperliquid app — MetaMask, WalletConnect-compatible wallets, and several hardware wallets work via the Connect button on the main interface. On the Bitcoin side, you just need a regular BTC wallet to send from; Hyperunit generates a one-time deposit address for each transaction so no special Bitcoin wallet integration is required.

Make sure the wallet you connect is the one you want assets delivered to. The "To" address shown during the deposit flow is your connected Hyperliquid wallet — you can't redirect funds to a different address mid-flow.

Yes. The interface has both a Deposit tab and a Withdraw tab. The withdraw flow works in reverse: you specify the amount you want to send back to a Bitcoin address, confirm the transaction from your Hyperliquid wallet, and Hyperunit handles the outbound transfer. Withdrawal times and fees follow a similar structure to deposits — Bitcoin confirmations apply on the receiving end.

Minimum withdrawal amounts apply just as they do for deposits. Check the withdraw tab directly in the app for the current minimums, since they can change as the protocol updates.

Deposits that take longer than expected are almost always the result of low Bitcoin transaction fees or unusual network congestion. The Transactions tab in the app shows the status of all your recent operations. If a transaction shows as pending for an extended period, the first step is to check whether your Bitcoin transaction has enough confirmations on a block explorer like mempool.space.

If the on-chain transaction confirmed but assets haven't appeared in your Hyperliquid account after a reasonable wait, use the Support contact in the app. The team asks that you include your transaction hash and deposit address when reaching out — it speeds up investigation significantly.

Centralised exchanges require KYC, impose withdrawal limits, and add an extra custodial layer between you and your assets. Hyperunit cuts out the middleman. You keep control of your keys throughout the process — the protocol only touches your funds during the active bridge transaction, not before or after.

There's also a speed argument. CEX withdrawals can take hours if compliance checks trigger a manual review. A well-timed Hyperunit deposit during low-fee periods on Bitcoin is often faster end-to-end. Plus, you're depositing directly into a non-custodial trading position on Hyperliquid rather than first sending to a hot wallet on a centralised platform.

Hyperliquid runs its own high-performance L1 with native perpetuals clearing. Hyperunit acts as a bridge layer that wraps incoming BTC into the format Hyperliquid accepts — specifically the USDC-margined or BTC-spot representation used on the exchange. The bridging logic monitors incoming Bitcoin transactions, confirms them, then calls the relevant Hyperliquid deposit function to credit your account.

The team behind Hyperunit built the integration to work with Hyperliquid's native API rather than relying on third-party bridge infrastructure. That design choice means fewer external dependencies and a tighter security perimeter around user funds during transit.

The Hyperunit platform's terms of service define which jurisdictions are permitted. You should read those carefully before connecting a wallet. The app does perform geolocation checks and may restrict access from certain regions. This is a legal and compliance decision by the team — the protocol itself is non-custodial, but the front-end interface applies access controls.

If you're in a restricted region and attempt to connect, the app will display a message explaining the restriction rather than silently failing.

The Revert page at /revert is a recovery tool for edge-case situations where a deposit transaction needs to be reversed or redirected — for example if you sent to a deposit address after the address expired, or if there was an issue with the destination account setup. It's not a standard withdrawal interface; it's specifically for resolving failed or incomplete deposit flows.

Most users will never need the Revert page. Normal withdrawals go through the Withdraw tab on the main app.

Yes. Hyperunit's protocol charges a service fee on top of the Bitcoin miner fee. The service fee is displayed in the deposit confirmation screen before you send any funds — you always see the full cost breakdown before committing. The fee structure covers the operational costs of running the relay infrastructure and on-chain verification steps.

Fee rates can change as the protocol evolves. Checking the app at the time of your deposit gives you the current rate. Historical fee changes are documented in the Docs.

Full documentation is available at docs.hyperunit.xyz. It covers the technical architecture, supported assets, fee schedules, API references, and audit reports. If you want to understand the bridge mechanics at a deeper level — or you're building something on top of Hyperunit — the docs are the right place to start.

You can also find context about the broader Hyperliquid trading environment at the Hyperliquid app directly. For background on the Hyperunit team and approach, see the info page.