> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/the-zirodelta-financial-engine/delta-neutral-explained.md). # Delta-Neutral Explained "Delta-neutral" means no net exposure to price. The position is designed so that if the price of the underlying asset goes up or down, it does not affect profit or loss. The only income source is the funding rate payment. This document explains how that works mechanically, why it eliminates liquidation risk, and what can actually go wrong. This is the strategy the [Yield Engine](/the-zirodelta-financial-engine/overview.md) runs for the pool. Your role is simple: you deposit USDC and hold a wzdUSD share; the Engine runs the position on the pool's behalf, and you never touch an order book. ## The mechanics ### Positive funding: the live path When Hyperliquid's funding rate is **positive**, longs pay shorts. Every hour, every long position holder pays a small fee to every short position holder. The rate is typically expressed as a percentage of notional per hour. To capture this yield delta-neutrally, the Engine runs two legs simultaneously: **Leg 1 Short the perpetual**: the pool receives the funding payment every hour. **Leg 2 Buy the spot**: the hedge. The pool owns the asset outright at spot. If the price rises by $1,000 while the position is open: * The pool's short perp loses $1,000 * The pool's spot holding gains $1,000 * Net P\&L from price: **$0** If the price falls by $1,000: * The pool's short perp gains $1,000 * The pool's spot holding loses $1,000 * Net P\&L from price: **$0** Every hour, regardless of which direction price moved, the pool collects the funding payment on the short perp. That funding, captured market-neutrally, is the yield. ### Negative funding: on hold When the funding rate is **negative**, shorts pay longs. To capture this delta-neutrally, the Engine would flip the strategy: **Leg 1 Long the perpetual**: the pool receives the funding payment every hour (longs receive when funding is negative). **Leg 2 Short the spot**: the hedge. This requires borrowing the underlying asset, selling it at current price, and buying it back later. Shorting spot requires a borrow source for the underlying asset, which is not in place yet. Until it is, the Engine runs the positive-funding path only. > **Note:** The negative funding path is currently on hold. The Yield Engine only supports the positive funding path (short perp + long spot) today. ## Why there is no liquidation risk "No liquidation risk" is a specific technical claim. Here is exactly what it means. In a normal leveraged long position, margin can be exhausted by a sustained price decline. When margin falls below the maintenance requirement, the position is liquidated, forcibly closed at a loss. In a delta-neutral position: * The short perp loses value when price rises, but the spot gains the same amount, so margin is automatically replenished by the increasing spot value * The short perp gains value when price falls, and the pool is not levered into the falling price, it is hedged by the spot it owns The perp margin loss is always offset by the spot gain (and vice versa). There is no directional margin call because there is no directional exposure. The position cannot be liquidated by price movement. The Yield Engine does not use leverage on either leg. Both the perp and the spot position are sized equally in notional, with no leverage multiplier applied. This eliminates the margin call scenario entirely. ## What CAN go wrong Being delta-neutral does not mean risk-free. There are real risk scenarios worth understanding. ### Sustained negative funding (rate reversal) The most common risk. The pool holds a short perp + long spot because funding was positive (the pool was earning). The funding rate reverses to negative. Now the pool pays the longs instead of receiving. When this happens, the pool loses money on the funding payment while holding the position. If the rate stays negative long enough, accumulated losses exceed accumulated gains. **Mitigation:** the Engine monitors funding continuously and can close the position when the rate turns unfavorable, rather than holding into sustained negative funding. ### Spot-perp basis risk In theory, spot and perp prices move together. In practice, there can be short-term divergence. The perpetual price temporarily deviates from spot. This is called basis risk. During a delta-neutral trade, a basis divergence means the two legs do not perfectly offset for a period. In most cases this is temporary and self-correcting (the funding mechanism exists specifically to prevent persistent basis). However, during extreme market stress, basis can widen significantly before correcting. This is not a liquidation risk. It is a mark-to-market fluctuation. The position remains open, and as long as the Engine does not close during the divergence, no loss is locked in. ### Operational risk The Yield Engine operates through Zirodelta's backend infrastructure. If the backend is unavailable or delayed, orders may not be placed or closed in time. This is a real operational risk, particularly during periods of extreme market volatility when the system most needs to act. **Mitigation:** Zirodelta's backend runs on dedicated server infrastructure with automated reconnection. The withdraw-capable key for the pool stays off-server, so a disruption is an execution delay, not a custody risk, and your own withdrawals are always available from your own keys. ### Negative-funding-path risks (on hold) When a spot-borrow source is wired up and the negative funding path ships, an additional risk class applies: spot-borrow availability. If the borrow source's health degrades (borrow demand exceeds supply, collateral value drops on the source side), the Engine would reduce or close the position rather than maintain it at maximum size. This is a risk reduction mechanism, not a liquidation. ## Summary of risk profile | Risk | Type | Severity | Mitigation | | ------------------------------------------------- | -------------------- | -------- | -------------------------------------------------------------------- | | Funding rate reversal | Yield erosion | Medium | The Yield Engine closes on a funding-rate threshold | | Basis risk (temporary) | Mark-to-market | Low | Hold through divergence, do not panic-close | | Operational downtime | Execution delay | Low | Dedicated infra with automated reconnection; withdraw key off-server | | Spot-borrow availability (negative path, on hold) | Forced partial close | Medium | Path not active today; will surface when a spot-borrow source ships | > **See also:** [The Yield Engine](/the-zirodelta-financial-engine/overview.md) · [Custody](/zidee-wallet/custody.md) · [wzdUSD](/zdlt-token/wzdusd.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zirodelta.com/the-zirodelta-financial-engine/delta-neutral-explained.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.