# Table of Contents - [About Unit | Unit](#about-unit-unit) - [Team | Unit](#team-unit) - [Deposit | Unit](#deposit-unit) - [Withdraw | Unit](#withdraw-unit) - [API | Unit](#api-unit) - [Security | Unit](#security-unit) - [Components | Unit](#components-unit) - [Overview | Unit](#overview-unit) - [Generate Address | Unit](#generate-address-unit) - [Key Addresses | Unit](#key-addresses-unit) - [Estimate Fees | Unit](#estimate-fees-unit) - [Withdraw Queue | Unit](#withdraw-queue-unit) - [Mainnet | Unit](#mainnet-unit) - [Withdrawal Lifecycle | Unit](#withdrawal-lifecycle-unit) - [Deposit Lifecycle | Unit](#deposit-lifecycle-unit) - [Testnet | Unit](#testnet-unit) - [Token Metadata | Unit](#token-metadata-unit) - [Token Metadata (Testnet) | Unit](#token-metadata-testnet-unit) - [Guardian Signatures | Unit](#guardian-signatures-unit) - [How do I get in touch with Unit? | Unit](#how-do-i-get-in-touch-with-unit-unit) - [Operations | Unit](#operations-unit) - [How do fees on Unit work? | Unit](#how-do-fees-on-unit-work-unit) - [How long does a deposit/withdrawal take? | Unit](#how-long-does-a-deposit-withdrawal-take-unit) - [What type of Bitcoin deposit address does Unit derive? | Unit](#what-type-of-bitcoin-deposit-address-does-unit-derive-unit) - [Regulatory Compliance | Unit](#regulatory-compliance-unit) - [Where's my transaction? | Unit](#where-s-my-transaction-unit) - [Privacy Policy | Unit](#privacy-policy-unit) - [Can I generate multiple deposit addresses for my Hyperliquid wallet? | Unit](#can-i-generate-multiple-deposit-addresses-for-my-hyperliquid-wallet-unit) - [Terms of Service | Unit](#terms-of-service-unit) - [Is my unique deposit address permanent? | Unit](#is-my-unique-deposit-address-permanent-unit) - [FAQ | Unit](#faq-unit) --- # About Unit | Unit [](https://docs.hyperunit.xyz/#what-is-unit) What is Unit? --------------------------------------------------------------- Unit is the asset tokenization layer on Hyperliquid, enabling seamless deposits and withdrawals for a wide range of assets. Our first integration allows major crypto assets (e.g. BTC, ETH, & SOL) to flow between Hyperliquid and their native blockchains. Built from first principles, Unit's architecture is designed exclusively for Hyperliquid. With Unit, Hyperliquid users can: * Deposit _BTC, ETH, or SOL_ from their personal wallet or exchange account, directly to Hyperliquid. * Trade, transfer, or otherwise utilize these major assets, along with existing ones, on Hyperliquid's spot order book. * Withdraw assets directly to their preferred address on the respective asset’s native blockchain. * * * ### [](https://docs.hyperunit.xyz/#unlocking-new-opportunities) Unlocking New Opportunities Bringing major spot assets to Hyperliquid is a major milestone, with several exciting possibilities: * Unified trading experience: traders can access both spot and derivatives markets within a single, integrated platform, meeting all their trading needs directly on Hyperliquid. * Multiple new capital onramps: send spot from any supported native source chain and sell in the spot order book to access USDC. * Portfolio margin: cross margining for the major assets; enhancing capital efficiency and potential on exchange-wide volumes. * On-chain spot-futures basis trades. * Options: spot delta hedging + real-time settlement of options. * Efficient CLOB Settlement for asset liquidations within DeFi protocols on the Hyperliquid EVM. * On-chain, verifiable treasury management for protocols and DAOs. Spot trading and settlement have long been some of the most requested features for Hyperliquid. With **Unit**, these capabilities are now a reality. * * * _If you are interested in building with Unit, see the_ [_Developers_](https://docs.hyperunit.xyz/developers/api) _section._ [NextTeam](https://docs.hyperunit.xyz/unit/about-unit/team) Last updated 4 months ago --- # Team | Unit **Unit** is a research and development collective dedicated to advancing the Hyperliquid ecosystem. The core team members bring expertise from HRT, Jump, Fortress, and cyber units. _Unit's mission is to build foundational primitives that drive the growth and utility of Hyperliquid._ [PreviousAbout Unit](https://docs.hyperunit.xyz/) [NextDeposit](https://docs.hyperunit.xyz/how-to/deposit) Last updated 1 month ago --- # Deposit | Unit With **Unit**, depositing assets into Hyperliquid is as simple as a transfer. Below we describe how it works, with a step-by-step guide for depositing Bitcoin (BTC) to Hyperliquid. ![](https://docs.hyperunit.xyz/~gitbook/image?url=https%3A%2F%2F1996930769-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F41RTutUTr9Yn1SkWRs3v%252Fuploads%252FobOFVJ8ecxxmxOvsyDod%252FDeposit%2520to%2520Hyperliquid.png%3Falt%3Dmedia%26token%3D48b9d274-ae18-4074-9501-650837d62f45&width=768&dpr=4&quality=100&sign=8c29946&sv=2) Unit deposit flow * * * ### [](https://docs.hyperunit.xyz/how-to/deposit#how-to-deposit-btc) How to Deposit: BTC 1 ### [](https://docs.hyperunit.xyz/how-to/deposit#connect-wallet-and-select-asset) Connect Wallet & Select Asset Navigate to the [Hyperliquid](https://app.hyperliquid.xyz/portfolio) or [Unit](https://app.hyperunit.xyz/) UI and connect your Hyperliquid wallet. In the "Deposit" tab, select "Bitcoin". 2 ### [](https://docs.hyperunit.xyz/how-to/deposit#retrieve-deposit-address) Retrieve Deposit Address Your unique Bitcoin deposit address will be displayed. This address was securely generated by Unit's MPC Guardian Network, and is permanently tied to your address on Hyperliquid. The integrity of this address may be verified by its Guardians' signatures. 3 ### [](https://docs.hyperunit.xyz/how-to/deposit#transfer-asset) Transfer Asset Simply transfer Bitcoin to your Unit Bitcoin deposit address, from wherever you hold BTC. 4 ### [](https://docs.hyperunit.xyz/how-to/deposit#done) Done! You can track your BTC transfer using a Bitcoin explorer such as [mempool.space](https://mempool.space/) . Upon the finalization of this transfer on the Bitcoin network (2 block confirmations), the Unit protocol will transfer the corresponding BTC amount to your address on Hyperliquid. * * * _For detailed information on how to deposit using the Guardian Network, please visit the_ [_Developers section_](https://docs.hyperunit.xyz/developers/api) _._ [PreviousTeam](https://docs.hyperunit.xyz/unit/about-unit/team) [NextWithdraw](https://docs.hyperunit.xyz/how-to/withdraw) Last updated 8 months ago --- # Withdraw | Unit Unit's withdrawal process is simple by design - mirroring the deposit process. Below is a step-by-step guide for withdrawing BTC from Hyperliquid to your desired Bitcoin address. ![](https://docs.hyperunit.xyz/~gitbook/image?url=https%3A%2F%2F1996930769-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F41RTutUTr9Yn1SkWRs3v%252Fuploads%252FxiDSYfS82mlmia8hzA4B%252FWithdraw%2520from%2520Hyperliquid%2520%281%29.png%3Falt%3Dmedia%26token%3D18fb9149-3e7d-4c81-9e22-4cf4b2b520cf&width=768&dpr=4&quality=100&sign=af0b2403&sv=2) * * * ### [](https://docs.hyperunit.xyz/how-to/withdraw#how-to-withdraw-btc) How To Withdraw: BTC 1 ### [](https://docs.hyperunit.xyz/how-to/withdraw#connect-wallet-and-select-asset) Connect Wallet & Select Asset Navigate to the [Hyperliquid](https://app.hyperliquid.xyz/portfolio) or [Unit](https://app.hyperunit.xyz/) UI and connect your Hyperliquid wallet. In the "Withdraw" tab, select "Bitcoin". 2 ### [](https://docs.hyperunit.xyz/how-to/withdraw#enter-destination-address-and-amount) Enter Destination Address & Amount Enter the Bitcoin address to which you want to withdraw, and the desired BTC amount. Similar to deposits, the Unit protocol will generate a unique "withdrawal" address on Hyperliquid, which is tied to the destination address you entered. 3 ### [](https://docs.hyperunit.xyz/how-to/withdraw#submit-your-withdrawal) Submit Your Withdrawal Click "Withdraw" and sign the transaction from your Hyperliquid wallet. This will transfer the BTC to the Hyperliquid address corresponding to your destination Bitcoin address. 4 ### [](https://docs.hyperunit.xyz/how-to/withdraw#done) Done! Upon the finalization of the Hyperliquid transaction (~10 seconds), the Unit protocol will generate and broadcast the corresponding transfer to your address on the Bitcoin network. You can monitor the progress of this transaction directly on Unit, or on Bitcoin explorers such as [mempool.space](https://mempool.space/) . * * * _For detailed information on how to withdraw using the Guardian Network, please visit the_ [_Developers section_](https://docs.hyperunit.xyz/developers/api) _._ [PreviousDeposit](https://docs.hyperunit.xyz/how-to/deposit) [NextOverview](https://docs.hyperunit.xyz/architecture/quickstart) Last updated 8 months ago --- # API | Unit Users have the option of interacting with the protocol directly via the Unit API `https://api.hyperunit.xyz` The Unit Testnet is live on Hyperliquid Testnet, Bitcoin Signet, and Ethereum Sepolia. The testnet endpoint is hosted at `https://api.hyperunit-testnet.xyz` * * * #### [](https://docs.hyperunit.xyz/developers/api#required-confirmations) Required Confirmations The Unit protocol requires finalization on every blockchain. Chain Required Confirmations Time Approximation Bitcoin 2+ At least 20 minutes. Some transactions are subject to longer confirmation times due to additional security checks. Hyperliquid 2000 3.5 minutes Ethereum 14 3 minutes Solana 32 13 seconds Plasma 3 3 seconds [PreviousSecurity](https://docs.hyperunit.xyz/architecture/security) [NextGenerate Address](https://docs.hyperunit.xyz/developers/api/generate-address) Last updated 1 month ago --- # Security | Unit ### [](https://docs.hyperunit.xyz/architecture/security#protocol-security-measures) Protocol Security Measures A deterministic state machine underlies all protocol actions, guaranteeing that transactions follow a strict, verifiable workflow. Each Guardian independently checks blockchain data, addresses, and transaction details before consenting to proceed. The network’s endpoints are rate-limited to prevent abuse, and Guardians collectively maintain circuit-breaker policies: if malicious activity is detected, the system can pause operations until issues are resolved. ### [](https://docs.hyperunit.xyz/architecture/security#consensus-and-key-management) Consensus and Key Management Consensus relies on a 2-of-3 MPC threshold signature scheme (TSS), requiring a majority of Guardians to sign any critical protocol event. During distributed key generation, each Guardian receives an independent share of the private key, which remains encrypted at rest using KMS services and is only combined at runtime for signing in the secure enclaves. These enclaves keep key material isolated from the broader system, preserving confidentiality even if one Guardian’s environment is compromised. ### [](https://docs.hyperunit.xyz/architecture/security#communication-security) Communication Security All Guardian-to-Guardian transmissions are end-to-end encrypted to prevent tampering or eavesdropping. The relay server does not introduce additional cryptographic assumptions: it simply forwards ciphertext. Out-of-band ID checks authenticate Guardians to one another before any communication can begin, further reducing the risk of impersonation. If a relay server fails or is compromised, the network remains safe, since no key material resides on it. ### [](https://docs.hyperunit.xyz/architecture/security#build-and-runtime-integrity) Build and Runtime Integrity For runtime integrity all Guardians validate configurations via hash-based checks, preventing divergence from the expected settings. Guardian's public keys are distributed and confirmed out-of-band, making it difficult for attackers to intercept or spoof critical key exchanges. Guardians perform deployments securely after manually verifying the authenticity of the version used. ### [](https://docs.hyperunit.xyz/architecture/security#validation-procedures) Validation Procedures Because every Guardian monitors blockchain data independently and confirms the signing of transactions, no single Guardian can stealthily subvert the system. Guardians log operations for audit, enforce consistent runtime configurations, and share authenticated status updates. This distributed validation framework—where each party operates indexers, Agents, and secure enclaves—creates multiple lines of defense, enhancing overall robustness. [PreviousComponents](https://docs.hyperunit.xyz/architecture/components) [NextAPI](https://docs.hyperunit.xyz/developers/api) Last updated 8 months ago --- # Components | Unit ### [](https://docs.hyperunit.xyz/architecture/components#guardian-network) Guardian Network The Unit Protocol is supported by a distributed leader-verifier network of independent operators known as **Guardians**. Each Guardian independently runs the **Agent**, an implementation of the protocol that: * **Operates and uses blockchain indexers** for each supported chain, verifying on-chain activity and transaction finality. * **Participates in a 2-of-3 Multi-Party Computation (MPC) threshold signature scheme (TSS)**, ensuring no single Guardian can unilaterally perform operations. * **Maintains key shares** generated and stored in a distributed manner. A leader is predetermined to coordinate proposals. The leader runs a relay server for message passing only—no key material resides there. Followers independently verify all leader messages. ### [](https://docs.hyperunit.xyz/architecture/components#agent) Agent Every Guardian’s **Agent** enforces the rules and logic needed for cross-chain flows. Four main components provide structure and clarity: 1. **Chain Services** track incoming deposits, confirm finality of on-chain transactions, and build or broadcast transaction payloads. 2. A **Flow Manager** oversees a multi-step state machine enforcing strict sequencing and ensuring adherence to protocol requirements. 3. The **Consensus Service** implements t-of-n quorum rules (commonly 2-of-3), requiring Guardians to agree on critical operations before proceeding. 4. The **Wallet Manager** handles MPC-based key operations, running within secure enclaves (e.g., AWS Nitro). It stores encrypted secret shares and coordinates threshold signatures. ### [](https://docs.hyperunit.xyz/architecture/components#initial-guardian-network-participants) Initial Guardian Network Participants ![Cover](https://docs.hyperunit.xyz/~gitbook/image?url=https%3A%2F%2F1996930769-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F41RTutUTr9Yn1SkWRs3v%252Fuploads%252FqVbxBz9m2quSABxYx1rM%252FLogo%2520%286%29.png%3Falt%3Dmedia%26token%3D40f735d0-5bf1-4c85-b65f-0d69a269a17f&width=490&dpr=4&quality=100&sign=dcd91b66&sv=2) Unit ![Cover](https://docs.hyperunit.xyz/~gitbook/image?url=https%3A%2F%2F1996930769-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F41RTutUTr9Yn1SkWRs3v%252Fuploads%252FX6mRm5z3uLBQ5zfjjptQ%252FLogo%2520%2810%29.png%3Falt%3Dmedia%26token%3De2c18872-eb1c-47bc-bbdc-7bdb9675c0b3&width=490&dpr=4&quality=100&sign=e02233b5&sv=2) Hyperliquid ![Cover](https://docs.hyperunit.xyz/~gitbook/image?url=https%3A%2F%2F1996930769-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F41RTutUTr9Yn1SkWRs3v%252Fuploads%252Fe9sjyR5esAkQB3Ac4vH9%252Finfinite-field-400x400.jpg%3Falt%3Dmedia%26token%3Df830221d-9a75-47e0-ba86-e5164c6e06e2&width=490&dpr=4&quality=100&sign=ea15b89c&sv=2) Infinite Field [PreviousOverview](https://docs.hyperunit.xyz/architecture/quickstart) [NextSecurity](https://docs.hyperunit.xyz/architecture/security) Last updated 8 months ago --- # Overview | Unit Unit operates as a neutral infrastructure component within the Hyperliquid ecosystem, allowing users to deposit and withdraw major crypto assets directly to and from their spot balance on Hyperliquid's native exchange. ![](https://docs.hyperunit.xyz/~gitbook/image?url=https%3A%2F%2F1996930769-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F41RTutUTr9Yn1SkWRs3v%252Fuploads%252Fn8UszATC5DEmExfwO7er%252FDiagram.png%3Falt%3Dmedia%26token%3D2a3e4ee6-46c8-47c5-94ea-6bfb0de6d629&width=768&dpr=4&quality=100&sign=8be9f52e&sv=2) [](https://docs.hyperunit.xyz/architecture/quickstart#core-protocol) Core Protocol --------------------------------------------------------------------------------------- At the center of the Unit protocol is a distributed leader-verifier network of operators, called "Guardians". Each Guardian is independently running the "agent", an implementation of the Unit protocol developed by the Unit core team. Guardians also operate and use nodes and indexers for the native blockchains of all Unit-supported assets, enabling independent verification of blockchain data. The Guardians all participate in consensus and Multi-Party Computation (MPC) Threshold Signature Scheme (TSS) to perform protocol operations. * * * ### [](https://docs.hyperunit.xyz/architecture/quickstart#app-ui) App / UI The Unit core contributors developed an interface for users to interact with the protocol, which can be found at [app.hyperunit.xyz](https://app.hyperunit.xyz/) . This is a centralized interface maintained by the core team, and is optional in using the protocol. Users may also access the protocol on [app.hyperliquid.xyz](https://app.hyperliquid.xyz/) , or by making requests to the Guardian Network directly, as described in our developer documentation. * * * ### [](https://docs.hyperunit.xyz/architecture/quickstart#compliance-layer) Compliance Layer The protocol includes OFAC-compliant transaction screening and monitoring, as well as IP-based geoblocking and VPN detection. For more details, see the [Legal Section](https://docs.hyperunit.xyz/legal/regulatory-compliance) . [PreviousWithdraw](https://docs.hyperunit.xyz/how-to/withdraw) [NextComponents](https://docs.hyperunit.xyz/architecture/components) Last updated 8 months ago --- # Generate Address | Unit On Unit, protocol addresses are tied to the _destination_ address, the recipient of the deposit or withdrawal. * For deposits, the _protocol address_ is a Unit-derived address on the source chain (Bitcoin, Ethereum, or Solana) assigned to a user's Hyperliquid address. * For withdrawals, the _protocol address_ is a Unit-derived Hyperliquid address assigned to a user's address on the destination chain. Once a protocol address is created, all future transfers received by this address - above the minimum amount - are credited to the respective destination address. The minimum BTC amount is 0.002 BTC (20,000 sats), the minimum ETH amount is 0.05 ETH (5e16 wei), and the minimum SOL amount is 0.1 SOl. This ensures the deposit/withdrawal is sufficiently beyond the network fees associated with the operation. ### [](https://docs.hyperunit.xyz/developers/api/generate-address#endpoint) Endpoint `**GET**` `/gen/:src_chain/:dst_chain/:asset/:dst_addr` #### [](https://docs.hyperunit.xyz/developers/api/generate-address#request-parameters) Request Parameters Name Type Required Description src\_chain String Yes source chain ("hyperliquid", "bitcoin", "solana", "ethereum", "plasma") dst\_chain String Yes destination chain ("hyperliquid", "bitcoin", "solana", "ethereum", "plasma") asset String Yes asset symbol (e.g. "btc", "eth", "sol", "xpl") dst\_addr String Yes destination address. #### [](https://docs.hyperunit.xyz/developers/api/generate-address#example-request) **Example Request** The following generates a Bitcoin _deposit address_ for a Hyperliquid user `0x99a5...9e1D` Copy curl -X GET https://api.hyperunit-testnet.xyz/gen/bitcoin/hyperliquid/btc/0x99a5F7202c4983a6f0Ca9d8F0526Fcd9d2be9e1D #### [](https://docs.hyperunit.xyz/developers/api/generate-address#id-200-ok-successful-response) **200: OK Successful Response** Copy { "address": "tb1pwv4p3sgpy8g323mxsa5z4dnm0qnzlqcxk70gwdqvrmaf92psselsxcwf75", "signatures": { "field-node": "6FdyoeFFKkzT1fylI5xmMNSLMPC3aNICBL0Nj6KokYYpA9dqEpjdLoKBw4uGPDIdZEARc1QagKIirNzqoW5cNw==", "hl-node": "gkMJhxswzNqqMBx03wJy5zzHIcXyTrzfgb077F2CC4kDSyXqMPKE/HQOvaLpgMC21v3Fb/G8ujAuXafBIz2tVg==", "node-1": "6AbTFibJ7BQEXGFXRP5lROQ6w2aqVMDyy1xMLJL0mnyB1MeIPFIEPKbHKtAbsAdB37NhxSeL9iMKUkM5XnUnFg==" }, "status": "OK" } #### [](https://docs.hyperunit.xyz/developers/api/generate-address#id-400-error-response) **400: Error Response** Copy {"error":"invalid request"} [PreviousAPI](https://docs.hyperunit.xyz/developers/api) [NextGuardian Signatures](https://docs.hyperunit.xyz/developers/api/generate-address/guardian-signatures) Last updated 1 month ago --- # Key Addresses | Unit [Mainnet](https://docs.hyperunit.xyz/developers/key-addresses/mainnet) [Testnet](https://docs.hyperunit.xyz/developers/key-addresses/testnet) [PreviousWithdraw Queue](https://docs.hyperunit.xyz/developers/api/withdraw-queue) [NextMainnet](https://docs.hyperunit.xyz/developers/key-addresses/mainnet) Last updated 7 months ago --- # Estimate Fees | Unit Deposits & withdrawals are comprised of a source transaction, initiated by the user, and a destination transaction, initiated by the Unit Guardians. The user pays for the network fees associated with each of the respective transactions. Unit exposes a fee estimation endpoint to get the current fee rates (and expected processing times) associated with each network. ### [](https://docs.hyperunit.xyz/developers/api/estimate-fees#endpoint) Endpoint `**GET**` `/v2/estimate-fees` #### [](https://docs.hyperunit.xyz/developers/api/estimate-fees#id-200-ok-successful-response) **200: OK Successful Response** Copy { "bitcoin": { "deposit-fee-rate-sats-per-vb": 8, "deposit-size-v-bytes": 113, "depositEta": "21m", "depositFee": 1404, "withdrawal-fee-rate-sats-per-vb": 5, "withdrawal-size-v-bytes": 143, "withdrawalEta": "44m", "withdrawalFee": 715 }, "ethereum": { "base-fee": 4180642406, "depositEta": "3m", "depositFee": 542339092071454, "eth-deposit-gas": 21000, "eth-withdrawal-gas": 50000, "priority-fee": 7000, "withdrawalEta": "7m", "withdrawalFee": 209032470300000 }, "solana": { "depositEta": "1m", "depositFee": 8711125, "withdrawalEta": "4m", "withdrawalFee": 8000 }, "spl": { "depositEta": "1m", "depositFee": 7857245, "withdrawalEta": "4m", "withdrawalFee": 2815836 } } [PreviousGuardian Signatures](https://docs.hyperunit.xyz/developers/api/generate-address/guardian-signatures) [NextOperations](https://docs.hyperunit.xyz/developers/api/operations) Last updated 5 months ago --- # Withdraw Queue | Unit As explained in the lifecycle section, withdrawal operations are completed by the withdraw queue, a process is triggered every ~3 Bitcoin blocks for bitcoin withdrawals, and ~every 21 Ethereum slots for ethereum withdrawals. The withdraw queue processes the destination transactions of staged operations in batches due to the throughput constraints of supported networks. This endpoint can better inform the status of withdrawal operations. ### [](https://docs.hyperunit.xyz/developers/api/withdraw-queue#endpoint) Endpoint `**GET**` `/withdrawal-queue` #### [](https://docs.hyperunit.xyz/developers/api/withdraw-queue#id-200-ok-successful-response) **200: OK Successful Response** Copy { "bitcoin": { "lastWithdrawQueueOperationTxID": "f15cf8bb590cd7d50dc9d892c9d4d5ba370887f462cd5ac5e61ad2696b19e6cd", "withdrawalQueueLength": 2 }, "ethereum": { "lastWithdrawQueueOperationTxID": "0x95f792c9ba7d31d33b6d631824756e74cd85e6c1cb5d677b4614c324f57c6aa7", "withdrawalQueueLength": 0 } } **400: Error Response** Copy {"error":"invalid request"} [PreviousWithdrawal Lifecycle](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle) [NextKey Addresses](https://docs.hyperunit.xyz/developers/key-addresses) Last updated 5 months ago --- # Mainnet | Unit [](https://docs.hyperunit.xyz/developers/key-addresses/mainnet#unit-treasury-addresses) Unit Treasury Addresses -------------------------------------------------------------------------------------------------------------------- The Unit protocol supports deposits and withdrawals directly between HyperCore and the asset's respective native chain. A user-initiated transfer's destination transaction is fulfilled from Unit's respective treasury address. Native Chain Native Chain Treasury Address HyperCore Treasury Address Bitcoin `bc1pdwu79dady576y3fupmm82m3g7p2p9f6hgyeqy0tdg7ztxg7xrayqlkl8j9` `0x574bAFCe69d9411f662a433896e74e4F153096FA` Ethereum `0xBEa9f7FD27f4EE20066F18DEF0bc586eC221055A` `0x8DAfBe89302656a7Df43c470e9EbCB4c540835c0` Solana `9SLPTL41SPsYkgdsMzdfJsxymEANKr5bYoBsQzJyKpKS` `0xA822a9cEB6D6CB5b565bD10098AbCFA9Cf18D748` Plasma `0x8e88826F42A0f5f199a9c91C3798c626326730b4` `0xE6111266AfdcdF0b1fE8505028cC1f7419d798a7` [](https://docs.hyperunit.xyz/developers/key-addresses/mainnet#guardian-information) Guardian Information -------------------------------------------------------------------------------------------------------------- Users' protocol addresses (deposit addresses & withdrawal addresses) are generated through consensus of Unit guardians. Each guardian attests to address generations with a signature performed by their key pair. The guardian public keys below may be used to [verify the integrity](https://docs.hyperunit.xyz/developers/api/generate-address/guardian-signatures) of [generated addresses](https://docs.hyperunit.xyz/developers/api/generate-address) . Guardian Name Public Key `unit-node` Copy 04dc6f89f921dc816aa69b687be1fcc3cc1d48912629abc2c9964e807422e1047e0435cb5ba0fa53cb9a57a9c610b4e872a0a2caedda78c4f85ebafcca93524061 `hl-node` Copy 048633ea6ab7e40cdacf37d1340057e84bb9810de0687af78d031e9b07b65ad4ab379180ab55075f5c2ebb96dab30d2c2fab49d5635845327b6a3c27d20ba4755b `field-node` Copy 04ae2ab20787f816ea5d13f36c4c4f7e196e29e867086f3ce818abb73077a237f841b33ada5be71b83f4af29f333dedc5411ca4016bd52ab657db2896ef374ce99 [PreviousKey Addresses](https://docs.hyperunit.xyz/developers/key-addresses) [NextToken Metadata](https://docs.hyperunit.xyz/developers/key-addresses/mainnet/token-metadata) Last updated 1 month ago --- # Withdrawal Lifecycle | Unit 1 ### [](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle#sourcetxdiscovered) SourceTxDiscovered This is the initial state of an operation, which is created when a deposit is discovered in a Hyperliquid block. A withdrawal is identified as a [Hyperliquid transfer](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint#l1-spot-transfer) - greater than the [minimum](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle) for the source-chain - to a Unit withdrawal address. Once a sourceTx is discovered, the deposit operation goes through validation, which includes checks for [sanctioned addresses](https://docs.hyperunit.xyz/legal/regulatory-compliance) . 2 ### [](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle#waitforsrctxfinalization) WaitForSrcTxFinalization Unit requires 5000 confirmations for a Hyperliquid withdrawal to be considered final. 3 ### [](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle#readyforwithdrawqueue) ReadyForWithdrawQueue In accordance with throughput limitations of supported networks, destination transactions are staged on a withdraw queue to be triggered in batches. Like sweeps, withdraw queue transactions are triggered every ~3 Bitcoin blocks for bitcoin withdrawals, and ~21 Ethereum slots for ethereum withdrawals. The operation's `positionInWithdrawQueue` may be used to inform the expected completion of this state. 4 ### [](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle#queuedforwithdraw) QueuedForWithdraw The operation has been included in a withdraw queue batch, the tx-hash of which corresponds to the tx-hash returned by the [withdraw queue endpoint](https://docs.hyperunit.xyz/developers/api/withdraw-queue) and can be inspected on any explorer for the destination network. 5 ### [](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle#done) Done The withdrawal is finalized on the destination network. The operation's state is officially "done" - this state is terminal. [PreviousDeposit Lifecycle](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle) [NextWithdraw Queue](https://docs.hyperunit.xyz/developers/api/withdraw-queue) Last updated 7 months ago --- # Deposit Lifecycle | Unit 1 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#sourcetxdiscovered) SourceTxDiscovered This is the initial state of an operation, which is created when a deposit is discovered in a block. A deposit is identified as follows: * **Bitcoin:** A [Bitcoin output](https://learnmeabitcoin.com/technical/transaction/input/vout/) - greater than the minimum 0.002 BTC - to a Unit deposit address. * **Ethereum**: An ETH transfer from an EOA or contract - greater than the minimum 0.05 ETH - to a unit deposit address. Ethereum deposits uniquely correspond to a [trace](https://docs.alchemy.com/reference/trace-block) . * **Solana:** A solana transfer to a Unit deposit address greater than 0.2 SOL * **Fart:** An SPL transfer of fart to a Unit deposit address greater than 20 FART * **PUMP:** An SPL transfer of pump to a Unit deposit address greater than 10000 PUMP Once a sourceTx is discovered, the deposit operation goes through validation, which includes checks for [sanctioned addresses](https://docs.hyperunit.xyz/legal/regulatory-compliance) . 2 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#waitforsrctxfinalization) WaitForSrcTxFinalization A transaction is considered unconfirmed until it has been included in a block on the source blockchain, at which point it has one confirmation. Each additional block is another confirmation. Confirmation requirements per source-chain are defined below * **Bitcoin:** 2 confirmations * **Ethereum:** 14 confirmations * **Solana:** 32 confirmations 3 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#buildingdsttx) BuildingDstTx The guardians are constructing the Hyperliquid transaction payload to fulfill the deposit. 4 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#additionalchecks) AdditionalChecks Additional verification steps before Guardians sign the Hyperliquid transaction. 5 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#signtx) SignTx The guardians are performing the MPC signature event for the Hyperliquid transaction. 6 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#broadcasttx) BroadcastTx The guardian network is submitting the destination transaction to the Hyperliquid network. 7 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#waitfordsttxfinalization) WaitForDstTxFinalization Unit requires 10 confirmations for a Hyperliquid transaction to be considered final. 8 ### [](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle#done) Done The sweep of the source transaction has been performed and is finalized on the source network. The operation's state is officially "done" - this state is terminal. [PreviousOperations](https://docs.hyperunit.xyz/developers/api/operations) [NextWithdrawal Lifecycle](https://docs.hyperunit.xyz/developers/api/operations/withdrawal-lifecycle) Last updated 4 months ago --- # Testnet | Unit [](https://docs.hyperunit.xyz/developers/key-addresses/testnet#unit-treasury-addresses) Unit Treasury Addresses -------------------------------------------------------------------------------------------------------------------- Deposits and withdrawals are fulfilled by Unit treasury addresses. Native Chain Native Chain Treasury Address HyperCore Testnet Treasury Address Bitcoin Signet `tb1phrd66lrhm7rtjh5a6jzkcum8ru4yyxsssrzhpdgez52hasjngc5q58gffn` `0x5B6Fce52630f5f11FC9b77DfA5cFa8970f944Ec2` Ethereum Sepolia `0x762420d851318c47F256E22AF95E861DB9A77b94` `0xdC78799911e46bacA335e6c5BA50dA89e9885520` Solana Devnet `F2yH7AU1S3ef37m2MJ4RvEfjHNpum1KQwsjK74krtQAS` `0x8ac07902383196B25a8A48eFEB5A59E317da789e` Plasma Testnet `0x4805DEFa769b71D97Ba2DBEd6CE9078D1de4B86e` `0xbFDf5fb5680cD15375f751F6262143fC4b3f6E1e` [](https://docs.hyperunit.xyz/developers/key-addresses/testnet#guardian-information) Guardian Information -------------------------------------------------------------------------------------------------------------- The guardian public keys below may be used to [verify the integrity](https://docs.hyperunit.xyz/developers/api/generate-address/guardian-signatures) of [generated addresses](https://docs.hyperunit.xyz/developers/api/generate-address) on Testnet. Guardian Name Public Key `unit-node` Copy 04bab844e8620c4a1ec304df6284cd6fdffcde79b3330a7bffb1e4cecfee72d02a7c1f3a4415b253dc8d6ca2146db170e1617605cc8a4160f539890b8a24712152 `hl-node-testnet` Copy 04502d20a0d8d8aaea9395eb46d50ad2d8278c1b3a3bcdc200d531253612be23f5f2e9709bf3a3a50d1447281fa81aca0bf2ac2a6a3cb8a12978381d73c24bb2d9 `field-node` Copy 04e674a796ff01d6b74f4ee4079640729797538cdb4926ec333ce1bd18414ef7f22c1a142fd76dca120614045273f30338cd07d79bc99872c76151756aaec0f8e8 [PreviousToken Metadata](https://docs.hyperunit.xyz/developers/key-addresses/mainnet/token-metadata) [NextToken Metadata (Testnet)](https://docs.hyperunit.xyz/developers/key-addresses/testnet/token-metadata-testnet) Last updated 1 month ago --- # Token Metadata | Unit ### [](https://docs.hyperunit.xyz/developers/key-addresses/mainnet/token-metadata#hypercore) HyperCore Unit tokens are deployed on HyperCore through the [HIP-1](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-1-native-token-standard) native token standard. The Unit HyperCore deployer is a multi-sig user with address `0xF036a5261406a394bd63Eb4dF49C464634a66155` Name L1 Name Full Name Native Chain Token ID (Explorer Details) BTC UBTC Unit Bitcoin Bitcoin [0x8f254b963e8468305d409b33aa137c67](https://app.hyperliquid.xyz/explorer/token/0x8f254b963e8468305d409b33aa137c67) ETH UETH Unit Ethereum Ethereum Mainnet [0xe1edd30daaf5caac3fe63569e24748da](https://app.hyperliquid.xyz/explorer/token/0xe1edd30daaf5caac3fe63569e24748da) SOL USOL Unit Solana Solana Mainnet Beta [0x49b67c39f5566535de22b29b0e51e685](https://app.hyperliquid.xyz/explorer/token/0x49b67c39f5566535de22b29b0e51e685) PUMP UPUMP Unit Pump Fun Solana Mainnet Beta [0x544e60f98a36d7b22c0fb5824b84f795](https://app.hyperliquid.xyz/explorer/token/0x544e60f98a36d7b22c0fb5824b84f795) FARTCOIN UFART Unit Fartcoin Solana Mainnet Beta [0x7650808198966e4285687d3deb556ccc](https://app.hyperliquid.xyz/explorer/token/0x7650808198966e4285687d3deb556ccc) SPX UUUSPX Unit SPX6900 Solana Mainnet Beta [0x2ff71b802a6788a052c7f1a58ec863af](https://app.hyperliquid.xyz/explorer/token/0x2ff71b802a6788a052c7f1a58ec863af) BONK UBONK Unit Bonk Solana Mainnet Beta [0xb113d34e351cf195733c98442530c099](https://app.hyperliquid.xyz/explorer/token/0xb113d34e351cf195733c98442530c099) XPL XPL Unit Plasma Plasma Mainnet [0x2c54c60600e1d786b2dfc139a38a5a99](https://app.hyperliquid.xyz/explorer/token/0x2c54c60600e1d786b2dfc139a38a5a99) ### [](https://docs.hyperunit.xyz/developers/key-addresses/mainnet/token-metadata#hyperevm) HyperEVM A subset of Unit tokens are also deployed on the HyperEVM. These tokens are fungible between Hyperliquid's two execution environments. HyperCore <> HyperEVM transfers can be done via the respective token's system address. This feature is enabled by the Hyperliquid protocol, more information can be [found here](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/hypercore-less-than-greater-than-hyperevm-transfers) . **Note: Users should understand this mechanism and its caveats before use.** Due to orderbook constraints, the number of decimals for a given token may vary between the HyperEVM and HyperCore. If you are transferring tokens to the environment in which the token has fewer decimals, it is recommended to only specify up to this amount, as [the non-round amount is burned](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/hypercore-less-than-greater-than-hyperevm-transfers#caveats) . This is true for all spot tokens, including HYPE. HyperEVM contracts are deployed from `0xB4FC973924a91362D301E583E839Cdaf4f19cdF8`. The Unit HyperEVM deployer is controlled via multi-party computation (MPC), requiring key-shares from multiple signers to construct and perform transactions, such as deployments. Unit Token HyperEVM Contract Address Explorer Link Bitcoin `0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463` [https://hyperevmscan.io/address/0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463](https://hyperevmscan.io/address/0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463) Ethereum `0xBe6727B535545C67d5cAa73dEa54865B92CF7907` [https://hyperevmscan.io/address/0xBe6727B535545C67d5cAa73dEa54865B92CF7907](https://hyperevmscan.io/address/0xBe6727B535545C67d5cAa73dEa54865B92CF7907) Solana `0x068f321Fa8Fb9f0D135f290Ef6a3e2813e1c8A29` [https://hyperevmscan.io/address/0x068f321Fa8Fb9f0D135f290Ef6a3e2813e1c8A29](https://hyperevmscan.io/address/0x068f321Fa8Fb9f0D135f290Ef6a3e2813e1c8A29) Pump `0x27eC642013bcB3D80CA3706599D3cdA04F6f4452` [https://hyperevmscan.io/address/0x27eC642013bcB3D80CA3706599D3cdA04F6f4452](https://hyperevmscan.io/address/0x27eC642013bcB3D80CA3706599D3cdA04F6f4452) Fartcoin `0x3B4575E689DEd21CAAD31d64C4df1f10F3B2CedF` [https://hyperevmscan.io/address/0x3B4575E689DEd21CAAD31d64C4df1f10F3B2CedF](https://hyperevmscan.io/address/0x3B4575E689DEd21CAAD31d64C4df1f10F3B2CedF) [PreviousMainnet](https://docs.hyperunit.xyz/developers/key-addresses/mainnet) [NextTestnet](https://docs.hyperunit.xyz/developers/key-addresses/testnet) Last updated 1 month ago --- # Token Metadata (Testnet) | Unit Unit deploys many Testnet tokens. Testnet deployments do not necessarily indicate future mainnet deployment. Name L1 Name Full Name Native Chain Token ID (Explorer Details) BTC UNIT Test UNIT Bitcoin Signet [0x5314ecc85ee6059955409e0da8d2bd31](https://app.hyperliquid-testnet.xyz/explorer/token/0x5314ecc85ee6059955409e0da8d2bd31) ETH UETH Unit Ethereum Sepolia Testnet [0xe4371d8166f362d6578725f11e0a14f3](https://app.hyperliquid-testnet.xyz/explorer/token/0xe4371d8166f362d6578725f11e0a14f3) SOL USOL Unit Solana Solana Devnet [0x57ead23624b114018cc0e49d01cc7b6b](https://app.hyperliquid-testnet.xyz/explorer/token/0x57ead23624b114018cc0e49d01cc7b6b) PUMP UPUMP Unit Pumpfun Solana Devnet [0xdc348378290f167692e50bfb49c60696](https://app.hyperliquid-testnet.xyz/explorer/token/0xdc348378290f167692e50bfb49c60696) FARTCOIN UFART Unit Fartcoin Solana Devnet [0x5c1a98b4df03401e19acb16bcf2ffabf](https://app.hyperliquid-testnet.xyz/explorer/token/0x5c1a98b4df03401e19acb16bcf2ffabf) SPX USPXS Unit SPX6900 Solana Devnet [0x2f5b5d85f4f86f683f681d2fa791adab](https://app.hyperliquid-testnet.xyz/explorer/token/0x2f5b5d85f4f86f683f681d2fa791adab) BONK UBONK Unit Bonk Solana Devnet [0x07258d30c89f37d852314bbdd90ac0ff](https://app.hyperliquid-testnet.xyz/explorer/token/0x07258d30c89f37d852314bbdd90ac0ff) UENA UENA Unit Ethena Sepolia Testnet [0xb54d72e8a850b91b4250a1c92c1d19b5](https://app.hyperliquid-testnet.xyz/explorer/token/0xb54d72e8a850b91b4250a1c92c1d19b5) SPX USPXS Unit SPX6900 Sepolia Testnet [0x2f5b5d85f4f86f683f681d2fa791adab](https://docs.hyperunit.xyz/cdn-cgi/l/email-protection#35405b5150535c5b5051) UXPL UXPL Unit Plasma Plasma Testnet [0x9d63f24c61da7bd3c67ff78ed1799756](https://app.hyperliquid-testnet.xyz/explorer/token/0x9d63f24c61da7bd3c67ff78ed1799756) [PreviousTestnet](https://docs.hyperunit.xyz/developers/key-addresses/testnet) [NextFAQ](https://docs.hyperunit.xyz/faq) Last updated 1 month ago --- # Guardian Signatures | Unit Included in the address generation response are signatures from the Unit guardians. Alongside the Public Keys of the Unit guardians, these signatures may be used to verify the integrity of the generated address. Users are encouraged to verify their addresses before making a deposit or withdrawal. Developers building on Unit are likewise encouraged to incorporate address verification in their interfaces & use cases. * * * Below is example code for verifying these signatures. Copy // Constants export const TESTNET_GUARDIAN_NODES = [\ {\ nodeId: 'node-1',\ publicKey: '04bab844e8620c4a1ec304df6284cd6fdffcde79b3330a7bffb1e4cecfee72d02a7c1f3a4415b253dc8d6ca2146db170e1617605cc8a4160f539890b8a24712152',\ },\ {\ nodeId: 'hl-node-testnet',\ publicKey: '04502d20a0d8d8aaea9395eb46d50ad2d8278c1b3a3bcdc200d531253612be23f5f2e9709bf3a3a50d1447281fa81aca0bf2ac2a6a3cb8a12978381d73c24bb2d9',\ },\ {\ nodeId: 'field-node',\ publicKey: '04e674a796ff01d6b74f4ee4079640729797538cdb4926ec333ce1bd18414ef7f22c1a142fd76dca120614045273f30338cd07d79bc99872c76151756aaec0f8e8',\ },\ ]; export const MAINNET_GUARDIAN_NODES = [\ {\ nodeId: 'unit-node',\ publicKey: '04dc6f89f921dc816aa69b687be1fcc3cc1d48912629abc2c9964e807422e1047e0435cb5ba0fa53cb9a57a9c610b4e872a0a2caedda78c4f85ebafcca93524061',\ },\ {\ nodeId: 'hl-node',\ publicKey: '048633ea6ab7e40cdacf37d1340057e84bb9810de0687af78d031e9b07b65ad4ab379180ab55075f5c2ebb96dab30d2c2fab49d5635845327b6a3c27d20ba4755b',\ },\ {\ nodeId: 'field-node',\ publicKey: '04ae2ab20787f816ea5d13f36c4c4f7e196e29e867086f3ce818abb73077a237f841b33ada5be71b83f4af29f333dedc5411ca4016bd52ab657db2896ef374ce99',\ },\ ]; const GUARDIAN_SIGNATURE_THRESHOLD = 2; interface Proposal { destinationAddress: string; destinationChain: string; asset: string; address: string; sourceChain: string; coinType?: string; keyType?: string; } interface VerificationResult { success: boolean; verifiedCount: number; errors?: string[]; verificationDetails?: { [nodeId: string]: boolean }; } function hexToBytes(hex: string): Uint8Array { const cleanHex = hex.startsWith('0x') ? hex.slice(2) : hex; return new Uint8Array(Buffer.from(cleanHex, 'hex')); } function legacyProposalToPayload(nodeId: string, proposal: Proposal): Uint8Array { const payloadString = `${nodeId}:${[\ proposal.destinationAddress,\ proposal.destinationChain,\ proposal.asset,\ proposal.address,\ proposal.sourceChain,\ 'deposit'\ ].join('-')}`; return new TextEncoder().encode(payloadString); } function newProposalToPayload(nodeId: string, proposal: Proposal): Uint8Array { const payloadString = `${nodeId}:${[\ 'user',\ proposal.coinType,\ proposal.destinationChain,\ proposal.destinationAddress,\ proposal.address\ ].join('-')}`; return new TextEncoder().encode(payloadString); } function proposalToPayload(nodeId: string, proposal: Proposal): Uint8Array { if (proposal.coinType === 'ethereum') { return newProposalToPayload(nodeId, proposal); } return legacyProposalToPayload(nodeId, proposal); } async function processGuardianNodes(nodes: { nodeId: string; publicKey: string }[]) { const processed = []; for (const node of nodes) { try { const publicKeyBytes = hexToBytes(node.publicKey); if (publicKeyBytes.length !== 65 || publicKeyBytes[0] !== 0x04) { throw new Error(`Invalid public key format for node ${node.nodeId}`); } const publicKey = await crypto.subtle.importKey( 'raw', publicKeyBytes, { name: 'ECDSA', namedCurve: 'P-256' }, true, ['verify'] ); processed.push({ nodeId: node.nodeId, publicKey }); } catch (error) { console.error(`Failed to process node ${node.nodeId}:`, error); throw new Error(`Node processing failed: ${error instanceof Error ? error.message : 'Unknown error'}`); } } return processed; } async function verifySignature(publicKey: CryptoKey, message: Uint8Array, signature: string): Promise { try { const sigBytes = Uint8Array.from(atob(signature), c => c.charCodeAt(0)); if (sigBytes.length !== 64) { console.warn('Invalid signature length:', sigBytes.length); return false; } return await crypto.subtle.verify( { name: 'ECDSA', hash: { name: 'SHA-256' }, }, publicKey, sigBytes, message ); } catch (error) { console.error('Signature verification failed:', error); return false; } } export async function verifyDepositAddressSignatures( signatures: { [nodeId: string]: string }, proposal: Proposal ): Promise { try { const processedNodes = await processGuardianNodes(GUARDIAN_NODES); let verifiedCount = 0; const errors: string[] = []; const verificationDetails: { [nodeId: string]: boolean } = {}; await Promise.all( processedNodes.map(async (node) => { try { if (!signatures[node.nodeId]) { verificationDetails[node.nodeId] = false; return; } let isVerified = false; if (proposal.coinType !== 'ethereum') { const legacyPayload = legacyProposalToPayload(node.nodeId, proposal); isVerified = await verifySignature(node.publicKey, legacyPayload, signatures[node.nodeId]); if (!isVerified) { const newPayload = newProposalToPayload(node.nodeId, proposal); isVerified = await verifySignature(node.publicKey, newPayload, signatures[node.nodeId]); } } else { const payload = newProposalToPayload(node.nodeId, proposal); isVerified = await verifySignature(node.publicKey, payload, signatures[node.nodeId]); } verificationDetails[node.nodeId] = isVerified; if (isVerified) verifiedCount++; } catch (error) { errors.push(`Verification failed for node ${node.nodeId}: ${error instanceof Error ? error.message : 'Unknown error'}`); verificationDetails[node.nodeId] = false; } }) ); return { success: verifiedCount >= GUARDIAN_SIGNATURE_THRESHOLD, verifiedCount, errors: errors.length > 0 ? errors : undefined, verificationDetails }; } catch (error) { return { success: false, verifiedCount: 0, errors: [`Global verification error: ${error instanceof Error ? error.message : 'Unknown error'}`], verificationDetails: {} }; } } [PreviousGenerate Address](https://docs.hyperunit.xyz/developers/api/generate-address) [NextEstimate Fees](https://docs.hyperunit.xyz/developers/api/estimate-fees) Last updated 5 months ago --- # How do I get in touch with Unit? | Unit If you've already read our FAQs and still need help, you can connect with us on Telegram: [t.me/hyperunit](https://t.me/hyperunit) [PreviousFAQ](https://docs.hyperunit.xyz/faq) [NextWhere's my transaction?](https://docs.hyperunit.xyz/faq/wheres-my-transaction) Last updated 8 months ago --- # Operations | Unit Use the following endpoint to retrieve all operations for a user. ### [](https://docs.hyperunit.xyz/developers/api/operations#endpoint) Endpoint `**GET**` `/operations/:address` #### [](https://docs.hyperunit.xyz/developers/api/operations#request-parameters) Request Parameters Name Type Required Description address String Yes address associated with an operation #### [](https://docs.hyperunit.xyz/developers/api/operations#example-request) **Example Request** **The following request returns all operations associated with a Hyperliquid user** a6f1E...0132 Copy curl -X GET https://api.hyperunit-testnet.xyz/operations/0xa6f1Ef42D335Ec7CbfC39f57269c851568300132 #### [](https://docs.hyperunit.xyz/developers/api/operations#id-200-ok-successful-response) **200: OK Successful Response** Copy { "addresses": [\ {\ "sourceCoinType": "bitcoin",\ "destinationChain": "hyperliquid",\ "address": "tb1pncsdk2979x2nksu5mvf9uu6z0v0a7632ss5vuw3fu4wv8805d09sjd7m3e",\ "signatures": {\ "field-node": "KU9w0QF1/lJECrkPSz8ssUmcWpD6ZshftuONYSO/ockUgeovGgmAPKbBBBLt4A0X0WsqaTaFYwEQcRyTGp7xWQ==",\ "hl-node-testnet": "/lElUTMr/4q7QBV6fur2b4LqV7c9DCMDHnMZiC73XO5WOfy46Q+t+2ZmbiPCaW7THLW9r13otiVCjeb/zAfAKA==",\ "node-1": "PXtxH2B/KtCaceEeAD9/pZ37c+Ryv4FmdC7QeN1AB+D1HzjhDtJs75P4Xi3YQB4pP46ycyZkhXnz65AJvFahuA=="\ }\ },\ {\ "sourceCoinType": "ethereum",\ "destinationChain": "hyperliquid",\ "address": "0xf040d1E1e7BCDc9947E5F7871c7F205786CcC494",\ "signatures": {\ "field-node": "6DTX4nLPd8+hYb2aJNowdu3R3J6nsXmGnhOYnaKIiSC7h6w3evgUzWI6rKG3CmjrjA5s3+X2cqNmlSfGMo+z2w==",\ "hl-node-testnet": "bc4Z8k3y+FHsiB2Fzus/wqBRAbtrgvlrgVVWJ4dT7DMVoGF4c+Jd69Rk7uJMelLf31xjJdtxmtdCHwDVT5ryjw==",\ "node-1": "BoEW/3Za0+j+wi1NlbXYrRsgywJhLyDrawToSCQkpYwnwB9GVFnxBoEb4a57HhpX8LnJfrPxN51eS0PHZS73Zw=="\ }\ }\ ], "operations": [\ {\ "opCreatedAt": "2025-03-12T23:42:27Z"",\ "operationId": "",\ "protocolAddress": "tb1pncsdk2979x2nksu5mvf9uu6z0v0a7632ss5vuw3fu4wv8805d09sjd7m3e",\ "sourceAddress": "tb1qkwl2vjeplzj76qz544qzenl26w0fscsfmxlews",\ "destinationAddress": "",\ "sourceChain": "bitcoin",\ "destinationChain": "hyperliquid",\ "sourceAmount": "10000000",\ "destinationFeeAmount": "0",\ "sweepFeeAmount": "0",\ "stateStartedAt": "0001-01-01T00:00:00Z",\ "stateUpdatedAt": "0001-01-01T00:00:00Z",\ "stateNextAttemptAt": "0001-01-01T00:00:00Z",\ "sourceTxHash": "1c6f6abc977ec3ba381ad99f3903a258eaae366adf7c7a7627ef159357cd67a6",\ "sourceTxConfirmations": 0,\ "destinationTxHash": "",\ "asset": "btc",\ "state": "sourceTxDiscovered"\ },\ {\ "opCreatedAt": "2025-03-12T23:40:49.279929Z",\ "operationId": "914ea76e4329845f9c1e03c87b66bc339dd9a8789ce9be7a46170d68e70dd791:0",\ "protocolAddress": "tb1pncsdk2979x2nksu5mvf9uu6z0v0a7632ss5vuw3fu4wv8805d09sjd7m3e",\ "sourceAddress": "tb1qkwl2vjeplzj76qz544qzenl26w0fscsfmxlews",\ "destinationAddress": "0xa6f1Ef42D335Ec7CbfC39f57269c851568300132",\ "sourceChain": "bitcoin",\ "destinationChain": "hyperliquid",\ "sourceAmount": "10000000",\ "destinationFeeAmount": "0",\ "sweepFeeAmount": "0",\ "stateStartedAt": "2025-03-12T23:40:49.465291Z",\ "stateUpdatedAt": "2025-03-12T23:40:49.465291Z",\ "stateNextAttemptAt": "2025-03-12T23:42:50.804735Z",\ "sourceTxHash": "914ea76e4329845f9c1e03c87b66bc339dd9a8789ce9be7a46170d68e70dd791:0",\ "sourceTxConfirmations": 1,\ "asset": "btc",\ "state": "waitForSrcTxFinalization"\ },\ {\ "opCreatedAt": "2025-03-12T23:38:02.019431Z",\ "operationId": "0x2ebf75c61e1c78f89b8e04f1af6912ca46c936293920fb320f8e8ca3eda360f3:0",\ "protocolAddress": "0xf040d1E1e7BCDc9947E5F7871c7F205786CcC494",\ "sourceAddress": "0xa6f1Ef42D335Ec7CbfC39f57269c851568300132",\ "destinationAddress": "0xa6f1Ef42D335Ec7CbfC39f57269c851568300132",\ "sourceChain": "ethereum",\ "destinationChain": "hyperliquid",\ "sourceAmount": "100000000000000000",\ "destinationFeeAmount": "454545454545454",\ "sweepFeeAmount": "140761861078.125",\ "stateStartedAt": "2025-03-12T23:40:40.798707Z",\ "stateUpdatedAt": "2025-03-12T23:40:40.798707Z",\ "stateNextAttemptAt": "2025-03-12T23:40:40.798698Z",\ "sourceTxHash": "0x2ebf75c61e1c78f89b8e04f1af6912ca46c936293920fb320f8e8ca3eda360f3:0",\ "destinationTxHash": "0xdC78799911e46bacA335e6c5BA50dA89e9885520:1741822714587",\ "broadcastAt": "2025-03-12T23:38:46.170519Z",\ "asset": "eth",\ "state": "done"\ }\ ] } #### [](https://docs.hyperunit.xyz/developers/api/operations#id-400-error-response) **400: Error Response** Copy {"error":"Invalid input address"} * * * [](https://docs.hyperunit.xyz/developers/api/operations#operation-structure) Operation Structure ----------------------------------------------------------------------------------------------------- Unit Operations include both deposits and withdrawals, and are returned as follows: Copy export type Operation = { /** Unique identifier, equivalent to sourceTxHash */ operationId: string; /** ISO 8601 timestamp */ opCreatedAt: string; /** Addresses */ protocolAddress: string; sourceAddress: string; destinationAddress: string; /** Chain identifiers */ sourceChain: 'bitcoin' | 'hyperliquid' | 'ethereum'; destinationChain: 'bitcoin' | 'hyperliquid' | 'ethereum'; /** Amounts, in smallest native units of source currency (satoshis/ wei) */ // e.g. ethereum - 18 decimals, solana - 9 decimals, bitcoin - 8 decimals, pump - 6 decimals sourceAmount: string; destinationFeeAmount: string; sweepFeeAmount: string; /** Current operation status */ state: OperationState; /** Source chain transaction hash */ sourceTxHash: string; /** Destination chain transaction hash (empty until created) */ destinationTxHash: string; /** Position in withdraw queue (0 if state != "wait_for_sweep") */ positionInWithdrawQueue: number; /** asset being transferred (btc, eth, sol, fart). It's possible that there are multiple assets per chain (i.e solana) */ asset: string; }; export type Address = { /** coin-type of the protocolAddress's source chain according to SLIP-44 (BITCOIN, ETHEREUM) **/ sourceCoinType: string; /** destination chain of the protocol address **/ destinationChain: string; /** the protocol address **/ address: string; /** guardian signatures over the protocol address **/ [key: string]: string; }; **Response Fields** * **opCreatedAt:** The time at which the Unit protocol created a deposit/withdrawal operation corresponding to a given source transaction. The response is sorted by this timestamp in descending order. This field will reflect the server's current timestamp when the corresponding operation has not yet been created (`operationId` will be empty). This may be the case for newly discovered & unconfirmed transactions, as Unit operations are created after a certain number of source confirmations: * **Bitcoin:** 1 confirmation * **Ethereum:** 8 confirmations * **Hyperliquid**:1 confirmation * **sourceTxConfirmations:** The number of block confirmations of the source transaction. If this value is omitted from the response, the source transaction has reached finalization. * **destinationTxConfirmations:** The number of block confirmations of the destination transaction, applicable to operations in states `QueuedForWithdraw` and `WaitForDstTxFinalization` A value ≥ 1 signals that the recipient has received the funds on the destination network. * **broadcastAt**: The server-side timestamp of when the destination transaction was broadcasted, applicable to operations in states `BroadcastTx` and `WaitForDstTxFinalization`. * **addresses:** The Unit-generated `protocolAddresses` associated with the destination address given in `/operations/:address` * **sourceCoinType**: this is the SLIP-44 coin-type associated with the chain that the `protocolAddress` is on (Ethereum, Bitcoin). * **address:** this is the `protocolAddress` on the source-chain. **Additional Notes** * Unit does not collect revenue from deposits / withdrawals. All "fees" associated with an operation are those necessaryy to process the source and destination transactions on their respective networks. * `destinationFeeAmount` is the fee paid by the guardians to process the destination transaction on the destination chain (Hyperliquid for deposits, Bitcoin for withdrawals). * `sweepFeeAmount` is the fee paid by the guardians to "sweep" funds on the source chain for the fulfillment of future operations by the Unit treasury. Because this fee is deducted from the operation amount prior to sweep execution, the amount deducted by Unit is an estimate. This estimate may differ slightly from the actual fee later paid by guardians to the source chain. * Unit transaction hashes are formatted as follows * For Bitcoin transactions `:` * For Ethereum transactions `:` * For Hyperliquid transactions `:` * For Solana transactions `:` * Any operation that has yet to reach 2 bitcoin confirmations (whether discovered in a block or not) will be returned with the `srcTxDiscovered` state. ### [](https://docs.hyperunit.xyz/developers/api/operations#operation-states) Operation States An operation can be in one of the following states Copy /** Represents the current status of an operation */ enum OperationState { SrcTxDiscovered = 'sourceTxDiscovered', WaitForSrcTxFinalization = 'waitForSrcTxFinalization', BuildingDstTx = 'buildingDstTx', SignTx = 'signTx', BroadcastTx = 'broadcastTx', WaitForDstTxFinalization = 'waitForDstTxFinalization', ReadyForWithdrawQueue = 'readyForWithdrawQueue', QueuedForWithdraw = 'queuedForWithdraw', Done = 'done', Failure = 'failure', } The permutation of states differs slightly between deposits and withdrawals, as explained in depth in their lifecycles. [PreviousEstimate Fees](https://docs.hyperunit.xyz/developers/api/estimate-fees) [NextDeposit Lifecycle](https://docs.hyperunit.xyz/developers/api/operations/deposit-lifecycle) Last updated 1 day ago --- # How do fees on Unit work? | Unit Unit does not collect revenue from deposits or withdrawals - we aim to offer the lowest cost possible. The "fees" associated with an operation are those required to process the source and destination transactions on their respective native networks. [PreviousWhere's my transaction?](https://docs.hyperunit.xyz/faq/wheres-my-transaction) [NextWhat type of Bitcoin deposit address does Unit derive?](https://docs.hyperunit.xyz/faq/what-type-of-bitcoin-deposit-address-does-unit-derive) Last updated 8 months ago --- # How long does a deposit/withdrawal take? | Unit Deposits typically take ~25 minutes and withdrawals ~15 minutes to process, but this may vary depending on network block times - particularly Bitcoin. See [required confirmations](https://docs.hyperunit.xyz/developers/api#required-confirmations) . [PreviousWhat type of Bitcoin deposit address does Unit derive?](https://docs.hyperunit.xyz/faq/what-type-of-bitcoin-deposit-address-does-unit-derive) [NextIs my unique deposit address permanent?](https://docs.hyperunit.xyz/faq/is-my-unique-deposit-address-permanent) Last updated 8 months ago --- # What type of Bitcoin deposit address does Unit derive? | Unit Unit derives a taproot address "bc1p". When sending BTC funds to your unique deposit address, please make sure the sending account supports Taproot addresses. [PreviousHow do fees on Unit work?](https://docs.hyperunit.xyz/faq/how-do-fees-on-unit-work) [NextHow long does a deposit/withdrawal take?](https://docs.hyperunit.xyz/faq/how-long-does-a-deposit-withdrawal-take) Last updated 8 months ago --- # Regulatory Compliance | Unit **Unit Protocol** is dedicated to adhering to all relevant regulatory standards and compliance requirements, ensuring the integrity and legality of its operations. To achieve this, the protocol incorporates comprehensive screening processes that utilize blockchain analytics and intelligence software. These measures ensure compliance with Office of Foreign Assets Control (OFAC) sanctions regimes, effectively preventing known sanctioned entities from interacting with the Unit network. In addition to sanctions compliance, Unit employs IP-based geoblocking to restrict access from Prohibited Jurisdictions, as defined in the Terms of Service. The protocol also incorporates virtual private network (VPN) screening to further enforce these geographical restrictions, ensuring that only authorized users from permitted regions can engage with the network. Unit maintains a detailed log of all Hyperliquid deposits and withdrawals facilitated by the network. It is important for users to understand that Unit is not a "mixer"; all transactions are recorded with relevant information and may be disclosed to law enforcement agencies in response to subpoenas or other official legal procedures. Law enforcement inquiries can be directed to Unit Labs at legal (at) hyperunit (dot) xyz Data privacy is a top priority for Unit. The protocol upholds user information in accordance with global data protection regulations, ensuring that all user data is handled with the highest standards of privacy and security. To maintain and enhance compliance measures, Unit conducts regular legal and risk management audits, keeping its protocols up to date with the evolving regulatory landscape. * * * [PreviousCan I generate multiple deposit addresses for my Hyperliquid wallet?](https://docs.hyperunit.xyz/faq/can-i-generate-multiple-deposit-addresses-for-my-hyperliquid-wallet) [NextTerms of Service](https://docs.hyperunit.xyz/legal/terms-of-service) Last updated 5 months ago --- # Where's my transaction? | Unit It may take a few minutes for the protocol to reflect a recently submitted transaction. If you are depositing Bitcoin from a centralized exchange, note there may be a delay by the exchange before the transfer is broadcasted to the network. You can track the confirmations of a Bitcoin transaction using an explorer such as [mempool.space](https://mempool.space/) . Note: [Finalization is required](https://docs.hyperunit.xyz/developers/api#required-confirmations) by the Unit protocol on each blockchain. For further assistance, join the Unit telegram: [https://t.me/hyperunit](https://t.me/hyperunit_xyz) [PreviousHow do I get in touch with Unit?](https://docs.hyperunit.xyz/faq/how-do-i-get-in-touch-with-unit) [NextHow do fees on Unit work?](https://docs.hyperunit.xyz/faq/how-do-fees-on-unit-work) Last updated 8 months ago --- # Privacy Policy | Unit **Last Revised on November 2024** This Privacy Policy (“Policy”) for Hyperunit, describes the basis on which we will process personal data we may collect from users of the Company’s website, hyperunit_.xyz_, including any of its subdomains (“Website”), and any tools, services, features, and functionalities available through the Website (collectively, the “Services”), in accordance with applicable law. For purposes of applicable data protection laws, the Company is the data controller. For the purposes of this Policy, “you” and “your” refers to you as the user of the Services. Read this Policy carefully so that you understand your rights in relation to your personal data and how we might collect, use, and process your personal data. If you do not agree to this Policy, do not use, access, connect to, interact with, or download any of the Services or otherwise provide your information to us. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#personal-data-we-collect-about-you-why-we-process-it-and-the-legal-basis-for-processing) PERSONAL DATA WE COLLECT ABOUT YOU, WHY WE PROCESS IT, AND THE LEGAL BASIS FOR PROCESSING When you access, use, connect to, or interact with the Services, we may collect certain categories of information about you, including personal data, from a variety of sources. **Information you provide to us:** Personal data may include (i) any internet-protocol address (“IP Address”), (ii) any digital-asset, smart-contract, or protocol address (“Wallet”) information, associations, and/or identifiers; and (iii) geolocation data. In addition, personal data may include your social media handle and related information, transaction data or history (such as your blockchain transaction history and other information associated with a linked address or Wallet), certain information needed to transfer or allocate tokens, marketing data (such as preferences for receiving marketing communications and related details), token holdings, and any other information collected through the Services. Should you contact us, we will collect the content of the communications we have with you and any personal data contained within. We process this information to perform our contract with you, such as to provide you with our Services. **Information we collect automatically:** When you visit certain pages on our Website or access, use, connect to, or interact with certain Services, our servers save each access in a log file. The following data may be collected: (i) the IP Address of the requesting computer or device; (ii) the date and time of access; (iii) the country from which the website is accessed; (iv) any API endpoint; (v) user agent details; (vi) the operating system of your computer and the browser you are using (provider, version, and language); and (vii) the transmission protocol used (e.g., HTTP/1.1). The processing of this data is carried out for the purpose of enabling your access to, use of, connection to, and interaction with the Services, including (i) to facilitate your connection to the Website, (ii) to identify if you are likely to be a Prohibited Person, as defined in our general Terms of Service, available at \[url\] or if you are subject to any prohibitions with respect to the Services; and/or (iii) to verify your identity, identifying information, certain facts with respect to your identity or identifying information, and location to determine eligibility for certain Services. Each case with respect to any of (i), (ii), and/or (iii) is in order for us to perform our contract with you and in our legitimate interests to provide effective Services to you. We may also process this data in our legitimate interests to provide effective Services to you by processing the data to assist system security and stability for provision of the Services, to conduct troubleshooting, data analytics, testing, and research, and to enable optimization and internal statistical analysis with respect to the Services, as well as to maintain the safety and security of our users, the Website, our Services and business and to improve and develop our Services and Website. Finally, the Company may use cookies, web beacons/clear gifs, geolocation and tracking technologies, and other applications when you visit the Website, including technologies collecting certain information about your access to, use of, connection to, or interaction with the Services (“Usage Data”) that may be integrated with third-party service providers. With your consent, we may use any data collected, including Usage Data, to tailor features and content to you and to ensure content is presented in the most effective manner for you and your device and to run analytics and better understand your user experience with respect to the Services and, if you have opted into marketing, for marketing purposes. We may also use your information to provide the Services and perform our contract with you. In our legitimate interests to provide effective services to you, we may also use this data to create aggregated, anonymized, or de-identified data. In addition to the foregoing, we may use any of your information to comply with any applicable legal obligations, to enforce any applicable terms of service, and to protect or defend the Services, our rights, and the rights of our users or others. **Information we may collect from third-party wallet extensions or connections:** Certain transactions conducted via our Services may require you to connect a compatible third-party digital Wallet to the Services. By using such Wallet to conduct such transactions via the Services, you agree that your access to, use of, connection to, and/or interactions with such third-party Wallets are governed by the privacy policy for the applicable Wallet, and you agree that you are using the Wallet in accordance with the terms and conditions of the applicable third-party provider of such Wallet. Wallets are not maintained or supported by, or associated or affiliated with, the Company. We expressly disclaim any and all liability for actions arising from your use of third-party Wallets, including but without limitation, actions relating to the use and/or disclosure of personal information by such third-party Wallets. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#your-rights) YOUR RIGHTS Under applicable data protection laws, you may have certain rights in relation to your personal data. These rights may include the following: 1. Access to your personal data that the Company holds, information on how we use it, and who we share it with; 2. Correction of your personal data that the Company holds, subject to the Company’s investigation and verification of any disputed information; 3. Deletion or removal of your personal data, in certain circumstances; 4. Objection to the processing of your personal data, in certain circumstances; 5. Restriction of processing of your personal data, to stop us from processing the personal data we hold about you other than for storage purposes, in certain circumstances; 6. Portability of your personal data; the Company will endeavor to provide you, or a third party, with a copy of the personal data that we hold about you and transfer it to a third party in a structured, commonly used, machine-readable format; 7. Objection to marketing communications; you may opt out of any marketing communications at any time by using any unsubscribe or opt-out functionalities displayed in any such communications to you; 8. Notice of a personal data breach (unless the breach is unlikely to be prejudicial to you); 9. Complaint to the Cayman Islands Data Protection Ombudsman; 10. Withdrawal of consent, where the Company is relying on consent to process personal data; this will not affect the processing of personal data carried out before consent is withdrawn or on legal bases other than consent. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#automated-decision-making) Automated decision-making The Organisation will not take decisions producing legal effects concerning you, or otherwise significantly affecting you, based solely on automated processing of your personal data, unless we have considered the proposed processing in a particular case and concluded in writing that it meets the applicable requirements under applicable data protection laws You may submit a written request concerning the processing of your personal data to notices@\[URL\]. the Company shall use reasonable means to verify your identity before making any determination with respect to your request. Note that some of these rights may apply only in certain circumstances and all of these rights may be limited to some extent by law. Such limitations may apply, for example, where fulfilling your request would adversely affect other individuals or our trade secrets or intellectual property, where there are overriding public interests, or where we are required by law to retain your personal data. To the extent required under applicable data protection laws, the Company will be responsive to your request without undue delay and where required under applicable data protection laws, at least within one month (though this may be extended by a further two months in certain circumstances). #### [](https://docs.hyperunit.xyz/legal/privacy-policy#sharing-of-personal-data) SHARING OF PERSONAL DATA In certain circumstances, we may share your information with third parties with your consent, as necessary, or as otherwise required or permitted by law. Specifically, we may share your personal data: * With service providers and vendors: the Company may share your personal data with third parties to process on the Company’s behalf. Such third parties could include blockchain analysis service providers, know-your-customer and screening service providers, developers, content delivery service providers, and data analytics service providers. Such service providers may assist us with many different functions and tasks, including determining your eligibility with respect to participation in certain Services. * With professional advisors, in our legitimate interests or as required by law: As necessary, we will share your personal data with professional advisors such as auditors, law firms, cybersecurity specialists, data analysis organizations, and/or consulting or accounting firms. * For legal and security reasons and to protect our services and business, in our legitimate interests or as required by law. * With law enforcement and regulatory authorities, in order to comply with applicable legal and regulatory requirements, respond to mandatory legal or governmental requests or demands for information. * With our affiliates, in our legitimate interests: We may share your personal data with companies within our corporate family. * In connection with an asset sale or purchase, merger, bankruptcy, or other business transaction or re-organization, in our legitimate interests: We will share your personal data with relevant third parties as necessary while negotiating or in relation to a change of corporate control such as a restructuring, merger, or sale of our assets. Your personal information may be transferred to and stored or processed in countries outside the jurisdiction in which you live and reside, including outside the Cayman Islands, European Economic Area (“EEA”) and United Kingdom (“UK”), and including to the U.S., in order to provide the Services. Your personal information may also be processed by staff operating outside the Cayman Islands/UK/EEA who work for us or for third-party service providers or partners. We will take steps reasonably necessary to ensure that your personal information is treated securely and in accordance with this Policy and applicable data protection laws. Should we transfer your personal information to third parties located outside the Cayman Islands/EEA/UK, we will seek to put in place appropriate safeguards to ensure that this transfer occurs in accordance with applicable data protection laws. These measures include seeking entry into the standard contractual clauses (“SCCs”) approved by the European Commission (for transfers outside the EEA) and/or an international data transfer agreement/addendum to the SCCs approved by the UK Information Commissioner’s Office (“ICO”) (for transfers outside the UK), unless the data transfer is to a country that has been determined by the European Commission or the relevant UK authorities, as applicable, to provide an adequate level of protection for individuals’ rights and freedoms for their personal data. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#retention) RETENTION We will retain your personal data only for so long as necessary to fulfill the purposes for which it was collected, including for the purposes of satisfying any legal, accounting or reporting requirements, or as otherwise required by law. The length of time we retain your data will depend on the nature of the data and the purpose for which it was processed. We expect to delete your personal data (at the latest) once there is no longer any legal or regulatory requirement or legitimate business purpose for retaining your data. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#childrens-privacy-and-data-protection) CHILDRENS’ PRIVACY AND DATA PROTECTION Persons under the age of eighteen (18) are not permitted to use the Services, and we do not seek to or knowingly collect any personal data about children under thirteen (13) years of age (or sixteen (16) years of age for individuals in the EEA/UK). If we become aware that we have unknowingly collected information about any person under eighteen (18) years of age, we will make commercially reasonable efforts to delete such personal data and other information from our records. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#security-measures-taken-to-protect-personal-data) SECURITY MEASURES TAKEN TO PROTECT PERSONAL DATA Be aware that despite our efforts to protect your personal data and other information, we cannot guarantee “perfect security” of your information transmitted through the Website. In addition, note that any information you send to us electronically, while using the Services or otherwise interacting with us, may not be secure while in transit. Any transmission is at your own risk. You should carefully read any risk factors specified in any terms of services associated with your access to, use of, connection to, or interaction with the Services. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#usage-data-collection) USAGE DATA COLLECTION When you access, use, connect to, or interact with the Services, including the Website, the Company and its third-party service providers may receive and record personal data that you may have provided and your digital signature, such as your IP Address or information associated with or relating to your Wallet. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#social-media-and-other-third-party-websites-and-links) SOCIAL MEDIA AND OTHER THIRD-PARTY WEBSITES AND LINKS On the Website, the Company may provide links to websites or online platforms operated by third parties, including social media or content platforms operated by third parties, such as X (formerly Twitter) or Medium (such platforms, generally, “Social Media Platforms”). the Company also may provide links to websites or online platforms operated by third-party contributors to the Unit Protocol and ecosystem (“Contributors”). We do not own, operate, or control such third-party websites. If you follow links to sites not owned or operated by us, you should review their privacy and security policies and other terms and conditions. We do not guarantee and are not responsible for the privacy, security, or content of these sites, including the accuracy, completeness, or reliability of information and services found on these sites. Note that third parties and Contributors may provide services, information, dashboards, websites, tools, functionalities, and applications, such as those available through \[APP URL\] and its subdomains, and these may be linked from time to time through our Services or through our accounts on Social Media Platforms. Such third parties and Contributors are independent and as such, we do not own, operate, or control their services, information, dashboards, websites, tools, functionalities, and applications and cannot guarantee, and are not responsible for, the privacy, security, or content of these sites or the accuracy, completeness, or reliability of services, information, dashboards, websites, tools, functionalities, and applications found on these sites. Our inclusion of links, including through Social Media Platforms, does not, by itself, imply any endorsement of such services, information, dashboards, websites, tools, functionalities, and applications, or of their owners, operators, or publishers, except as disclosed on the Services. When you open a link to a Social Media Platform used by the Company, a direct connection may be established between your browser and the server of the Social Media Platform. This provides the Social Media Platform with information that you visited our Website with your IP Address and accessed the link. If you access a link to a Social Media Platform while logged-in to your account on the Social Media Platform concerned, the content of our website may be linked to your profile on the platform (i.e., the Social Media Platform may link your visit to our website directly to your user account). If you want to prevent this, you should log out before clicking on the relevant links. In any case, an association takes place when you log-in to the relevant Social Media Platform after clicking on the link. In addition, note that personal data and other information you provide on public or semi-public venues, including personal data and other information you share or post on Social Media Platforms or in a public forum, may be accessible or viewable by other users of the Services and/or users of third-party platforms without limitation as to use by us or by such third party. Certain technologies may provide access to personal data and information shared or posted on Social Media Platforms or in a public forum after such data or information is deleted. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#periodic-reviews-and-updates-to-policy) PERIODIC REVIEWS AND UPDATES TO POLICY This Policy takes into account the requirements of the Cayman Islands Data Protection Act 2021 and general privacy principles. Individuals located in the European Union (“EU”) and the United Kingdom (“UK”) may have rights under the EU General Data Protection Regulation 2016/679 and the UK General Data Protection Regulation, respectively (collectively, the “GDPR”). Note that you can file a claim with the data protection supervisory authority in the EEA country in which you live or work or where you think we have infringed data protection laws, or with the UK Information Commissioner’s Office, as applicable to you. Other applicable global privacy and data-protection laws may provide you rights with respect to your personal data and other information. the Company may review and update this Policy from time to time. Updates to our Policy will apply only to information collected after the date of the change. If we make material changes to the Policy, we will update the “Last Revised” date at the top of this Policy. #### [](https://docs.hyperunit.xyz/legal/privacy-policy#contact) CONTACT Should you have any questions or complaints about our privacy or data-protection practices, your personal data, or this Policy, you can email us at legal \[at\] nexus \[dot\] build. [PreviousTerms of Service](https://docs.hyperunit.xyz/legal/terms-of-service) Last updated 3 months ago --- # Can I generate multiple deposit addresses for my Hyperliquid wallet? | Unit Unit supports strictly 1 Bitcoin deposit address per Hyperliquid account. [PreviousIs my unique deposit address permanent?](https://docs.hyperunit.xyz/faq/is-my-unique-deposit-address-permanent) [NextRegulatory Compliance](https://docs.hyperunit.xyz/legal/regulatory-compliance) Last updated 8 months ago --- # Terms of Service | Unit Terms of Service Last Revised on November 2024 Welcome to the Terms of Service (these “Terms”) for: (i) the website, hyperunit.xyz (including its subdomains, the “Site”); and (ii) any other websites through which these Terms are linked (together with the Site, the “Website”), in each case as operated by or on behalf of Hyperunit. the Company’s services, including but not limited to the Website and any content, tools, software, documentation, features, and functionality offered by the Company on or through the Website or third-party sites and services, are collectively referred to as the “Services”. These Terms govern your access to and use of the Services. Read these Terms carefully, as they include important information about your legal rights. By accessing and/or using the Services, you are agreeing to these Terms. If you do not understand or agree to these Terms, you may not use the Services. For purposes of these Terms, “you” and “your” means you as the user of the Services. If you use the Services on behalf of a company or other entity then “you” includes both you in an individual capacity and that entity, and you represent and warrant that: (a) you are an authorized representative of the entity with the authority to bind the entity to these Terms; and (b) you agree to these Terms on the entity’s behalf, as well as on your individual behalf. SECTION 7 CONTAINS AN ARBITRATION CLAUSE AND CLASS ACTION WAIVER. BY AGREEING TO THESE TERMS, YOU AGREE: (A) TO RESOLVE ALL DISPUTES (WITH LIMITED EXCEPTION) RELATED TO THE COMPANY’S SERVICES AND/OR PRODUCTS THROUGH BINDING INDIVIDUAL ARBITRATION, WHICH MEANS THAT YOU WAIVE ANY RIGHT TO HAVE THOSE DISPUTES DECIDED BY A JUDGE OR JURY; AND (B) TO WAIVE YOUR RIGHT TO PARTICIPATE IN CLASS ACTIONS, CLASS ARBITRATIONS, OR REPRESENTATIVE ACTIONS, AS SET FORTH BELOW. 1\. Who May Use the Services 1.1. Eligibility. Who May Use the Services. You must be 18 years of age or older and not be a Prohibited Person to use the Services. A “Prohibited Person” is any person or entity that is (a) listed on (i) any U.S. Government list of prohibited or restricted parties, including the U.S. Treasury Department's list of Specially Designated Nationals or the U.S. Department of Commerce Denied Persons List or Entity List; (ii) the EU consolidated list of persons, groups and entities subject to financial sanctions; (iii) the UK Consolidated List of Financial Sanctions Targets; or (iv) any of Switzerland's respective sanctions lists, (b) located or organized in any U.S. embargoed countries or any country that has been designated by the U.S. Government as “terrorist supporting”, (c) a citizen, resident, or organized in, the following jurisdictions (the “Prohibited Jurisdictions”): Abkhazia, Afghanistan, Angola, Belarus, Burundi, Central African Republic, Congo, Cuba, Crimea, Ethiopia, Guinea-Bissau, Iran, Ivory Coast (Cote D’Ivoire), Lebanon, Liberia, Libya, Mali, Burma (Myanmar), Nicaragua, North Korea, Northern Cyprus, Russia, Somalia, Somaliland, South Ossetia, South Sudan, Sudan, Syria, Ukraine (Donetsk and Luhansk regions), United States, Venezuela, Yemen, Zimbabwe; (d) otherwise a party with which the Company is prohibited to deal under the laws of the U.S., the EU (or any of its Member States), the UK, or any applicable foreign jurisdiction, or (e) owned or controlled by such persons or entities listed in (a)-(d). The Company may utilize certain tools, such as IP-based geofencing and “VPN blocking” measures, to enforce the above restrictions. By using the Services and/or the App, you represent that you are not a Prohibited Person, and are not accessing the services from a Prohibited Jurisdiction using a virtual private network. These measures may be in addition to those measures enacted by the Unit Protocol directly. You acknowledge and agree that you are solely responsible for complying with all applicable laws of the jurisdiction you are a resident of, or located or accessing the Services from, in connection with your use of the Services. By using the Services, you represent and warrant that you meet these requirements and will not be using the Services for any illegal activity or to engage in the prohibited activities in Section 2.4. 2\. Rights We Grant You 2.1. The “Unit Protocol” is a means to replicate native digital assets from certain blockchains, such as BTC, ETH, and SOL, on the Hyperliquid L1. The protocol utilizes a distributed set of “operators” to validate transfers to the Unit Protocol MPC vaults and effectuate “mint” transactions on the Hyperliquid L1. You acknowledge and agree that we make no representations and warranties with respect to the Unit Protocol. Certain elements of the Unit Protocol may be made publicly available under an open-source or source-available license and these Terms do not override or supersede the terms of any such licenses. Notwithstanding anything to the contrary set forth herein, you agree that the terms of Section 6 (Disclaimers, Limitations of Liability and Indemnification) apply, mutatis mutandis, to your use of the Unit Protocol. 2.2. Documentation. The Services may display, include, or make available documentation, statistics, research, blog posts, images, videos, commentary, and other descriptions or materials related to the Unit Protocol community and the Unit Protocol (collectively, “Documentation”). This Documentation may also include summaries of digital asset balances held by connected wallets on the Hyperliquid L1; these balances are for informational purposes only and should not be construed as an indication that the Unit Protocol or the Company is holding such digital assets on your behalf. Such assets are held by you in your digital asset wallet. Such Documentation is part of the Services. 2.3. Right to Use Services. We hereby grant you a limited, revocable, non-transferable, non-sublicensable right and license to access and use the Services for your own, or your internal use only, provided that you comply with these Terms in connection with all such use. If any software, content or other materials owned or controlled by us are distributed or made available to you as part of your use of the Services (such as the Documentation), we hereby grant you a personal, non-assignable, non-sublicensable, non-transferrable, and non-exclusive right and license to download, access and display such software, content and materials provided to you as part of the Services, in each case for the sole purpose of enabling you to use the Services as permitted by these Terms. Your access and use of the Services may be interrupted from time to time for any or for no reason, including, without limitation, in the event of the malfunction of equipment, periodic updating, maintenance or repair of the Service or other actions that the Company, in its sole discretion, may elect to take. You agree that we shall have no liability to you arising from or related to any inability to access the Services. 2.4. Restrictions On Your Use of the Services. You shall not do any of the following in connection with your use of the Services, unless applicable laws or regulations prohibit these restrictions or you have our written permission to do so: (a) modify, copy, distribute, transmit, display, perform, reproduce, duplicate, publish, license, create derivative works from, or offer for sale any information contained on, or obtained from or through, the Services, except for temporary files that are automatically cached by your web browser for display purposes, or as otherwise expressly permitted in these Terms; (b) use, reproduce or remove any copyright, trademark, service mark, trade name, slogan, logo, image, or other proprietary notation displayed on or through the Services; (c) use automation software (bots), hacks, modifications (mods) or any other unauthorized third-party software designed to access, use, or modify the Services; (d) access or use the Services in any manner that could disable, overburden, damage, disrupt or impair the Services or interfere with any other party’s access to or use of the Services or use any device, software or routine that causes the same; (e) attempt to gain unauthorized access to, interfere with, damage or disrupt the Services, or the computer systems or networks connected to the Services; (f) circumvent, remove, alter, deactivate, degrade or thwart any technological measure or content protections of the Services or any of the computer systems, wallets, accounts, protocols or networks connected to the Services; (g) use any robot, spider, crawlers or other automatic device, process, software or queries that intercepts, “mines,” scrapes or otherwise accesses the Services to monitor, extract, copy or collect information or data from or through the Services, or engage in any manual process to do the same; (h) introduce any viruses, trojan horses, worms, logic bombs or other materials that are malicious or technologically harmful into our systems; (j) impersonate any other person or entity using the Services, including by falsely stating, implying or otherwise misrepresenting your affiliation with any person or entity; (k) violate any applicable law or regulation in connection with your access to or use of the Services; or (l) access or use the Services in any way not expressly permitted by these Terms. 2.5. Interactions with Other Users on the Services. You are responsible for your interactions with other users on, through, or in connection with the Services. While we reserve the right to monitor interactions between users, we are not obligated to do so, and you acknowledge and agree that we cannot be held liable for your interactions with other users, or for any user's actions or inactions. If you have a dispute with one or more users, you release the Company Persons (as defined below) from claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such dispute(s). In entering into this release you expressly waive any protections (whether statutory or otherwise) that would otherwise limit the coverage of this release to include only those claims which you may know or suspect to exist in your favor at the time of agreeing to this release. 3\. Ownership and Content 3.1. Ownership of the Services. The Services, including their “look and feel” (e.g., text, graphics, images, logos), proprietary content, information and other materials, are protected under copyright, trademark and other intellectual property laws. You agree that the Company and/or its licensors own all right, title and interest in and to the Services (including any and all intellectual property rights therein) and you agree not to take any action(s) inconsistent with such ownership interests. We reserve all rights in connection with the Services and its content. 3.2. Ownership of Feedback. You acknowledge and expressly agree that any contribution by you of feedback, bug reports, comments, and suggestions for improvements to the Services in any forum (“Feedback”), does not and will not give or grant you any right, title or interest in the Services or in any such Feedback. All Feedback becomes the sole and exclusive property of the Company, and you agree that the Company may use and disclose Feedback in any manner and for any purpose whatsoever without further notice or compensation to you, and without retention by you of any proprietary or other right or claim. You hereby assign to the Company any and all right, title and interest (including, but not limited to, any patent, copyright, trade secret, trademark, show-how, know-how, moral rights and any and all other intellectual property right) that you may have in and to any and all Feedback, and, to the extent that any rights in and to Feedback cannot be assigned (including without limitation any moral rights), you hereby agree to waive such rights. 4\. Third Party Services and Materials 4.1. Third Party Services and Materials. The Services may display, include, link to, or otherwise make available services, content, data, information, applications, or materials from third parties or provide links to certain third-party websites (“Third-Party Services and Materials”). All Third-Party Services and Materials are made available solely as a convenience, and the Company does not endorse any Third-Party Services and Materials. You agree that your access and use of such Third-Party Services and Materials is governed solely by the terms and conditions of such Third-Party Services and Materials, as applicable. the Company is not responsible or liable for, and makes no representations as to any aspect of such Third-Party Services and Materials, including, without limitation, their content or the manner in which they handle, protect, manage, or process data, or any interaction between you and the provider of such Third-Party Services and Materials. the Company is not responsible for examining or evaluating the content, accuracy, completeness, availability, timeliness, validity, copyright compliance, legality, decency, quality or any other aspect of such Third-Party Services and Materials or websites. You irrevocably waive any claim against the Company with respect to such Third-Party Services and Materials. We are not liable for any damage or loss caused or alleged to be caused by or in connection with your enablement, access, or use of any such Third-Party Services and Materials, or your reliance on the privacy practices, data security processes, or other policies of such Third-Party Services and Materials. Third-Party Services and Materials and links to other websites are provided solely as a convenience to you. 5\. Our Privacy Policy; Data Retention and Law Enforcement 5.1. Privacy Policy. Our Privacy Policy describes how we handle the information you provide to us when you use the Services. For an explanation of our privacy practices, visit our Privacy Policy located at \[URL\]. 5.2 Information Retention. We retain information pertaining to each use of the Unit Protocol, including origin public wallet address, destination public wallet address, certain IP information, assets utilized, and other relevant details. While transactions may not be publicly traceable via blockchain explorers, by using the Services you acknowledge and consent to this relevant information being collected and stored by us. The Unit Protocol is not a “mixer” and should not be considered as such. While we acknowledge the value of financial privacy, the Company is committed to ensuring the safety and security of the Unit Protocol and digital asset ecosystem. 5.3. Compliance with Law Enforcement. The information noted in Section 5.2, as well as any other information the Company collects, may be shared with law enforcement or other governmental authorities pursuant to validly issued subpoenas or similar binding processes. Law enforcement officials may contact us directly at legal (at) hyperunit (dot) xyz. 6\. Disclaimers, Limitations of Liability and Indemnification 6.1. Disclaimers (a) Your access to and use of the Services (including, for clarity, any Documentation) and, separately, the Unit Protocol , is entirely at your own risk. You understand and agree that the Services are provided to you on an “AS IS” and “AS AVAILABLE” basis. Without limiting the foregoing, to the maximum extent permitted under applicable law, the Company, its subsidiaries, affiliates, related companies, service providers, and its and their officers, directors, supervisors, consultants, advisors, agents, representatives, partners, and licensors (collectively, the “Company Persons”) DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION ANY WARRANTIES RELATING TO TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, USAGE, QUALITY, PERFORMANCE, SUITABILITY OR FITNESS OF THE SERVICES AND THE UNIT PROTOCOL FOR ANY PARTICULAR PURPOSE, OR AS TO THE ACCURACY, QUALITY, SEQUENCE, RELIABILITY, WORKMANSHIP OR TECHNICAL CODING THEREOF, OR THE ABSENCE OF ANY DEFECTS THEREIN WHETHER LATENT OR PATENT. the Company Persons make no warranty or representation and disclaim all responsibility and liability for: (a) the completeness, accuracy, availability, timeliness, security or reliability of the Services (including any Documentation) and the Unit Protocol; (b) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or the Unit Protocol; (c) the operation or compatibility with any other application or any particular system or device; (d) whether the Services or the Unit Protocol will meet your requirements or be available on an uninterrupted, secure or error-free basis; and (e) whether the Services or the Unit Protocol will protect your assets from theft, hacking, cyber-attack, or other form of loss caused by third-party conduct. Nothing contained in the Services constitutes, or is meant to constitute, financial, legal, or other professional advice of any kind. If you require advice in relation to any financial, legal, or other professional matter you should consult an appropriate professional. No advice or information, whether oral or written, obtained from the Company Persons or through the Services, will create any warranty or representation not expressly made herein. (b) THE LAWS OF CERTAIN JURISDICTIONS, INCLUDING THE CAYMAN ISLANDS, DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES AS SET FORTH IN SECTION 6.2 BELOW. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS, EXCLUSIONS, OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS. 6.2. Limitations of Liability TO THE EXTENT NOT PROHIBITED BY LAW, YOU AGREE THAT (i) IN NO EVENT WILL COMPANY PERSONS BE LIABLE (A) FOR DAMAGES OF ANY KIND, INCLUDING INDIRECT SPECIAL, EXEMPLARY, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF USE, DATA OR PROFITS, BUSINESS INTERRUPTION OR ANY OTHER DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OR INABILITY TO USE THE SERVICES), HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER UNDER THESE TERMS OR OTHERWISE ARISING IN ANY WAY IN CONNECTION WITH THE SERVICES OR THESE TERMS AND WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE), EVEN IF COMPANY PERSONS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE, OR (B) FOR ANY OTHER CLAIM, DEMAND, OR DAMAGES WHATSOEVER RESULTING FROM OR ARISING OUT OF OR IN CONNECTION WITH THESE TERMS OR THE DELIVERY, USE, OR PERFORMANCE OF THE SERVICES; AND (ii) IN THE EVENT THAT COMPANY PERSONS ARE FOUND TO HAVE ANY LIABILITY TO YOU NOTWITHSTANDING THE FOREGOING, SUCH LIABILITY SHALL NOT EXCEED THE GREATER OF (1) ONE HUNDRED DOLLARS ($100.00), (2) THE AMOUNT YOU PAID COMPANY PERSONS, IF ANY, IN THE PAST SIX (6) MONTHS FOR THE SERVICES (OR OFFERINGS PURCHASED ON THE SERVICES) GIVING RISE TO THE CLAIM; OR (3) THE STATUTORY REMEDY FOR SUCH CLAIM. THE FOREGOING LIMITATIONS WILL APPLY EVEN IF THE ABOVE STATED REMEDY FAILS OF ITS ESSENTIAL PURPOSE. 6.3. Acknowledgement; Assumption of Risks (a) By using the Services or the Unit Protocol, you represent that you have sufficient knowledge and experience in any business or financial matters that may be applicable, including a sufficient understanding of blockchain technologies, cryptocurrencies, and other digital assets, storage mechanisms, and blockchain-based software systems to be able to assess and evaluate the risks and benefits of the Services contemplated hereunder, and will bear the risks thereof, including loss of all amounts paid or stored, and the risk that the cryptocurrencies and other digital assets may have little or no value. You acknowledge and agree that there are risks associated with purchasing and holding cryptocurrency and using blockchain technology. These include, but are not limited to, risk of losing access to cryptocurrency or digital assets due to slashing; loss of private key(s); custodial error or purchaser or user error; risk of mining, staking, or blockchain-related attacks; risk of hacking and security weaknesses; risk of unfavorable regulatory intervention in one or more jurisdictions; risk related to token taxation; risk of personal information disclosure; risk of uninsured losses; volatility risks; and unanticipated risks. (b) You acknowledge that vulnerabilities in the Unit Protocol programming and design or other vulnerabilities that may arise due to hacking or other security incidents can have adverse effects to digital assets, including but not limited to significant volatility and risk of loss. (c) You acknowledge that there are inherent risks associated with using or interacting with public blockchains and blockchain technology. There is no guarantee that such technology will be available or not subject to errors, hacking, or other security risks. Blockchain protocols may also be subject to sudden changes in operating rules, including forks, and it is your responsibility to make yourself aware of upcoming operating changes. 6.4. Indemnification By entering into these Terms and accessing or using the Services or the Unit Protocol, you agree that you shall indemnify, and hold the Company Persons harmless, and at the Company’s election defend such Company Persons from and against any and all claims, costs, damages, losses, liabilities and expenses (including attorneys’ fees and costs) incurred by the Company Persons arising out of or in connection with: (a) your violation or breach of any term of these Terms or any applicable law or regulation; (b) your violation of any rights of any third party; (c) your use or misuse of the Services or the Unit Protocol; or (d) your dishonesty, negligence, fraudulence or willful misconduct. If you are obligated to indemnify any Company Person hereunder, then you agree that the Company (or, at its discretion, the applicable Company Persons) will have the right, in its sole discretion, to control any action or proceeding and to determine whether the Company wishes to settle, and if so, on what terms, and you agree to fully cooperate with the Company in the defense or settlement of such claim. 6.5. Third Party Beneficiaries You and the Company acknowledge and agree that the Company Persons (other than the Company) are third party beneficiaries of these Terms, including under Sections 2.5, 6 and 7. 6.6. Third Party Rights. Any Company Person not being a party to these Terms, may enforce any rights granted to it pursuant to these Terms in its own right as if it were a party to these Terms. Except as expressly provided in this paragraph, a person who is not a party to these Terms shall not have any rights under the Contracts (Rights of Third Parties) Act, (as amended) to enforce any term of these Terms. Notwithstanding any term of these Terms, the consent of or notice to any person who is not a party to this Agreement shall not be required for any termination, rescission or agreement to any variation, waiver, release or settlement under these Terms at any time. 7\. Arbitration and Class Action Waiver 7.1. READ THIS SECTION CAREFULLY – IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT AND TO HAVE A JURY HEAR YOUR CLAIMS. IT CONTAINS PROCEDURES FOR MANDATORY BINDING ARBITRATION AND A CLASS ACTION WAIVER. 7.2. Informal Process First. You and the Company agree that in the event of any dispute between you and the Company Persons, either party will first contact the other party and make a good faith sustained effort to resolve the dispute before resorting to more formal means of resolution, including without limitation, any court action, after first allowing the receiving party 30 days in which to respond. Both you and the Company agree that this dispute resolution procedure is a condition precedent which must be satisfied before initiating any arbitration against the other party. Nothing in this clause shall prevent a party from seeking interim or provisional relief where it is reasonably necessary to do so. 7.3. Arbitration Agreement and Class Action Waiver. After the informal dispute resolution process, any remaining dispute, controversy, or claim (collectively, “Claim”) relating in any way to the Services and any usage of the Unit Protocol, will be resolved by arbitration, including threshold questions of arbitrability of the Claim, and except as otherwise set forth in Section 7.5 (Exceptions). You and the Company agree that any Claim will be settled by final and binding arbitration, using the English language, administered by JAMS under its Comprehensive Arbitration Rules and Procedures (the “JAMS Rules”) then in effect (those rules are deemed to be incorporated by reference into this section, and as of the date of these Terms). Legislation concerning arbitration may govern the arbitrability of all disputes in an applicable jurisdiction. However, the arbitrator will apply applicable substantive law consistent with such legislation and the applicable statute of limitations or condition precedent to suit. The arbitration will be handled by a sole arbitrator appointed in accordance with the JAMS Rules and the seat of the arbitration shall be New York. Judgment on the arbitration award may be entered in any court having jurisdiction thereof. Any arbitration under these Terms will take place on an individual basis – class arbitrations and class actions are not permitted. You understand that by agreeing to these Terms, you and the Company are each waiving any right to participate in a class action or class arbitration. 7.4. Batch Arbitration. To increase the efficiency of administration and resolution of arbitrations, you and the Company agree that in the event that there are one-hundred (100) or more individual Claims of a substantially similar nature filed against Company Persons by or with the assistance of the same law firm, group of law firms, or organizations, then within a thirty (30) day period (or as soon as possible thereafter), JAMS shall (1) administer the arbitration demands in batches of 100 Claims per batch (plus, to the extent there are less than 100 Claims left over after the batching described above, a final batch consisting of the remaining Claims); (2) appoint one arbitrator for each batch; and (3) provide for the resolution of each batch as a single consolidated arbitration with one set of filing and administrative fees due per side per batch, one procedural calendar, one hearing (if any) in a place to be determined by the arbitrator, and one final award (“Batch Arbitration”). All parties agree that Claims are of a “substantially similar nature” if they arise out of or relate to the same event or factual scenario and raise the same or similar legal issues and seek the same or similar relief. To the extent the parties disagree on the application of the Batch Arbitration process, the disagreeing party shall advise JAMS, and JAMS shall appoint a sole standing arbitrator to determine the applicability of the Batch Arbitration process (“Administrative Arbitrator”). In an effort to expedite resolution of any such dispute by the Administrative Arbitrator, the parties agree the Administrative Arbitrator may set forth such procedures as are necessary to resolve any disputes promptly. The Administrative Arbitrator’s fees shall be paid by the Company. You and the Company agree to cooperate in good faith with JAMS to implement the Batch Arbitration process including the payment of single filing and administrative fees for batches of Claims, as well as any steps to minimize the time and costs of arbitration, which may include: (1) the appointment of a discovery special master to assist the arbitrator in the resolution of discovery disputes; and (2) the adoption of an expedited calendar of the arbitration proceedings. This Batch Arbitration provision shall in no way be interpreted as authorizing a class, collective and/or mass arbitration or action of any kind, or arbitration involving joint or consolidated claims under any circumstances, except as expressly set forth in this provision. 7.5. Exceptions. Notwithstanding the foregoing, you and the Company agree that the following types of disputes will be resolved in a court of proper jurisdiction: (i) disputes or claims within the jurisdiction the Summary Court of the Cayman Islands consistent with the jurisdictional and value limits that may apply, as long as it is brought and maintained as an individual dispute and not as a class, representative, or consolidated action or proceeding; (ii) disputes or claims where the sole form of relief sought is injunctive relief (including public injunctive relief); or (iii) intellectual property disputes. 7.6. Costs of Arbitration. Payment of all filing, administration, and arbitrator costs and expenses will be governed by the JAMS Rules, except that if you demonstrate that any such costs and expenses owed by you under those rules would be prohibitively more expensive than a court proceeding, the Company will pay the amount of any such costs and expenses that the arbitrator determines are necessary to prevent the arbitration from being prohibitively more expensive than a court proceeding (subject to possible reimbursement as set forth below). Fees and costs may be awarded as provided pursuant to applicable law. If the arbitrator finds that either the substance of your claim or the relief sought in the demand is frivolous or brought for an improper purpose (as measured by the applicable standards set forth in civil procedures), then the payment of all fees will be governed by the JAMS rules. In that case, you agree to reimburse the Company for all monies previously disbursed by it that are otherwise your obligation to pay under the applicable rules. If you prevail in the arbitration and are awarded an amount that is less than the last written settlement amount offered by the Company before the arbitrator was appointed, the Company will pay you the amount awarded in the arbitration. The arbitrator may make rulings and resolve disputes as to the payment and reimbursement of fees or expenses at any time during the proceeding and upon request from either party made within 14 days of the arbitrator’s ruling on the merits. 7.7. WAIVER OF RIGHT TO BRING CLASS ACTION AND REPRESENTATIVE CLAIMS. To the fullest extent permitted by applicable law, you and the Company each agree that except as expressly set forth in Section 7.4 (Batch Arbitration), any proceeding to resolve any dispute, claim, or controversy will be brought and conducted ONLY IN THE RESPECTIVE PARTY’S INDIVIDUAL CAPACITY AND NOT AS PART OF ANY CLASS (OR PURPORTED CLASS), CONSOLIDATED, MULTIPLE-PLAINTIFF, OR REPRESENTATIVE ACTION OR PROCEEDING (“CLASS ACTION”). You and the Company AGREE TO WAIVE THE RIGHT TO PARTICIPATE AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS ACTION. You and the Company EXPRESSLY WAIVE ANY ABILITY TO MAINTAIN A CLASS ACTION IN ANY FORUM. If the dispute is subject to arbitration, then except as expressly set forth in Section 7.4 (Batch Arbitration), THE ARBITRATOR WILL NOT HAVE THE AUTHORITY TO COMBINE OR AGGREGATE CLAIMS, CONDUCT A CLASS ACTION, OR MAKE AN AWARD TO ANY PERSON OR ENTITY NOT A PARTY TO THE ARBITRATION. Further, you and the Company agree that except as expressly set forth in Section 7.4 (Batch Arbitration), the ARBITRATOR MAY NOT CONSOLIDATE PROCEEDINGS FOR MORE THAN ONE PERSON’S CLAIMS, AND IT MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A CLASS ACTION. For the avoidance of doubt, however, you can seek public injunctive relief to the extent authorized by law and consistent with the Exceptions clause above. IF THIS CLASS ACTION WAIVER IS LIMITED, VOIDED, OR FOUND UNENFORCEABLE, THEN, UNLESS THE PARTIES MUTUALLY AGREE OTHERWISE, THE PARTIES’ AGREEMENT TO ARBITRATE SHALL BE NULL AND VOID WITH RESPECT TO SUCH PROCEEDING SO LONG AS THE PROCEEDING IS PERMITTED TO PROCEED AS A CLASS ACTION. If a court decides that the limitations of this paragraph are deemed invalid or unenforceable, any putative class, private attorney general, or consolidated or representative action must be brought in a court of proper jurisdiction and not in arbitration. 8\. Additional Provisions 8.1. Updating These Terms. We may modify these Terms from time to time in which case we will update the “Last Revised” date at the top of these Terms. If we make changes that are material, we will use reasonable efforts to attempt to notify you, such as by placing a notice on the Website. However, it is your sole responsibility to review these Terms from time to time to view any such changes. The updated Terms will be effective as of the time of posting, or such later date as may be specified in the updated Terms. Your continued access or use of the Services after the modifications have become effective will be deemed your acceptance of the modified Terms. No amendment shall apply to a dispute for which an arbitration has been initiated prior to the change in Terms. 8.2. Suspension; Termination. If you breach any of the provisions of these Terms, all licenses granted by the Company will terminate automatically. Additionally, the Company may, in its sole discretion, suspend or terminate your access to or use of any of the Services, with or without notice, for any or no reason, including, without limitation, (i) if we believe, in our sole discretion, you have engaged in any of the prohibited activities set forth in Section 2.4; (ii) if you provide any incomplete, incorrect or false information to us; (iii) if you have breached any portion of these Terms; and/or (iv) if we determine such action is necessary to comply with these Terms, any of our policies, procedures or practices, or any law, rule, or regulation. All sections which by their nature should survive the termination of these Terms shall continue in full force and effect subsequent to and notwithstanding any termination of this Agreement by the Company or you. Termination will not limit any of the Company’s other rights or remedies at law or in equity. 8.3. Injunctive Relief. You agree that a breach of these Terms will cause irreparable injury to the Company for which monetary damages would not be an adequate remedy and the Company shall be entitled to equitable relief in addition to any remedies it may have hereunder or at law without a bond, other security or proof of damages. 8.4. Force Majeure. We will not be liable or responsible to you, nor be deemed to have defaulted under or breached these Terms, for any failure or delay in fulfilling or performing any of our obligations under these Terms or in providing the Services, when and to the extent such failure or delay is caused by or results from any events beyond our ability to control, including acts of God; flood, fire, earthquake, epidemics, pandemics, tsunami, explosion, war, invasion, hostilities (whether war is declared or not), terrorist threats or acts, riot or other civil unrest, government order, law, or action, embargoes or blockades, strikes, labor stoppages or slowdowns or other industrial disturbances, shortage of adequate or suitable Internet connectivity, telecommunication breakdown or shortage of adequate power or electricity, and other similar events beyond our control. 8.5. Miscellaneous. If any provision of these Terms shall be unlawful, void or for any reason unenforceable, then that provision shall be deemed severable from these Terms and shall not affect the validity and enforceability of any remaining provisions. These Terms and the licenses granted hereunder may be assigned by the Company but may not be assigned by you without the prior express written consent of the Company. No waiver by either party of any breach or default hereunder shall be deemed to be a waiver of any preceding or subsequent breach or default. The section headings used herein are for reference only and shall not be read to have any legal effect. 8.6. Governing Law and Jurisdiction. These Terms are governed by the laws of New York, without regard to conflict of laws principles. Any disputes arising out of or relating to these Terms, the Services, or any transactions contemplated herein shall be governed by and construed in accordance with the laws New York. [PreviousRegulatory Compliance](https://docs.hyperunit.xyz/legal/regulatory-compliance) [NextPrivacy Policy](https://docs.hyperunit.xyz/legal/privacy-policy) Last updated 3 months ago --- # Is my unique deposit address permanent? | Unit Yes. Protocol (Unit-generated "deposit" and "withdrawal") addresses are generated by the Guardian Network, and are permanently tied to their corresponding destination address. 1. Alice has a Hyperliquid wallet `0x1234...9876` , and wants to deposit BTC. 2. The Unit protocol generates a deposit address for Alice: `bc1q...ukhe` This address is permanently and uniquely tied to Alice's HL address `0x1234...9876` 3. Any and all future transfers made to Alice's deposit address will be credited to `0x1234...9876` on Hyperliquid. 4. If Alice begins to use a different account on Hyperliquid `0x6789...4321` , she must generate a new unique deposit address for this account. The same is true for withdrawals, and withdrawal addresses. [PreviousHow long does a deposit/withdrawal take?](https://docs.hyperunit.xyz/faq/how-long-does-a-deposit-withdrawal-take) [NextCan I generate multiple deposit addresses for my Hyperliquid wallet?](https://docs.hyperunit.xyz/faq/can-i-generate-multiple-deposit-addresses-for-my-hyperliquid-wallet) Last updated 8 months ago --- # FAQ | Unit [](https://docs.hyperunit.xyz/faq#general-faqs) General FAQ’s ------------------------------------------------------------------ [**What is Unit?**](https://docs.hyperunit.xyz/) [**Who is the team behind the project?**](https://docs.hyperunit.xyz/unit/about-unit/team) [**What are Unit Guardians?**](https://docs.hyperunit.xyz/architecture/components#guardian-network) [**How do I get in touch with Unit?**](https://docs.hyperunit.xyz/faq/how-do-i-get-in-touch-with-unit) ### [](https://docs.hyperunit.xyz/faq#product) **Product** [**How do I deposit or withdraw Bitcoin from Hyperliquid?**](https://docs.hyperunit.xyz/how-to/deposit) [**How long does a deposit/withdrawal take?**](https://docs.hyperunit.xyz/faq/how-long-does-a-deposit-withdrawal-take) [**Where's my transaction?**](https://docs.hyperunit.xyz/faq/wheres-my-transaction) [**Is my unique deposit address permanent?**](https://docs.hyperunit.xyz/faq/is-my-unique-deposit-address-permanent) [**Can I generate multiple deposit addresses for my Hyperliquid wallet?**](https://docs.hyperunit.xyz/faq/can-i-generate-multiple-deposit-addresses-for-my-hyperliquid-wallet) [**What type of Bitcoin address does Unit derive?**](https://docs.hyperunit.xyz/faq/what-type-of-bitcoin-deposit-address-does-unit-derive) [**How do fees on Unit work?**](https://docs.hyperunit.xyz/faq/how-do-fees-on-unit-work) **Are there any audits planned?** [PreviousToken Metadata (Testnet)](https://docs.hyperunit.xyz/developers/key-addresses/testnet/token-metadata-testnet) [NextHow do I get in touch with Unit?](https://docs.hyperunit.xyz/faq/how-do-i-get-in-touch-with-unit) Last updated 8 months ago ---