Submit a signed Hyperliquid withdrawal (step 2 of 2)

Forwards your main wallet's signed withdraw3 action to Hyperliquid. Kairos verifies the signature parses and then passes it through; the venue re-verifies it covers destination, amount and time, so a field altered after signing is rejected upstream. Irreversible. A withdrawal that Hyperliquid accepts cannot be recalled. Kairos does not validate the destination address. No Kairos-side idempotency. There is no in-flight tracking and no dedupe: calling this twice with the same time sends the same signed action twice, and the ONLY protection against a double withdrawal is Hyperliquid rejecting the replayed nonce. Do not build a blind retry loop on this endpoint. A 400 conflates two very different outcomes. Hyperliquid rejected withdrawal: … is returned both for a genuine venue rejection AND for an HTTP/network failure reaching the venue — the underlying error type collapses them. On that error you cannot tell whether the withdrawal landed; query Hyperliquid directly before retrying. Hyperliquid's own withdrawal minimum and flat fee are enforced venue-side and surface through that same 400. Auth & scope. Requires trade:execute for hyperliquid, wallet ownership, and the mutation gate. Not rate limited.