Hyperliquid Market-Making Bot

Hyperliquid market-making bot development

A quoting script is only one part of a market-making system. The production workload must also handle partial fills, cancelled orders, stale market data, connection loss and a process restart while positions remain open. We scope these operational paths alongside the strategy rules, rather than treating them as later additions.

You supply the markets, reference-price method, quoting parameters and permitted risk. We translate those requirements into an implementation plan with explicit interfaces and acceptance tests. A project can start with an API adapter or an order-management component instead of commissioning an entire trading platform.

Quoting, inventory and account state

The quoting component can calculate bid and ask targets using your spread, size and inventory-skew rules. Limits should account for current positions and outstanding orders, not just the most recent fill. Funding inputs can be included in a specified model, but neither funding income nor captured spread guarantees a positive net result.

The order manager tracks intended actions separately from acknowledged orders and observed fills. It must reconcile uncertain outcomes before resubmitting an action after a timeout. API permissions, signing requirements and rate limits are checked against the official Hyperliquid API documentation during implementation.

Controls and acceptance scenarios

• Stop creating quotes when required market data exceeds the configured age limit.
• Reject actions that breach the agreed position, order-size or account-exposure policy.
• Reconcile open orders and fills after reconnecting or restarting.
• Exercise partial-fill, rejection, timeout and cancellation scenarios with recorded inputs.
• Record quote decisions, exchange responses and resulting account state for review.

Emergency cancellation and position reduction are separate actions. A cancellation request is not proof that all orders have been cancelled; a flattening order is not a guarantee of an immediate fill. We define what the system should attempt, how the result is verified and when operator intervention is required.

What is included in the proposal

The proposal lists supported markets, components, tests, deployment ownership and handover materials. A dashboard, alert routing, historical replay and ongoing maintenance can be added to the agreed scope. Development fees are separated from hosting, data-provider and trading costs.

For technical background, see our Hyperliquid market-maker project planning guide. If you already have software, describe the missing component or failure mode rather than preparing a complete replacement specification.

Request a Hyperliquid development estimate with your markets, quoting rules, existing stack and interface requirements. Production accounts and credentials remain client-controlled; we provide engineering, not discretionary account management or a guaranteed-return product.