Hyperliquid API Wallet Nonce Management Across Multiple Bot Processes

How to prevent replay errors and nonce collisions when Hyperliquid strategies, subaccounts and workers submit actions concurrently.

Nonces belong to the signer

Hyperliquid tracks nonces per signing address. One API wallet acting for several subaccounts still shares one nonce set, so splitting business accounts does not automatically isolate concurrent writers.

Use one signer per execution process

Assign separate API wallets to independent strategies or subaccounts. This reduces coordination scope and limits the damage of a leaked or stalled process. Never reuse a deregistered agent address.

Allocate through an atomic counter

A single task should batch actions and allocate monotonically unique millisecond nonces. Fast-forward the counter to current time when necessary and persist enough state to prevent reuse after a crash.

Respect the acceptance window

Generated values must remain within the protocol time window. Monitor host clock drift and reject local timestamps that jump backward or too far forward.

Handle lifecycle events

Agent expiry, replacement, deregistration and an unfunded master can prune associated state. Rotate to a newly generated API wallet and revoke old authorization as a controlled deployment event.

Audit your Hyperliquid executor

TierZero develops Hyperliquid perps bots, market makers and secure deployment. See the official nonce documentation or request a review.

Production checklist

Before launch, define ownership, test fixtures, failure states, alerts and a rollback procedure. For a scoped engineering review, use the TierZero project form.