> 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/impel/points.md). # Points The Points and Contribution Rewards module is the foundational engine designed to incentivize verifiable value creation across the OURS (`ours.meme`) ecosystem on the open, EVM-compatible Robinhood Chain (Chain ID: 4663). The platform rejects vanity clicker bots, arbitrary Sybil scorecards, and off-chain point schemes. Instead, authentic on-chain activities—launching, trading, graduating, referring—along with creative cultural output through our independent Content Mining System are indexed into transparent contribution records, distributing real protocol value to verified participants. ### 1. Core Principles & Accounting Boundaries * Contribution Records Are Not Tokens: Points represent on-chain contribution logs and do not equal platform tokens ($OURS). They carry no fixed exchange peg (e.g., frontend displays represent demonstration samples and must not be interpreted as a rigid "1 USD volume = 1 point" ratio). * Strict Separation of Capital Pools: Platform token supplies, fundraising seed funds, project-level creator fees, and platform fee revenues are strictly segregated into isolated smart contracts. Contribution rewards operate out of dedicated budgets without intermingling with trading reserves or liquidity capital. * Non-Custodial "Pull" Architecture: All distributions adhere to a trustless pull-claim model. Eligible participants claim accrued $OURS directly from the "My OURS" dashboard into their private wallets, eliminating centralized push transfers and batch-processing vulnerabilities. ### 2. Dual-Track Recognized Contribution Vectors The platform evaluates ecosystem contribution across on-chain actions and verified cultural output: | **Contribution Vector** | **Activity Scope & Accounting** | **Boundary & Verification Rules** | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | Trading Volume | Settled volume across internal Bonding Curves and external Uniswap v4 pools. | Evaluated strictly via confirmed on-chain events; wash trades, self-swaps, and circular volume are scrubbed. | | Launch Milestones | Deploying authentic community tokens on the platform. | Requires active curve participation and verified community links to prevent malicious empty launches. | | Graduation Volume | Successfully driving a curve to reach capacity and migrate into Uniswap v4. | Multi-project graduations accumulate perpetually across creators and primary volume contributors. | | Single-Tier Referrals | Onboarding new wallets that execute trades or reach graduation milestones. | Governed by an immutable single-tier on-chain binding; attributed strictly to verified invitee transactions. | | Independent Content Mining | Producing tutorials, crafting videos, creating viral memes, publishing deep research, and driving verified community onboarding. | Rewarded based strictly on verified contributions—filtering out bots, fake engagement, circular wallet manipulation, and vanity noise. | ### 3. Reward Funding Sources & Value Realization Contribution points are converted into claimable $OURS tokens through two isolated funding pools that operate independently: Plaintext ``` Contribution Reward Sources │ ┌────────────────────────────┴────────────────────────────┐ ▼ ▼ [ 50% Behavior & Content Mining Pool ] [ 16% Ecosystem Support & Rewards ] (Hardcoded in Total Platform Supply) (Funded via 30% Net Protocol Fees) │ │ Accrues shares from verified on-chain Flywheel market-buys $OURS to fund actions and verified content production active contributor reward budgets │ │ └────────────────────────────┬────────────────────────────┘ ▼ [ Isolated Reward Distributor ] Epoch calculations & Merkle root publication │ v [ Claimable by Qualified Users ] (Non-Custodial FeeEscrow) ``` 1. 50% Behavior & Content Contribution Mining Pool: Allocated directly from the platform's genesis tokenomics, hardcoded in immutable contract bytecode to reward real builders, traders, and creators. 2. Flywheel Ecosystem Support Allocation (from the 16% Leg): Within the platform's transparent 48/16/16/20 fee flywheel, 16% of the platform's net fee revenue is allocated to Eligible Ecosystem Project Support and Contributor Rewards. A dedicated portion executes programmatic open-market buybacks of $OURS to stream directly into the contributor reward budget (these tokens are distributed to active contributors and referrers rather than burned). #### Epoch Distribution Formulation $$\text{User Epoch Reward} = \text{Allocated Epoch Budget} \times \frac{\text{User Valid Contribution Points}}{\text{Total Valid Points Across Eligible Users}} \quad \text{}$$ ### 4. Anti-Sybil Filtering & Volume Scrubbing To safeguard real community builders, traders, and creators, the protocol enforces strict verification rules: * Self-Referral & Circular Wallet Filtering: The indexing pipeline detects and scrubs circular volume and self-referrals between linked addresses controlled by the same actor. * Protocol Action Exemption: Internal protocol transactions—such as automated Protocol-Owned Liquidity (POL) injections, fee buyback-and-burn calls, and user claim interactions—do not generate contribution points. * Wash-Trading Scrubbing: Synthetic volume generated through zero-slippage wash trades, circular cross-swaps, and automated ledger padding is excluded from rewarded metrics. * Reorg Reversal Protection: Reward attribution settles strictly on finalized block heights; if an underlying blockchain reorganization occurs, unconfirmed records roll back automatically. ### 5. Non-Custodial Execution & Gas Responsibilities In accordance with non-custodial Web3 principles, network gas fees are borne strictly by the transaction initiator without centralized subsidies: | **Operation** | **Executing Actor** | **Privilege & Boundary** | **Gas Fee Payer** | | ------------------------- | --------------------------- | ----------------------------------------------------------- | ------------------------- | | Trading & Accruing Points | Trader / Participant | Standard on-chain interactions emitting verified events. | Initiating User | | Publishing Merkle Root | Protocol Keeper / Multi-Sig | Submits verified reward root; cannot alter or divert funds. | Platform Execution Path | | Claiming $OURS Rewards | Reward Beneficiary | Submits cryptographic Merkle proof to withdraw tokens. | Claiming User (Self-Paid) | > Notice: Smart contract vaults holding reward tokens cannot execute meta-transactions to cover gas on behalf of external EOAs. Users must hold sufficient native Robinhood Chain ETH to cover network gas when claiming rewards. ### 6. Specification & Implementation Standards | **Parameter** | **Specification Standard** | **Implementation Status** | | ---------------------- | ----------------------------------------- | ---------------------------------------------------------- | | Network | Robinhood Chain (Chain ID: `4663`) | Open, EVM-compatible L2 infrastructure. | | Scoring Model | Dynamic epoch-based settlement | Relative weighting across volume, referrals, and content. | | Cycles & Caps | Uncapped contribution framework | No daily limits or arbitrary task caps for genuine users. | | Fee Revenue Stream | Part of 16% Eco Support & Contributor Leg | Streams market-bought $OURS into non-burned reward vaults. | | Production Integration | Isolated Distributor & On-Chain Indexer | Claimable non-custodially via the My OURS dashboard. | > 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/impel/points.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.