TWAP

A TWAP splits a larger crypto trade into scheduled slices. In Velora, TWAP is a Delta order that the user signs once and Velora settles over time.

A TWAP (time-weighted average price) splits a larger trade into smaller slices executed over time.

In Velora, TWAP is a Delta order. The user signs one scheduled order that defines the total trade, number of slices, interval, and deadline. Velora then settles eligible slices over time through Delta instead of asking the user to sign or submit a transaction for every slice.

Use TWAP when a one-shot swap is too sensitive to execute at a single market moment.

What problem TWAP solves

A large immediate trade consumes available liquidity and worsens its own execution price. It also stakes the whole trade on one market moment, and executing everything at once makes the trade easier for other participants to detect and react to.

TWAP reduces those risks by spreading execution across smaller settlements. It does not remove market risk, and it does not guarantee a better final average price.

How Velora TWAP works

Velora TWAP is scheduled Delta execution:

1. The user chooses the pair, side, total amount, number of slices, interval, deadline, and execution constraints.
2. Velora builds a signable Delta order for the schedule.
3. The user signs once.
4. When a slice becomes eligible, Velora runs execution for that slice.
5. The Delta contract enforces the slice timing on-chain.
6. The order completes after the final slice settles, or fails/expires if its constraints can no longer be met.

For a sell TWAP, the user fixes the total source amount to sell, and Velora splits that source amount across slices. For a buy TWAP, the user fixes the total destination amount to receive, and Velora splits that destination target across slices while capping the total source amount spent.

Key terms

• Scheduled order: the signed Delta order that defines the TWAP.
• Slice: one settlement inside the scheduled order.
• Number of slices: how many settlements the trade is split into.
• Interval: the minimum time between slices. Velora enforces a schedule; slices are not independent user actions.
• Deadline: the latest time the order can remain valid.
• Side: sell TWAPs fix and split the source amount; buy TWAPs fix and split the destination amount while capping source spend.

TWAP vs Swaps vs Limit Orders

A swap executes the full amount now. A limit order waits for a target price and fills only if the market reaches it. A TWAP commits the trade upfront and settles slices as they become eligible, whatever the price does within the order’s constraints.

TWAP and limit orders are both signed Delta orders that settle after signing. The difference is the trigger: a limit order is price-conditional, a TWAP is time-driven.

Build it

• Use the Widget if you want a ready-made TWAP form in your app; Configure Widget controls whether it appears.
• Use POST /v2/delta/orders/build if you are building the HTTP flow directly. Submit the signed order through POST /v2/delta/orders and track slice execution through the Delta order endpoints.
• How Delta works explains how signed orders are auctioned and settled.