# Dploy.fun {% hint style="info" %} Dploy is the next-gen launchpad on SOL network, designed to benefit all stakeholders. {% endhint %} SOL has a rapidly growing meme coin ecosystem, with thousands of new projects launching daily. However, 99% of these projects either fail to complete their bonding curve or end in a rug pull. As a result, Dev usually focuses on short-term farming projects, while traders are in a negative-sum game. ### **Challenge for Creators** #### **Current Problem** Launching tokens is still complex and risky for creators: * **Technical barrier** – Requires coding, contract deployment, and liquidity setup. * **Lack of trust** – Traders don’t know if the dev is real or just another anonymous rug puller. * **Unfair competition** – PVP deployers spam multiple tickers, leaving genuine creators overshadowed. * **No proper distribution of fees** – Creators cannot make changes to the reward pool or designate other beneficiaries for fees. *** #### **Solution with Dploy.fun** * **Instant/multi-platform deployment** – Deploy tokens directly via Telegram bot, group chats, Twitter, or Discord using a simple command (`Image + Name + $Ticker + Tweet + Url`). * **Zero token creation fee** – Removes entry barriers for new creators. * **Verified dev identity** – Each token shows the dev’s TG/X/Discord handle (doxxed by default). This builds trader trust. * **Anti-PVP system** – Only **one ticker every 24 hours** per creator unless the existing ticker falls below migration mcap, reducing PvP wars. * **Automatic rewards distribution** – Creator fees (40% of TX fees) can be modified to selected TG/Twitter/Discord users, who are notified by a claim bot and can claim fees directly. * **Top 10 Tokens Bar** – Paid visibility for creators to attract engagement and stand out. * **Bundler detection + IP bans** – Protects traders from being overshadowed by bots or unfair bundling tactics. * **Automatic Dexscreener updates** – Every token that reaches graduation mcap (85 SOL) automatically gets a Dexscreener update at no cost—ensuring instant visibility and credibility. *** ### **Challenge for Traders** #### **Current Problem** Traders face massive risks while entering new tokens: * **Lack of transparency** – No guarantee of dev identity or proper communication. * **Missed opportunities** – Hard to track new launches and claimable fee for fee recipients. * **Inflationary pressure** – Most platforms don’t provide mechanisms to sustain token value. * **Trading Fees** – Every transaction on a Bonding Curve platform and DEX incurs a fee, removing liquidity from the market, even remove from SOL Ecosystem instead of circulating it back into projects or traders. * **Negative-Sum Game in Meme Coin Ecosystems** – The current meme coin market operates as a negative-sum game, where more value is extracted from the ecosystem than is injected. * **Insider Trading & Manipulation** – Insiders behind major meme coin launches extract enormous profits before the market even reacts. *** #### **Solution with Dploy.fun** * **Graduation system** – At **85 SOL market cap**, 76.5 SOL auto-goes to liquidity pool, 6 SOL goes to Dploy.fun as LP fee, ensuring LP depth and reducing rug pull chances. * **One-click token lock** – Any holder can lock their supply from the dashboard for chosen days, boosting confidence in long-term holding. * T**okens Are Non-Transferable Before Migration** – Eliminates early insider movements and manipulation. * **Buyback & burn mechanism** – 20% of fees go to an automated contract that buys $DPLOY and burns it, making $DPLOY deflationary and strengthening its value. * **Claim bot alerts** – Traders/beneficiaries get notified if a creator sends them fee rewards, with details like token name, ticker, and contract address. * **Metadata editing** – Updates for project URLs and descriptions keep traders informed and avoid misinformation. * **Treasury allocation (40%)** – Funds are consistently reinvested, ensuring the ecosystem grows instead of draining liquidity. * **Creators Earn on Every Trade** – Developers get SOL rewards from every transaction. *** --- # 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://wp.dploy.fun/dploy/readme.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.