> 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/welcome.md). # Welcome OURS is not just where a Meme launches. It’s where a Meme grows. Most launchpads are built for a single transaction: create a token, open trading, collect fees, and move on. OURS is built for everything that comes next. From bonding-curve trading and project graduations to Uniswap v4 liquidity, continuous fee sharing, buybacks, and long-term community operations, OURS is engineered to support the full lifecycle of a Meme project—not just its first day. OURS (`ours.meme`) is the native Meme launchpad and community-driven liquidity layer built on the open, EVM-compatible Robinhood Chain (Chain ID: 4663). We bridge internet culture with compliant, real-world equity assets. By integrating automated Bonding Curve mechanics with Uniswap v4 pool deployments, OURS enables fair-launch tokens paired directly against native crypto assets (ETH, USDC) and 190+ authorized Robinhood Stock and ETF Tokens (e.g., NVDA, AAPL, TSLA, SPY). Engineered to align creators, active traders, content builders, and long-term liquidity providers through non-custodial smart contracts, OURS strictly enforces a "0% Team Allocation / 0% Private Pre-mine" policy. Platform token emissions are distributed to verifiable contributors, protocol liquidity, and community seeders via immutable code—completely eliminating insider dumps and cabal allocations. ### 1. Core Value Proposition * Equities Meet Meme Culture: Launch and trade memes priced directly against 190+ tokenized US equities and benchmark index ETFs alongside ETH and USDC, unlocking real macro liquidity. * Sustainable Creator Fee Sharing (70%): When fee sharing is enabled, 70% of eligible project fees are allocated directly to the project team. This provides builders with a sustainable way to fund ongoing development, community growth, project buybacks, and continuous operations. * Transparent Platform Fee Flywheel (48/16/16/20): Net protocol fee revenue routes through an autonomous, transparent model: * 🔥 48% dedicated to $OURS Buyback & Burn (continuous deflationary engine) * 💧 16% dedicated to Liquidity Development (permanent deep asset base) * 🌟 16% dedicated to Eligible Ecosystem Project Support (backing leading memes & builders) * ⚙️ 20% dedicated to Security, Development, and Operations * Independent Content Mining System: A thriving ecosystem requires more than just developers and traders. OURS introduces an independent Content Mining system recognizing builders who create tutorials, produce videos, craft memes, publish research, grow communities, and onboard verified real users. Rewards are distributed strictly on verified contribution—filtering out bots, fake engagement, linked-wallet manipulation, and vanity noise. * Proof-of-Behavior Mining: Uncapped distribution based on verifiable on-chain actions: settled trading volume, permanent single-tier referral turnover, and bonding-curve pool graduations—claimable non-custodially at any time. * Anti-Rug Liquidity Migration: Trustless automation from the internal curve into permanent, locked Uniswap v4 liquidity pools with zero backdoor privileges. ### 2. Platform Architecture at a Glance Plaintext ``` +------------------------------------+ | Creator / Trader Action | +-----------------+------------------+ | +---------------------v---------------------+ | Phase 0: Bonding Curve Launch | | (ETH / USDC / 190+ Compliant Stock Tokens)| +---------------------+---------------------+ | [ Target Volume Reached ] | +---------------------v---------------------+ | Phase 1 & 2: Swept & Uniswap v4 Migration | | (Hook-Enforced Continuous Protocol Fee) | +---------------------+---------------------+ | [ 1.00% Base Trading Fee Split ] | +---------------+---------------+ | | 70% to Project / Creator 30% to Protocol (for Continuous Ops) (Transparent Flywheel) | | Claimable Anytime +-------+-------+ | +---------------+------+-------+---------------+ | | | | 48% Burn 16% LP 16% Eco 20% Ops (OURS Deflation)(Liquidity POL) (Project Fund) (Sec & Dev) ``` ### 3. Key Operational Parameters | **Category** | **Specification Standard** | **Implementation Status** | | -------------------- | ----------------------------------------------------------- | -------------------------------------------------------- | | Network | Robinhood Chain (Chain ID: `4663`) | Open, EVM-Compatible L2 Baseline | | Domain | `ours.meme` | Production Portal | | Initial Meme Supply | 1,000,000,000 (1B) per deployment | 100% Curve Allocation (0% Team Reserve) | | Base Trading Fee | 1.00% of transaction volume | Fee Sharing Enabled: 70% Project / 30% Platform | | Platform Fee Model | 48% Burn / 16% Liquidity / 16% Eco Support / 20% Operations | Transparent On-Chain Execution | | LP Token Custody | Swept into Uniswap v4 upon graduation | Protocol Custodied / Permanently Locked | | Contribution Rewards | Behavior Mining + Independent Content Mining | Real swaps, referrals, graduations, and verified content | ### 4. Platform Tokenomics ($OURS) The total supply of $OURS is strictly budgeted into immutable categories to eliminate insider dump risk and guarantee long-term alignment: Plaintext ``` $OURS Token Distribution +-------------------------------------------------------------+ | [■■■■■■■■■■■■■■■■■■■■■■■■■] 50% Behavior & Content Mining | | [■■■■■■■■■■■■■■■] 30% Protocol-Owned Liquidity (POL) | | [■■■■■■■■■■] 20% Community Seed (12-Month Linear Vesting) | | [ ZERO ] 0% Team / VC / Insider Allocation | +-------------------------------------------------------------+ ``` * 50% Behavior & Content Contribution Mining: Released dynamically via verified on-chain actions and approved creative contributions. Features no daily caps, no per-wallet limits, and continuous non-custodial claiming. Rewards settled swap volume, single-tier referral turnover, pool graduations, as well as educational tutorials, viral memes, in-depth research, and genuine community onboarding. * 30% Protocol-Owned Liquidity (POL): Dedicated to backing primary DEX trading pairs and seeding permanent liquidity pools paired with tokenized US equities and ETFs, permanently custodied by the protocol. * 20% Community Seed Allocation: Distributed strictly on a fixed-pool basis to early community contributors. To protect the secondary market from Day-1 sell-offs, tokens vest continuously and linearly over 12 months with a 0% initial cliff. 80% of raised capital is routed directly into market liquidity creation. * 0% Team & Insider Reserve: Zero tokens are allocated to founders, core teams, or advisors. To hold $OURS, operators must participate alongside the community through real contribution mining or open-market acquisition. > 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/welcome.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.