Hyperliquid Advanced Actions for Openclaw

Prerequisites

• Use the same Hyperliquid SDK and integration header as the standard hyperliquid-orders workflow.
• Run against the configured network; the skill metadata defaults to testnet.
• Keep the main wallet private key off the desk computer. API wallet approval normally occurs in the Hyperliquid app and must be signed by the main wallet.
• Use one Execution Trader process per API wallet to prevent nonce collisions.

Dead-man's switch

from hyperliquid.utils.signing import get_timestamp_ms

# Schedule cancellation at least 5 seconds in the future
res = exchange.schedule_cancel(get_timestamp_ms() + 10 * 60 * 1000)

# Clear the scheduled cancellation
res = exchange.schedule_cancel(None)

TypeScript uses exchange.scheduleCancel({ time: Date.now() + 600_000 }); omit time to clear it. The account is limited to 10 triggers per day, reset at 00:00 UTC.

TWAP

TWAP is not exposed through Python's high-level Exchange; use the TypeScript SDK or a raw action.

const twap = await exchange.twapOrder({
  twap: { a, b: true, s: "10", r: false, m: 30, t: true }
});

const twapId = (twap.response.data.status as {
  running: { twapId: number }
}).running.twapId;

await exchange.twapCancel({ a, t: twapId });

The raw action uses type: "twapOrder" with the a, b, s, r, m, and t parameters. TWAP duration is 5 minutes to 7 days in the documentation, while the TypeScript schema caps m at 1440 minutes; longer runs require the raw action.

Spot orders

Resolve the pair through spotMeta, calculate size precision from the base token's szDecimals, calculate price precision as 8 - szDecimals, and verify that order value is at least 10 quote tokens. Use spotClearinghouseState to read balances.

Expiration and addressing

In Python, configure a following-action expiration with exchange.set_expires_after(get_timestamp_ms() + 60_000). TypeScript supports per-call expiresAfter. For vault or sub-account execution, configure Python's vault_address, TypeScript's defaultVaultAddress, or a per-call vaultAddress only when the request explicitly authorizes it.

Action and account fields

Generated records and operational metadata

• Ticket records should state action type, account or vault address, asset or pair, size, price or duration, reduce-only status, randomization, and requested execution time.
• TWAP monitoring records the returned twapId and slice fills from twapStates or userTwapSliceFills; TWAP fills carry a zero hash.
• Spot calculations should retain the resolved pair metadata, base-token decimals, rounded size, rounded price, and notional validation.
• API wallet records should identify the agent name and lifecycle status without exposing private keys. Named agents may include valid_until <ms> and expire for up to 180 days.
• Desk configuration records any explicitly approved vault or sub-account address in desk.md.
• Excluded actions are classified as transfers, withdrawals, balance-class transfers, vault or sub-account fund movements, builder fees, staking, or margin abstraction changes.