> For the complete documentation index, see [llms.txt](https://ours-meme-1.gitbook.io/ours.meme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ours-meme-1.gitbook.io/ours.meme-docs/feature/launch.md). # Launch The Launch Token page serves as the non-custodial deployment terminal of the OURS platform (`ours.meme`). Natively built on the open, EVM-compatible Robinhood Chain (Chain ID: 4663) using automated Bonding Curve infrastructure, it enables creators, communities, and builders to deploy fair-launch meme projects seamlessly. Tokens launched on OURS can be paired directly with native crypto assets (ETH, USDC) or against any of the 190+ compliant Robinhood Stock and ETF Tokens (such as AAPL, NVDA, TSLA, and SPY). Every token follows an automated, irreversible lifecycle: starting from internal bonding-curve price discovery to permanent Uniswap v4 liquidity pool migration, backed by sustainable fee sharing, buybacks, and long-term community operations. ### 1. Step-by-Step Deployment Workflow #### Step 01: Token Metadata & Community Verification Establish the visual identity and official verification channels across the Market Discovery and Trading terminals: * Token Image: Upload an avatar in PNG, JPG, GIF, or IPFS URI format. * Token Name: Project title (up to 32 characters). * Token Symbol (Ticker): Market ticker (e.g., `$JOY`, `$BUBU`, up to 10 characters). * Description: Cultural narrative, mission, or meme origin story. * Social Proof: Direct input fields for X (Twitter), Telegram Community, and Official Website. These are registered on-chain during deployment to deter copycats and malicious phishing links. #### Step 02: Select LP Pairing / Quote Asset Creators select exactly one settlement quote asset per token, which is permanently locked on-chain upon launch: * Crypto-Native & Stablecoins: * ETH: Native Robinhood Chain gas currency. * USDC: Compliant USD stablecoin. * Robinhood Stock & ETF Token Registry (190+ Synchronized Assets): * Direct pairing against mega-cap tech stocks (AAPL, TSLA, NVDA, MSFT, AMZN, META, GOOGL), crypto proxies (COIN, HOOD), retail momentum assets (GME, AMD), and benchmark index/commodity ETFs (SPY, QQQ, GLD). * Custom Contract Verification: * If a supported asset is not in the default list, creators can paste any verified Robinhood Chain equity contract address. * The system performs atomic verification across the Asset Registry and `LaunchFactory`, verifying asset identity, token decimals, active trading status, and baseline liquidity before unlocking deployment. #### Step 03: Economic Parameters & Programmable Revenue Routing All economic terms are fully transparent and previewed before on-chain signing: * Sustainable Fee Sharing (70% to Project) & Revenue Routing: * When fee sharing is enabled, 70% of eligible project swap fees are allocated directly to the project team (while the remaining 30% enters the platform's 48/16/16/20 flywheel). * Creators can pre-configure how their 70% allocation routes on-chain to build a sustainable operational runway: * Pure Dev Escrow: 100% routes to an isolated `FeeEscrow` ledger for non-custodial claiming anytime to fund ongoing development and operations. * Pure Buyback & Burn: 100% routes into the curve to market-buy project tokens and call `burn`, enforcing continuous supply deflation. * Pure Stock Asset Dividends: 100% routes to an isolated dividend vault to distribute the underlying Stock Tokens directly to token holders. * Custom Split: Configure custom proportions across dev claims, buybacks, and dividends. * Optional Creator Tax (0.00% – 10.00%): * Configure an optional creator tax charged on every buy and sell, flowing 100% to the project's escrow with zero platform cuts. * Developer Initial Buy (Bundled Atomic Buy): * Creators can configure an initial purchase using the selected quote asset (e.g., ETH or NVDA Token). * Atomic Bundling: The initial purchase executes within the exact same deployment transaction, securing early supply at the initial curve price while neutralizing MEV sandwich bots and front-runners. * Standard Creation Fee: * A fixed protocol deployment fee (e.g., 0.0005 ETH) to cover contract instantiation and factory indexing. ### 2. Launch Preview & Contract Specifications Before signing the deployment transaction in your wallet, the terminal generates an unalterable specification summary: | **Parameter** | **Protocol Specification** | **Operational Significance** | | -------------------- | -------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | Trading Pair | Ticker / Quote Asset (e.g., `$JOY / NVDA`) | Dictates the pricing and settlement currency across the curve and v4 pool. | | Total Supply | 1,000,000,000 (1B Fixed) | 100% allocated to the Bonding Curve with zero team insider pre-mint. | | Internal Curve | Automated Bonding Curve Algorithm | Enforces mathematical price discovery with strict `minOut` slippage protection. | | Graduation Route | Uniswap v4 Deep Liquidity Pools | Sweeps curve assets to deploy a v4 pool; LP is protocol-custodied or permanently locked. | | Quote Currency | Selected Asset (ETH / USDC / Stock Token) | Internal trades, graduation triggers, creator royalties, and dividends settle natively in this asset. | | Project Revenue | 70% to Project (when fee sharing is active) | Supports dev withdrawals, curve buyback & burn, and stock dividends. | | Platform Fee Model | 30% protocol cut follows 48/16/16/20 | 48% $OURS Burn, 16% Liquidity, 16% Eco Support, 20% Operations. | | Contribution Rewards | Behavior Mining + Independent Content Mining | Rewards verified volume, pool graduations, and quality educational/meme content. | ### 3. Core Security & Architectural Principles * Non-Custodial Self-Signing: All deployment transactions are signed directly via the creator's wallet; OURS does not take custody of deployment funds, treasury escrows, or user keys. * True Fair-Launch Integrity: The entire 1B token supply enters the public bonding curve. Developers receive zero free tokens; if they wish to hold supply, they must buy along the exact same mathematical curve as the community. * End-to-End Asset Compatibility: Selecting a tokenized US equity (e.g., NVDA, SPY) ensures all swaps, liquidity sweeps, graduation thresholds, and creator distributions remain natively denominated in that specific equity token without wrapped bridge friction. * Frictionless Deployment: Connect your Web3 wallet, verify network parameters on Robinhood Chain (Chain ID: 4663), and deploy on-chain via "Connect Wallet & Preview Launch →". > Launch Tokens. Fund Builders. Reward Culture. Grow the Market Together. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ours-meme-1.gitbook.io/ours.meme-docs/feature/launch.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.