> 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/ours-token.md). # OURS Token The OURS Token page serves as the macroeconomic command center and protocol infrastructure terminal of the OURS ecosystem (`ours.meme`). Deployed natively on the open, EVM-compatible Robinhood Chain (Chain ID: 4663), this portal provides complete transparency into the platform's native utility token ($OURS), detailing supply allocation, fundraising architecture, the programmatic buyback-and-burn flywheel, and open trading gateway routing. All protocol metrics are indexed directly from Robinhood Chain smart contracts and RPC endpoints, establishing transparent baseline indicators from zero as mainnet operations commence. ### 1. Top Price Action & Core Action Shortcuts The header gives immediate visibility into fundamental secondary market metrics and verified smart contract routing: * Current Price: `$0.0000` (Dynamically synced via live on-chain DEX pairs and oracles upon TGE and pool deployment). * 24h Change: `+0.00%` (Continuously calculated from confirmed block-level swap events). * Contract ↗: Direct link to the official Robinhood Chain block explorer to inspect token bytecode, open-source verification status, and immutable supply parameters. * Trade OURS ↗: Seamless one-click routing to the official swap interface, facilitating liquidity provision and direct trading against ETH, USDC, or 190+ compliant US Equity and ETF Tokens. ### 2. Macroeconomic & Deflationary Dashboard This section provides real-time transparency into the platform's supply mechanics and market activity from inception: * Market Cap: `$0.00` (Derived programmatically by multiplying live DEX execution price by verified on-chain circulating supply). * 24h Volume: `$0.00` (Cumulative volume generated across all verified $OURS trading pairs on Robinhood Chain). * Holders: `0` (Real-time count of unique non-zero wallet addresses holding $OURS on-chain). * Total Burned: `0 OURS` (Tracks cumulative tokens permanently removed from the total supply via the automated fee flywheel calling `burn`). ### 3. Platform Tokenomics ($OURS Allocation) The total supply of $OURS is strictly budgeted into non-dilutable categories via smart contracts, enforcing 0% team allocation, 0% advisor reserves, and 0% private pre-mines: 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 to real ecosystem builders. * On-Chain Behavior Mining: Accrues from verified swap volume, single-tier referral turnover, and successful curve pool graduations. * Independent Content Mining System: Rewards builders who produce tutorials, craft videos, make memes, publish research, and onboard verified real users—filtering out bots, fake engagement, linked-wallet manipulation, and vanity noise. * 30% Protocol-Owned Liquidity (POL): Dedicated to seeding deep DEX trading pairs and establishing permanent liquidity pools paired with 190+ compliant Robinhood Stock and ETF Tokens, custodied and held permanently by the protocol. * 20% Community Fundraising Allocation: A fixed, non-dilutable pool distributed among fundraising participants strictly proportional to their valid capital contribution. * 0% Team & Insider Reserve: Zero tokens are allocated to founders, core teams, or advisors. To acquire $OURS, operators must participate alongside the community through real contribution mining or open-market acquisition. ### 4. Four Core Functional Tabs #### ① Token Overview * Baseline Parameters: Symbol ($OURS), Network (Robinhood Chain – ID: `4663`), standard ERC-20 decimals, and code-enforced zero-inflation guarantees. * Core Utility: Decentralized governance voting, liquidity incentives, and direct participation in cash flows driven by the protocol fee flywheel. #### ② Community Fundraising Structure * Valuation & Target Model: * Planned raise range: $1,000,000 to $2,000,000 USD equivalent in Robinhood Chain Native ETH. * Dynamic valuation ratio: Final Platform Valuation = Final Effective Raised Capital × 5 (locking an initial FDV range of $5.0M to $10.0M). * Allocation pool: Fixed 20% of total supply, shared proportionally with zero variable dilution. * Linear Vesting Schedule: Continuous 12-month linear vesting starting at TGE (unlocked per second/block) with 0% initial cliff, eliminating Day-1 speculative dump pressure. * Capital Utilization: 80% assigned to market and liquidity architecture, 20% reserved for product engineering, smart contract security audits, and treasury operations. #### ③ Buyback & Burn Engine When fee sharing is active (70% allocated to the project team), the platform's 30% net fee revenue routes through the transparent on-chain flywheel: Plaintext ``` Platform 30% Net Fee Revenue │ ┌─────────────────────────────┼─────────────────────────────┐ ▼ ▼ ▼ 【 48% Buyback & Burn 】 【 16% Liquidity Depth 】 【 16% Eco Support 】 Market-buys $OURS on DEX Pairs $OURS with Stocks Backs top memes & Calls burn permanently Builds protocol LP (no burn) funds rewards budget │ │ │ └─────────────────────────────┼─────────────────────────────┘ ▼ 【 20% Security & Ops 】 Audits, infrastructure, & ops ``` * 🔥 48% Buyback & Burn: Market-buys $OURS using quote assets and calls `burn` for continuous supply deflation. * 💧 16% Liquidity Development: Pairs $OURS with verified Robinhood Stock and ETF Tokens to deepen Protocol-Owned Liquidity (LP tokens are custodied by the protocol, not burned). * 🌟 16% Eligible Ecosystem Project Support: Backs leading meme projects through dedicated buybacks and streams $OURS into verified contributor reward budgets. * ⚙️ 20% Security, Development, and Operations: Dedicated to protocol security, third-party audits, node maintenance, and core development. * Permissionless Public Trigger: Once accumulated fees hit execution thresholds, anyone can trigger the buyback & burn transaction directly on the UI by paying the simple network gas fee, executing an atomic on-chain execution with zero centralized intervention. #### ④ Trading & Open API Gateway * Standardized Trading Gateway: A smart contract routing layer for traders, arbitrage bots, and aggregators, supporting automated path selection between internal Bonding Curves and graduated Uniswap v4 pools. * Developer Ecosystem: Provides standard SDKs, REST endpoints, WebSocket feeds, and on-chain event indexers, allowing quantitative teams and bot operators to integrate seamlessly. ### 5. Ecosystem Value Alignment & On-Chain Proofs * "Those Who Build the Market, Own It": Eliminates the disconnect between speculation and ownership by channeling launch, swap, graduation, and cultural creation achievements directly into platform equity. * Cryptographic Verification (View Fee Flywheel →): A direct portal enabling community members, analysts, and auditors to inspect on-chain receipts for every buyback, liquidity injection, reward transfer, and treasury distribution. --- # 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/ours-token.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.