> 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/free/allocation.md). # Allocation Across the OURS (`ours.meme`) ecosystem, the protocol's 30% share of base trading fees (equivalent to 0.30% of total gross swap turnover) serves as the core value capture and economic distribution engine. Rejecting legacy models that route protocol fees to centralized team wallets or opaque private entities, all platform revenue flows directly into the on-chain vault (`OursFlywheelVault`), executing an automated, unalterable 48 : 16 : 16 : 20 flywheel allocation. ### 1. The 48 : 16 : 16 : 20 Allocation Model The distribution base is derived strictly from the protocol's 30% base fee share, with each of the four legs executed programmatically on-chain: ``` Protocol 30% Net Fee Revenue (100%) (0.30% of Total Transaction Volume) │ ┌──────────────────────────────┼──────────────────────────────┐ ▼ ▼ ▼ [ 48% ] [ 16% ] [ 16% ] [ 20% ] Buyback & Burn Liquidity Depth Eco Project Support Security & Ops (Direct Deflation) (Protocol-Owned POL) (Top Memes & Contributors) (Multi-Sig Treasury) ``` | **Allocation Purpose** | **Split Ratio** | **Programmatic Action** | **Beneficiary / Asset State** | | ---------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | Buyback & Burn | 48% | Market-buys $OURS across DEX pools using quote assets and immediately calls the `burn` interface. | All $OURS Token Holders (continuous supply reduction and permanent deflation). | | Liquidity Development | 16% | Pairs $OURS with 190+ compliant Robinhood Stock and ETF Tokens to seed and deepen liquidity pools. | Protocol-Owned Liquidity (POL) (LP tokens custodied by the protocol, not burned, providing an unshakeable asset base). | | Eligible Ecosystem Project Support | 16% | Supports leading ecosystem memes via targeted buybacks and funds the verified contributor reward budget. | Ecosystem Meme Leaders & Active Builders (Behavior mining, independent content mining, and referrers). | | Security, Development & Operations | 20% | Routes raw quote assets directly to the public multi-sig treasury vault. | Protocol Multi-Sig Treasury (reserved for smart contract security audits, node operations, and ongoing engineering). | ### 2. Decentralized Execution Mechanics To guarantee censorship resistance and eliminate counterparty risk, the flywheel operates under strict cryptographic constraints: * Permissionless Invocation: * Any public wallet address, community member, or automated keeper bot can trigger the `execute` function once threshold balances are reached. * Callers cannot redirect funds, alter recipient addresses, or adjust split ratios. Callers receive no protocol privileges or fee kickbacks, ensuring zero front-running extraction. * Atomic Execution (All-or-Nothing): * All four legs (buyback & burn, POL liquidity pairing, ecosystem support, and treasury transfer) execute within the exact same block transaction. * If any leg reverts due to excessive slippage, price deviation, or pool illiquidity, the entire transaction reverts cleanly, preventing partial or inconsistent states. * Immutable Bytecode Base: * The 48 : 16 : 16 : 20 split ratios are compiled constants in deployed bytecode with zero administrative setters, ensuring protocol rules cannot be modified behind closed doors. ### 3. Contributor Reward Distribution Within the 16% ecosystem support allocation, the portion streamed to active contributors aligns directly with the platform's Dual-Engine Mining Architecture (50% of Total Supply): * Verifiable On-Chain Output: Eligible contribution shares derive exclusively from confirmed trading turnover, permanent single-tier referral volume, successful pool graduations, and verified high-signal content (tutorials, videos, memes, research). * Sybil & Wash-Trade Scrubbing: Rewards settle strictly on verified on-chain actions and objective review, filtering out bots, wash trading, and vanity engagement. * Non-Custodial On-Demand Claiming: Newly acquired reward tokens stream into non-custodial escrow ledgers, enabling verified participants to claim $OURS at any time directly through the My OURS dashboard. ### 4. Transparent On-Chain Audit Trail Every execution of the fee flywheel generates verifiable logs on the Robinhood Chain block explorer: * Pending Balance: Real-time visibility into quote assets accumulating within the vault awaiting execution. * Execution Receipt: Full transparency over caller address, gross quote asset input, block timestamp, and final settled leg balances. * Proof of Burn: Verifiable burn event logs displaying the exact quantity of $OURS destroyed and the updated circulating supply. * Liquidity & Treasury Proofs: On-chain position IDs for newly seeded Protocol-Owned Liquidity (POL) and confirmation receipts for multi-sig treasury inflows. --- # 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/free/allocation.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.