Hyperliquid Transaction Expiry and Delayed Order Risk
Summary
The document explains why an action such as placing an order can fail with an expiration message: the exchange’s L1 has not accepted it within the stated 15-second window. This delay protection is intended to prevent an action from executing much later when a connection is unstable or the chain is congested.
It describes a setting that disables the protection for traders who still want delayed actions to proceed. The key operational risk is that queued attempts may execute after connectivity returns or congestion eases. Multiple attempts could therefore create multiple orders, potentially changing the intended position—for example, repeated short orders meant to close a long could also open a short. The note gives no measurements of how often this happens or guidance on managing the risk beyond explaining the setting and its consequence.
Key ideas
- An action can expire if the L1 does not accept it within 15 seconds.
- Transaction delay protection limits the chance that an order executes long after it was submitted.
- Disabling the protection can allow delayed orders to execute after reconnection or reduced congestion.
- Repeated attempts may produce multiple orders and create an unintended position.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.