Add RFP-010 for Private Launchpad & Token Issuance

RFPs/RFPs/RFP-010-launchpad-token-issuance.md

@@ -0,0 +1,139 @@
+---
+id: RFP-010
+title: Private Launchpad & Token Issuance Platform
+tier: L
+funding: $XXXXX
+status: open
+category: Applications & Integrations
+---
+
+
+# RFP-010 — Private Launchpad & Token Issuance Platform
+
+## 🧭 Overview
+
+Build a launchpad and token issuance platform that enables new projects to
+launch tokens directly into the Logos shielded ecosystem with fair, private
+distribution mechanisms. The platform must protect both issuers and
+participants — preventing sniper bots, whale manipulation, and the public
+exposure of participant identities and allocation sizes.
+
+Launchpads are the ecosystem growth engine. They create a continuous
+pipeline of new assets, attract builder and investor communities, and
+generate economic activity across DEXs, lending, and other DeFi primitives.
+A private launchpad is uniquely powerful: it uses ZK proofs for fair
+distribution (proving eligibility without revealing identity) and protects
+new projects from the predatory bot activity that plagues transparent
+launches.
+
+The ideal team has experience in token sale mechanism design, ZK-based
+eligibility verification, and anti-bot/anti-manipulation systems.
+
+## 🔥 Why This Matters
+
+Launchpads play a critical role in ecosystem velocity. Berachain's Honeypot
+suite included a launchpad (Dreampad) and a meme-coin launcher (Pot2Pump)
+at launch to ensure a continuous pipeline of new assets and community
+engagement from day one. Historically, launchpads on BSC (PancakeSwap IFO),
+Solana (Raydium AcceleRaytor), and Polkadot (Polkastarter) were key drivers
+of ecosystem adoption and capital inflow.
+
+On transparent chains, token launches are plagued by predatory dynamics:
+sniper bots front-run public sales, whales manipulate allocation mechanisms,
+and all participant wallets and amounts are publicly visible — enabling
+targeted social engineering and tax exposure. A private launchpad on Logos
+fundamentally changes this dynamic. ZK proofs can verify eligibility
+criteria (e.g., staking duration, community membership) without revealing
+the participant's identity. Allocations and purchase amounts remain
+confidential, and anti-bot mechanisms can leverage the encrypted mempool
+to prevent front-running. This creates genuinely fair launches that
+attract honest participants and legitimate projects.
+
+## ✅ Scope of Work
+
+### Hard Requirements
+
+#### Functionality
+1. Support creation and configuration of token launches by project
+   teams, including token supply, pricing model (fixed price, bonding
+   curve, Dutch auction), allocation limits, and launch schedule.
+2. Support private participation — users can contribute to a launch
+   without revealing their identity, contribution amount, or
+   allocation publicly.
+3. Implement ZK-based eligibility verification — projects can define
+   eligibility criteria (e.g., minimum staking time, holding a
+   specific NFT, community membership) that participants prove via
+   ZK proofs without revealing underlying data.
+4. Launched tokens must be issued directly into the Logos shielded
+   pool as standard shielded tokens.
+5. Implement anti-bot and anti-manipulation mechanisms — contribution
+   transactions must be resistant to front-running and sniper attacks.
+6. Support a vesting mechanism for launched tokens with private
+   cliff and release schedules.
+
+#### Security
+1. Implement fair distribution guarantees — the platform must enforce
+   allocation caps and prevent single entities from acquiring
+   disproportionate allocations (verifiable via ZK proofs without
+   revealing identities).
+2. Include an emergency pause mechanism for active launches.
+3. Implement escrow for contributed funds with clear refund mechanisms
+   if a launch is cancelled.
+
+#### Usability
+1. Provide a front-end UI for project teams to configure and manage
+   launches.
+2. Provide a participant-facing UI for browsing upcoming launches,
+   verifying eligibility, contributing, and claiming tokens.
+3. Provide a launch history and aggregate statistics page.
+
+### Soft Requirements
+
+1. Support for community-driven launches (e.g., meme-coin fair
+   launch mechanisms) with simplified configuration.
+2. Integration with the Logos DEX (RFP-004) for automatic liquidity
+   pool creation post-launch.
+3. Support for tiered launch structures (e.g., private round,
+   public round) with different eligibility criteria.
+4. Governance mechanisms for platform curation and project vetting.
+5. Exploration of retroactive distribution mechanisms — airdropping
+   tokens to eligible users without them needing to claim (private
+   push-based distribution).
+
+## 👤 Recommended Team Profile
+
+Team experienced with:
+
+- Token sale and launchpad platform design
+- Zero-knowledge proof systems and eligibility verification
+- Anti-bot and anti-manipulation mechanism design
+- Smart contract development and security
+- Token economic modeling and bonding curves
+- Front-end development for consumer-facing applications
+
+## ⏱ Timeline Expectations
+
+Estimated duration: **10–16 weeks**
+
+
+## 🌍 Open Source Requirement
+
+All code must be released under the **MIT+Apache2.0 dual License**.
+
+
+## Resources
+
+- [Logos Documentation](https://github.com/logos-co/logos-docs)
+- [Logos Blockchain Node Quickstart](https://github.com/logos-co/logos-docs/blob/main/docs/blockchain/quickstart-guide-for-the-logos-blockchain-node.md)
+- TODO: LEE official doc
+- TODO: Shielded token standard specification
+
+
+## ✏️ How to Apply
+
+👉 Submit a proposal using the Issue form:
+
+**[Submit Proposal](https://github.com/logos-co/rfp/issues/new?template=proposal.yml)**
+
+We typically respond within **14 days**. For clarification questions,
+please use **Discussions**.