> 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/overview.md). # Overview The Yield Engine is the part of the Zirodelta Financial Engine that earns. It runs a delta-neutral, market-neutral strategy that captures funding payments on Hyperliquid, and the income it produces is what funds the rewards you are paid in wzdUSD for holding ZDLT. It never holds your funds. ## What it does A delta-neutral trade has two legs, opened at the same size at the same time: 1. A short perpetual futures position 2. A long spot position in the same asset If price moves up, the short perp loses and the spot gains. If price moves down, the reverse. The two legs cancel, so there is no bet on price direction. What is left is the funding payment: every hour, in a positive-funding market, the long side pays the short side. That funding, captured market-neutrally, is the source of the yield. The Yield Engine opens both legs at the right sizes, monitors them, rebalances as they drift, and closes them cleanly. There is no order book for you to watch. ## Proving phase The Yield Engine is real, but it is not open to user funds yet. It is being proven on the founder's own roughly $10k on a public address, so the track record is built in the open before anyone else is at risk. It opens to users only after an independent security audit and a legal review. The yield is variable and can be low or even zero. Delta-neutral removes the price bet, not every risk: funding can turn negative, and fees can eat into the return. ## Non-custodial by construction You never hand your funds to a person. You deposit USDC into the vault and hold **wzdUSD**, your market-priced share of the pool, in your own wallet. The Yield Engine then runs one delta-neutral position for the whole pool, not a separate one per user. The key that can move funds out of the pool's Hyperliquid account is held **off-server**. To run the strategy, the server signs with a trade-only key whose authority is capped by Hyperliquid itself: it can place, cancel, and close the pool's orders, and the protocol rejects any withdraw or transfer signed by it. So the worst a full server compromise can do is trade the pool badly, never move a dollar off it, and never touch your own wallet. See [Custody](/zidee-wallet/custody.md). ## One engine of several Zirodelta builds programmable personal balance sheets. The platform behind that is the Zirodelta Financial Engine: the Yield Engine (this page) plus the Credit, Conversion, Settlement, and Treasury Engines, the Referral Graph, and Fiat Rails, rolling out in stages. The Yield Engine is the one being proven in public first, and [Zidee](/zidee-wallet/overview.md) is the wallet that puts it in your hands. ## Read next * [Custody](/zidee-wallet/custody.md): the trust boundary, and exactly what the Yield Engine can and cannot do with the pool. * [Delta-Neutral Explained](/the-zirodelta-financial-engine/delta-neutral-explained.md): the mechanics, the real risks, and what "no liquidation from price" actually means. * [wzdUSD](/zdlt-token/wzdusd.md): the dollar the Yield Engine's income is paid out in. --- # 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/overview.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.