Hyperliquid Customer Support for Stuck Trades and Disputes

How can I contact Hyperliquid customer support?

There is no published contact route we could verify: no support email, no live chat and no ticket address, and no stated response time. What follows is what the available material does and does not cover.

In practice, use only a contact route you independently verify through official Hyperliquid surfaces. Save a screenshot of the route and a copy of the message you submit. The mobile app is not publicly disclosed in the supplied materials, so it cannot be assumed to provide a support inbox or a faster escalation path.

What should I collect before opening a Hyperliquid support ticket?

Gather the public wallet address, transaction hash, UTC timestamps, market and asset, order details, wallet screenshots, and a concise account of the requested resolution before contacting any verified route. Exact identifiers give a support reviewer a clearer starting point than a general statement that funds or an order are stuck.

For a delayed trade, preserve the order, trade, and liquidation records shown at the time of the issue. Hyperliquid lists onchain order, trade, and liquidation records as a strength, so record links or identifiers where available. For a spot order, include the pair, side, size, visible order status, and expected outcome. For a perpetual position, include the market, position direction, entry details, liquidation-related event if relevant, and timestamps.

Never include a seed phrase, private key, or wallet recovery material in a support request. If the dispute concerns a charge or account calculation, include the figures you expected and the figures displayed, then compare your notes with fees and funding rates. Account eligibility and verification are not publicly disclosed, so do not assume an outcome based on kyc requirements unless Hyperliquid gives you a verified instruction.

A delayed transaction needs an evidence trail

The supplied information leaves deposits and withdrawals undisclosed and does not describe a procedure for delayed or stuck transactions. That means the published material cannot confirm how Hyperliquid classifies a pending withdrawal, a wallet transaction, an unfilled order, or a disputed position event.

Label the problem precisely before asking for help. A wallet submission, an order that has not filled, a completed trade, and a liquidation-related event are different records. Include the moment you first noticed the problem, the current visible status, every transaction or order identifier, and what changed after submission.

Do not present a delay as proof that a refund is due. Ask for a status explanation, record review, or clarification of the event first. This approach also preserves a cleaner record if you later need to compare the issue with alternatives that publish more detailed support and dispute terms.

Disputes and refunds have no disclosed playbook

Hyperliquid is non-custodial and does not take custody of user funds. That fact does not establish that the platform can reverse a transaction, issue a refund, or resolve a disputed execution in any particular way. The supplied information does not publish a refund policy, appeal route, dispute timetable, or final decision process.

State the remedy you seek without assuming it is available. For example, request a review of a transaction status, trade record, order state, or liquidation-related record, then attach the evidence needed to identify it. If you believe protocol, validator, oracle, or smart contract behavior contributed to an outcome, describe the observable event and timestamp. The supplied materials do not describe an appeals scheme for those issues.

A non-custodial model can make accurate records more important because support cannot be treated as a conventional account-recovery or chargeback desk. Keep copies of each message, supporting screenshot, and onchain reference until the matter is resolved or a verified route gives a final response.