Syncs the SDK with the Aug-2026 Hyperliquid API drop (HIP-4 outcome templates) and lands two opt-in transport features. All schema changes were verified against upstream nktkas/hyperliquid v0.33.3, live testnet probes, and the full offline gate (format/lint/docs/types/jsdoc/export/imports + 2034 tests, 0 fail).
Added
HIP-4 outcome templates and usdcRouting (#98–#111). New info.outcomeTemplates and info.usdcRouting endpoints, exchange.activateOutcomeDeployer, and the outcome sub-actions of spotDeploy. outcomeTemplates is deliberately widened beyond upstream after live testnet probes: it accepts the questionOutcome / "question" roles and the uDecimal, uInt, and shortString keywords. New optional parameters: twapOrder.details, reserveRequestWeight.destination, and marginTable.dex.
InfoCacheTransport. An opt-in TTL cache in front of eight slow-changing info endpoints, with param-distinct cache keys and in-flight request dedup — repeated metadata lookups no longer cost a round trip each.
retryOnRateLimit transport option. Opt-in 429 retry that honors the server's Retry-After header. Off by default; no existing behavior changes unless you enable it.
Changed
Schemas widened to the current API surface. Order grouping cap raised from 80,000 to 1e8; enum widenings across OrderProcessingStatus, twapHistory, and FrontendOpenOrder; new borrowLendUserState health states; the userFees stakingLink union; and drift fixes in UserFill, spotClearinghouseState, outcomeMeta, settledOutcome, subAccounts2, and legalCheck.
Exchange weight billing now bills the longest array at any depth (#49). Previously only top-level arrays were counted, so nested batch actions under-reported their weight against the rate limiter.
Upgrading from 0.2.1
No API breaks and no changed defaults — the new transport features are opt-in. Schema widenings only accept more of what the live API already returns, so payloads that validated before still validate.
The new outcome-template shapes are documented in docs/reference/known-drift.md (entry 11); the official GitBook docs have not caught up yet and will be reconciled when they publish.