# Overview ## What ZDLT is ZDLT is the **access + alignment token** for the Zirodelta ecosystem. We are building in public: a DEX, a Hyperliquid-native wallet (Zidee), automation strategies, and research tooling. ZDLT is how that work gets funded and how the people who care earliest get aligned with the upside. It is not a share of revenue. It is not a claim on the company. It is an SPL token that gates tier-based access to Zirodelta products and benefits from a transparent, revenue-funded buyback-and-burn mechanism. ## Key facts | Property | Value | | ------------------- | ------------------------------------------------------------------- | | Chain | Solana | | Standard | SPL | | Mint address | `4PX31xRA1BaAyb2Js45ZKYp92VGWGp47yWeVs5CGVKbf` | | Total supply | **1,000,000,000 ZDLT** (fixed, fair-launched) | | Mint authority | **Revoked** (non-mintable, supply can never increase) | | Freeze authority | **Revoked** (non-freezable, no one can lock your wallet) | | Team allocation | **0%** (no tokens set aside for founders or contributors at launch) | | Treasury allocation | **30,000,000 ZDLT (3%)**, operational reserve, use rules below | | Primary liquidity | Meteora DLMM pool | | Team pool fee | **0.5%** per swap (team wallet, funds operations + buyback) | ## Why it exists Zirodelta's thesis is that building real products in public, with a real token that holders can value against real revenue, is a stronger alignment mechanism than either closed-door SaaS or speculation-only meme tokens. ZDLT lets us do three things at once: 1. **Monetize the build.** Pool fees and product revenue fund development without us needing to raise venture capital or sell equity. 2. **Give early supporters a seat at the table.** Holding ZDLT is how you access the Discord, earn tier perks, and (over time) get product-level benefits like fee discounts. 3. **Share the upside transparently.** As products earn revenue, a committed share of that revenue is used to buy ZDLT from the open market and burn it. Supply only shrinks. Transparency of that flow is the entire deal. ## Who ZDLT is for Both of these audiences are welcome and designed for: * **Product users**: you want access to the Discord, tier perks, future fee discounts on the DEX, and a say in how things develop. Holding ZDLT makes you a resident, not a tourist. * **Speculators**: you want exposure to a small-cap SPL whose supply can only shrink and whose value floor is pinned to a real, auditable stream of product revenue. Every burn is an on-chain tx you can verify. Different people hold for different reasons. The mechanism design reflects that. ## Treasury (3% / 30M ZDLT): locked until $11M market cap The 30M ZDLT in the treasury is **not** a team allocation in disguise. It is an operational reserve with two hard commitments: ### 1. Market-cap unlock gate **The treasury is locked until ZDLT reaches a fully-diluted market cap of $11,000,000 USD.** Until that threshold is reached, zero ZDLT leaves the treasury wallet. No partner grants, no liquidity provisioning, no bounties funded from reserves, nothing. Why $11M: at 1B fixed supply, $11M mcap = $0.011/token, which puts the treasury's 30M at \~$330K. That's the first scale at which any reserve usage becomes proportionate to the protocol's credibility and at which premature treasury draws stop being a lever we should even have access to. Before that, everything the team does comes out of pool fees and product revenue. This is an on-chain-observable commitment: anyone can check the treasury balance on Solscan and verify it hasn't moved. ### 2. Post-unlock use rules Once the $11M mcap gate is crossed (a one-way unlock, not a continuous gate), the treasury may be used for: * **Liquidity provisioning** on new pools (e.g., bridged ZDLT on other venues, CEX listings). * **Partner + integration incentives**: grants to builders who integrate ZDLT into third-party products. * **Community bounty top-ups**: supplementing (not replacing) the live engagement bounty program. * **Emergency reserves**: only spent under publicly-announced extraordinary circumstances. > **Note on the engagement bounty program.** The 200k ZDLT/month engagement bounty (see `Engagement` docs) is **paid from operational revenue, not from the locked treasury**. It is a live program that runs today, independent of the $11M gate. Treasury top-ups become possible only post-unlock. **What the treasury will never do:** fund team salaries directly, dump on the market, or distribute to holders as "rewards". Team compensation comes from pool fees and product revenue, not from the reserve. **Treasury wallet address:** [`EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW`](https://solscan.io/account/EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW) All treasury outflows (post-unlock) will be publicly auditable on Solscan and preceded by a public announcement describing intent. ## What's on-chain today * ✅ Mint + freeze authority revoked (verifiable on Solscan) * ✅ 30M ZDLT in treasury wallet ([`EaJ4...PoW`](https://solscan.io/account/EaJ4aEKCSJKiLvJMBUMXZcmJp4GFqR5w1B94Xgv17PoW), verifiable on Solscan), **locked until $11M FDV mcap** * ✅ Meteora DLMM pool live * ✅ 0.5% pool tx fee flowing to team wallet * ✅ Discord tier gating via Matrica (6 Orion tiers, all ZDLT-balance-gated) ## What's next See: * [Tokenomics](/zdlt-token/tokenomics.md): the revenue pipeline and buyback-and-burn mechanism in numbers. * [Utility](/zdlt-token/utility.md): what holding ZDLT unlocks, now and next. * [Hard Rules](/zdlt-token/hard-rules.md): the regulatory posture and transparency commitments we've bound ourselves to. --- # Agent Instructions: 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: ``` GET https://docs.zirodelta.com/zdlt-token/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.