> 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/vision.md).

# Vision

Those who build the market, own it.

### 1. Why We’re Here: Beyond Single-Swap Launchpads

The current launchpad meta is fundamentally broken.

Every cycle follows the exact same script: traders pump volume in the trenches, KOLs drive marketing funnels, and devs create culture out of thin air. Yet most launchpads are built for a single transaction: create a token, open trading, extract fees, and move on. Retail participants are left holding volatile bags while centralized operators and cabal VCs siphon pure cash flow.

Meanwhile, meme tokens playing PvP inside closed, recycled ETH and SOL liquidity loops have hit a dead end. Meme culture moves at breakneck speed, yet it remains completely detached from the largest asset classes in human history: mega-cap tech equities, benchmark index ETFs, and real-world equities.

OURS (`ours.meme`) is built for everything that comes next.

OURS is not just where a Meme launches; it is where a Meme grows. Built natively on the open, EVM-compatible Robinhood Chain (Chain ID: 4663), OURS bridges internet meme culture with compliant, tokenized US equities and ETFs.

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. The platform enforces a strict 0% team allocation and 0% private pre-mine policy, using immutable smart contracts to align developers, volume-makers, content creators, and community builders as true protocol co-owners.

### 2. The Three Pillars

Plaintext

```
                             OURS Core Pillars
                                     │
       ┌─────────────────────────────┼─────────────────────────────┐
       ▼                             ▼                             ▼
【 1. True Ownership Economy 】 【 2. Meme Velocity Meets Equities 】 【 3. Full-Lifecycle Liquidity 】
 • Dual Mining: Behavior + Content • 190+ Tokenized US Stock/ETF Pairs • 1B Fixed Supply to Curve (0% Team)
 • Transparent Model: 48/16/16/20 • Real Macro-Narrative Settlement     • Locked v4 Graduation Pools
 • 70% Fees to Sustain Builders   • On-Chain Equity Liquidity Engine   • 16% Revenue to Protocol-Owned LP
```

#### Pillar I: The True Ownership Economy

* Dual-Engine Contribution Rewards: Behavior Mining & Content Mining
  * Say goodbye to fake clicker bots, off-chain sybil scorecards, and arbitrary daily caps. 50% of the total $OURS supply is hardcoded for community contribution mining.
  * On-Chain Behavior Mining: Accrues continuously from verified trading volume, permanent single-tier referral turnover, and successful bonding-curve pool graduations.
  * Independent Content Mining System: A real 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.
* Real Fee Flow, Zero Vaporware Governance
  * Governance means nothing without protocol revenue. When fee sharing is enabled, 70% of eligible project fees are allocated to the project team, providing builders with a sustainable way to fund ongoing development, community growth, project buybacks, and continuous operations.
  * The platform's net fee revenue runs through a transparent on-chain model:
    * 🔥 48% dedicated to $OURS Market Buyback & Burn (continuous deflationary engine)
    * 💧 16% dedicated to Liquidity Development (deepening protocol-owned reserves)
    * 🌟 16% dedicated to Eligible Ecosystem Project Support (backing leading memes and ecosystem builders)
    * ⚙️ 20% dedicated to Security, Development, and Operations

#### Pillar II: Meme Velocity Meets Real Equities

* Break Out of the Crypto-Native Sandbox
  * Stop settling for recycled ETH or USDC pairs. OURS integrates directly with compliant asset registries to support 190+ compliant US Stock and ETF Tokens as native quote assets across internal bonding curves.
* Trade Culture Denominated in Real-World Assets
  * Launch and trade meme tokens priced directly against NVIDIA ($NVDA), Apple ($AAPL), Tesla ($TSLA), Robinhood ($HOOD), or the S\&P 500 ($SPY).
  * From initial curve discovery to automated liquidity sweeps, all trades, graduation milestones, and creator royalties settle natively in that chosen equity token. Real-world macro narratives can now be memed and traded directly on-chain.

#### Pillar III: Autonomous, Anti-Rug Liquidity

* 100% Fair Launch, Zero Insider Allocations
  * Every deployment features a standardized 1,000,000,000 (1B) fixed token supply injected entirely into the curve, with zero team pre-mines.
  * Developers trade on the exact same mathematical curve as the community, with optional atomic initial buys bundled inside deployment transactions to neutralize MEV sandwiching and sniper front-running.
* Permanent Protocol-Owned Liquidity (POL)
  * Once a curve hits its target threshold, assets are automatically swept to seed Uniswap v4 pools, with LP tokens permanently locked or custodied by the protocol—no backdoors, no manual sweeps, and zero rug pulls.
  * Simultaneously, 16% of platform fee revenue is continuously allocated to liquidity development, market-buying $OURS and stock tokens to deepen permanent protocol-owned liquidity pools.

### 3. The Endgame: Built for Trench Builders

OURS is not merely another terminal; it is an open market protocol engineered for the builders in the trenches:

* For Devs & Creators: Receive 70% of eligible trading fees with customizable on-chain revenue profiles (escrow claim, curve buyback & burn, or equity dividends), securing runway from day one to fund ongoing operations.
* For Degens & Traders: Execute swaps with sub-second curve pricing, programmatic `minOut` slippage protection, and MEV resistance, accumulating platform equity through behavior mining on every trade.
* For Content Creators & Cultural Builders: Tap into the dedicated Content Mining system to turn tutorials, research, viral memes, and community-building efforts into verified $OURS allocations.
* For Network Referrers: Secure permanent, single-tier on-chain attribution with zero caps, converting referred trading activity into a perpetual stream of mining rewards.

Just better infrastructure, clearer rules, transparent fee flows, sustainable incentives for builders, and more ways for real contributors to earn recognition.

> 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/vision.md?ask=<question>&goal=<user_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.
