About this guide: I'm Lawrence, the writer behind supa.is. I've been tracking Hyperliquid order-type changes since February 2026, and the same question keeps coming up: how does the new dynamic suborder interval actually behave inside a TWAP order? This guide answers that directly, with links to the 7-day setup guide, trigger and max/min price guide, and order types guide where the surrounding mechanics are covered.
If you have ever watched a TWAP order on Hyperliquid and wondered why the suborders are not landing at perfectly even time gaps, you are not imagining it. The platform changed the execution model. The old mental model was simple: divide your total size by the number of slices, spread those slices evenly across the running window, and call it done. The current model is different. As of 2026-08, Hyperliquid supports 7-day running time on TWAP orders and uses dynamic suborder intervals rather than a fixed cadence. That single change affects how you size slices, how you estimate fill timing, and how you read the order status.
This guide explains the mechanism. It is not a step-by-step trading tutorial, and it does not pretend to have executed a live TWAP order for you. What it does is walk through the public documentation and the official announcement so you can build an accurate mental model of what the system actually does.
What a TWAP Order Does on Hyperliquid
A TWAP (Time-Weighted Average Price) order splits a larger position into smaller suborders and executes them over a defined time window. The goal is to reduce market impact. Instead of hitting the order book with one large order that could move the price, you let the system work through the size gradually.
On Hyperliquid, the TWAP order type lives alongside other order types in the trading interface and in the API. The TWAP order is one of the more complex ones because it has multiple interacting parameters: total size, running time, suborder interval logic, trigger conditions, and price constraints.
Before the recent update, the running time was effectively shorter and the suborder interval was more predictable. You could estimate the number of slices by dividing the total size by the per-slice size, and you could estimate the time between slices by dividing the running window by the number of slices. That arithmetic still works as a rough approximation, but it no longer describes what the engine actually does.
The 7-Day Running Time Change
The most visible change is the maximum running time. As of 2026-08, Hyperliquid allows TWAP orders to run for up to 7 days. The official announcement at Hyperliquid TWAP update confirms this extension.
Why does this matter in practice? A 7-day window changes the math of market impact. If you are trying to accumulate or distribute a large position, a longer window means each suborder can be smaller, which reduces the per-slice footprint on the order book. It also means the order is exposed to price movement for a longer period. Those two effects work in opposite directions, and the right tradeoff depends on your size relative to the book depth.
Here is a concrete example using explicit inputs. Suppose you want to buy 10,000 units of a perp and you choose a simple planning assumption of one suborder per minute.
For a 1-hour window:
- Window length: 1 hour = 60 minutes
- Planned slices: 60
- Size per slice: 10,000 / 60 = 166.67 units
For a 7-day window:
- Window length: 7 days × 24 hours/day × 60 minutes/hour = 10,080 minutes
- Planned slices: 10,080
- Size per slice: 10,000 / 10,080 = 0.992 units
This example is only a planning approximation. The dynamic interval engine does not guarantee one slice per minute, and it does not guarantee that every slice is the same size. The point is that the 7-day window changes the scale of the calculation: the same 10,000 units spread across 10,080 minutes produces much smaller planned slices than the same size spread across 60 minutes.
The 7-day window is a ceiling, not a default. You can still choose a shorter running time, but the dynamic interval logic applies either way. The useful takeaway is that the longer window changes the scale of the problem, not the basic idea of slicing the order.
Dynamic Suborder Interval: How It Actually Works
This is the part that trips up most traders who are used to the old model. In the old model, the suborder interval was essentially fixed. If you had 100 slices over a 2-hour window, each slice fired every 72 seconds. Simple, predictable, and easy to reason about.
As of 2026-08, the dynamic interval model works differently. Instead of locking in a fixed time gap at order creation, the system adjusts the interval between suborders based on market conditions. The exact algorithm is not fully documented in the public materials, but the practical effect is that suborders do not fire at perfectly even intervals. Some gaps will be shorter, some will be longer. The system is trying to balance two competing goals:
- Fill efficiency: Get the full size executed within the running window.
- Market impact control: Avoid sending suborders when the book is thin or when the spread is wide, because that would push the price.
When you place a TWAP order, you specify the total size and the running window. The system handles the slice decomposition and the interval scheduling internally. You do not manually set the interval; the dynamic logic does that for you.
How Dynamic Interval Differs from Trigger and Max-Min Price
This is where confusion creeps in, because the TWAP order has three separate control mechanisms that people tend to conflate:
| Mechanism | What it controls | When it activates |
|---|---|---|
| Dynamic suborder interval | Timing between suborders | Continuously, throughout the running window |
| Trigger price | Whether the order starts executing | Once, when the market price crosses the trigger |
| Max/min price | Price ceiling/floor for each suborder | Per suborder, before it is sent to the book |
A common mistake is to think that the dynamic interval is controlled by the trigger price. It is not. The trigger price gates the start of the order. Once the order is active and suborders are being sent, the interval logic takes over independently. The max and min price constraints are applied to each individual suborder as it is constructed, but they do not affect the timing between suborders.
If you are setting up a TWAP order with a trigger, the sequence is:
- You place the order with a trigger price. The order sits in a pending state.
- The market price crosses the trigger. The order activates.
- The dynamic interval engine begins sending suborders according to its internal scheduling logic.
- Each suborder is checked against the max and min price constraints before it is sent to the order book.
- The process repeats until the total size is filled or the 7-day window expires.
Sizing Your Suborders for a 7-Day Window
The 7-day window gives you more flexibility in slice sizing, but it also introduces a new consideration: the relationship between slice size and book depth. If your slices are too large relative to the visible depth at the current price, each suborder will still move the price, even though it is smaller than your original total order.
A practical approach is to look at the order book depth at your target price and size your slices so that each one represents a small fraction of the available liquidity. The Hyperliquid Slippage Math: Depth, Spread, Fill guide walks through the math for estimating how much a given size will move the price. That math applies to each individual TWAP suborder, not to the total order size.
There is no single "right" slice size. It depends on the asset, the current book depth, and how much slippage you are willing to accept. But the 7-day window does make it easier to keep slices small, because you have more time to work through the total size. If you are trading a highly liquid perp, you may not need the full 7 days. If you are trading a less liquid perp or a large size, the longer window becomes more valuable.
Like what you're reading? Try it yourself — this link supports ChartedTrader at no cost to you.
Sign up on Hyperliquid →One thing to watch: the dynamic interval engine does not guarantee that all suborders will be the same size. The last suborder in the sequence may be smaller than the others to account for the remaining unfilled quantity. This is normal and does not indicate a problem.
What the Announcement Actually Says
The official announcement at Hyperliquid TWAP update is short and to the point. It confirms two things: the 7-day running time extension and the dynamic suborder interval. It does not publish the full algorithm for the dynamic interval, and it does not provide a formula for predicting individual slice timing.
This is worth being honest about. If you are building a system that needs to predict the exact timing of each suborder, the public documentation does not give you that information. You can estimate the total number of slices and the total window, but the individual timing is an internal implementation detail. If your use case requires precise timing predictions, you may need to monitor the actual suborder fills in real time rather than relying on a pre-computed schedule.
The Hyperliquid TWAP 7-Day Order Setup & Sizing Math guide covers the practical setup process and the sizing math in more detail. This article focuses on the interval mechanism because that is the part that changed and the part that is least intuitive.
Common Misconceptions
A few misconceptions are worth separating. The suborder interval is not fixed: you can estimate total slices, but individual timing varies, so monitoring systems should not assume a fixed cadence. The trigger price does not control suborder timing; it only determines whether the order starts. Max and min price do not control timing either; they determine whether a suborder is sent at a given price. A 7-day window also does not guarantee a 7-day fill: the order can finish earlier or expire with unfilled quantity. Finally, dynamic interval is not the same as a chase order. A TWAP order spreads size over time, while a chase order tracks price; the chase order guide covers that separately.
How to Monitor a TWAP Order with Dynamic Intervals
Since you cannot predict the exact timing of each suborder, your monitoring approach needs to be reactive rather than predictive. Here is what that looks like in practice:
- Track filled quantity over time, not individual slice timestamps. If you are 50% filled after 3 days in a 7-day window, that is a useful data point. If you are 10% filled after 3 days, that is a different signal.
- Watch the remaining unfilled size. This tells you how much of the order is still exposed to price movement.
- Check the order status regularly. The status will tell you whether the order is active, partially filled, or expired.
- Do not assume a linear fill rate. The dynamic interval means the fill rate will not be perfectly linear. Some periods will see more fills, some will see fewer.
When to Use a 7-Day TWAP vs. a Shorter Window
The choice of running window is a tradeoff between market impact and price risk. A longer window reduces per-slice impact but increases exposure to adverse price movement. A shorter window does the opposite.
A longer window, closer to 7 days, usually makes sense when your size is large relative to book depth, the asset is less liquid, or you can tolerate price movement while the order runs. It also fits slower accumulation or distribution. A shorter window is better when your size is small relative to depth, the asset is liquid, you need the position established quickly, or you do not want the order to drift toward a specific price target.
There is no universal answer. The right window depends on your specific size, the specific asset, and your risk tolerance for price movement during execution.
Relationship to Other Order Types
The TWAP order is one of several order types available on Hyperliquid. Understanding how it fits in the broader picture helps you choose the right tool for the job.
The Hyperliquid Order Types Explained guide covers all the available order types and when to use each one. The TWAP order is specifically designed for large orders where you want to reduce market impact by spreading execution over time. If your order is small enough to execute in a single shot without meaningful impact, a simple limit order is simpler and faster. If you need to track price rather than spread over time, a chase order is the right tool. If you need a conditional entry, a trigger-based order is what you want.
The TWAP order with dynamic intervals is the most complex of the execution order types, and it is the one most likely to produce unexpected behavior if you are working from an outdated mental model. The 7-day window and the dynamic interval are not just incremental improvements; they change the fundamental assumptions about how the order executes.
What Has Not Changed
It is worth being clear about what the update did not change, because the documentation and the announcement can make it seem like everything is new.
- The basic concept of a TWAP order (split size, execute over time) is unchanged.
- The total size parameter works the same way.
- The max and min price constraints work the same way.
- The trigger price mechanism works the same way.
- The order status and fill reporting work the same way.
Practical Checklist Before Placing a TWAP Order
Before you place a TWAP order on Hyperliquid, run through this checklist:
- Confirm your total size. Make sure the size is what you intend. The 7-day window makes it easy to accidentally set a very large size because the per-slice size is so small.
- Check the current book depth. Look at how much liquidity is available at your target price. Size your slices accordingly.
- Decide on your running window. Do you need the full 7 days, or is a shorter window sufficient? A shorter window reduces your exposure to price movement.
- Set your max and min price constraints. These are your guardrails. If the price moves outside these bounds, the suborders will not execute. Make sure the bounds are wide enough to allow fills but tight enough to protect you.
- If using a trigger, set it deliberately. The trigger price determines when the order starts. Do not set it too close to the current price if you do not want the order to activate immediately.
- Plan your monitoring. Decide how you will track the order. Will you check the UI periodically, or will you use the API? Do not assume you can predict the exact fill timing.
FAQ
Does the dynamic suborder interval mean my TWAP order will fill faster or slower than before?
Not necessarily. As of 2026-08, the dynamic interval adjusts timing based on market conditions. In some market states, suborders may fire more frequently; in others, less frequently. The total fill time depends on the market, not just the interval logic.
Can I set a custom suborder interval on a Hyperliquid TWAP order?
No. The interval is determined internally by the dynamic scheduling engine. You set the total size and the running window; the system handles slice timing. There is no user-facing parameter to override the interval.
What happens to my TWAP order if the price moves outside my max/min price range?
The affected suborders will not execute at prices outside your constraints. The order may continue running until the remaining size fills within the allowed price range or the running window expires.
Is the 7-day TWAP window a guarantee that the order will finish in 7 days?
No. The 7-day window is the maximum running time. The order can fill earlier if liquidity and price conditions allow, or it can expire with unfilled quantity if the market does not cooperate.
How should I estimate slice size for a 7-day TWAP order?
Use your total size and the number of minutes in the window as a planning approximation. For example, 7 days is 10,080 minutes, so 10,000 units divided by 10,080 minutes is about 0.99 units per minute under a one-slice-per-minute assumption. Treat this as a sizing estimate, not a guaranteed execution schedule.
Risk Warning
Risk Warning: Crypto trading involves substantial risk of loss. Never invest more than you can afford to lose. This is not financial advice.
Continue with Hyperliquid
Browse the Hyperliquid guide hub for the complete user journey.
Official reference: Hyperliquid documentation.