> 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/zdlt-token/hard-rules.md). # Hard Rules Things we have bound ourselves to, in code, in process, or in public commitment, that protect holders and the integrity of the token. These are not marketing promises, each has a concrete enforcement mechanism. *** ## 1. Non-custodial: we can never move your funds **The rule:** Your master key lives in Privy (it is yours, and exportable), and you hold your own ZDLT and wzdUSD. No key Zirodelta holds can move your funds anywhere you have not authorized. The Yield Engine trades the pool with a trade-only key that can only place and cancel orders, never withdraw, and the key that could move funds out of the pool is held off-server. The deposit rail uses a policy-locked signer that can only forward your USDC along the single route you authorize. **None of them can withdraw or send your funds to anyone, including us.** **Enforcement:** On Hyperliquid, the pool's trade-only key is approved for order actions only; the protocol itself rejects any withdraw or transfer signed by it. The deposit signer is locked by a server-side Privy policy to that one operation, and you can revoke it. Even if Zirodelta's backend were fully compromised, an attacker could trade the pool badly but could not take your funds. See [Custody](/zidee-wallet/custody.md). ## 2. Fair launch, no team allocation, no retained mint authority **The rule:** The team received zero ZDLT at launch. Mint authority and freeze authority were revoked on-chain immediately after supply was set. **Enforcement:** On-chain and irreversible. Verify `mintAuthority = null` and `freezeAuthority = null` on Solscan for mint `4PX31xRA1BaAyb2Js45ZKYp92VGWGp47yWeVs5CGVKbf`. ## 3. Holders are paid in wzdUSD, never in ZDLT **The rule:** Rewards for holding are paid in [wzdUSD](/zdlt-token/wzdusd.md). They are never paid by minting or selling ZDLT. **Why:** Paying holders out of the token's own supply is dilution dressed up as a reward. Paying in a separate, backed dollar means paying holders never waters down holders. Supply stays fixed at 1B forever. **Enforcement:** Supply is fixed (mint authority revoked); there is no emission path that pays rewards in ZDLT. ## 4. No user money until audited and legal-reviewed **The rule:** The vault that backs wzdUSD and holds the strategy's collateral stays **closed to user funds** until an independent security audit **and** a legal review are complete. Until then, the strategy is proven on the founder's own capital, not on yours. **Enforcement:** The deposit-and-earn flow is gated; user deposits are not accepted into the strategy before the audit and legal review land. See [Vault Overview](/vault/overview.md). ## 5. Treasury is locked until $11M market cap **The rule:** The 30M ZDLT treasury reserve is **locked until ZDLT's fully-diluted market cap reaches $11,000,000**. Until that one-way gate is crossed, no ZDLT leaves the treasury wallet, for any purpose. The treasury never funds salaries directly, never dumps in routine operations, and never distributes ZDLT to holders as "rewards." **Enforcement:** The treasury wallet ([`EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW`](https://solscan.io/account/EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW)) is public; any outflow before the gate is a protocol violation requiring a public post-mortem. Post-gate outflows require prior public announcement. ## 6. Transparency: public proving address and published opex **The rule:** The strategy runs in the open on a public address before user funds are accepted, and operating costs are reported so the split between the reward pool and opex is never opaque. **Enforcement:** The proving address is published and on-chain readable. Opex is reported alongside the proving track. ## 7. Yield is variable and never guaranteed **The rule:** We will never publish a guaranteed APR or a fixed return. Rewards in wzdUSD are variable and can be low or even zero, and wzdUSD is not a $1 stablecoin. **Why:** A guaranteed return on a market strategy is a lie, and a token that promises a fixed yield invites exactly the wrong expectations. Honesty about variability is the commitment. **Enforcement:** No marketing surface states a guaranteed number; the docs and app state the variable-and-can-be-zero language directly. ## 8. Upgrades are audited, time-locked, and opt-in **The rule:** The SPL mint itself is immutable. Any future on-chain program (staking locks, reward accounting, governance weight) ships behind a time-locked contract (minimum 30 days between deployment and activation), is audited by at least one reputable third party before activation, and is opt-in only, no existing holder balance is touched without explicit user approval. *** ## Summary: what this means for you as a holder * **We cannot take your funds.** No key we hold can withdraw or send money anywhere you have not authorized. * **You cannot be rugged via the mint or frozen out.** Supply is fixed; no freeze authority. * **You are paid in a real dollar, not in dilution.** Rewards are wzdUSD, never ZDLT. * **Your money isn't at stake until it's audited.** The strategy proves on the founder's capital first. * **You can verify the claims on-chain.** Mint, freeze, treasury balance, and the proving address are all public. --- # 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/zdlt-token/hard-rules.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.