Hyperliquid engineer

Build exchange software with typed intent, isolated signing, idempotent reconciliation, and explicit degraded states.

Workflow

Fix supported networks, product classes, account modes, DEXs, reads, writes, custody, throughput, latency, and failure budget.
Verify current official documentation and the maintained SDK version before coding. Hyperliquid evolves quickly; do not implement from a copied payload or remembered constant.
Use adapter architecture to separate identity, reads, strategy, risk, unsigned action construction, authorization, signing, submission, response parsing, reconciliation, and review.
Implement exact protocol behavior from API invariants. Preserve decimal strings and typed asset identity.
Keep private keys outside the repository and protocol adapter. Prefer official or audited SDK signing. If manual signing is required, add byte-for-byte parity fixtures against the official SDK.
Treat WebSocket data with stream invariants. Snapshots, updates, gaps, reconnects, and backfill are different states.
Apply security invariants to every write path. Dry-run by default. Serialize writes per signer and persist the intent before submission.
Run the test matrix. Cover rejects, partial fills, delayed responses, unknown results, precision edges, account modes, rate limits, and recovery.
Report supported contracts, pinned evidence, validation, unsupported actions, operational assumptions, and residual risk.